In this release we've updated the icon to the old new icon and fixed a few bugs.
In this release we've updated the icon to the old new icon and fixed a few bugs.
In 8.8.28:
In 8.8.27:
In 8.8.26:
In 8.8.23:
In 8.8.21:
Please note: Retina mode requires up to 4x the number of pixels an may have a performance impact on connections.
Jump Desktop for Windows now supports running remote displays in separate windows! This lets you breakout your remote displays into their own window locally so that you can utilize multiple screens.
Each window can be placed any where locally and even maximized. Jump will remember your window placement for each connection.
To get started, connect to a machine with multiple displays and then click View -> Displays In Separate Windows.
In 8.4.26 we fixed an issue with the Cycle Displays shortcut not working. We also fixed a crash when running on some Intel graphics adapters.
Here's whats new in 8.4.22:
Jump Desktop for Windows 8.4.22 adds the following improvements:
Jump can now show real-time connection statistics for Fluid connections. Connection stats include the average ping time to the machine, packet loss and the type of connection Jump has established to the machine. This is useful info when diagnosing performance problems.
To turn on live stats click Help -> Show Fluid Connection Stats. After turning this on, an overlay will appear on the bottom right hand corner of all connection windows.
Related Help Article: Live Fluid Connection Stats
Jump Desktop's Fluid protocol automatically monitors available bandwidth and dynamically adjusts bandwidth usage and image quality while you use the connection. By default Jump uses a maximum of 20mbps for Fluid connections.
There are times when you want to override the maximum 20mbps default. For example, if you know you're on a slow connection, you can turn down the default to 5 or 10mbps.
How it works: When you lower maximum bandwidth, Jump will automatically lower image quality during complicated screen updates and automatically boost image quality to high when there is left over bandwidth available. This way you get the best of both worlds: lower bandwidth usage while maintaining high image quality. It works seamlessly and without user intervention. Try it out!
You can now set Maximum Bandwidth for each connection. Connect to the computer and then click Remote -> Maximum Bandwidth menu for Fluid connections and select a maximum.
Bandwidth above 20mbps is currently available for Teams Enterprise customers. Warning: Increasing bandwidth above 20mbps will put a strain on your network and may make things worse if your network isn't designed to handle it. Please speak to your administrator before increasing bandwidth above 20mbps.
Jump Desktop Connect 6.5.x now ships it's very own high quality, low latency audio drivers for Mac. Third party drivers are no longer needed to stream audio from a Mac (though we will still support third party audio drivers).
The drivers are automatically installed when you install Jump Desktop Connect 6.5.x or later. Once installed you will see a new audio device called Jump Desktop Audio. Any audio sent to this device will be streamed to the Jump Desktop client.
The new audio drivers are compatible with macOS 10.10+ on Intel and Apple Silicon.
Jump Desktop lets you add computers to a team so that all members can access and share the computers. This feature raises a problem, i.e., multiple users trying to access the same machine.
Jump Desktop (Mac), now shows you if a remote computer has users connected to it. It also shows the emails of the connected users so that you can identify the users currently accessing it.
This feature is available for Teams Enterprise customers.
We have added helpful, but unobtrusive, indicators in the UI.
"Occupied" computers have a distinctive red icon in the icon mode, hovering over the icon shows the connected users' emails.
The list view has a column for "Connected Users".
You can also take advantage of the "Occupied" and "Unoccupied" filters from the filter bar.
"Current Active Connections" card shows the list of computers to which users are currently connected. A subtle badge, with a red background, displays the number of connected users.
In the list of team computers, you can identify the computers to which users are currently connected from the red badge.Visit the active computer's page to view the currently connected users details like their IP addresses.
"Occupied" computers have a distinctive red icon in the icon mode, hovering over the icon shows the connected users' emails
How to access Jump Desktop for Teams Beta
Visit: https://beta-app.jumpdesktop.com
How to get Jump Desktop for Mac Beta
Open up Jump Desktop and click Jump Desktop -> Preferences -> General -> Check For Beta Updates and then click Jump Desktop -> Check For Updates.
If you don't see the Check for Beta Updates, you'll need to download the web version of Jump Desktop for Mac from here: http://jumpdesktop.com/downloads/JumpDesktopMac.zip
How to get Jump Desktop for Windows Beta
Open open up Jump Desktop for Windows -> File -> Settings -> Updates -> Check the checkbox Beta Updates and click Check for updates.
How to get Jump Desktop for iOS Beta
Send us an email: support@jumpdesktop.com and let us know you want to be included in the Testflight iOS Public Betas.
How to get Jump Desktop Connect Beta
Most of the beta features require new Jump Desktop Connect apps on the host machines. To update to the beta, open up Jump Desktop Connect and then click Settings -> Updates -> Beta updates. Then click Check for updates.
Jump Desktop Connect has a built-in technology that tries its best to create an end to end encrypted connection between machines, even if there is no direct path between the two hosts using indirect networking routes and relays. This feature frees up users from manually opening ports and configuring network settings. However, this also creates problems in locked-down environments where administrators need to control when a user is allowed to connect.
You can now configure Jump Desktop Connect to allow connections only when there is a direct networking path between the devices.
In this mode, Jump will never fallback on relay servers or take indirect networking routes. So for example, if a user tries to connect without VPN enabled from another network, the connection attempt fails because Jump will not be able to find a direct route between the user and the target machine.
Note: In this mode, Administrators must make sure that their firewall rules allow the VPN IP address pool to communicate over UDP with the host machines. Connections will fail otherwise.
How to configure Direct Connection Mode