Deyda Consulting Blog
Update of the article to the Workspace Environment Management Version 1906.
Here is the first small roundup of the WEM Administration Console and their underlaying setting options.
Supported operating systems:
A short listing of the older WEM topics that I noticed and can serve as an argument for you to update to WEM 1808.
If the above service terminates, resources can no longer be distributed from this server. This is due to a memory allocation error that WEM still makes in the earlier versions.
Citrix Article: https://support.citrix.com/article/CTX226339
Continue reading “Known issues until Citrix WEM 1808”The main task of every CPU is to process data. But here is the misconception, the faster the CPU (or the more CPUs I allocate), the faster the data will be processed. This is unfortunately not quite that easy, because before the CPU can process the data, it must be read out by the slower system RAM and that latency can slow the CPU processing. In order to minimize the time the CPU is waiting on reading data, CPU architectures include on-chip memory caches (local RAM) that are much faster than RAM (the access is up to 95% faster).
A few days ago, Workspace Environment Management (WEM) Version 1808 was published. Below an introduction to WEM and a guide to upgrade to version 1808.
Workspace Environment Management is a Performance Management and UEM (User Environment Management) tool from Citrix. It is licensed to all customers with Virtual Apps/Virtual Desktop Advanced and Premium (formerly XenApp/XenDesktop Enterprise and Platinum) Versions, as well as an active customer success services. Workspace Environment Management is a Performance Management and UEM (User Environment Management) tool from Citrix.
The activation of Office365 in Terminal Server environment is enabled with shared computer activation, but will not work without further configuration. What is not described in the Microsoft article, from my older blog entry, Office puts in the user directory “AppDataLocalMicrosoftOffice16.0Licensing” (the 16.0 stands for Office 2016, at 2013 there must be 15.0) a license token for the host (Server/Client). This token is valid only for the host on which the user has just activated the office. If the user logs on another host, a new token is placed in the directory.
For roaming profiles, the existing configuration must be extended by the folder listed above, or the folder that you defined with the GPO, so that it’s synchronized across all hosts.
Unlike the normal license token for FatClients, this is only valid for a few days. Microsoft has published this TechNet article: TechNet Shared Computer Activation
Continue reading “Activation of Office365 through multiple Citrix Worker (Activation Token Roaming)”
