No, not a word from support! And consequently I'm not sure how this option works in U3, but since they promised to let me know when a solution is available, I guess they haven't fixed it yet..

Yes, you can use VI Toolkit and a script. I believe this is the right script for turning this feature ON:

connect-viserver -server <server> -user <user> -password <pwd> $vm = Get-View (Get-VM VMName).Id $vmConfigSpec = New-Object VMware.Vim.VirtualMachineConfigSpec $vmConfigSpec.Tools = New-Object VMware.Vim.ToolsConfigInfo $vmConfigSpec.Tools.ToolsUpgradePolicy = "UpgradeAtPowerCycle" $vm.ReconfigVM($vmConfigSpec)

For turning it OFF I believe you should change "UpgradeAtPowerCycle" to "Manual", but I can't confirm this right now since I don't remember it and as I'm at home right now I can't check my script at work.

I believe you can verify the syntax by checking this value in the .vmx-file for a VM. Check the vmx-file for a VM with the "check and upgrade" option turned ON, it should have "UpgradeAtPowerCycle" somewhere, and then check the corresponding value in av .vmx-file belonging to a machine with the feature turned OFF, I'm positive it should read "Manual".

Let me know your results!

Sorry I am not very verse in scripting. Would I not need the below to connect to my vc server? Your second post looks quite different than your first. I just need to paste your second post in the vi tool kit window?

connect-viserver -server <server> -user <user> -password <pwd>

Thank you

Hello Again It errored on me. I think it might be formating? Are there carriage returns after each of your lines in your image?

PS C:\Program Files\VMware\Infrastructure\VIToolkitForWindows> Get-View (Get-VM
VMName).Id $vmConfigSpec = New-Object VMware.Vim.VirtualMachineConfigSpec $vmCon
figSpec.Tools = New-Object VMware.Vim.ToolsConfigInfo $vmConfigSpec.Tools.ToolsU
pgradePolicy = "UpgradeAtPowerCycle" $vm.ReconfigVM($vmConfigSpec)
Get-VM : 10/17/2008 12:50:20 PM Get-VM VM with name 'VMName' not foun
d, using the specified filter(s).
At line:1 char:17
+ Get-View (Get-VM <<<< VMName).Id $vmConfigSpec = New-Object VMware.Vim.Virtu
alMachineConfigSpec $vmConfigSpec.Tools = New-Object VMware.Vim.ToolsConfigInfo
$vmConfigSpec.Tools.ToolsUpgradePolicy = "UpgradeAtPowerCycle" $vm.ReconfigVM(
$vmConfigSpec)
You cannot call a method on a null-valued expression.
At line:1 char:229
+ Get-View (Get-VM VMName).Id $vmConfigSpec = New-Object VMware.Vim.VirtualMach
ineConfigSpec $vmConfigSpec.Tools = New-Object VMware.Vim.ToolsConfigInfo $vmCo
nfigSpec.Tools.ToolsUpgradePolicy = "UpgradeAtPowerCycle" $vm.ReconfigVM( <<<<
$vmConfigSpec)
PS C:\Program Files\VMware\Infrastructure\VIToolkitForWindows>
PS C:\Program Files\VMware\Infrastructure\VIToolkitForWindows> [Reflection.Assem
bly]::LoadWithPartialName("vmware.vim")

GAC Version Location
---

---

---

True v2.0.50727 C:\WINDOWS\assembly\GAC_MSIL\VMware.Vim\1.0.0.0__10980...

PS C:\Program Files\VMware\Infrastructure\VIToolkitForWindows> $vmConfigSpec = N
ew-Object VMware.Vim.VirtualMachineConfigSpec
PS C:\Program Files\VMware\Infrastructure\VIToolkitForWindows> $vmConfigSpec.Too
ls = New-Object VMware.Vim.ToolsConfigInfo
PS C:\Program Files\VMware\Infrastructure\VIToolkitForWindows> $vmConfigSpec.Too
ls.ToolsUpgradePolicy = "UpgradeAtPowerCycle"
PS C:\Program Files\VMware\Infrastructure\VIToolkitForWindows> Get-VM | %{(Get-V
iew $_.ID).ReconfigVM(vmConfigSpec)}

...and yes, it's a CR after each line.

Ok I figured it out. I was missing a dollar sign in the below line. Right before vmConfigSpec. Thanks

Get-VM | %{(Get-View $_.ID).ReconfigVM($vmConfigSpec)}

I am assuming even though this value will be changed. It will not become active until the vm is re-booted? Because the vmx is already loaded in memory. A vmotion could still initiate a tools upgrade?