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

CRM 4: Workflows not running at all

I've only seen this once and I think it was due to bad installation, since we had to change hostnames and port numbers AFTER the install, so it may not happen to many people but if it does... hopefully this will save you some time :)

*You want to go into your SQL Server Management studio and then go to, your CRM_CONFIG Database.

*Expand Tables and look for the record "Deployment Properties"

*Right click and select "Open Table"

*Navigate down to "AsyncSdkRootDomain" and then accross to "NVarCharColumn" and fill in the correct hostname and port number (Usually something like 'CRM:80')

*Do the same for "ADSdkRootDomain" and "ADWebApplicationRootDomain"

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