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

Microsoft CRM V.4 "Unable to Load Client Print Control"

When clicking the Print icon to print a CRM v4.0 report (in a SQL Server 2005 database) you receive the message 'Unable to Load Client Print Control' and the report does not print.

It is caused by Windows Security Update KB956391. Once installed you will see the issue above with Windows Server 2003, Windows XP, and possibly others. Windows Vista machines do not appear to be affected.

The solution to this issue is as follows:

Install the fixes below on the necessary servers and reboot each server.

CRM Server:

Microsoft Report Viewer Redistributable 2005 Service Pack 1

SQL Server:

Security Update for SQL Server 2005 Service Pack 2 (KB954606)


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