Provisioning Server: Exporting vDisk fails


Provisioning Server is one of those workhorse products that works well day in and day out and then it doesn’t. There’s so many things that can go wrong for a number of reasons. This post covers a simple fix for when you can’t export a vDisk.


There is a Mac/PC debate among Citrix engineers on whether MCS (Machine Creation Services) or PVS (Provisioning Services) is better. This post will NOT engage in this debate because clearly, PVS is better :).

One thing that distinguishes PVS from MCS, is vDisk versioning. With vDisk versions you can isolate updates to a vDisk or allow for quick revisions without affecting and copying a 30-40 GB file every time you want to make a change or update to your vDisk. For each version you can (and should) add notes to the Properties field.


One thing we recently decided as a team was to utilize Bugzilla to track changes to our vDisks. Having a method for tracking changes is essential, especially if you have multiple team members and want everyone on the same page. As you can see above, I like to put a lot of info into the properties so that there’s no question as to what changes the vDisk has. This unfortunately caused an issue recently as I was not able to export the vDisk to our other PVS farm.


When working with vDisk versions, exporting the vDisk is the easiest way to move those versions to another farm.


You can select from what version you wish to export the vDisk and an XML file is generated. You then copy the XML and the AHVDX files to the destination PVS Store. From the destination Store, right-click and select “Add vDisk Versions…” and your vDisk versions are added.


Normally, this works well in our environment, but this time I was not able to export the vDisk. I could bring up the export vDisk dialog and go through the motions, but no XML was generated. It turns out if you have multiple lines in the version description field, the export fails. You don’t get any warning message or event log entry about it either so before you start going down the rabbit hole trying to find a fix. Double-check your properties field and make sure you have everything on one line. I hope Citrix resolves this in an upcoming PVS version, as it seems like a minor thing to fix.



Thanks for reading,

WEM: Notes From the Field 3



I noticed that my WEM Console would no longer connect to my WEM broker server. I started digging and saw that the Norkscale Broker Service kept crashing on the broker. I had the service configured to auto restart, but this wasn’t resolving my issue. I put in a call to Citrix Support for guidance.


It turned out that I had created the issue accidentally. My team and I were working to remediate issues generated by a security compliance product. In the process of this I activated FIPS compliance on the WEM Broker Server. As a result, no agents or consoles could connect to the broker server and the broker server itself could no longer communicate with the SQL database.

Once FIPS was turned off, everything started working again. I later got confirmation from Citrix that WEM is not FIPS compliant. Keep that in mind if your company/government agency requires servers to be FIPS compliant.

Thanks for reading,

WEM: Notes from the Field 2


Quick Note

If you are using group policy (and why wouldn’t you) to configure your WEM agents, pay close attention to leading and/or trailing spaces. This has happened twice to me with agent versions 4.2 and 4.3.

The Connection Broker Name and Site Name fields in the Workspace Environment management\Agent Host Configuration administrative template must NOT contain any leading or trailing spaces. If you have any, then the agent cannot communicate with your WEM Broker server nor can it load the correct Configuration Site.

Thanks for reading,