VMRCplus has a very straightforward installation process. If you do not want to change the location of VMRCplus, you only have two options left. Either you use the defaults or you add the Virtual Server COM object (VSCOMAPI).
The default installation (meaning you leave everything default by clicking Next) results in a local installation of VMRCplus without the Virtual Server COM object. This type is meant for a local installation on a Virtual Server host. Virtual Server already registered the COM object so you should not (must not) install it through VMRCplus.
If you want to remotely manage Virtual Server AND you do not have Virtual Server installed on the machine you install VMRCplus on, you must install VSCOMAPI. If you don't, you will get the message that the COM object could not be found.
VMRCplus exists in two packages for two platform architectures; an x86-package for 32-bit operating systems and an x64-package for 64-bit operating systems. The x64-package is for x64 (AMD64); there is no support for IA64 (as there is also no support for IA64 by Virtual Server).Although you might expect the x86-package to work on x64, it won't. It allows you to install however which is fixed in a newer build.So always install the x64-package on x64 architecture.
Matthijs the application looks great!!
I've been having an issue running it in Vista. No matter how hard I tried the only way to get it to work is by disabling the Windows Firewall. when the windows firewall is enabled I get "The RPC Server is unavailable. (Exception from HRESULT: 0x800706BA).
I have added firewall exceptions for VMRCPlus.exe and for port 135 but still dont get it to run with Firewall on.
I wonder if you can point me in the right direction to solve this problem.
I avoided this problem by the following method.
1. Click Start, click Run, type gpedit.msc, and then click OK.
2. In the console tree, expand Computer Configuration, expand Administrative Templates, expand Network, expand Network Connections, expand Windows Firewall, and then click Domain Profile.
3. In the results pane, right-click Windows Firewall: Allow remote administration exception and then click Properties.
4. On the Setting tab, click Enabled.
5. Under "Allow unsolicited incoming messages from:", add the IP address for Virtual Server host, and then click OK.
This is probably old news now but I'm just getting back on top of blogging again!! Matthijs has made
Thanks for the help, I tried the compouter configuration steps but I still have the same issue. It only works If I turn off the firewall. Any other ideas?
This Blog entry references the download location for the Virtual Machine Remote Control Client Plus used with Virtual Server 2005 R2 SP1. VMRCplus is an 'advanced client' used for managing Virtual Servers. Additionally, Blog entries from the Microsoft
Isn't VMRC Plus supported under Windows Vista Ultimate 64-bit? In the system requirements for VMRC Plus, only Vista Enterprise is mentioned.
Yes it is. Basically any edition.
I have just reformated my laptop to use Vista and Onecare, however VMRC+ even with hole punched in te onecare firewall will not access VS 2005 R2 servers.
Enable both in an out. based on
I like this util but, OneCare does not.
What other port can I enalbe to make this work?
It seems that if you are pushing a firewall policy via Group Policies and do not allow local exceptions (as I am) you cannot use VMRCplus.
If I disable the policy and create the two exceptions below, it works just fine.
Unfortunatley, we require forced policies and no local exceptions. Has any found a way around this isue?
I have tried every incarnation of the above firewall settings (on the server side) and nothing short of disabling the server firewall works.
Here are the Port/Program Exceptions i have unsuccessfully implemented so far.
135:TCP:*:Enabled:Virtual Server Remote Config
135:UDP:*:Enabled:Virtual Server Remote Config
137:TCP:*:Enabled:Virtual Server Remote Config
137:UDP:*:Enabled:File and Print Sharing
138:TCP:*:Enabled:Virtual Server Remote Config
138:UDP:*:Enabled:File and Print Sharing
139:TCP:*:Enabled:File and Print Shaing
445:UDP:*:Enabled:Virtual Server Remote Config
1024:TCP:*:Virtual Server Admin Website
1024:UDP:*:Virtual Server Admin Website
3183:TCP:*:Virtual Remote Config Website
3183:UDP:*:Virtual Remote Config Website
5900:TCP:*:Enabled:Virtual Server Control Port
5900:UDP:*:Enabled:Virtual Server Control Port
Obviously there is a required port not mentioned above getting blocked preventing VMRCplus from connectiing. Has anyone found this mystery port?
I have tried Group Policies with "Allow local prgram exceptions" and "Allow local port exceptions" Enabled with the exceptions listed below and it does not work.
I tried "Allow remote administration excepton" Enabled with the IP for the client connecting to the server listed in the "Allow unsolicited incoming messages from:" box, and still no go.
I have tried Group Policies with all settings in a "Not configured" state, then I entered the exceptions below manually via the Control Panel>>Windows Firewal>>Exceptions Tab, still no wanno.
The VMRCplus interface is great, but there is no way I will leave my servers firewall down in order to use it. There has to be a yet to be mentioned port/program exception.
5900:UDP:*:Enabled:Virtual Server Control Port
Virtual Machine Remote Control Client Plus (VMRCplus) If you prefer a 'tabbed metaphor' in your