Citrix’s software developers are hard at work and have rolled out version 4.5 of Workspace Environment Manager. You can now download the new version here (requires Platinum licenses and login to Citrix.com). I’ve provided the release notes below.

What’s new

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

Application security

Application Security functionality has been added to the administration console Security pane. This allows you to control the applications users are permitted to run by defining rules in Workspace Environment Management. This functionality is similar to Windows AppLocker but gives you the additional ability to:

  • define rules without immediately assigning them,
  • bulk-assign rules to users,
  • import rules from Windows AppLocker.

For more information, see Security.

Workspace Environment Management SDK PowerShell Modules

PowerShell modules are released as the first part of a Workspace Environment Management SDK. The modules are installed by the infrastructure services installation process. You can perform the following administrative tasks by running the cmdlets in the modules directly from the PowerShell console, or from PowerShell scripts:

  • create a Workspace Environment Management database
  • update a Workspace Environment Management database
  • get the configuration from a local or remote infrastructure server
  • set the configuration of a local or remote infrastructure server

For more information, see the Citrix Developer Documentation.

Note: This is the initial release of the PowerShell SDK modules, and Citrix reserve the right to make further syntax improvements in future releases.

Support for SQL Server Always On availability groups

Workspace Environment Management has been tested with SQL Server Always On availability groups, and is now certified for use on that technology. For more information and advice, see System requirements.

Process optimization

History now user-centric. Workspace Environment Management (WEM) intelligent optimization relies on WEM “remembering” how many times a process infringes rules configured in the administration console. Based on this “memory,” WEM optimizes (or not) the process when it is next started.

In previous releases, this “memory” was based only on process name. In other words, if a process infringed a rule when it was running as User A, it was also considered to be infringing for all users connecting to the agent, and the process was optimized globally for all users.

Starting in this release, the intelligent optimization “memory” is based on both process name and user details. This means that intelligent optimization is now user-centric. In other words, if a process infringes a rule when it was running as User A, but does not infringe a rule when it was running as User B, the process is optimized only when running as User A.

History now in local database. Workspace Environment Management (WEM) has two local databases: one contains the agent local cache, and another stores local data. Historically, WEM’s intelligent optimization memory was stored either in the agent registry or in an XML file. An XML file was used if the custom argument UseNonPersistentCompliantHistory was set during agent installation.

From this release, WEM’s intelligent optimization memory is stored in the agent local database (LocalAgentDatabase) located in the agent installation folder.

AgentServiceUseNonPersistentCompliantHistory custom argument for agent installation

The Citrix Workspace Environment Management Agent Setup executable no longer acknowledges the AgentServiceUseNonPersistentCompliantHistorycustom argument. This custom argument previously allowed you to save agent service process optimization history to an XML file. The optimization history is now stored in the agent local database (LocalAgentDatabase) located in the agent installation folder.

User interface

The following changes are made to the administration console user interface:

  • A new Application Security pane is added to the Security tab.


Workspace Environment Management documentation is updated to reflect current product behavior.

Workspace Environment Management SDK documentation is added to the Citrix Developer Documentation.


Thanks for reading,


PowerShell – Add PowerShell to Context Menu

Here’s a holiday hack for PowerShell. If you would like the ability to right-click on a directory and have PowerShell open to that directory here’s what you do…

  1. Open the registry on the system you want to do this on (regedit.exe)
  2. Navigate to HKEY_CLASSES_ROOT\directory\shell

Image 001

  1. Right-click and create a new key called PowerShellPrompt

Image 002

  1. Rename the Default Data to “PoSH Here” or something similar. This is what will display in the context menu when you right-click

Image 003Image 004

  1. Right-click on the PowerShellPrompt key and create a new key. Name it Command

Image 005

  1. Change the Default data to the following command-line
powershell.exe -noprofile start-process  powershell.exe -verb runas -argumentlist "{ -noprofile -noexit cd %1}

Image 006

  1. Now, when you right-click on a directory, An elevated PowerShell prompt will open at that directory

Image 009

  1. If you want to load your profile when this prompt opens, remove the second “-noprofile” from the command-line
powershell.exe -noprofile start-process  powershell.exe -verb runas -argumentlist "{ -noexit cd %1}"
  1. If you want to have an Icon show up in the Context menu add the following String value to the PowerShellPrompt key

Image 011Image 012
Thanks for reading,


A list of articles/blog posts to review, research, or archive

Thanks for reading,

A hard, rough, abrasive look at camel spotting…no dromedaries…no virtualization.

%d bloggers like this: