Rename a VM without shutting down…using storage vMotion


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.


  • vCenter 4.0 U1
  • ESX 4.0 U1


  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.


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?


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

Popular posts from this blog

NSX-T: vCenter and NSX-T Inventory out of Sync (Hosts in vSphere not showing up in NSX-T)

NSX-T: Release associated invalid node ID from certificate

MacOS: AnyConnect VPN client was unable to successfully verify the IP forwarding table modifications.