This is part 4 of our posts regarding Windows Virtual Desktop, until now we have covered:
- Part 1 – Created a Windows Virtual Desktop tenant – Part 1
- Part 2 – Created a service principal and some customization of our on-premises AD – Part 2
- Part 3 – Provisioning a host pool – Part 3
In this post we will take a closer look at incorporating FSLogix to the solution.
In this test we will use a file server joined to our on-premises domain running in Azure.
On this file server we first create a share (here called FSLogix)
With the following share permissions.
Then setting NTFS permissions as shown:
Now let’s download the FSLogix agent here https://aka.ms/fslogix_download
Inside the downloaded file we can find the admx and adml files needed for our central store.
Lets copy the ADMX file (fslogix.admx) to [DC]sysvol[domain]policiesPolicyDefinitions
and the ADML file (fslogix.adml) to [DC]sysvol[domain]policiesPolicyDefinitionsen-US
In next step we create a group policy for the WVD OU in Active Directory, this is the OU where our Windows virtual desktops will end up.
Name the policy.
Edit the policy.
Go to Computer Configuration – Policies – Administrative Templates – FSLogix – Profile Containers – Enabled
Enable it as shown.
Go to Computer Configuration – Policies – Administrative Templates – FSLogix – Profile Containers – VHD location
Enable it and set the location to the share we created earlier.
Both settings enabled.
On our Windows Virtual desktop host, we need to install the downloaded FSLogix agent.
Execute FSLogixAppsSetup.exe and agree to license terms and click Install.
If you wish to change the installation folder you do that by clicking Options
Click Close .
If you check registry HKLMSoftwareFSLogixProfiles you will find the defined in our GPO
In the next post we will test our new Windows Virtual Desktop setup.
