No, my script didn't force a reboot. I ran this in a production environment and reboots were scheduled at later dates. You could produce another script to force all VMs to reboot. From what I recall, an OS restart was not sufficient, it had to be a Virtual Machine power reset (power off, power on).

I attached my script. Not a lot of error checking, but if you hit any bugs just drop me a note I'll be happy to help you. It only pushes that one configuration change, so don't worry about anything disastrous :). Worst case a guest may not get the new policy setting.

You'll need a workstation with the VI Perl toolkit installed, when you run the script it'll prompt for your virtual center url, username and password. URL is https:///sdk.

Of course you'll have to re-run this when new VMs are added if you don't consciously build into templates or your new VM process the policy setting.

R