I just upgraded from esxi 5.0 to 5.1 to get rid of constantly crashing VMtools on my 2008r2 terminal server. Well, errors are back, just in different form.
At first I got this:
[ warning] [vmusr:vmtoolsd] Failed registration of app type 2 (Signals) from plugin unity.
By following instructions in http://communities.vmware.com/message/2110430 I got rid of it. But then another error came up, it is raised after any user logs in to terminal:
Seems like the issue described here:
http://kb.vmware.com/kb/2036350
This problem is supposed fixed in patch ESXi510-201212402-BG to the VMware Tools from December:
http://kb.vmware.com/kb/2035778
Make sure you upgrade your VMware Tools in the Guests with this version.
I installed ESXi510-201212001 right after the upgrade, and AFAIK it includes the patch you mentioned. Guest tools were also upgraded, but it didn't help.
Well, instead of AFAIKing, can you just make sure you're running this Tools version?
Check the Tools Tray Icon or run this in a cmd:
"C:\Program Files\VMware\VMware Tools\VMwareToolboxCmd.exe" -v
With this patch you should be running version 9.0.1.18551 (build-913578).
Yes, this is the version I have.
I did remove the unity.dll (workstation feature) from here C:\Program Files\VMware\VMware Tools\plugins\vmusr.
First kill / stop all vmware tools services and traybar indicator ...
Guess it will be back when updating the tools but by that time it should be fixed wouldn't it be?
One has to question when VMware will finally notice that it's a better idea to simply not package ESXi VMware Tools with workstation/player components (no, I do not want my VMs to share files with the host, which won't work anyways).
But that's an interesting point you have there if this fixed your issue.
As suggested by the vSphere Security Hardening Guide (http://www.vmware.com/files/xls/security/HardeningGuide-vSphere50-v1.2.xlsx), there are a couple of supposedly unexposed unity features that can be explicitly disabled through VMX-parameters.
It would be interesting if can you test whether this issue is still present on a VM with these parameters set (and having been power-cycled), while keeping the original unity.dll in place:
isolation.tools.unity.disable=true
isolation.tools.unity.push.update.disable=true
isolation.tools.unity.taskbar.disable=true
isolation.tools.unity.windowContents.disable=true
isolation.tools.unityActive.disable=true
isolation.tools.unityInterlockOperation.disable=true
There may be even more undocumented parameters pertaining unity features, but these have been stated in the Hardening Guide.
Anyone tried this?
I didn't experience the dramatic log spew issue but got a few Eventlog errors on every login:
http://communities.vmware.com/message/2149923#2149923