New-RdsTenant -Name $tenantName -AadTenantId $AadTenantId -AzureSubscriptionId $subscriptionId
#New Tenant Keep in mind that Access rights need to be set before doing the next step. $subscriptionId = in to Windows Virtual Desktop $AppGroupName = “Desktop Application Group” $TenantGroupName = “Default Tenant Group” #Setup Settings, TenantName of WVD tenant, Hostpool name So to start with windows virtual desktop I created a little Powershell script that does step 1 In this blog post it could be that not all host pools and tenant names are the same as I had a lot of test WVD configs.Īs we all know the Infrastructure that is needed for windows virtual desktop, we also know that a lot can go wrong and then where to look ? Well I thought lets do a Step By Step windows virtual desktop, Well not exactly I’ll believe you can follow the wizard in Azure and Do all the prereq’s by your self. Not a bad thing but testing the windows virtual desktop leaves me multiple tenants and host pools dead. Different places to go, and management is a pain no GUI available from Microsoft there is only PowerShell. and there comes all the different builds and setups. And yes its all Azure but thanks can be build and tested. I see a huge demand on WVD, Customers wants to try this and see the difference between the traditional RDS setup.
Vm_create on ui failed how to#
Windows virtual desktop is GA and already there are tons of blog post on how to install windows virtual desktop, first steps on windows virtual desktop.