{"id":15261,"date":"2019-07-16T08:24:52","date_gmt":"2019-07-16T08:24:52","guid":{"rendered":"https:\/\/www.microsoft.com\/en-gb\/industry\/blog\/?p=15261"},"modified":"2019-07-16T08:24:52","modified_gmt":"2019-07-16T08:24:52","slug":"windows-virtual-desktop-first-thoughts-part-2","status":"publish","type":"post","link":"https:\/\/www.microsoft.com\/en-gb\/industry\/blog\/technetuk\/2019\/07\/16\/windows-virtual-desktop-first-thoughts-part-2\/","title":{"rendered":"Windows Virtual Desktop \u2013 First Thoughts, Part 2"},"content":{"rendered":"
<\/p>\n
Last month, I published the first part of this post. You can read it here<\/a>.<\/p>\n In the first part, I wrote about the initial setup and config experience for creating and accessing Windows Virtual Desktop<\/a> (WVD). Overall, I found the experience to be good, but at times, slightly basic. This is to be expected with a brand new service that is in preview, but for the second part of this post, I wanted to explore the more advanced options of configuration that are currently available.<\/p>\n So in this post, I am going to discuss the following:<\/p>\n Starting with fslogix, I think it\u2019s kinda cool that you are given a free license as part of WVD to use the service. The actual install was quick and easy; just download the client, run it, set up two reg keys, and you’re done. However, I wasn\u2019t overly familiar with fslogix and as such thought it wasn\u2019t working – I have a solid background in desktop virtualisation, so I understand profile redirection explicitly. I found the Microsoft docs for this are light currently, but clicking through to the fslogix docs<\/a> I spotted the issue, the local profile cannot exist first or fslogix will ignore it.<\/p>\n A quick tidy up and my profiles were redirecting, loading quickly and generally behaving as expected. So far so good! I\u2019d like to see how it scales with a ton of users, but my expectation is that we’d see similar performance to Citrix UPM. One thing that is perhaps a bit annoying out of the box is, when you choose to sign out from the web client, it simply disconnects the user from an app group. This can be fixed with some Group Policy, but I would expect sign out to mean sign out.<\/p>\n A little tip, check out the reg key \u201cFlipFlopProfileDirectoryName\u201d for a quick way to make finding your user profiles within your file share a bit easier. There are also more advanced options like \u201cSIDDirNamePattern\u201d, more\u00a0here<\/a>.<\/p><\/blockquote>\n Next up is load balancing the session hosts. This obviously only applies to non-persistent session hosts, as the persistent relationship is 1:1. You also need to understand two concepts:<\/p>\n Both options are simple to setup via PowerShell and behave exactly as outlined. You can find instructions on how to do this here<\/a>.<\/p>\n Third, I created a new host pool. To do this I first needed a custom image, so I deployed a VM to Azure to convert later. I skipped a bit here by using the new Windows 10 image with 365 ProPlus pre-installed for you, which is very handy. However, I then realised this wasn\u2019t the multi-user version and even though all is good with image creation, it fails when trying to register with WVD (30 mins later\u2026). So to save you some time, just use the Windows 10 multi-user image instead! I installed my apps, then I made the following changes:<\/p>\n\n
\n
\n
\n