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

SMTP: message submitted to categorizer

Messages just appear to be falling into the realms of Cyber space with this error, when running the tracking console in ESM you simply see the message:
SMTP: message submitted to categorizer

To Resolve:

I've found this to be two seperate issues, most commonly issue one will work.

Resolution 1
It is Anti Spam that is causing the issue - submitted to categoriser is not a standard entry in exchange, meaning its been sent out of exchange to be sorted for spam. I can't stress enough that checking your quarantine or your instant delete settings will solve this issue.

Resolution 2
It's an issue with the listing in exchange for the GC, follow the below steps to resolve.

Step 1.
Open ESM, expand "Servers", right click on the server and select "Properties", click "Directory Access", select "Global Catalog Servers" from the dropdown and uncheck "Automatically discover servers" (Bypass the warning) and add the GC (Servername in SBS environments) manually.

Step 2.
Then Restart exchange services to find that all mail begins to deliver to store as per normal.

Comments

  1. Thanks for the post. I had an issue like this and indeed the email was being put in the quarentine because it had profanity in it. Made a quick adjustment to the content filter and bobs your uncle

    ReplyDelete

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