As you have probably already heard or read is that Windows Virtual Desktop (WVD) is now available in Public Preview. Windows Virtual Desktop is a desktop and application virtualization service running in Microsoft Azure. The backend is completely managed by Microsoft itself. You can create host pools to publish full desktops or to publish your LOB applications. A big advantage is that Windows 10 multi user edition is available with WVD. As a result, it is no longer necessary to give each user their own VDI in case your LOB application only runs on a Windows 10 OS and not on a Windows Server OS.
In this blog I want to show you step-by-step how I configured Windows Virtual Desktop in my test environment. Remember that Windows Virtual Desktop is still in Public Preview by the time I wrote this blog. Some steps can only be performed using PowerShell commands at this moment. Once Windows Virtual Desktop is out of Preview, I expect that there will be a nice WVD console available in the Microsoft Azure Portal.
It is possible to upload an own customized image with all your LOB applications and tools like FSLogix for your host pools, but I skip this step for this blog and will use a standard Gallery Image with Microsoft Office 365 ProPlus installed on it to show you how easy and quick you can enroll your own WVD environment.
Before you can start with the deployment of Windows Virtual Desktop, make sure you have the following;
In my test environment I have an on-premises domain controller with ADSync configured to my Micosoft Azure tenant. On-premises I have created an user account which I will use to join machines to the domain (email@example.com). In my Microsoft Azure tenant I have assigned the Global Administrator role to this user and made him Owner of my Azure subscription.
I also have installed a new clean Windows 10 machine without any app installed on it. I will use this machine to test the configuration results at the end of this blog.
In this blog
In this blog I will cover the following steps;
The very first step is to allow the Windows Virtual Desktop services to access your Azure tenant. For this step we need the Azure Tenant ID. For the next steps login to the Microsoft Azure Portal.
Browse to Azure Active Directory > Properties and copy the Directory ID
Open a new browser tab and browse to the Windows Virtual Desktop Consent Page.
Make sure you select Server App as Consent Option. Past your Azure Tenant ID next to AAD Tenant GUID or Name and hit the Submit button.
Sign in with a Microsoft Azure Global Administrator account. As mentioned before I have created a separate admin account to setup Windows Virtual Desktop. Later in the process, this account is also needed to create the Windows Virtual Desktop tenant, hostpool and to assign applications to groups via PowerShell.
We need to repeat this step one more time. So open a new browser tab and navigate to the Windows Virtual Desktop Consent Page.
This time, make sure you select Client App as Consent Option. Past your Azure Tenant ID next to AAD Tenant GUID or Name and hit the Submit button.
Login again with the same Global Administrator account.
Close the browser tab.
During the first step, two new Enterprise Applications are created in your Microsoft Azure tenant. We need to grant the Azure AD account extra permissions to one of these applications before we can continue with the next step.
Within the Microsoft Azure portal, navigate to: Azure Active Directory > Enterprise Applications and open the Windows Virtual Desktop application.
Open the Users and groups page and click the + Add user button
Search for the user account (in my case the firstname.lastname@example.org account again). Click Select and Assign. As you can see the TenantCreator role is automatically assigned.
Now we can create a Windows Virtual Desktop tenant. In this tenant we are going to create Hostpools in later steps. For the following steps we need the Azure Tenant ID and the Azure Subscription ID. I have copied these ID’s to a Notepad for later use. To get your Azure and Subscription ID’s take the following steps;
Within the Microsoft Azure tenant, navigate to; Azure Active Directory > Properties and copy the Directory ID (Azure tenant ID).
Within the Microsoft Azure tenant, navigate to; Subscriptions and copy the Subscription ID
Start the Windows PowerShell ISE application with Administrator rights and run the following command;
Install-Module -Name Microsoft.RDInfra.RDPowerShell
The NuGet provider is required to continue, if not already installed on the machine you got prompted to do so, if this is the case, click Yes to install.
Click Yes to All
Run the following command;
Import-Module -Name Microsoft.RDInfra.RDPowerShell
Select the Microsoft.RDInfra.RDPowerShell module. Find the Add-RdsAccount commando and fill in the following information;
DeploymentUrl : https://rdbroker.wvd.microsoft.com
You can also run the following PowerShell command directly;
Add-RdsAccount -DeploymentUrl https://rdbroker.wvd.microsoft.com
Login with the account with the TenantCreator role (in my case the email@example.com account).
Your now logged in with the account and ready to create the Windows Virtual Desktop tenant.
To create the RDS tenant, go to the New-RdsTenant command and fill in the AadTenantId (Azure Tenant ID) and the AzureSubscriptionId (Your Azure Subscription ID). Give the RDS Tenant a name. In my case I will call it RobinHoboCom. NOTE: This name will be visible for end users and is also needed when creating Host pools and Application groups.
You can also run the following command directly;
New-RdsTenant -Name <NEW RDS TENANT NAME> -AadTenantId <Your Azure Tenant ID> -AzureSubscriptionId <Your Azure Subscription ID>
The Windows Virtual Desktop Tenant is now created.
During this step I will show you how to create a Windows Virtual Desktop Host Pool to publish a Full Desktop.
For the next steps we need to go back to the Microsoft Azure Portal.
Click + Create a resource button and search for Windows Virtual Desktop – Provision a host pool. Click on it to open.
Fill in the following information;
Hostpool name : In my case it will be Desktop (this will also be the name of the published desktop for the end user!)
Desktop type : Pooled or Personal (In my case it will be Pooled (random host from the pool)
Default desktop users : Users that must have access to this desktop. NOTE: Once a user is assigned to the desktop from a host pool, no separate applications from the same host pool can be assigned to that user!
Subscription : Your Azure subscription
Resource group : I will create a new Resource group with the name “WVD”
Location : Your location NOTE: your network resources must be in the same region
Select the Usage Profile type, the total number of users and the Virtual machine size. For this demo I will select Medium user Profile and 5 users in total.
For the Virtual machine name prefix I fill in DSK.
Configure the following;
Image source : In this case I will go for a Gallery image. You can also use your own image with the LOB apps you need
Image OS version : For this demo I select Windows 10 Enterprise multi-session with Microsoft Office 365 ProPlus
Disk Type : select the disk type you want for your hosts
AD domain join UPN : Fill in the account you can use for the Active Directory Domain Join. NOTE: Use the UPN of the local domain if that domain is different that your public domain
Admin Password : Fill in the password of the user
Specify domain or OU : If needed you can do it here
Virtual network : Select the correct VNET
Subnets : Select the correct Subnets NOTE: Remember the Domain Controllers needs to be accessible from this subnet!
Configure the following;
Windows Virtual Desktop tenant group name : Default Tenant Group (leave as is)
Windows Virtual Desktop tenant name : The name of the tenant we have created in step 3 of this blog, in my case RobinHoboCom
Windows Virtual Desktop tenant RDS Owner : UPN or Service principal (in my case UPN)
UPN : Enter the UPN of the user account you created the tenant with
Password : Enter the password of the account
Select I give Microsoft permissions to use and share my contact information so that Microsoft or the Provider can contact me regarding this product and related products and click Create
After a few minutes (mostly between 7 and 20 minutes) the deployment is finished and the host pool is up and running.
If an user is assigned to the default desktop group of this host pool, he/she now have the possibility to logon to this full published desktop (I will show you this in the final step of this blog).
If you want to add a user to the default desktop group, you can do this by running the following PowerShell script;
Add-RdsAppGroupUser -TenantName <Tenant Name> -HostPoolName <Host Pool Name> -AppGroupName “Desktop Application Group” -UserPrincipalName <firstname.lastname@example.org>
The steps for creating a Host pool to publish applications is exactly the same as for a host pool for only a desktop. So I’m not going to add the same screenshots again. The only different settings with the Full Desktop host pool are the following;
Hostpool name : Apps
Default desktop users : Do not enter users you want to assign applications from this host pool to.
Virtual machine name prefix : APPS
For the rest, same Windows Virtual Desktop tenant name and same image with Office 365 ProPlus installed on it.
Now that the Host pool for applications is up and running we can start creating an Application Group for it and add applications to it.
At this moment (during writing this blog WVD is still in preview) this can only be done via PowerShell commands. Therefore we need to go back to PowerShell ISE.
Assuming you still logged in (otherwise import the RDInfra module first and run the Add-RdsAccount command as described in step 3 of this blog), search for the New-RdsAppGroup command and fill in the following;
HostPoolName : The name of the hostpool created in step 5. In my case Apps
Name : A name for this application group. In this case I will name it OfficeApps
TenantName : The name of your tenant created in step 3. In my case this is RobinHoboCom
ResrouceType : RemoteApp
You can also run the following command (with correct information) directly;
New-RdsAppGroup -HostPoolName <host pool name> -Name <name for the new app group> -TenantName <name of your WVD tenant> -ResourceType "RemoteApp"
The output of the command should be like in the screenshot above.
To get a list of all applications available within the disk image of the host pool, search for the Get-RdsStartMenuApp command and fill in the following information;
AppGroupName : The name of the group just created. In my case OfficeApps
HostPoolName : The name of your Host pool. In my case Apps
TenantName : The name of your tenant created in step 3 of this blog. In my case RobinHoboCom
Alternatively you can run the following command directly (with the correct information);
Get-RdsStartMenuApp -AppGroupName <application group name> -HostPoolName <your hostpool name> -TenantName <your WVD tenant name>
This command gives the output as you can see above. For adding applications to the Application Group we need the application AppAlias and FriendlyName if you want to publish all the Microsoft Office 365 the following list will help you to quickly publish them all;
AppAlias : access
FriendlyName : Access
AppAlias : excel
FriendlyName : Excel
Microsoft OneNote 2016
AppAlias : onenote2016
FriendlyName : OneNote 2016
AppAlias : outlook
FriendlyName : Outlook
AppAlias : powerpoint
FriendlyName : PowerPoint
AppAlias : project
FriendlyName : Project
AppAlias : publisher
FriendlyName : Publisher
AppAlias : visio
FriendlyName : Visio
AppAlias : word
FriendlyName : Word
To add a application to the application group, search for the New-RdsRemoteApp command and fill in the following information on the RA2 tab;
AppGroupName : The just created application group, in my case OfficeApps
HostPoolName: The name of the host pool. In my case Apps
Name : The application FriendlyName
TenantName : Your WVD Tenant name. In my case RobinHoboCom
AppAlias : The application AppAlias
Click Run and repeat this for every app you would like to add to this Application Group.
You can also run the following PowerShell command directly with the correct information filled in;
New-RdsRemoteApp -AppGroupName <name of the application group> -HostPoolName <the host pool name> -Name <friendly name of app> -TenantName <your WVD tenant name> -AppAlias <application AppAlias>
In case of adding Microsoft Excel the output looks like this.
The final step is to assign users to this group. Search for the Add-RdsAppGroupUser commando and fill in the following information;
AppGroupName : Name of the application group. In this case OfficeApps
HostPoolName : Name of the host pool. In my case Apps
TenantName : Your WVD tenant name. In my case RobinHoboCom
UserPrincipalName : The UPN of the user you want to add
Click Run or run the following command directly with the correct information;
Add-RdsAppGroupUser -AppGroupName <name of the application goup> -HostPoolName <name of the host pool> -TenantName <your WVD tenant name> -UserPrincipalName <email@example.com>
It’s now time to install the Remote Desktop Client app and test the results. Alternatively you can also use the Remote Desktop web portal.
Remote Desktop Client : http://aka.ms/wvd/clients/windows
Remote Desktop Web client : https://rdweb.wvd.microsoft.com/webclient/index.html
In the following steps I will install the Remote Desktop Client app and test if everything works as it should.
Start the installation and click Next
Select I accept the terms in the License Agreement (if you do) and click Install
Select Launch Remote Desktop when setup exits and click Finish
Login with your (test) account.
As you can see all the applications and the Desktop are visible. I will start the Desktop first.
As you can see, I can successfully login to the desktop. I’m running the Windows 10 Enterprise for Virtual Desktops edition.
Also Microsoft Word is starting up successfully.
The Icon on the taskbar is the only visible different between the local installed applications.
Published Applications and Desktops can also be integrated in the Windows 10 Startmenu.
The cookie settings on this website are set to "allow cookies" to give you the best browsing experience possible. If you continue to use this website without changing your cookie settings or you click "Accept" below then you are consenting to this.