Xtravirt is about to release another great tool; the vSphere Client RDP Plug-in. Last week Paul Davey has invited me to join the Xtravirt RDP Plug-in beta program. I was feeling very honored with his invitation and started performing some tests on their new RDP extension right away. I works like a charm, the installation is straight forward, after firing up the vSphere client the new RDP Plug–in is available at the vSphere Client plug-in manager.
![]()
When you jump to “Home” (I still have to get used to that) you'll find the new RDP plug-in at the Solutions and Applications section. Here you can configure the RDP behaviour like screen size, username, domain and port. When the setup of the global setting is done, it’s time to put the plug-in to test.
Just right click one of your virtual machines and check-out the context menu, you’ll see an extra option appears called Connect over RDP. Just select the new menu option and your RDP connection will initiate.
Update: I’ve just received an updated version from Paul with the following new features:
Password – you can now set a password to be used for all connections, allowing automatic logon.
Security Warning – Security Warnings can be disabled by ticking the relevant tick box.
Update: vSphere Client RDP Plug-in is released - http://xtravirt.com/vsphere-client-rdp-plug-in
I’ve created a little Jing movie which shows the new version of the Plug-in in action.











I think RDP is definitely faster than the Native Console window. Also, in multiuser environments, its not uncommon for me to find the console locked - RDP will just pop a new session and I don't have to inquire about whether the locked console is needed.
Not a 'need to have' but definitely a 'nice to have'.
CARLO.
-Carlo.
Manfred
And Eric thanks for testing!
For instance, suppose I have a MSCS cluster, the Resources are on one of the Node, so the Node is dedecting the Original IP, the Shared Public IP and the Private IP. In my case, the MSCS private IP is dedecting in the vi-Client.
When I initiate an RDP Connection to the MSCS Node, it picks the Private IP instead of the Public Shared or it's orginal IP. In this case, RDP will not establish the connection.
Another one is the ISA Enterprise Array Nodes, one of the ISA Nodes is detecting the DMZ IP Address, and when I initiate the RDP Connection it picks up the DMZ IP instead of the LAN IP in order to connect.
Thanks,
Habibalby
Thanks!
Paul Davey
Xtravirt