Hello friends and existing customers! We’re excited to let you know that the release of Remote Desktop Commander v4 is just about ready, and wanted to give you a sneak peak of all of the new features it contains.
We will be releasing Version 4 shortly after the start of the new year, along with a small price increase – our first price increase in over 18 months. If you’d like to test drive a release candidate of version 4, please complete the form here and mention that you want to try the release candidate of Version 4 in your comments.
Now You Can Pinpoint Historic CPU, Memory, and Other Session Load Bottlenecks on Servers Instantly With the “Historical Performance and Load Across the Farm” Dashboard
Previous versions of Remote Desktop Commander allowed you to view recent performance metrics across your servers, as well as pull up snapshots of performance for all user sessions given a specific period of time. However, the new Historical Performance And Load Across The Farm Dashboard allows you to scroll through hour-by-hour graphs of when your RDS session host servers were under peak load, in terms of memory, CPU, or session count. The graph is interactive, so you can click on a point of interest, and you will immediately be transported to another dashboard that shows you all of the sessions active in that time frame, so you can review the user session(s) that contributed most to the server load and determine what they were doing at the time.
Quickly Filter Dashboards By Date Range and RDS Collection Name / Server Groups
For organizations with larger RDS deployments, attempting to review all of the session host servers in a single dashboard can get complicated. Version 4 of Remote Desktop Commander allows you to quickly filter dashboards by an 1.) RDS collection name, 2.) a user-defined group of RDS servers, and 3.) in some cases, a date range lookback. By doing so, you can keep multiple dashboards up and running inside the Remote Desktop Commander Client, with one dashboard per RDS collection.
Azure and Standard SQL Server Authentication Support
Previous versions of Remote Desktop Commander required use of a local SQL Server deployment with Windows Integrated Authentication. Version 4 now also allows you to use a.) an on-premise SQL server with Standard (explicit username/password) Authentication and/or b.) a Microsoft Azure SQL Server deployment. This provides organizations with the flexibility to create multiple SQL databases for multiple RDS deployments on a single SQL Server, even when each deployment is isolated in a different, non-trusting Windows domain.
Other Performance Improvements
In addition to the features listed above, we’ve made many other performance improvements and bug fixes in this version. Stay tuned for our official launch announcement shortly!