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

Modifying Recipient Policies in Exchange 2003

This is just a handy one for people to keep hold of, I know there has been many times when it is just so much easier to setup an organisations email in one policy and then let the server do the rest for you...

So here are your most common:

%s : Surname (last name)
%g : Given name (first name)
%i : Middle initial
%d : Display name
%m : Exchange 2003 alias

All that needs to be done is edit the recipient policy and click add SMTP, then use any of the above given examples to constuct a default email address.

I.E

%g.%s@domain.com - kris.haynes@domain.com

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