The Storage vMotion Approach does no longer work in Version 5. It was an undocumented one in the versions before and is gone.
Thanks for the great work on the tests
Yves Sandfort
Yeves: The storage vMotion approach of renaming .vmdk files is still valid. Although it currently doesn't work. VMware have acknowledged this issue affecting vSphere 5.0 and is scheduled to be resolved in a future update.
Just took the vSphere 5 fast-track class. And straight from the instructors, they thought this would not be rewritten due to the code that was changed to make storage vmotion more efficient. Apparently the engineers didn't know people were using storage vmotion for this purpose, and did not work it in when they rewrote storage vmotion
Agree with Yves. Storage vMotion does not rename all files. I had this point at vSphere 5 classes.
This is now fixed!
A Virtual machines appear in the vSphere Client inventory list with (orphaned) appended to their name. What is the quickest solutions to correct this?
Reboot the Host that VM is hosted onReboot the VMRemove the VM from Inventory, Browse to the VM .vmx file on the Datastore and add the VM to InventoryRight click the VM, select Relocate and select a different host with the cluster
Correct answer: Right click the VM, select Relocate and select a different host with the cluster
I'm not agree with it. Is it anything written about cluster in the question?
In 5.5 troubleshooting guide, page 12, it is stated. The wording is changed from "relocate" to "migrate" though
@google-39cb74aad818efd6ab973d58794c2a49:disqus :Storage Vmotion will rename the files TESTED FOR SURE
For question "An Ex-employee had named all of the virtual machines using the wrong naming conventions. After renaming the virtual machines what is the next step to ensuring that all virtual machine files are named the same?"
FWIW - just read the OVFtool documentation and on page 36 the use case "Rename the OVF Package" provides another ansewr to this: "You can rename an OVF package by converting the OVF to an OVF. This action also renames all the disk names and changes the references in the OVF descriptor".
However, we are talking about live VMs, not OVFs.
Hi Simon, the green ticks and bold chosen answers don't seem to be appearing?
Evan, this should now be fixed. A Plugin was causing an issue with the Exam
View Comments
The Storage vMotion Approach does no longer work in Version 5. It was an undocumented one in the versions before and is gone.
Thanks for the great work on the tests
Yves Sandfort
Yeves: The storage vMotion approach of renaming .vmdk files is still valid. Although it currently doesn't work. VMware have acknowledged this issue affecting vSphere 5.0 and is scheduled to be resolved in a future update.
http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2008877
Jerry
Just took the vSphere 5 fast-track class. And straight from the instructors, they thought this would not be rewritten due to the code that was changed to make storage vmotion more efficient. Apparently the engineers didn't know people were using storage vmotion for this purpose, and did not work it in when they rewrote storage vmotion
Agree with Yves. Storage vMotion does not rename all files. I had this point at vSphere 5 classes.
This is now fixed!
A Virtual machines appear in the vSphere Client inventory list with (orphaned) appended to their name. What is the quickest solutions to correct this?
Reboot the Host that VM is hosted onReboot the VMRemove the VM from Inventory, Browse to the VM .vmx file on the Datastore and add the VM to InventoryRight click the VM, select Relocate and select a different host with the cluster
Correct answer: Right click the VM, select Relocate and select a different host with the cluster
I'm not agree with it. Is it anything written about cluster in the question?
In 5.5 troubleshooting guide, page 12, it is stated. The wording is changed from "relocate" to "migrate" though
@google-39cb74aad818efd6ab973d58794c2a49:disqus :Storage Vmotion will rename the files TESTED FOR SURE
For question "An Ex-employee had named all of the virtual machines using the wrong naming conventions. After renaming the virtual machines what is the next step to ensuring that all virtual machine files are named the same?"
FWIW - just read the OVFtool documentation and on page 36 the use case "Rename the OVF Package" provides another ansewr to this: "You can rename an OVF package by converting the OVF to an OVF. This action also renames all the disk names and changes the references in the OVF descriptor".
However, we are talking about live VMs, not OVFs.
Hi Simon, the green ticks and bold chosen answers don't seem to be appearing?
Evan, this should now be fixed. A Plugin was causing an issue with the Exam