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

ActiveSync only working when Outlook is open

We had a series of issues leading up to this problem and its unknown whether or not we actually caused this however here's how I fixed it in case anybody else see's a similar problem.

The scenario:
Outlook 2010, Exchange 2003(SBS), iPhone 3GS, iPhone 4, WM5's and WM6's

All of the above phones were seeing symptoms, the iPhones batteries were reduced by at least 60% and the windows mobiles didnt seem to be picking up all emails.

Whenever Outlook 2010 was open, emails to the phone was brilliant and worked almost perfectly. Once closed, the doors were shut and no more email!

The Fix
Edit this key, no reboots necessary.

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeIS\VirusScan
Set ProactiveScanning = 1 (proactive scanning occurs when an item is delivered to a folder, but a request has not been made by a client)

Set ReloadNow = 1 (By default this value is set to zero, by setting this value to "1", Exchange will reload the configuration settings from the registry and reload the Vendor's DLL. Once completed this value is reset to "0" by Exchange.)

This sounds like a really unbelievable fix but it genuinely works and I've tested it on other sites where it has worked also.

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


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