If a service tries to interact with the desktop in session 0 , Interactive Services Detection will freeze the application and present the user with the following dialog:. In the case of the VMware Tools install you have to actually be logged into the VM to see the message. Unfortunately this only pops up automatically if you are using a bit OS. If you are using a bit OS, such as Server R2, you will need to manually start the Interactive Services Detection service to see the above dialog.
If you do nothing at all, the VM will sit there perpetually waiting for you to allow the installer to proceed. I found a relatively simple way around this issue — set your VMware Tools service to start as a user with rights to the server instead of Local System.
This allows the install to occur in Session 1 a user session and the install proceeds as expected. This is probably more of a combination of a Microsoft issue and a VMware issue. And although not pretty the above does work as a workaround until it is resolved. Have you tried disabling the Interactive Services Detection service on the VM Guests to see if the installs work when notifications are disabled.
The fact that services run in session 0 is now a feature of Windows and the Interactive Service Detection service is there to help you identify when an application wants to run in session 0.
I have found the easiest way to update tools is to use PowerCli and issue the Update-Tools cmdlet. It will update all windows systems and if you use the -NoReboot tag it will update without a reboot. My experience has shown that you may drop a ping, but otherwise the upgrade runs smoothly.
Keep in mind that it only works for upgrading tools, not installing them. Your email address will not be published. Notify me of follow-up comments by email.
Notify me of new posts by email. Skip to content. Home Contact. TheSleepyAdmin vCenter 7. The vunerablity has been fixed in VMware tools version If the tools required a reboot it would show under impact Next we will create a baseline to apply the latest tools. Go to baselines and select new baseline. Give the baseline a name and select patch Untick Automatically update this baseline Untick show only rollup updates and filter for VMware tools, there will probable be a different VMware tools for 6.
Click next and complete the baseline creation. We can now apply the baseline and run the check again and it should show as out of date. Select the VMware tools baseline and attach. Next run a compliance check on the ESXi host. Check the baseline status. Next we will remediate the baseline to apply the latest tools. If there are no issue with the pre-check click remediate. Once the remediation is done the tools should show as compliant.
Once applied the VM should now pickup that there is a new tools version available. The tools can now be applied to the VM either using a script, update on reboot or manually. Share this: Twitter Facebook. Like this: Like Loading Published by TheSleepyAdmin.
Published July 1, October 27, Leave a Reply Cancel reply Enter your comment here Fill in your details below or click an icon to log in:. Email required Address never made public.
0コメント