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

Visual Basic Dialogue when opening new email in Word 2003

There are only two possible solutions to this from what I understand and then one workaround,

Resolution one:
In Outlook, Go to Tools > Macro's> Security and lower the security then restart outlook.


Resolution two:
Close Outlook, Go to Word > Tools > Macro's > Security > Then enable the checkbox that says Trust VBA project.

If neither of these work I have found a workaround of simply stopping Outlook from using word as the default editor, to do this go to Outlook, Tools > Options > Mail formatting and uncheck the box.

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