iAndroid's Posts

Luc, thanks for answering. No, we do not want to remove the overrides for any VM sitting on the datastore cluster, but only for the VM (known by name) which has just been created. The reason is t... See more...
Luc, thanks for answering. No, we do not want to remove the overrides for any VM sitting on the datastore cluster, but only for the VM (known by name) which has just been created. The reason is that there are in fact some VMs for which we indeed want to have (and keep) an override, so deleting ​all​ overrides is not an option.
We've got the very same issue: every time a new VM is being created with New-VM, an unwanted VM override entry is being created at the respective datastore cluster, and as there seems to be no wa... See more...
We've got the very same issue: every time a new VM is being created with New-VM, an unwanted VM override entry is being created at the respective datastore cluster, and as there seems to be no way to keep the New-VM cmdlet from behaving like that, the only suitable options seems to be to delete the override entry right away after the VM has been created. Now I'm not sure what the code provided by adamjg​ really does. I get it that the StorageDRS configuration of a given VM ($MyVM) is being extracted from the settings of a given storage cluster ($datastorecluster), but where exactly is this VM config being modified or (what we are looking for) being entirely deleted? Or, to put it the other way round: what would be the correct code to entirely delete the override entry for the given VM $MyVM? Thanks very much - this issue is annoying us since months an I'd be very grateful to get a solution.