Jump to content
Welcome to our new Citrix community!
  • FSLogix Policies Deployment from Citrix WEM


    cugcblogs

    SachinBhardwajRnd.png.bbe6fe7017f47b023dffe16c15e61e89.png by Sachin Bhardwaj, CUGC Member

    Introduction

    In this blog, I share some information about the deployment of FSLogix policies using Citrix WEM. FSLogix integration is a popular choice today, but most deployments are made using Active Directory Group Policies because it’s the preferred method to import .Admx for creating FSLogix AD GPOs.

    However, what if we could find an alternative solution to apply FSLogix policies deployment? Yes is the response – WEM (Workspace Environment management). All of the FSLogix policies (office/profile) should be managed via Citrix WEM as well, thanks to Citrix. I’ll walk you through the procedures for archiving such situations as follows:

    This article outlines the various registry settings applicable to FSLogix that includes (App Services, Profile Containers, ODFC Containers, Cloud Cache) Configuration Settings – FSLogix | Microsoft Learn. You can note down those regedit settings applicable for your environment because we are going to create them in WEM group policies.

    Lets begin with deployment:

    1. Login to WEM SaaS portal https://wem.cloud.com or your onprem WEM controller.
    2. Select your Configuration set and navigate to “Actions” in left pane.
    3. Under Action we have “Group Policies Settings,” we have to enable this option as soon as FSlogix polices will be ready.

    Legacy console:

    Citrix WEM

    WEB Console:

    image-48.png.4c262a443c251132bc466f4bdf2501d1.png

    Note: I am following the WEB console because we have the additional option to import all the registries in one go in WEM console.   

    1. Enable Group Policy Settings (if not already enabled)
    1. Leave Registry-based selection
    image-49.png.07493956e0faeff0e0a99e24999b910f.png
    1. Click on Create GPO
    image-50.png.b59eb1b9582e533d0b1e5019490a4787.png
    • Add Name and description (example below)
    • Name: ODFC(Office Data Fslogix Container)
    • Description: Configuration set for Office solutions
    • Click Add to create a new entry
      • Set the Action
      • Select Root Key
      • Add Subpath
      • Add Name (should be the name of key as per)
      • Select the Type
      • Add Data (0 or 1)
      • Select the type of the data (Hexadecimal/Decimal)
      • Click Save to add the GPO
      • Click Done in the next window
    image-51.png.af26de7aebd810dbec79ee8d000e5c4e.png
    • IncludeOneDrive is added in the list
    • Can add all the keys in same way
    • We can Move keys up and down from top selection Menu. For this we have to select EDIT and Move whatever key you want to priority.
    image-52.png.2c579c7c6a0ddf7d3871ffdb1f332c5a.png
    • Same way we can create Profile Container GPOs as below:
    image-53.png.68b884fbdc81f11975217bdd219b03de.png
    • Once both container created, next step is assignments:
    image-54.png.0b3cd808488b0fdeefcffb12cd5dcb1a.png
    1. Select the group policy created, assignment status is “Not assigned” click on Manage assignments.
    image-55.png.0970bdda675f5a79ae31375b42037aa0.png
    1. Select assignment targets (users and groups) to Everyone. Click Save.
    image-56.png.d523b945a172a0a7aea686b5c6999247.pngimage-57.png.37360d6a7412c13f0a9b092f935377c5.pngimage-58.png.e17798477c3a876924eba196fb820203.png

    To know how to create custom assignment group follow the below steps:

    1. Now Go back to Web Console
    1. Select the Configuration Set.
    image-59.png.6ba26aff45d3df6ded9468b04e3c5b72.png
    • Select Assignments
    • Select Assignment Targets
    image-60.png.9e1d6a08a831ffb4cb0dd9f24b1ef9df.png
    • Click Add assignment target
    image-61.png.b37767df0c43e7de53eb7afa4f3dbd42.png
    • Select the identity provider
    • Active Directory
    • Azure Active Directory
    image-62.png.2b113f80b5f01824d122b2bfae78acb5.png
    • Select Users and/or Security groups
    • Add domain
    image-63.png.7cce01f9eea9eb253dd7a4485c79cb03.png
    • Search for the users or security group
    • Click Add

    Now we have to add filters for controlling when to assign actions to users. A filter can comprise multiple conditions.

    1. Go to back to Web Console again
    • Select the Configuration Set
    • Select Assignments
    • Select Filters
    image-64.png.6778e7ceea1d11221b912b42aed9ed24.png
    • Click Create filter
    image-65.png.c928e0bad246ac186fb8ba03ef4b40d2.png
    • Under Basic Information
    • Add a Filter name
    • Type in a Description
    image-66.png.0f86ccf9efefffd30bdeb7e86d3c239c.png
    • Select Enable this filter? – Yes, click Next.
    • Click on Add Condition
    • Select an Default condition (Always True) or click on Create new
    image-67.png.49f36de3d2523c60a97febb6565d44a5.png
    • If you have chosen Create New
    • Add a Condition name
    image-68.png.80a0f071f0db4a9c212d1c723100fe3f.png

    Some conditions are user based only so select based on your use case.

    1. Select if you would like to Enable this condition? – Yes/No
    1. Dependent on the Condition type you will get additional options
      • Click Done next window to add the condition

    Once we finish with FSLogix policies creation and settings in WEM, the next step is to bind them to the Machine catalog in Citrix Studio as follows:

    1. Login to Citrix DaaS and navigate to Machine Catalog that has to apply the Fslogix policies
    1. Go to Manage Configuration Set – Bind Catalog to WEM (Select a configuration set to which you want to bind this catalog:
    image-69.png.3a7a049be79a277b0361533cc365e761.png
    1. Tag this MC to respective DG for VDI assignment.

    Now as the FSLogix polices are assigned to Machine catalog, any session utilizing these Catalogs will get the same set of policies.

    1. Login to VDI and verify if all Office/Profile container are working as expected.
    image-70.png.5b2f72fa7ca980ef83eaffc61d280ccf.png
    1. Navigate to “C:\Program Files\FSLogix\Apps\frxtray.exe” to verify the VHD status.
    image-71.png.932831f51af3b1bcafb89f34b86f6676.png
    1. Open regedit -Navigate to profiles folder, all OFC keys are applied, similarly for PFC.
    image-72.png.482e2b64b30476d1d4151813ab4ce6da.pngimage-73.png.533bd412b299060be342efde87df639b.png

     

     

    See more posts on Citrix WEM here.

     

    Are you a member of CUGC? Join for free today!


    User Feedback

    Recommended Comments



    Create an account or sign in to comment

    You need to be a member in order to leave a comment

    Create an account

    Sign up for a new account in our community. It's easy!

    Register a new account

    Sign in

    Already have an account? Sign in here.

    Sign In Now

×
×
  • Create New...