Hi Tomas. That's kinda weird, it worked for me.
Let's try this:
$VM.name = VM_Name
Update-Tools -NoReboot -VM $VM.Name -Verbose
Maybe this can clear some things for you. Automating Upgrade of VMware Tools and VM Compatibility - VMware vSphere Blog
Or from vCenter/s /v/qn ADDLOCAL=ALL REBOOT=ReallySuppress in the advanced settings of the VMware Tools upgrade console
Moderator: Thread moved to the PowerCLI area.
It depends a bit on what kind of Guest OS you have running in that VM.
And which virtual HW and drivers you are using.uirement
In several cases you can't avoid a reboot requirement, but you can postpone it with the NoReboot switch.
My experience has shown me that it is not always obvious why a reboot was done.
Check the logs to find clues.Blog: http://lucd.info | Twitter: @LucD22 | PowerCLI Reference co-author: http://tinyurl.com/hkn4glz