Category Archives: Workspace Management

WEM 4.5 UPDATE AVAILABLE

update
Intro

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.

Documentation

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,
Alain

Advertisements

WEM 4.4 UPGRADE AVAILABLE

free_upgrade

Intro

Citrix’s software developers are hard at work and have rolled out version 4.4 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.4 includes the following new features. For information about bug fixes, see Fixed issues (below).

Data analytics

From this release, the Workspace Environment Management infrastructure service sends anonymous usage data to Google Analytics. For more information, and for opt-out instructions, see Infrastructure services.

Profile Management

From this release, Workspace Environment Management supports Citrix Profile Management 7.15. The following new options are now available in the administration console:

  • Enable Logon Exclusion Check (options controlling file system exclusions)
  • Enable Profile Streaming Exclusion List – Directories (option controlling user profile streaming)

Database maintenance

In the Infrastructure Services Configuration utility, the Database Maintenance tab has a new option Agent registrations retention period. This allows agent registration logs to be deleted after a set time, which reduces the size of the database. It also reduces lag in populating the Registrations tab in the administration console.

Documentation

At this release, Workspace Environment Management documentation is updated to reflect current product behavior. The documentation has also been remodeled as a single “versionless” documentation set describing the “current release.” This approach reduces duplication in the online documentation set, gives more focused search results, and is better suited to agile release processes. Associated changes include:

  • A top level “current release” article contains links to previous documentation sets in PDF format only. (HTML documentation for previous releases is no longer provided.)
  • “What’s new” summarizes the new functionality at the current release, and in previous releases.
  • A new “Reference” section gathers reference information in one location. Port information previously in the introductory article is relocated to “Reference.”

Fixed issues

The following issues have been fixed since Version 4.4

  • If you run the Workspace Environment Management administration console as a standard Windows user, and you attempt to start the Modelling Wizard, the wizard does not start. [#WEM-187]
  • When you attempt to add a user group, which is in a different AD domain to the infrastructure server, as a processed group in the Citrix User Profile Management tab in the administration console, the exception *IndexOutOfRangeException is raised, and the group is not processed. #WEM-210]
  • Links in “This PC” in Windows 10 do not reflect folder redirection, and still point to local folders. [#WEM-234]
  • The Agent Host waits about 5 minutes before starting if Workspace Environment Management is installed on Windows version 8, or Server 2012, and a language pack is installed. [#WEM-244]
  • If you launch or refresh a UI session agent when it is not bound to a configuration set, keyboard and mouse locks which are active during the agent refresh are not released. [#WEM-321]
  • If you attempt to add an agent host machine to a configuration set when the agent host machine is in a different domain to the infrastructure service, the machine is not added in the administration console Active Directory Objects tab. This happens regardless of the actual AD topology involved (parent/child domains, multi-forest setups, one- or two-way trust relationships, and so on). [#WEM-326, #WEM-299]

WEM: Notes From the Field 3

toodamnhigh

Intro

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.

FIPS

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,
Alain