Forum Discussion
azure windows virtual desktop: there are currently no resources available to connect to
- Apr 26, 2019
BSuleyman Ali Below are the commands I used to clean up a host pool. You may need to remove user assignments before the resource can be removed.
Get-RdsAppGroup -TenantName $tenant -HostPoolName $hostPoolNameGet-RdsAppGroupUser -TenantName $tenant -HostPoolName $hostPoolName -AppGroupName "Remote App Group"Get-RdsAppGroup -TenantName $tenant -HostPoolName $hostPoolName | Remove-RdsAppGroupGet-RdsHostPool -TenantName $tenantGet-RdsSessionHost -TenantName $tenant -HostPoolName $hostPoolNameGet-RdsSessionHost -TenantName $tenant -HostPoolName $hostPoolName | Remove-RdsSessionHostGet-RdsHostPool -TenantName $tenant | Remove-RdsHostPool
Suleyman AliI created a playlist with of walk-throughs on setting up and managing WVD. Link below. Be sure that the Virtual Network you are connecting to exists and has access to a domain controller. If you are recreating host pools, you should also remove the pool in the WVD environment with PowerShell. Removing the Resource Group won't remove the WVD host pool and I haven't seen a spot to manage that in the portal. It could be that you are connecting to a host pool that had the VM's removed.
https://www.youtube.com/playlist?list=PLnWpsLZNgHzXMtKjaQJf4Rn64W86nUDv1
Our Azure Domain is too long to use in Azure Domain Services wondering if i use a custom domain set it as the primary and make it the domain name for azure domain services would that work for WVD?TravisRoberts
- TravisRobertsJun 26, 2019Iron Contributor
tommy_barnes Any valid domain should work. It can be either Active Directory Directory Services or Azure Directory Services. The VM's will join the domain and users will authenticate to it just as if it was on the local domain.
- tommy_barnesJun 27, 2019Brass ContributorThanks Travis it is now joining the domain but now getting that provisioning resources error which I believe folks are fixing it about creating a service principal?