Cannot use client on vCenter server

[ITTamer]

I can run the vSphere client just fine on my desktop, but cannot run

it properly on the vCenter VM. What happens is that after logging in

successfully to the client I am presented with the usual "Security

Warning" dialog about the SSL certificate and I am able to ignore the

certificate on the first warning but the second warning dialog freezes

up and cannot be ignored. I cannot even move the window and the title

bar gets greyed out and cannot be selected as the foreground window.

It seems that there is a hidden modal dialog box somewhere, preventing

interaction with the "Security Warning" dialog box.

Another user (user1) can make it work properly.

I could not find a real solution anywhere but based on

the VMware KB Article: 1010955 "After uninstalling and reinstalling

the vSphere Client, previously installed and ignored certificates do

not result in a security warning" I was able to develop a workaround.

I exported the key HKEY_CURRENT_USER\Software\VMware\Virtual

Infrastructure Client\Preferences\UI\SSLIgnore to a file as a backup

while logged in as the functional user (user1) and then removed the

values as directed in the KB Article. Once this was done even

user1 was unable to use the client on the vCenter VM.

Importing the registry settings resolves the issue for all users, but

each user must import this registry setting in order to use vSphere

client on the vCenter VM.

I suspect that exporting this key from any PC with a functional client

and importing it into any user profile on a PC with this problem would

resolve the problem.

Tried uninstalling and reinstalling but that did not help. Experimented with setting permissions on the reg key but that didn't help.

Any ideas?

Thanks, Marcus

http://www.itwheel.com

Message was edited by: ITTamer add screen shot, ask for help.

[MauroBonder]

fyi

*If you found this information useful, please consider awarding points for "Correct" or "Helpful"*

[ITTamer]

Mauro,

I suppose if I set trusted certificates then that would fix the problem with the untrusted certificates, but that would be just a harder workaround than the one I already came up with. Exporting and importing a registry file is much easier.

We are looking for a fix that would allow us to use untrusted certificates without the registry import, or why the dialog becomes unusable and how to fix it.

Thanks, Marcus