search

stgeorgi / wvdquickstart

26 stars 31 forks source link

Deployment failed - Automation #18

Open isotonicuk opened 3 years ago

isotonicuk commented 3 years ago

Hi I have tried to create an ARM deployment using Azure Devops setup via www.wvdquickstart.com. I have an AD server already created with domain admin privileges with a domain join account. This is in a separate resource group with a separate vnet.

The deployment I am creating is in a different resource group but in the same region Deployment-Microsoft.Template-20201104193615.zip

I attach the deployment error zip file.

stgeorgi commented 3 years ago

It looks like there is no piering between the two VNETs (the one with dc and the one where new host pools are being deployed), is my observation correct?

isotonicuk commented 3 years ago

It looks like there is no piering between the two VNETs (the one with dc and the one where new host pools are being deployed), is my observation correct?

Ok thanks, how would I check and enable peering?

justin-shiah commented 3 years ago

@isotonicuk If you go to your VNet, under settings there should be a Peerings option. If you click on it, you can see all existing peerings or create a new peering.

isotonicuk commented 3 years ago

Ok great, so effectively this just joins the vnets together as they are currently in different resource groups?

justin-shiah commented 3 years ago

@isotonicuk You're correct in the sense that this joins the VNets together, but the issue isn't that they're in different resource groups. The point of peering the VNets is so that the second VNet can still talk to the domain controller.