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

your out of office settings cannot be displayed because the server is unavailable

I'm going to try my best to help anyone out stuck in this situation because it took me ages to sort out! BUT please note that my scenario may not be the best or the easiest or even the most accurate!

So my scenario was I had Server 2003 standard with Exchange 2007 VLK enterprise, all clients with Outlook 2007 couldnt enable OOF (Out Of Office) they had to go into Outlook Web Access to enable it.

After some initial digging I found out that I had to look at the certificate in exchange incase it was invalid as well as check the autodiscover service to make sure it points to the right place.

1. Check your certificate!

2. Check in outlook the autodiscover settings
what URL's are pointing to where by holding control and then right clicking on the outlook icon in the system tray then select test autoconnection. This will show you the URL's it is using.

3. Internal / External URL Check
Check your URL's for Outlook within the Exchange Management Shell
"Get-WebServicesVirtualDirectory | fl InternalURL,ExternalURL" run this command and make sure that the URL's are correct. You should change them if not, then try again.

Does this help anyone...?

Comments

  1. Thank you for this piece of information. Usually get a server is unavailable. I will try this solution.

    ReplyDelete
  2. No Joy. Cert is good. autodiscover looks good. Testing the connection succeeds. URLs are good. Browsing to the URL yields a bunch of XML.

    But I can't do OOF and I can't download the offline address book. I haven't found any other users with this issue, and I am one of the Exchange admins.

    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