In the coming blogs could you cover the best ways to provision WEM agent in non persistent environments?

CTX226494
the-simplest-way-to-get-your-wem-agent-cache-up-to-date

Hi Ray, WEM only deploys UPM’s registry settings to the machine on startup, as with MS Group Policy or Citrix Policy. WEM is just another UPM Policy deployment option (WEM just “pulls the UPM levers”. The UPM Service still handles all profile operations as normal. If the WEM agent cannot communicate with the WEM broker, then it would run from the local cache and there should be no issues with UPM. WEM UPM configuration would also be overwritten by any leftover / rogue AD GPO or Citrix Policy UPM settings. It would be interesting to see if you had the same results in a clean test OU with the latest version of WEM? I don’t suppose this is something you can try?

Personally I prefer the ease of CPM setup through WEM rather than through traditional GPO or Citrix Policies. Plus, there is the major advantage that CPM policies configured through WEM are processed synchronously by the WEM Agent. So processing CPM through the WEM Agent is faster. As Leee mentions, CPM is CPM, we are just using WEM as the method of configuration. Something to bear in mind. (The WEM CPM capabilities are one release behind traditional GPO / Citrix Policy capabilities at the moment).

Hi Ray, there is no difference with regards to CPM. WEM however is a seperate product which enables a sort of replacement for certain types of GPO actions.