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

A Potential Security Concern Has Been Identified : Access Runtime 2007

We found that in Access 2007 to use a database without the trusted location error bugging the user everytime they open it wasn't quite as simple as you might initially suspect using Access 2007 Pro.

To trust a location you have to specify the path in the registry as Trusted Sources / Access Options isn't to be found in the runtime version of Access.

Navigate to the following Key:


Create a string for:
'Path': Specify the full path to the database (excluding *.mdb)
'Description' : The description isnt relevant but from testing it appears it is required as an entry.

Additionally create a DWORD value for
'AllowSubfolders' : 1 to trust any subfolders of Path (Not a requirement)

This should eradicate the error from presenting itself, thereby trusting the database.

Did I solve your problem? Buy me a virtual beer by clicking on a Google ad :). Thanks!


  1. Chris
    Thanks for the info above, i am just over the hill in Buxton!
    Came across this problem when trying to deploy a app that automates Access using 2007 runtime components only, all works ok except the nagging screen, tried the reg mods and various suggested permutations but nothing seems to have any affect? even tried the 2010 runtime components and adding the database as a trusted file but nothing seems to have any affect, am logged on as admin, any suggestions?
    ps location i am trying to trust is a network location!

  2. If you hold shift when entering the database, then go to Access options and disable Macro security..?


Post a Comment

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