WagtheReal Digest – July 29th 2017

1tcvjb

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

 

Thanks for reading,
Alain

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