After implementing VM Storage Profiles this week at a client’s site, I noticed that even though I had added the correct storage profile to the virtual machine, and to the datastore, it was showing as ‘Noncompliant’.
On further inspection in the host profiles section of the c# client, I noticed that the ‘vm home’ (The location of the .VMX file) did not make itself compliant, even though the location was in the same place as its virtual hard drives (.vmdk files).
After a lot of trial and error, I found the workaround was to Storage vMotion the VM to the same datastore (So go through the process of migrating the VM but selecting the same datastore as it currently resides).
Be First to Comment