Kace Agent Breaks Vmware View 4.6

Recently deployed the kace agent to some Vmware View 4.6 machines and we started having an issue with the machines losing connection after 15mins.
The kace agent makes a registry change located here
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon\Userinit
It changes it to

Vmware View 4.6 needs this for the userinit
"C:\Program Files\VMware\VMware View\Agent\bin\wssm.exe"

Has anyone else come across this?

0 Comments   [ + ] Show comments

Answers (4)

Posted by: jknox 11 years ago
Red Belt

You can fix this issue by uninstalling VMware View, installing the agent and reinstalling VMware. Apparently, the VMware installer doesn't overwrite the information there, just appends to it.

Otherwise, you could also use an online script or GPO to set the registry value as needed once the agent was installed.

"Userinit"="c:\\program files\\vmware\\vmware view\\agent\\bin\\wssm.exe\", C:\\Windows\\system32\\KUsrInit.exe,"

Posted by: eschencedq 10 years ago
Senior Yellow Belt
This still doesn't appear to be fixed in 5.3 - Is the work around the only option?
Posted by: KevinG 11 years ago
Red Belt
What version of the agent are you using?
Posted by: CordlezToaster 11 years ago
Purple Belt
Thanks for the response jknox.

I did think the fix for it would be to add the extra bit to the end.

Glad to see some resolution in sight.
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login


This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ