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 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 pr

Your client does not support opening this list with Windows Explorer.

I recently came accross a client who recieved this message when they tried to use a sharepoint (V3) list:

"Your client does not support opening this list with Windows Explorer. "

Obviously this isnt a very helpful message but after a short while of searching through events and web pages I found the following Microsoft Article which helped to resolve the issue. It is caused by a long URL or List name exceeding 100 characters.
Microsoft have noted the problem and now released a patch for download so you can clear this problem.

Support Link:


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