Hyper-V, SCVMM 2008 and Failover clustering volume GUIDS

I have about 25 VMs on Hyper-v in a 4 node Windows 2008 Failover cluster.  I created the first 6 or so VMs before I learned about using volume GUIDs instead of drive letters.  How can I successfully change the existing VMs using drive letters to use volume GUIDs.  I learned the hard way that you simply cannot go into Failover Clustering and change the drive letter of the shared storage object since when the VM restarts, it no longer finds itself and getting it back is a difficult process.

I hear there is a possibility of manually editing the XML for the VM, but I also understand this is not a supported option and I am not sure it would work anyway.
vppincAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

plimpiasCommented:
your best bet to take the safe side is to migrate them to another host that is not in the cluster. Fix the GUID on your cluster and migrate it back.
0
plimpiasCommented:
Also to add to this, delete all your snaps. shutdown the VM and let it finish the merge. Backup the VMM files. Delete the drive, create a new GUID an move it all back to it and add a new virtual machine and reconfigure your VM settings.
0
vppincAuthor Commented:
What a pain.  Not worth it.  I will leave these at drive letter for now until Microsoft comes up with a quick way to change it.
0
mdmiddleCommented:
This is what I have done in the past...
- Shut down the VM.  
- Using Hyper-V Manager, Export it to a new location
- From a command prompt, use Mountvol to list the GUID associated with the drive letter that is being used.  Copy the GIUD path.
- Remove the drive letter from the volume using Disk Management
- In Hyper-V Manager, start the Import process
- Use the GUID copied above as the target location
**TIP:  If you add an extra backslash to the end of the GUID path you can click Browse and browse the directory (it works elsewhere too).
- Complete the import process and start the VM.

HTH!
0
vppincAuthor Commented:
Rumors that R2 handles this.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Virtual Server

From novice to tech pro — start learning today.