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

ActiveSync error: 85010004 / 80072f12

Synchronising WM5/ WM6 to a SP1 Server 2003 running Exchange server 2003 SP2 you receive one of the above error messages or one of the following:

"Your Microsoft Exchange server does not have permission to synchronise with your current settings. Contact you exchange administrator "

You are most likely to see this message if the following Conditions are true:
* The Exchange virtual directory on an Exchange back-end server is configured to require SSL.
* Forms-based authentication is enabled.

The following Article helped me resolve this issue, simply re-create the Exchange virtual container without SSL limited to only access from the system itself and then one short registry change later you will find it works.

See link: http://support.microsoft.com/kb/817379

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