Tuesday, 5 May 2020

JoinDomain VMExtensionProvisioningError when deploying WVD (aka Conflict Error)

Deploying WVD Fails with a conflict error and when clicking for more information it presents a conflict and not much else that is useful by way of toubleshooting.

Hopefully this helps someone else as it had me head scratching for a little while..

When creating the Host Pool, make sure that you haven't made the fatal error of using the Azure Active Directory Credential INSTEAD of the Local AD Domain Credential. 

i.e do not use USER@m365xxxxx.onmicrosoft.com to domain join, even if it links back to the domain - this is where the conflict arrises.   

Instead, use your full internal domain UPN. 

Re-deploy your same configuration and you should find it goes through now without any problems.

Additional findings....
Albeit my mistake above was an easy one, it does appear the error is directly linked to the domain join process.

If you go into your resource groups, locate the session host and MSTSC directly to it.  Try the domain join process yourself, you'll probably find the credentials you're using are wrong, or the account doesn't have the right privileges. 

No comments:

Post a Comment

Bulk discount code 2022 - 35% Off First Order Discount Code at bulk.com

Bulk.com / Bulk Ltd - First Order Discount Code!  Get 35% off of your first order at Bulk, home of award-winning Sports Supplements, high ...