<

Citrix Provisioning Services 7.X Error: Management Interface: vDisk properties were lost

Published on
3,969 Points
969 Views
Last Modified:
Paul Wagner
Looking for robots from the future to take me into deep space to find the cure for the zombie apocalypse.
If your vDisk VHD file gets deleted from the image store accidentally or on purpose, you won't be able to remove the vDisk from the PVS console. There is a known workaround that is solid.
Citrix Provisioning Services 7.X Error: Management Interface: vDisk properties were lost

If your vDisk VHD file gets deleted from the image store accidentally or on purpose, you won't be able to remove the vDisk from the PVS console. There is a known workaround that is solid.

Brief version (for the peeps who just want the answer now):
The vDisk label won't delete out of the PVS console because it can't find the VHD and/or PVP file in the image store. They need to be there in order for the PVS Console to delete them. If it can't find them, it freaks out. Recreate those files using the exact vDisk name and then try to delete again from the PVS console.

Long version (for the peeps who want to nerd out with me):

0. Of course, you made sure that any device assignments were removed before trying to delete the vDisk
0.png
1. You right click the vDisk and click Delete
1.png2. You then check the box to delete the associated VHD file(s)
2.PNG3. Oops! vDisk properties lost?
3.PNGUmmm, ok... It sounds like the PVS Console doesn't know where to find the files.

4. Let's go to the image store and check it out.
4.pngSure enough, there's only a lonely little LOK file there. That means the PVS Console can't delete the VHD because there's nothing to delete. It isn't there! Well, now what do we do?

5. Let's COPY another VHD and PVP file from the image store. (Size or age doesn't matter. You can select the smallest VHD file to reduce wait time.)

5.PNG
6. PASTE the copied files into the same folder.

6.PNG
7. Rename the files to the exact name of the vDisk you are trying to remove (see image in Step 1)

7a.PNG8. You should have a VHD, PVP and maybe a LOK file with the same name
8.png9. Now, go to the PVS Console and try to delete

Presto!

This article was written because the existing documentation on this error doesn't exactly solve the problem quickly. Please let me know if there are any corrections or enhancements to make as well as any grammatical or technical errors. Hopefully this helps!
0
Comment
Author:Paul Wagner
0 Comments

Featured Post

Windows Server 2016: All you need to know

Learn about Hyper-V features that increase functionality and usability of Microsoft Windows Server 2016. Also, throughout this eBook, you’ll find some basic PowerShell examples that will help you leverage the scripts in your environments!

Join & Write a Comment

In this video tutorial I show you the main steps to install and configure  a VMware ESXi6.0 server. The video has my comments as text on the screen and you can pause anytime when needed. Hope this will be helpful. Verify that your hardware and BIO…
Video by: ITPro.TV
In this episode Don builds upon the troubleshooting techniques by demonstrating how to properly monitor a vSphere deployment to detect problems before they occur. He begins the show using tools found within the vSphere suite as ends the show demonst…
Suggested Courses

Keep in touch with Experts Exchange

Tech news and trends delivered to your inbox every month