Hello,
I am aware of the steps you need to take in order to enable this feature and that a vMotion of the VM is enough to apply the config. However, if you are using vSAN is there an easier way to apply the change without a reboot of the VM?
Thanks
Did you try unregister/register of the VM?
An alternative could be the reloadVirtualMachineFromPath_Task method.
Blog: lucd.info Twitter: @LucD22 Co-author PowerCLI Reference
Haven't tired the re-register as I'm looking for the most less impact method. Ideally, you make the change and away you go but I am cautious of a VM breaking.
Had a look at the reload option but it mentions "It can be invoked on inaccessible or orphaned virtual machines, but it cannot be invoked on powered on, connected virtual machines."
I want the VM to remain powered on as it could be a critical VM that needs downtime out of hours.
It could also be that the answer is you cannot do it without a restart
What impact do you expect from an unregister/register?
Blog: lucd.info Twitter: @LucD22 Co-author PowerCLI Reference
In theory nothing but I have seen VMs not register before.
Err on the side of caution
Anyone know of any other methods?
Thanks
Did you already try with the vim-cmd on the ESXi node?
See KB1026043
Blog: lucd.info Twitter: @LucD22 Co-author PowerCLI Reference
I did come across this in my Google search but it says the VM needs to be powered off
To resolve this issue, reload the virtual machine's .vmx configuration file.
Note: Configuration changes through .vmx file require the Virtual Machine to be Powered off.
Little confused by that statement as you can storage vmotion and it works but of course this isnt an option with vSAN
Just bringing this one back up if anyone has managed to work out another way before closing...