There are many tutorials already on WVD, but none that satisfied my needs for a full configuration with custom image. So why not create one myself…. Obviously there are backend services like Brokers, Web Portal and other stuff, but this is the logical build-up of items we have to keep in mind when deploying. Under that default group you create a tenant name.

Permissions for the RDS farm are set on tenant name level. You can create multiple tenants if needed for permission reasons. Each Tenant then has one or more Hostpools. They are regular clients and can have group policy applied to them.

That agent communicates to the WVD managed services in Azure and listen for any request. Secondly, we will also need an Active Directory account that can join our WVD machines to the domain. The image will be the master for the WVD deployed machines and will have all the settings and applications that we need and that are specific to the enterprise.

It is possible to create multiple images, and then multiple Host pools to publish these different images so each application has its own runtime and environment.

Create a Generation 1 VM, with a managed disk. After deployment, log-in to the VM and deploy your applications. If you only have web-applications, there is no need to create short-cuts in the start menu, as we can manually start an installed browser with the destination URL.

For the other applications, make sure to either add them to the start menu or to keep track of the Executable path as we will need it later-on if we publish only the application instead of the full desktop. For profiles, you are allowed to use the FXLogix application as part of the service. The installation is pretty simple and only requires a fileshare to store the VHD files on. For this, go to the VM and click the Disks option. Create a HDD based snapshot. As the deployment of the image can still be on Premium SSD, the snapshot is only used as a reference image.

Now that our image is ready, we can make a second snapshot of the drive and then copy that snapshot to a blob storage account. If you already have a storage account, make sure to set the parameters as we will need them for copying the managed disk to the blob container. For this, browse to rdweb. Now that the application is authorized, we need to add a user who will be the administrator for the WVD tenant.

Obviously this could be a group, but could also be a single user. There select Add user, type the username and select TenantCreator as the role. The next part is based on PowerShell. In there we will create a Tenant and a service principle we will grant access to this new tenant which we will need later to automate the creation of the WVD images and attach them to our deployed system. For this, go to the marketplace in the Azure portal and type Windows Virtual Desktop.

Type the name for the resource group to be used, the region and the hostpool name. Here you can also select the Desktop type. If you want multiple users to share the same VM at the same timeselect Pooled. Next, select the VM size to use, and how many. Also set a prefix for the VM names. On the next page, you can provide the template in the form of the URL to the blob exported earlier. And then select the disk-type.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. In this blog I want to show you step-by-step how I configured Windows Virtual Desktop in my test environment.

How to remove a HostPool from the Windows Virtual Desktop on Azure

Some steps can only be performed using PowerShell commands at this moment. 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 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. On-premises I have created an user account which I will use to join machines to the domain wvd robinhobo. 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. 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. Make sure you select Server App as Consent Option. Sign in with a Microsoft Azure Global Administrator account.

Windows Virtual Desktop how-to - Step 2: Deploy

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. This time, make sure you select Client App as Consent Option.

During the first step, two new Enterprise Applications are created in your Microsoft Azure tenant.

Tutorial: Create a host pool by using the Azure Marketplace

We need to grant the Azure AD account extra permissions to one of these applications before we can continue with the next step. Search for the user account in my case the wvd robinhobo. 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. 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.

Select the Microsoft. RDPowerShell module. Find the Add-RdsAccount commando and fill in the following information.In this tutorial, you'll learn how to create a host pool within a Windows Virtual Desktop tenant by using a Microsoft Azure Marketplace offering.

Host pools are a collection of one or more identical virtual machines within Windows Virtual Desktop tenant environments. Each host pool can contain an app group that users can interact with as they would on a physical desktop.

After that, follow the instructions in the next section to enter the information for the appropriate tabs. For Resource groupselect Create new and provide a name for the new resource group. Select Desktop type. If you select Personaleach user that connects to this host pool is permanently assigned to a virtual machine.

Enter users who can sign in to the Windows Virtual Desktop clients and access a desktop. Use a comma-separated list. For example, if you want to assign user1 contoso. For Service metadata locationselect the same location as the virtual network that has connectivity to the Active Directory server.

If the specific virtual machine size you're looking for doesn't appear in the size selector, that's because we haven't onboarded it to the Azure Marketplace tool yet. To request a size, create a request or upvote an existing request in the Windows Virtual Desktop UserVoice forum. Enter a prefix for the names of the virtual machines. For example, if you enter prefixthe virtual machines will be called prefix-0prefix-1and so on.

For Image sourceselect the source and enter the appropriate information for how to find it and how to store it. Your options differ for Blob storage, Managed image, and Gallery. If you choose not to use managed disks, select the storage account that contains the.

Enter the user principal name and password. This account must be the domain account that will join the virtual machines to the Active Directory domain. This same username and password will be created on the virtual machines as a local account. You can reset these local accounts later. Accounts from external directories associated with your Azure AD tenant can't correctly authenticate during the domain-join process.

Select the Virtual network that has connectivity to the Active Directory server, and then choose a subnet to host the virtual machines. For Windows Virtual Desktop tenant group nameenter the name for the tenant group that contains your tenant.The following script creates the WVD tenant with the relevant parameters:. The script will ask you for your credentials, relevant subscription Id and the name you would like to give to your WVD tenant.

In this section, we will deploy a new host pool and one or more session host VMs in the WVD tenant we just created. Unlike the previous steps, we will use the Azure Portal this time. Hostpool Name — Choose a preferred name for the new hostpool. You can select multiple users separated by comma e.

Omer contoso. Location — Select the preferred location for your hostpool. You can use custom to select the number of VMs. In this example, we choose the Gallery option, which let you select an image from the Azure Gallery. Usually, a Domain Admin account will be used.

Pay attention that a local user account with the same name will be created on each virtual machine. Pay attention that this password will be used by the local user account, and therefore required to have at least 12 characters. If the selected vnet could not contact the domain, the VMs will not be able to join the domain and the whole deployment process will fail. Make sure that the selected vnet is configured with the IPs of the internal DNS servers and that it has connectivity to them.

Review your configuration. Click Create when ready to start the deployment process.

Tutorial: Create a tenant in Windows Virtual Desktop

If you would add more users to your Windows Virtual Desktop deployment, you can use the following PowerShell script. You must log in to post a comment. Skip to content. Omer Eldan Azure April 23, 6 Minutes. An Azure subscription within the Azure tenant. This is required because your Session Host VMs must be join-to-domain.

Pay attention that Azure AD-joined is not supported.If you ever worked with on-premises VDI solutions such as Microsoft RDS or Citrix solution, you may already know how much planning, management involve with it. But now with a cloud-based solution, we can create a robust, scalable VDI solution with few clicks.

As same as any other VDI solution, user experience has a huge impact from "connectivity". Therefore Microsoft says. There are few new terms related to the Windows Virtual Desktop setup, let's see what are they.

It is the primary interface for managing Windows Virtual Desktop environment. Each tenant must be associate with Azure Active Directory instance. Host pools. Host pool is collection of virtual machines which will serve the users as session hosts.

Host pool operations can categorize in to two types. App Groups. There are two types of app groups. A host pool only can have one desktop app group but it can contain multiple remote app groups. In this demo I am only going to use desktop app group. I will be writing another blog post to cover remote apps. Tenant Groups. Tenant groups help to manage multiple Windows Virtual Desktop tenants at once. This is helpful if you are a service provider. In this blog post, I am going to demonstrate how to set up a desktop application group.

As the first step of the configuration, we need to grant Azure AD permissions for the service.

windows virtual desktop tenant name

In order to do that. In the page, select the Server app for the Consent Option. In the next page, it asks for the permissions.

Click on Accept to grant permissions. As the next step, we need to do the same and grant permission for the Client app. A new Windows Virtual Desktop tenant can only be created by a user who has TenantCreator application role associated. Type Install-Module -Name Microsoft. RDPowerShell and press Enter. Then type Import-Module -Name Microsoft. RDPowerShell and press Enter to import the module.

This asks for sign in and log in with the user who as TenantCreator role assigned. Then search for Windows Virtual Desktop — Provision a host pool and click on it.This is my personal website, which I maintain to support the cloud community.

Windows Virtual Desktop is generally available and under continuous improvement. There was the time before Ignite where no administration GUI was publicly available. This changed with Ignite. The PG of Remote Desktop services releases an in-portal configuration for Windows Virtual Desktop which looks very nice and has a lot of configurable options. Sometimes it helps to have a native GUI to make some configuration. Therefore I build a tool to do this and last night I finished the project in the current version and provide it as a community tool for WVD.

Download WVDAdmin. Logoff or send messages to multiple sessions. Important for prior 1. I recommend to use the new version and to remove the logs from older session hosts or to re-deploy these hosts. I found these logs while checking what other services are running on an Azure VM. From version 1. You can now rollout your session hosts with ephemeral disks. Ephemeral disks are running on the Azure hypervisor and not stored in the fabric. This has some advantages:.

To work with the GUI you need a service principal function account with the permission to administrate your WVD tenant or tenants. I decide to use a service principal at this time to avoid confusion if my Azure Ad user is only a guest account in the WVD tenant I have to administrate.

To image template VMs and to rollout new session hosts the service principal needs permission to the resource groups containing your session hosts or are the target for these. Open the Azure portal and go to the resource groups. Click the principal and save the settings. The service principal must have permissions to your virtual network vnet to assign new VMs to the right subnet.

To add new session hosts unattended we need two more things:. Please note the OU canonical name. Create a file share for the configuration script which adds new session hosts to the domain and install the WVD agent. Give everyone at least read permissions. Set the NTFS permissions to everyone and read. This is necessary while during the first startup the VM extension tries to execute the script.

In this process, the file share is accessed anonymously. Important: If you are using Windows Server as file share make sure that anonymous file share access is enabled. Create a GPO for the session hosts containing the following configurations:. Please start WVDAdmin.

Before you load WVD and Azure data copy the Azure tenant id, service principal id and service principal key into the welcome tab. The first time you want to rollout new session hosts you have to enter some information from your Active Directory and file share configuration from above:.

Local Admin and local pw. You can simple create an image from a template VM.Tom Hickling. It went into public preview in March ofwith many successful deployments for testing purposes having been completed. However we have seen a large number of failures of the Azure Resource Manager deployment from a set of customers, all for very similar quite simple errors entered into the Azure portal deployment process, things like incorrect accounts, or lack of name resolution.

Step-by-Step Guide to Deploy Windows Virtual Desktop in Azure

Hence this simple guide is designed to save you some time by avoiding common errors in the deployment process. There are a few pieces of information you need and it is possible to get this wrong. Hence this will clearly explain what prerequisites are required to be in place and where to get the relevant information and then where to exactly put these details into the Windows Virtual Desktop HostPool creation process in the Azure portal.

This is to ensure the deployment process will complete successfully. This is not a full deployment guide, there is already existing full deployment instructions available.

This guide will enable to collect all the relevant pieces of prerequisite information and have them all in one place that you can then put back into the Azure portal at deployment time. In this guide you will either create and record or if already existing just record the information needed in the WVD deployment process and keep it in one place in Notepad to use later in the full deployment.

From a high level you will require the following items before you can deploy Windows Virtual Desktop. To do this open the Azure Portal. On the left click on All Services. In the Azure portal go the Virtual Network that your domain controller was deployed onto.

Click on the Subscription you want to deploy your hostpools into. Then in the Overview section copy the Subscription ID. This site uses cookies for analytics, personalized content and ads. By continuing to browse this site, you agree to this use. Learn more. Microsoft Industry Blogs - United Kingdom.

windows virtual desktop tenant name

Apply Filters Loading Clear all filters. Windows Virtual Desktop pre-requisites — everything in the right place to enable you to deploy without errors.

windows virtual desktop tenant name

Use this in conjunction with the existing deployment guide from Microsoft docs. A Windows Virtual Desktop tenant Why do you need all of these? The Virtual Machines all need to be located on a Virtual Network. That vNet needs access to Active Directory, that can either be located in Azure or on-premises as long as there is connectivity.

The high level deployment process for a WVD hostpool and why you need these pre-requisites already in place is to automate all of the following actions:. Click on the copy button at the right of this fieldNow open Notepad and paste this in as Item 1. Notepad should look like this: 1.

Or alternatively deploy it manually on a Virtual Machine. This account password has to conform to Azure password complexity reqirements as well as any local AD requirements.

The Azure requirements means the password need to be a minimum of 12 and maximum of characters.