Current version is Workspace Environment Management 2206.
In the following I will give an insight into the menu items System Optimization, Policies & Profiles and Security.
These settings are used to reduce resource usage on the host. They are used to free up resources and make them available for other applications, thereby increasing the user density per host.
While the System Optimization settings are machine-based and apply to all user sessions of a machine, the Process Optimization under CPU Management is user-based.
That is, when a process triggers CPU Spike Protection in user A’s session, the event is recorded and limited for user A only. When user B starts the same process, the behavior of process optimization is determined only by process triggers in user B’s session.
Continue reading “WEM Administration Console – Part 2 (System Optimization, Policies & Profiles and Security)”
Workspace Environment Management optimizes Citrix workers for the best possible performance (user density, logon time and application response time).
WEM is subject to the Current Release Lifecycle (Additional Component) and therefore there is no LTSR version of WEM available.
To use WEM, you must have an active Customer Success Services (CSS) for one of the following licenses:
- Citrix Virtual Apps Advanced
- Citrix Virtual Apps Premium
- Citrix Virtual Apps and Desktops Advanced
- Citrix Virtual Apps and Desktops Premium
- Citrix Workspace Premium
- Citrix Workspace Premium Plus
Workspace Environment Management (WEM) is based on the following architecture:
Continue reading “Installing Workspace Environment Management”
Update of the existing article to the latest requirements and features.
User Based Microsoft Teams
The standard installation that the user can perform, e.g. via the Microsoft365 Apps portal, is a user-based installation. In the Citrix environment, this is only recommended for desktop operating systems (pooled or personal desktop).
A User-Based Installation can be detected very quickly in the User Profile, because data are then located under AppData\Local\Microsoft\Teams.
This type of installation in a worker with server operating system has many cons:
Continue reading “Install Teams & OneDrive in Citrix (Machine-Based)”
- No control over the installed version
- Several different versions possible installed on the same worker
- Complete data (~1 GB) are in the user profile
What is Hybrid Azure AD Join ?
Let’s just start with the official definition from the Microsoft documentation:
Hybrid Azure AD Join: Joined to on-premises AD and Azure AD requiring organizational account to sign in to the device.
This means that after the device is Hybrid Azure AD joined, it behaves the same as any other computer connected to Active Directory.
Sign in with an Active Directory account is required.
User credentials are verified against an Active Directory domain controller.
Group Policy objects for users & computers read from the domain controller are applied automatically.
After the Active Directory connection process is complete, additional steps are performed asynchronously in the background to register the device in Azure AD as well.
Continue reading “Why a Windows Server 2019 VDI should be Hybrid Azure AD joined”