WEM 2009 UPDATE AVAILABLE

Intro

Fall is the season and the Citrix Developers didn’t make like a tree and leave. Citrix has released the next version of WEM,version is 2009. You can download the new version here (requires Platinum/Premium licenses and login to Citrix.com). I’ve provided the release notes below.

What’s new in 2009

Workspace Environment Management 2009 includes the following new features. For information about bug fixes, see Fixed issues.

Support for the Windows 10 1909 template

WEM adds support for the Windows 10 1909 template introduced in Citrix optimizer. You can now use WEM to perform template-based system optimizations for Windows 10 1909 machines. For information about using Citrix optimizer, see Citrix optimizer.

Profile Management

Workspace Environment Management now supports all versions of Profile Management through 2009. The following new options are now available on the Administration Console > Policies and Profiles > Citrix Profile Management Settings > Profile Container Settings tab:

  • Enable Folder Exclusions for Profile Container (option for excluding the listed folders from the profile container)
  • Enable Folder Inclusions for Profile Container (option for keeping the listed folders in the profile container when their parent folders are excluded)

For more information, see Profile Container Settings.

Administration console

The administration console user interface has changed:

  • In Administration Console > Policies and Profiles > Citrix Profile Management Settings, there is a new Profile Container Settings tab for you to configure Profile Management profile container settings.
  • The Enable Profile Container option now moves to the Profile Container Settings tab. Previously, the option was present on the Synchronization tab.

Depreciated Features

Click here to see depreciated features.

Thanks for reading,
Alain

WEM 2006 UPDATE AVAILABLE

Intro

Despite stay at home orders, the Citrix update cycle never stops. Citrix has released the next version of WEM. This version is 2006. You can download the new version here (requires Platinum/Premium licenses and login to Citrix.com). I’ve provided the release notes below.

What’s new in Workspace Environment Management 2006

Workspace Environment Management 2006 includes the following new features. For information about bug fixes, see below.

Enhancements to Group Policy Object (GPO) migration

This release makes further enhancements to GPO migration. Different from the Migrate wizard, which lets you migrate only Group Policy Preferences (GPP), you can now also import Group Policy settings (registry-based settings) into WEM. After importing the settings, you can have an itemized view of the settings associated with each GPO before you decide which GPO to assign. You can assign the GPO to different users or user groups. To import Group Policy settings, navigate to Administration Console > Actions > Group Policy Settings, select Enable Group Policy Settings Processing, and then click Import to open the import wizard. For more information, see Group Policy Settings.

Administration console

The administration console user interface has changed:

  • In Actions, there is a new Group Policy Settings pane. In the pane, there is a Group Policy Settings tab for you to configure Group Policy settings.

Fixed Issues

  • The WEM agent in an OU might fail to retrieve its configuration set from the infrastructure service. As a result, the agent fails to register with the associated configuration set. The issue can occur if there are multiple OUs that are present in the administration console and one or more OUs cannot be accessed. [WEM-6214, CVADHELP-13442]
  • On the agent host, attempts to start a published application as an application shortcut might fail. The issue occurs with application shortcuts that are created using StoreFront URLs. [WEM-7348, CVADHLEP-14061]
  • Attempts to start an application from the My Applications icon list in the agent UI might fail. The issue occurs with application shortcuts that are created using StoreFront URLs. [WEM-7578, CVADHELP-14171]
  • When the number of connected agents exceeds a certain threshold (for example, 800), Norskale Broker Service.exe might consume a significant amount of CPU resources. For example, its CPU usage can increase to 70%. [WEM-7773]
  • When the number of connected agents exceeds a certain threshold, Norskale Broker Service.exe might consume a significant amount of CPU resources. [WEM-7886, CVADHELP-14272]

Known Issues

Workspace Environment Management contains the following issues:

  • No new issues have been observed in this release.

Depreciated Features

Click here to see depreciated features.

Thanks for reading,
Alain

XenServer: Drivers for WinPE

Intro

If you deploy images with a Microsoft product, you are using WinPE (Microsoft Windows Preinstallation Environment) to configure and install an operating system. If you use XenServer for your Hypervisor of choice, then you will have to extract the XenServer drivers to import into your WinPE

Extracting the Files

The simplest way to get the files is to load the XenTools ISO onto a system and copy the install files over to a temporary location. Select your Virtual Machine, click the Console tab and select the DVD Drive drop down and select guest-tools.iso. In this case, my XenServer environment is on version 8.1.

This will mount the current XenServer tools ISO onto the virtual machine’s DVD drive.

To get the drivers, copy managementagentx64.msi (and managementagentx86.msi if you need drivers for a 32-bit operating system) to a temporary location on your system.

Here, we have the managementagentx64.msi file in the D:\temp folder. To extract the files we run the following command:

msiexec.exe /a managementagentx64.msi /qb TARGETDIR="D:\temp\drivers"

This runs installs managementagentx64.msi as an administrative install. This is why we used /a as a parameter and the TARGETDIR parameter so it will expand the MSI files into the D:\temp\drivers folder. I also used /qb to run the install in Quiet mode with a Basic GUI.

After running this command, we can now drill-down into folders created by the administrative install.

The MSI contains a lot of files and executables, but we’re looking for drivers. Fortunately, there is a Drivers folder. Under Drivers there are v8 and v9 folders. v9 holds the newer drivers. Under v9 we have the folders that contain the driver files (both 64-bit and 32-bit versions).

Importing the Drivers

There are five drivers that we will want to import into WinPE. In the following examples, I’m importing the drivers into Microsoft Deployment Tool.

I drill-down to my Deployment Share (MDT Production), expand Out-of-Box Drivers and right-click on WinPE 5.0 x64. The Import Driver Wizard start and we can drill down to the location of our drivers.

Click Next, Next and the import will begin. At the end a Confirmation window will display the status.

Since I didn’t drill down into each driver folder, the wizard imported both the 32-bit and 64-bit versions of the drivers. I can delete the 32-bit versions by selecting them, right-clicking, and choosing delete.

Now to use the new drivers, you right-click on the Deployment share and select Update Deployment Share.

The Update Deployment Share Wizard comes up. My preference is to always choose “Completely regenerate the boot images.” This takes longer, but the results are consistent.

The wizard will complete and a new ISO is generated in the Boot folder under your deployment share.

You copy this ISO to your XenServer ISO share, and when you want to build a new image, you point your XenServer virtual machine to this ISO and WinPE will use the new drivers you imported.

I hope this post helps you track down the XenServer drivers you need to automate builds in the future. Please comment if you have any questions.

Thanks for reading,
Alain Assaf