VMware Console Connection Not Functioning

VMware Console Connection Not Functioning

avatar

I recently downloaded a trial of RDM. I followed the instructions listed here in an attempt to connect to a VMware vSphere host with your VMware Console connection. I receive the following error when attempting to connect:

ERROR SILENT MissingMethodException : Method not found: 'Void VMware.Vim.VimClient..ctor()'.

vSphere PowerCLI has been installed and the vSphere host certificate installed.

Version Information:

Remote Desktop Manger 6.3.9600.16415

vSphere Host 5.5.0 Build 1623387

vSphere PowerCLI 5.5 Release 2

Any assistance you can provide would be appreciated.

Regards,

Dave

All Comments (7)

avatar

Hi,

What versions of the .net framework are installed on your workstation?

Maurice

avatar

Requirements

To use VMware vSphere PowerCLI, you need to have installed the following software:

Windows PowerShell 2.0

A supported version of .NET Framework

.NET Framework 2.0 with Service Pack 2

.NET Framework 3.0 or .NET Framework 3.0 with Service Pack 1, or Service Pack 2

.NET Framework 3.5 or .NET Framework 3.5 with Service Pack 1

Maurice

avatar

and so you know : http://forum.devolutions.net/topic13999-configureing-vmware-remote-console.aspx

I'd like to know if anyone with R2 is able to get the player to work, it doesn't work on my machine either.

Here's an email I had sent to another user recently, the command line didn't work for him either.

Hello,

Can you adapt this command line for your environment?

Target: "C:\Program Files\Common Files\VMware\VMware VMRC Plug-in\Internet Explorer\vmware-vmrc.exe" -h 10.112.96.8 -u "root" -p "vmware123" "[datastore1 (2)] VCSA51-2/VCSA51-2.vmx"

Start in: C:\Program Files\Common Files\VMware\VMware VMRC Plug-in\Internet Explorer”

On my machine, with the 5.5 plugin, the path is "c:\Program Files (x86)\Common Files\VMware\VMware Remote Console Plug-in 5.5\Internet Explorer\vmware-vmrc.exe"

Does it work?

Just to let you know, because of this exchange with a customer of ours:

Currently there are two options for opening a remote console to a VM. First via "vmware-vmrc.exe" and second via VMware Player. If i understood the people at VMware forum right the VMware Remote Console Plug-in "vmware-vmrc.exe" Version 5.1 and later only work as browser plugin due to the lack of the VMware Player UI and the problem of VMware Player is more a licensing issue. The free VMware Player is for "non-commercial use only" or you have to buy VMware Workstation.

The feature to add is a third option, that uses the VMware Remote Console IE Browser Plug-in. With the PowerCLI command "open-VMConsoleWindow -VM [VMNAME] -UrlOnly" we get a URL and open it with the embedded or external browser integration. There are two big advantages. We could embedd the remote console and we clould use the real VM name (no datastore location or VM ID).

we have just implemented using the pssnapin which will because the preferred way of connecting remotely. This will be in v9.5 that will come out in May. I still havent been able to configure my workstation to perform what you’re attempting. I have all the plugins, the vmplayer, etc

Not too long ago, many features of our console have become disabled when working against an ESXi host, it seems that the licensing forbids write operations against such a host, meaning even start/stop commands raises errors. I hope this isn’t a repeat.

I think I need to browse the vmware forums

edited by mcote on 5/22/2014

Maurice

avatar

https://communities.vmware.com/message/2380940#2380940

It seems they changed the API without mentioning it in the release notes.

Maurice

avatar

https://communities.vmware.com/message/2380940#2380940

It seems they changed the API without mentioning it in the release notes.

I need to have a look at how we can fix this, at least we know have a cause.

Maurice

avatar

Any word on a fix Maurice?

avatar

If you have vSphere 5.5 R2, you need to use our beta from http://remotedesktopmanager.com/Home/Download#beta

Sadly, we cannot support two versions of the powerCLI and users of the R2 release must use our beta.

For users that must remain with R1, they will have to use an older version of our VMware interface library

Please consult our troubleshooting topic at http://help.remotedesktopmanager.com/index.html?troubleshooting_vmware.htm#typeloadexception for further details and a detailed procedure.

Maurice