06-15-2020 09:20 AM
06-15-2020 09:20 AM
How do you delete a wvd fall 2019 cmdlet created tenant name and template created hostpool?
After deleting all the resources i could see in azure portal resource group associated with wvd fall 2019 template created hostpool i find that the tenant name and its child hostpool still come up in wvd remote desktop client subscription feed. This suggests to me they are still provisioned but not directly viewable and able to be deleted from azure portal UI.
When i create a wvd spring 2020 hostpool deployment i see that it uses a default application group Workspace instead of a Tenant and child session type hostpools both of which can be viewed and deleted from azure portal UI.
06-16-2020 12:00 PMSolution
@Rob Ob: As documentation indicates Fall release cannot be managed with the new Azure Portal presence as. Use this PowerShell cmdlet to delete your tenant: https://docs.microsoft.com/en-us/powershell/module/windowsvirtualdesktop/remove-rdstenant
Don't forget to sign into your deployment with your admin account first: Add-RdsAccount -DeploymentUrl "https://rdbroker.wvd.microsoft.com"
More info: https://aka.ms/wvdgetstarted > select Fall/Spring release section to land on the proper documentation path.
06-16-2020 12:21 PM - edited 06-16-2020 12:33 PM
@Eva Seydl thanks for the followup on this, seems i have an issue getting rid of sessionhosts not exposed in portal first, e.g.
executing remove-rdstenant complains about existing hostpools
Remove-RdsTenant -Name "My Wvd Tenant" Remove-RdsTenant : TenantName: 'My Wvd Tenant' cannot be removed because there are HostPools associated with it.
executing remove-rdshostpool complains about existing sessionhosts
Remove-RdsHostPool -TenantName "My Wvd Tenant" -Name "wvd-hostpool" Remove-RdsHostPool : The HostPoolName wvd-hostpool could not be deleted because it still has SessionHosts associated with it. Please remove all SessionHosts from the SessionHostPool and retry the operation.
where i was able to remove existing sessionhosts by executing
Remove-RdsSessionHost -TenantName "My Wvd Tenant" -HostPoolName "wvd-hostpool" -Name wvd-vm-0.mydomain.onmicrosoft.com
after that executing remove-rdshostpool complained about existing applicationgroups
Remove-RdsHostPool -TenantName "My Wvd Tenant" -Name "wvd-hostpool" Remove-RdsHostPool : The HostPoolName wvd-hostpool could not be deleted because it still has ApplicationGroups associated with it. Please remove all ApplicationGroups from the SessionHostPool and retry the operation.
which i was able to remove using . . .
Remove-RdsAppGroup -TenantName "My Wvd Tenant" -HostPoolName "wvd-hostpool" -Name "Desktop Application Group"
After that I was able to walk back through Remove-RdsHostPool and then Remove-RdsTenant cmdlets to clear everything out from fall 2019 template deployed setups.
With the spring 2020 wvd template deployed setups is everything that gets provisioned also removable from the portal vs having to walk things back using a bunch of powershell cmdlets?