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

Logon Via Dialup - Windows Vista

When logging on to a corporate network from a remote location, you're usually required to authenticate against the Windows domain.

For years that's been accomplished by using 2000 or XP's "Logon via Dialup connection" checkbox at startup.

But it's not there in Vista, so what do you do?

Don't worry as the process is similar; it's just not obvious. The setting is located in the Control Panel's "Network and Sharing Center". The secret is to select the "Allow other people to use this connection" option, allowing Windows to display the connection prior to a user login.

Next time you logoff you will see a blue icon to the lower right of the screen, select this option to "dial up at logon"

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