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.  USER@prefix.domain.co.uk  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 pr

New Tech: Google Latitude

Google latitude the new and very cool feature from Google in association with Google Maps. Simply download the latest version of Google maps and from the right hand menu select Latitude.

You are asked to sign into your google email account; from which point you can add friends as easy as searching for there email addresses. It's that easy to setup!

Once connected to your friends, although not 100% accurate you can see your friends locations...the best i've seen so far using GPS is a distance of 40metres.

No more sneaking off to the pub though after work guys if your wife has a smart phone eh...


Download and More Info here:Google Latitude

Comments

Popular posts from this blog

This product type does not match the list of supported product types

SBS 2008 hangs on Applying Computer Settings

LSASS.EXE - System Error / Rebuilding Active Directory Indices. When booting windows server 2003