Rename a VM without shutting down…using storage vMotion

Summary

When renaming a VM in vCenter, underlying files and folders remain named the same as when the VM name was first designated.  This can make for a difficult recovery scenario if file/folders and names in vCenter are out of sync.

Config

  • vCenter 4.0 U1
  • ESX 4.0 U1

Solution

  1. Rename the VM in vCenter
  2. Migrate the VM to another Datastore
  3. Done!
    • If you check the VM’s settings and/or datastore, all related files/folders should now match the VM name in vCenter.

Maybe this was obvious to some folks, but it wasn’t until I was doing maintenance @ the wonderful hour of 2am that this dawned on me as a possible solution.  I’m so used to having to go through this process.

Comments

Martijn said…
Hi Chris,

Thanks for sharing!

I tried your method and it worked partially for me.

All the files were renamed except for the .vmdk files. They still have the original name.. :(

Did I miss something?

Thanx!

Martijn
Zsoldier said…
That is strange. Not sure why it would rename everything but the vmdk's.

Popular posts from this blog

Macbook Pro OSX 10.5.x Sprint Blackberry 8830 Data Tethering

Misc: Fire TV Stick 2 Screen Cut Off, no display adjustment option

PowerCLI: The SSL connection could not be established, see inner exception.