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
"C:\Windows\system32\KUsrInit.exe,"
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?
The kace agent makes a registry change located here
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon\Userinit
It changes it to
"C:\Windows\system32\KUsrInit.exe,"
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)
Please log in to answer
Posted by:
jknox
13 years ago
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
12 years ago
Posted by:
CordlezToaster
13 years ago
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
so that the conversation will remain readable.