This project has moved. For the latest updates, please go here.

Feature requests: Experience controls, VRMC

Topics: User Forum
Mar 13, 2007 at 10:33 PM
This tool is almost perfect...

1) please add the experience options available in the standard RDP client - e.g. themes, backgrounds etc. It's nice to be able to turn these things off if you have a slow connection

2) sometimes rdpclip.exe will stop working in an RDP session, and when that happens you can't copy/paste to/from the client PC or between RDP sessions. It would be nice if you could find away for Terminals to restart it. This isn't your bug, but you could fix it anyway!

3) it would be really, really cool if you could integrate support for the Virtual Server 2005 client (VRMC) which works a bit like VNC (i.e. it's less efficient than RDP). Most of the time I would use RDP, but sometimes it's important to be able to get into the bios of a virtual machine, or maybe run a virtual machine without enabling terminal services on it, or it could be running something other than Windows. Maybe as someone else has requested support VNC too, and the VNC based vmware client too. Then instead of organising connections, we use terminals to organise computers, with a preferred connection method - RDP, VRMC or VNC and an option to use any other configured connection.
Mar 30, 2007 at 5:16 PM
I second a request for #3. 'Terminals' is going to be my new favorite application. I run VMWare's virtual server. The clients are network bandwidth hogs, so RDP is the better solution. Unfortunately, VMWare's console is awesome when run full sreen on a second monitor ---- I was starting some prototypes of hosting mstscax.dll to replicate the experience and found this... !

What would really be nice is a more "Universal" terminal. Support for both VMWare and Microsoft clients, VNC, heck, even VMR9 (windows media video player). Through in a bit of ICA from Citrix.

This could be done. Is there any interest?
Nov 18, 2007 at 2:19 AM
I am dealing with a VMWare Cluster and sometimes it is just necessary to use the VMWare protocol instead of RDP

There seems to be plenty of API info here and I have seen a few 3rd party clients pop up but none of them are very good or tabbed from what I recall.
http://jeff.bovine.net/VMWarevmcontrolAPI#VMControlAPIs:toplevelfunctions
Coordinator
Nov 18, 2007 at 4:34 AM
1) please add the experience options available in the standard RDP client - e.g. themes, backgrounds etc. It's nice to be able to turn these things off if you have a slow connection

DONE

2) sometimes rdpclip.exe will stop working in an RDP session

maybe a feature request. this would defintely be a hard one to get right...

3) it would be really, really cool if you could integrate support for the Virtual Server 2005 client (VRMC)

Althought this IS Supported in the product, right now I've been struggling with getting it to work correctly. I a future revision I see the basic VMRC UI with the list of running machines AND the ability to manage the entire virtual server settings as well.

4) I am dealing with a VMWare Cluster and sometimes it ....

*Let me dig into just how easy/hard it is to include VMWare... Essentially what I would need is a .NET based (or COM) control which I can host in Terminals. http://jeff.bovine.net/VMWarevmcontrolAPI *

Nov 18, 2007 at 6:42 AM
"*Let me dig into just how easy/hard it is to include VMWare... Essentially what I would need is a .NET based (or COM) control which I can host in Terminals. http://jeff.bovine.net/VMWarevmcontrolAPI *"

This is one of the 3rd party tools that exists.
http://www.ntpro.nl/blog/categories/7-Virtual-Machine-MKS-Client

On his site I found this PDF that outlines how he accesses the VMWare API
http://www.ntpro.nl/VMwareVBApp.pdf

Looks like the Dlls he is useing are already .Net based.
May 29, 2008 at 9:11 PM
Any more research been done on this? Nearly half of my Windows Servers are now virtual, it would be great to have another built in way to manage them.