Search This Blog

Tuesday, January 14, 2020

Windows Virtual Desktop - Part 5

This is part 5 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
  • Part 4 – FSLogix – Part 4

Now it’s time to give it a test spin.

Let’s start out by trying the Windows client, it can be downloaded here:

https://docs.microsoft.com/en-us/azure/virtual-desktop/connect-windows-7-and-10

image_thumb

Let’s download the x64 version, and start the installation.

image

On the welcome page click Next.

image

Accept the license agreement.

image

In this test setup I will install it for all users.

image

Close the installation and start the client.

image

Click Subscribe.

image

Enter credentials.

image

Enter password and click sign in.

image

Now our available desktops or applications are shown, let’s start the MC

image

Enter password for our test user. Seamless SSO will for now require ADFS.

image

And here are our desktop also notice that OneDrive has been setup.

image

2019-11-29 13_16_09-LAB-DC01 on PCP70 - Virtual Machine Connection

Using Winver we can see that this OS is Windows 10 Enterprise for Virtual Desktops.

image

On the fileserver we now got the FSLogix profile disk for our test server.

image

Let’s also try to connect to an on-premise file share, this works as expected.

image

Now let’s try to connect with the webclient

https://rdweb.wvd.microsoft.com/webclient

Since my test device is Hybrid Azure AD joined, it will do SSO on the first page and present the same as the Windows client.

image

image

Allow selected local resources.

image

Now we must enter credentials. Seamless SSO will for now not be available when using the HTML5 client.

image

And now the desktop is shown using the HTML5 webclient.

image

Finally I will use my android phone, first thing is to install the Microsoft Remote Desktop app.

image

Then open the app.

2020-01-14 09_57_29-Connect

The first time you use the app you need to accept license terms.

Capture1 (002)

Use the plus sign and select Remote Resource Feed.

image

Enter the address https://rdweb.wvd.microsoft.com and select Next.

image

Enter credentials.

image

Enter password and select sign in.

image

Click on our available session.

app

In this test Local storage access will be allowed.

2020-01-14 10_32_06-Connect

Android will ask you to allow access.

2020-01-14 10_32_21-Connect

Enter password and select connect.

image

And here are our desktop on the phone.

2020-01-14 10_33_30-Connect

Here we see the same desktop using a big screen and Samsung DEX with mouse and keyboard working connected through a USB dock, this is really nice.

https://www.samsung.com/global/galaxy/apps/samsung-dex/

Capture3 (002)

This will for now complete our Windows Virtual Desktop blog series, but trust me – we will be back later with more on this very useful solution from Microsoft.

Monday, December 9, 2019

Windows Virtual Desktop - Part 4

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)

image

With the following share permissions.

image

Then setting NTFS permissions as shown:

image

image

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.

image

Lets copy the ADMX file (fslogix.admx) to [DC]\sysvol\[domain]\policies\PolicyDefinitions

image

and the ADML file (fslogix.adml) to [DC]\sysvol\[domain]\policies\PolicyDefinitions\en-US

image

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.

image

Name the policy.

image

Edit the policy.

image

Go to Computer Configuration – Policies – Administrative Templates – FSLogix – Profile Containers - Enabled

Enable it as shown.

image

Go to Computer Configuration – Policies – Administrative Templates – FSLogix – Profile Containers – VHD location

Enable it and set the location to the share we created earlier.

image

Both settings enabled.

image

On our Windows Virtual desktop host, we need to install the downloaded FSLogix agent.

image

Execute FSLogixAppsSetup.exe and agree to license terms and click Install.

image

If you wish to change the installation folder you do that by clicking Options

image

Click Close .

image

If you check registry HKLM\Software\FSLogix\Profiles you will find the defined in our GPO

image

In the next post we will test our new Windows Virtual Desktop setup.