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

C Drive Filling with Exchange .log files

This is one that doesnt explain itself very well, whether it be fault, feature or otherwise you can decide.

The solution is simple: Exchange has a "Self protect" feature by recognising if it has been backed up or not. If it detects that the database isnt properly backed up either using NTBackup the SBS Backup or another body which correctly cleans the database then the exchange will begin logging every email in plain text into a Text document in the C:\Progr~\Exchsrv\MDBDATA directory.

So the solutions are simple if you are using a backup program then make sure it is running ok. if you are using your own custom built backup script like Xcopy or something like, you may need to look at Circular Logging to stop the build up of log files.

The only other reason I have so far found that this can happen however are Database corruption; to check this again is relatively simple if you have used the ESEUtil application before.

Open a command prompt and navigate to C:\Progr~\Exchsrv\Bin\
Then run Check the value "State" which should display Clean, if it instead displays "Dirty" or "Inconsistent" you will need to repair the database using ESEUtil and the transaction logs created so do not delete them.

To repair look at following the below articles:

How to remove Transaction logs

OR

How to Maintain after repair

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