Posts

Showing posts from July, 2012

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

iPhone / MAC can't connect to Exchange Server from inside the network.

I believe this is a relatively simple one in the case I've witnessed anyway.  The scenario is that you turn on WiFi, connect and then lose access to the exchange.  Turn off WiFi go back to 3G and voila you're connected again. The reason that the phones and iMail (to name a few) cant connect to the Exchange from inside the network is because you will most likely be using an external IP or URL right?  Thus meaning that everytime you try to access this URL from inside the server bounces packets backwards and forwards around the network not truly knowing what to do with them.  I found that if you create a new DNS zone for (mail.domain.com), create an A record within that zone leaving the host blank (to use parent domain). Then point it at your internal exchange.  This time if the users phone requests connection to mail.domain.com they get redirected (internally) to 192.168.x.x/24 Simples.. :) Note - You may not need to make a new zone if your domain is already running as