Changed drive letter in parent image not propagating to deployed desktop

[Meghaj]

Hi

We currently have a View 4.0 environment with vSphere. The parent VM, has two disks.

We had earlier created the second disk drive with letter F and deployed the desktops using the relevant snapshot. The desktops were deployed with second disk named as F.

However, we later found out that it was mandatory for desktops to have the second disk letter as E. We then powered on the parent VM, changed the second drive letter(using my computer->disk management), powered off the VM and took snapshot. We then deployed this snapshot using automated desktop pool in linked clone mode, choosing the newly created snapshot The desktops got deployed, however when we checked them, we found that the second disk letter was still F and not E as changed in the parent VM.

We tried taking the snapshot again and still the same behaviour was observed. We checked the snapshot name etc and it seemed ok.

Please assist.

[JoeDDfS]

Hi,

I don`t know if it is still up to date, but I have some infos which it may be helpful. I have same issue and I think there is problem with created VD (virtual desktop) If y ou change parent image and create NEW desktop it will be, i hope, created with proper drive letter. If you chose recompose it will cause nothing changed. I have tried this with changing letter of disposable diskin win7 VDs. Only which worked was delete VDs and create new with proper leter.

JZ