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.
We've released Jump Desktop's Cloud REST API. Jump Desktop's cloud API lets you integrate Jump Desktop into your own apps, custom workflows as well as automate tasks you'd manually do on the web dashboard.
Start building today. See the API documentation.
Add notes to computers, users and access groups on your Team dashboard. You can even create custom fields to help with your workflow. You'll see a new Note field under each computer, user and access group in your team dashboard.
Of course, notes or annotations is completely accessible using Jump Desktop's Cloud API.
Starting with Jump Desktop Connect 6.7.42 you can run on-premise, high availability relay servers. Relay servers allow you to control how Jump Desktop traffic is routed through your infrastructure and isolate traffic to a specific host. All traffic is run through a specific set of UDP ports so you can control exactally what goes in and out and apply proper QoS if needed. You can use on-premise relay servers for better performance and increased security.
To get started, see the On-Premise Relay documentation.
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.
