Forum Discussion
Domain Join Error while deploying HostPool
myusrn Ah, sorry for the confusion.. That screen shot is for creating a host pool (from the marketplace) for the fall release and the pool will not appear under Windows Virtual Desktops, which is only for the spring update and future releases. Personally, I would not deploy any fall release components and focus on the spring update release; it will go GA sometime in June so you can use it for production use hopefully very soon. I think there is some community scripts out there to migrate from FR19 to SU20, but I would just build out SU20 from scratch if you only have a single host pool at this time.
Of the videos, #1,2,7,14 would not be that relevant since they only apply to fall release, all others certainly are valuable. If you want, start with #20 to show you the new release and then go back through the others.
As for Win7, you call select it from all images and disk in the gallery since it's not part of the drop down list. See the screen shot below...
-Jeff
Jeff_Bryant thanks for the clarifications and additional details that helps.
I will watch the suggested videos and attempt another wvd host pool setup but this time from the context of the services | Windows Virtual Desktop (preview) | host pool | add UI wizard as this appears to be process that creates a spring 2020 preview deployment versus the <resource group> | add | Windows Virtual Desktop - Provision a host pool UI wizard that it seems creates a fall 2019 deployment.
It appears that using the noted UI wizard to create fall 2019 wvd host pool deployments provides the option to specify a user principal or service principal [ / spn ] for identity with TenantCreate permissions versus some other method for creating one of these deployments being implied in prior exchanges of this thread, perhaps powershell cmdlets approach, that only provides option to specific a service principal for identity with TenantCreate permissions.
q1. I'm noticing that the spring 2020 deployment wizard, i.e. services | Windows Virtual Desktop (preview) | host pool | add UI wizard doesn't have the fall 2019 deployment wizard's "Windows Virtual Desktop Information" tab that asked for default wvd tenant group and tenant name and rds owner upn [ user principal or service principal ] that has "Windows Virtual Desktop" 1st party app TenantCreate role permissions assigned. Is collection of that information gone because its no longer used in spring 2020 deployment or is it gone because now it gets automatically provisioned for you using some automatically create user or service principal identity?
q2. I'm noticing that the spring 2020 deployment wizard, i.e. services | Windows Virtual Desktop (preview) | host pool | add UI wizard you can specify a Network Security Group [ nsg ] of None | Basic | Advanced. The informational bubble suggests one should use None and assign a nsg to the subnet versus managing things using nsg defined in wizard that gets applied to each vm instances network interface. Is that a correct interpretation of the guidance on that aspect of the wvd host pool networking setup?
q3. When creating multiple spring 2002 preview wvd host pool setups do they have to be isolated in different virtual networks or different subnets of the same parent virtual network or is it fine to have multiple host pools sharing the same virtual network and subnet address space?
q4. My attempt to use spring 2020 wvd host ppol template to create a windows 7 enterprise based pool produced this `Cannot process argument transformation on parameter 'rdshIs1809OrLater'` error which this https://techcommunity.microsoft.com/t5/windows-virtual-desktop/unable-to-deploy-window-host-for-azure-wvd/m-p/1414609#M4175 search hit said is an issue with deployment of windows 7 discussed in this https://docs.microsoft.com/en-us/azure/virtual-desktop/virtual-desktop-fall-2019/deploy-windows-7-virtual-machine article. Are we awaiting a spring 2020 wvd host pool deployment template update to enable using windows 7 enterprise images in addition to windows 10 ones?