vsphere console issue w/Workstation 10 installed

Hello,

the player is touchy because of licensing issue (along with manipulating an ESXi server, but thats another story)

when you say the plugin, what do you mean?

Have you seen this? http://blog.devolutions.net/2014/06/breaking-change-in-vmwares-powercli.html

Hi,
Thanks for the response - I'm running the most updated version of powerCLI, and by plugin I mean the plugin that is supposedly 'required' for the console to work, C:\Program Files (x86)\Common Files\VMware\VMware Remote Console Plug-in 5.5\Internet Explorer

I install this, and it doesn't launch as it's not an 'application' as near as I can tell. At least not one that will run outside of a browser.

ok, that plugin AFAIK is bypassed by the new PS snapin

The "new" method launches the player embedded in a browser. Can you install the latest beta of RDM?

I havent been able to launch the old style vplayer with the last two versions of the powercli

Thank you Maurice,
I updated to the Beta, and now cannot even connect to vsphere.

I get this error:

Yes, that was described in the blog I linked above, please consult http://help.remotedesktopmanager.com/troubleshooting_vmware.htm for the fix

If you cannot upgrade the PowerCLI, the note below the http://help.remotedesktopmanager.com/troubleshooting_vmware.htm topic has a link to a download to patch your RDM

Unfortunately all of this hasn't changed - now a powershell box opens, spurts out a lot of red responses (which means errors) and the connection does nothing.

It does load vsphere in the RDM, but doesn't allow the console.

please list the errors, they are PowerCLI configuration related an can easily be fixed

They vanish far too fast for me to see them - is there a way to debug this?

I have same problem. Powershell opens with a bunch of errors and closes too fast to be of any use.

This happens on two different computers.

I just managed to see the error messages using snipping tool.

It was a credential issue with the vcenter server, i was using credential repository with an account that should be ok.

But after setting credentials to default and putting username and password under the vcenter server the powershell part began to work.

I then had a lot of problems with script blocking in IE11, and decided to make Chrome default browser. After that my vm console works as expected.

We will try and catch the errors, but its a secondary process and I'm looking for the best way to handle them

What we are in fact executing is something like

If you open a powershell console, and type each command, you should see the error.

@Oletho, the credentials in the credential entry were identical to what you set in the session itself?

Yes, in both cases it was the domain administrator.

we'll need to continue via private messages, I need to view the session settings. Can you send me the result of Right click-Clipboard-Copy on the session? I would need the one that was configured with a credential link.

thanks