A few weeks ago I had the opportunity to try out a tool (although “suite” might be a better description) to manage all types of different Remote Connections from a single console. It’s called Remote Desktop Manager by Devolutions.
Devolutions describes their product as “…Remote Desktop Manager lets you centralize all your remote connections, passwords and credentials into a unique platform that people love to work with…” I have been using it for a few weeks now, and I must say the feature set is absolutely huge!. Whether its managing Remote Desktop Sessions, Remote Assistance, Azure Consoles, Hyper-V consoles it’s all in there.
During my testing I found out that there was a new feature they did not fully support yet. If you’re a frequent reader of this blog you might have read my blogs on the way the RD Connection Broker role works in Windows Server 2012 and that it now also the serves the initial connection, similar to the Dedicated Redirector sub-role we used to know in Windows Server 2008 R2. In order for this to work you need to specify additional RDP properties to allow the RD Connection Broker to know what Collection to redirect you to. I found out that importing an .RDP file in Remote Desktop Manager that contains those properties is not being picked up. I notified Devolutions about this and they fixed this in no-time in a their new Beta release! This feature is now available in their latest beta release version 18.104.22.168 which released 2 days ago.
Compliments to Devolutions fast support and development on this!
If you want to give their product a try you can sign up for a 30 day free trial here: http://remotedesktopmanager.com/