FSLogix Container (Office/Profile) in Citrix Environments

Recently, I have been involved more and more in projects where Office365 is to be fully implemented in Citrix environments. This means that the customer not only needs the standard Office applications Outlook, Excel and Word, but also wants to use teams and OneDrive.

But this is exactly where we, without additional software, have big problems in non-persistent desktop environments. For example with our profiles (Team Installer stores its data in the profile) or so that the data is downloaded from the Internet every time (excluding OneDrive Sync data in the profile).

However, we have recently been in the fortunate position of being able to use FSLogix “free of charge” for this purpose, if we meet the following requirements:

  • Microsoft 365 E3/E5
  • Microsoft 365 A3/A5/ Student Use Benefits
  • Microsoft 365 F1
  • Microsoft 365 Business
  • Windows 10 Enterprise E3/E5
  • Windows 10 Education A3/A5
  • Windows 10 VDA per user
  • Remote Desktop Services (RDS) Client Access License (CAL)
  • Remote Desktop Services (RDS) Subscriber Access License (SAL)
Profile Container Multiple Sessions FSLogix
Continue reading “FSLogix Container (Office/Profile) in Citrix Environments”

Update to Virtual Apps and Desktops Version 1909

On September 19, Citrix Virtual Apps and Desktops (CVAD) version 1909 was released. Following a little guide to the update to the latest version.

Link to Citrix Virtual Apps and Desktops Documentation

Citrix Virtual Apps and Desktops EOM EOL Matrix
Continue reading “Update to Virtual Apps and Desktops Version 1909”

SAML Authentication with Azure AD as IdP and Citrix as SP

Since Citrix XenApp / XenDesktop 7.9 the Federated Authentication Service (FAS) is available. Via Citrix FAS it is possible to authenticate a user via SAML and thus connect Citrix as a service provider to existing identity providers, such as Azure-AD.

Sequence of SAML authentication

  1. The user browse the FQDN (e.g. citrix.deyda.net) of the Citrix Gateway vServer (Service Provider) to start his VA / VD resources
  2. The Citrix Gateway vServer directs the unauthenticated user directly to the Identity Provider (Azure-AD) to authenticate itself (saml: authnRequest)
  3. The Identity Provider points to its SingleSignOnService URL (e.g. login.microsoftonline.com) and the user must authenticate
  4. The user enters his AD credentials and these are checked by the Identity Provider against the user database
  5. Upon successful verification in the user database, the IdP is informed
  6. The IdP issues a token (SAML assertion) and sends it to the Citrix Gateway (saml: response)
  7. Citrix Gateway checks the token (assertion signature) and extracts the UPN from the assertion token. This allows access via SSO to the VA / VD farm via FAS (The SP does not have access to the user’s credentials)
SAML Auth Azure AD & Citrix Gateway with FAS
Continue reading “SAML Authentication with Azure AD as IdP and Citrix as SP”

NVIDIA vGPU Licensing

Through various recent projects, I had to work through the clutter of information regarding NVIDIA vGPU licensing.

Here is a small summary of this information.

NVIDIA vGPU Architecture

Under the control of the NVIDIA GPU Virtual Manager, running in the hypervisor, the NVIDIA Physical GPU can operate multiple virtual GPU devices (vGPUs), that can be assigned directly to the Guest VM.

Diagram showing the high-level architecture of NVIDIA vGPU

The Guest VMs use the NVIDIA virtual vGPUs in the same way as a physical GPU would come from the hypervisor by direct passed through. The NVIDIA Driver loaded into the guest VM provides Direct GPU Access for high-performance operations. The NVIDIA Virtual GPU Manager paravirtualized interface performs the non-performance management operations for the NVIDIA Driver.

Continue reading “NVIDIA vGPU Licensing”