Summer is time for vacations, beaches, and WEM Upgrades! Citrix has released version 4.7 of WEM. You can now download the new version here (requires Platinum licenses and login to Citrix.com). I’ve provided the release notes below.
Workspace Environment Management 4.7 includes the following new features. For information about bug fixes, see Fixed issues.
New-wemDatabase PowerShell cmdlet updated
PowerShell modules in the Workspace Environment Management SDK are updated at this release. A new parameter CommandTimeout is provided for the New-wemDatabase cmdlet which allows you to configure timeout period for connection attempts to the WEM database. After the timeout period an error message is displayed. The default timeout is 300 seconds.
The Workspace Environment Management SDK documentation is updated to version 4.7.
Thanks for reading,
Spring has sprung and Citrix has released version 4.6 of WEM. You can now download the new version here (requires Platinum licenses and login to Citrix.com). I’ve provided the release notes below.
Workspace Environment Management 4.6 includes the following new features. For information about bug fixes, see Fixed issues.
Assigned applications can include StoreFront store apps
You can now assign resources published in Citrix StoreFront stores as application shortcuts in Workspace Environment Management. This allows you to configure Start menu shortcuts which Workspace Environment Management end users can use to easily access remote store resources. Agent host machines configured to use the Transformer feature show shortcuts to Citrix StoreFront store resources inside the Applications tab. Configure the StoreFront stores that Citrix Receiver connects to using a new Advanced Settings tab. Then add store resources as applications in the Add Application dialog, which contains a redesigned General settings tab. For more information see Applications.
Transformer integrated with Receiver for Windows SDK
Transformer is now integrated with the Citrix Receiver for Windows SDK. This allows you to make StoreFront-based assigned application actions available to Transformer kiosk users, and for Citrix Receiver pass-through authentication to be used. Only published applications which users have permission to access are displayed in the Transformer kiosk Applications tab.
Note: If you have previously configured Transformer for Enable Autologon Mode and now wish to configure users for Transformer integrated with Receiver for Windows SDK, you must clear the option Enable Autologon Mode (in the “Transformer Settings > Advanced > Logon/Logoff & Power settings” tab). This allows users to log in to the Transformer client endpoint machine using their own credentials. These credentials are passed through to provide access to their assigned StoreFront-based applications.
Active Directory performance
The Active Directory Subsystem has been redesigned to improve performance and stability. Performance improvements are particularly noticeable when you add AD or OU objects, and dead forests or domains are detected in your environment.
The administration console user interface has changed:
- In Advanced Settings > Configuration pane, there is a new StoreFront tab for configuring the StoreFront stores that Citrix Receiver connects to.
- In Actions > Applications, the Add Application dialog General Settings tab is redesigned for adding StoreFront store resources as applications. The Advanced Settings tab Application Type option is removed.
- In Active Directory Objects, there is a new Advanced pane. The AD Settings tab contains a new option Active Directory search timeout for configuring how long Active Directory searches are performed before they time out. The default value is 1000 msec. We recommend that you use a timeout value of at least 500 msec to avoid timeouts before searches complete.
Agent administrative templates
The administrative templates provided to configure the agent have been renamed to make the filenames versionless. For more information see Configure the agent.
Workspace Environment Management documentation is updated to reflect current product behavior.
Thanks for reading,
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,