Is there any way to rename a virtual machine (VM) or its files using vSphere Storage vMotion?
If you're going to change the name of a VM, then it's a good idea to change the underlying component file names. Changing the folder name of a data store by using a tool such as the vSphere Client doesn't change the underlying component file names in ESX/ESXi 3.5 and 4.x. It's easy to change file names through the ESXi console, but this is a time-consuming and potentially error-prone process.
Instead, you can change the VM name before a vSphere Storage vMotion process and then execute the migration. This will change the component file names to the new VM name during the migration. For example, access the vSphere Client, open the host inventory and locate the desired VM. Right-click and rename the desired VM and then migrate the VM to another location. When the migration finishes, the VM component file names will match the VM that you renamed.
This wasn't really a bug, but it was changed in updates for vCenter Server 5.x. You may need to enable the renaming capability in the advanced settings for vCenter Server by adding the
provisioning.relocate.enableRename advanced parameter and setting it to true.
Dig Deeper on vMotion and Storage vMotion
Related Q&A from Stephen J. Bigelow
Not all hypervisors and OSes can play nice with others. The best method for avoiding complications down the road is to thoroughly test your nested ...continue reading
Theoretically, there is no limit on how 'deep' a nested VM can go. The best way to avoid any confusion is to appropriately label hypervisor nesting ...continue reading
Interested in giving nested virtualization a try in your data center? There are a few software and hardware requirements you'll have to meet first.continue reading
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.