I’m often asked how to update a vDisk for use with XenDesktop, so I figured I should publish my answer.
1. Navigate to your store via Windows Explorer, Copy the .VHD file currently in use, then Paste it.
2. Rename it – We use A,B,C,D and rotate each time we update.
3. Open the PvS Console, Navigate to your vDisk Pool.
4. Right Click on vDisk Pool, Select Add Existing vDisk.
5. Make sure your Store and Server are correct, then click Search.
6. Select the new vDisk and click Add then Close.
7. Open your vDisk Pool in the PvS Console.
8. Right Click on the new vDisk, click Properties.
9. Click Edit file properties…
10. Change the Access Mode to Private Image and adjust your revision numbering.
For the next steps, I use a VM that is exactly like the VMs the image will be used on. This method is documented in the XD Getting Started Guide and is referred to as BaseDesktop1.
11. Expand Device Collections.
12. Assign your BaseDesktop1 (or whatever you’ve named it) the new vDisk that is in Private Mode.
13. Boot the VM in your Hosting Infrastructure of choice.
14. Make Changes.
15. Shut Down VM.
16. Change the vDisk to Standard Mode.
17. Assign vDisk to whichever VMs you wish.
These steps should suffice to answer most questions regarding updating vDisks for XenDesktop. I’ll be happy to assist you if you have more questions or require clarification. Just leave a comment.
Hi Roger,
So how would you recommend setting up vDisk’s in a situation where you have various end user hardware requirements? I want to be able to leverage one XenDeskop vDisk and manipulate it on demand and deploy it via PVS to an everchanging end user workstation environment.
for example: some workstations may have different video card needs for multi monitor support and others may have differnet sound card needs and so forth. its a very dynamic environment and is changing constantly. i dont want to have to create individual private mode vDisks for each and every version or combination of workstation’s that pop up.
suggestions?
Thank you kindly in advance….
Hal.
Nevermind. Figured it out.
http://support.citrix.com/servlet/KbServlet/download/17631-102-167256/ProductGuide.pdf
Managing vDisks -> Creating a Common vDisk Image -> Buiding the Common Image -> Exporting Specific Data Files using CIM.exe
Thanks!
Harold, the section of the admin guide you’re referring to is a great way to support additional hardware on a standard vDisk. Thank you for the information!
Thanks for share .Great site
i like to add a extra comment when you copy a vdisk and renamed it dont forget to put teh network rights back on, because the rights ” network service “are gone after copy.
also you need to copy the pvp file what is not mentioned above