I recently cloned a VM, lets say from 'server1' to 'server 1 clone'. Once the original VM was deleted, the display name for 'server1 clone' was renamed to 'server1'
OK, typically, to match up the VM's files to its display name, I storage vmotion the VM from one datastore to another. (Directions: http://kb.vmware.com/kb/1029513)
Well that hasn't worked. All of the files still say 'server1 clone'.vmdk, .vmx, etc etc.
Currently running vSphere 5 on Enterprise Plus. Is my only way to "fix" this is to use the console? Eeek..
By the way, the VM in question is our vCenter server.
I always thought this was expected behaviour and that an sVmotion only renamed the VM folder, not the files within it? Actually after reading that KB I see that the files should in fact be renamed too. Interesting... when I svmotion a vm I'm getting the same result as you, the filenames aren't changing?
Edit: Just tried again with an offline VM that I created from scratch. Folder name changed, all files stayed the same. That KB you referred to doesn't actually mention ESXi 5 in the applicable product versions. I imagine then what we're seeing is expected behaviour after all. Perhaps a future update for ESXi will add the file renaming feature.
I noticed that ESXi 5 wasn't referenced in the KB either. I'm not sure why that feature would be removed from this release though... But I'm glad I'm not the only one experiencing this.
No, problem m8. Im just happy to see that they've actually created a KB describing this 🙂
As you, I do this a lot as I like the naming to be identical all the way..