Category Archives: Workspace Management

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]
Advertisements

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

WEM: Notes from the Field 2

whatifitoldyou

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