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 to domain join, even if it links back to the domain - this is where the conflict arrises.    Instead, use your full internal domain UPN.  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

iMac 27" WiFi losing connection intermittently

In the aid that this helps anyone I thought I'd post it up there with my normal helpful stuff :).

This week I decided to finally bite the bullet, you can see through my exhaustive blog that I have found and fixed my fair share of Windows OS problems and it's only fair I give MAC OSX it's shot. So I invested in a brand new 27" iMac, Quad Core 3.4Ghz i7 with a 1TB hard drive I was more than looking forward to working on this bad boy.

I was incredibly disappointed when I took it home though, to find that at least three / four times an hour I was having frequent drops in Wireless Connection. I have a decent wireless router (Yes I'm perhaps 30ft away) but I can sit in my car outside (60ft away) and still get a good signal on my iPhone.

I found a few 'hot fixes' online, something about in Network Preferences, set it to a new name and not Automatic. I gave it a try, no joy.  So amongst my troubleshooting steps I took note of every change and tested and tested and tested until eventually JACKPOT.

The problem I have is that my wireless is running WPA-PSK encryption; although my Windows PC, two iPhones and iPad have NO PROBLEM whatsoever the iMAC does! The second you change it to WEP it works like a gem!

I have to say I am very, very unhappy about having my network open to WEP. So I went into my Access Point and locked my network down to mac address access only, so I have to approve anyone coming onto my wireless. It gave me that extra piece of mind.

To be fair, I'm not entirely against WEP and it will work fine for a lot of people, I just know from my own technical understanding of 'hacking' etc that it is fairly easy to break!

Hopefully this post finds those in need well and let me know if it helps.


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


  1. I got the same problem and it bothered me for more than half year. It started when I changed my wireless router. The new router uses WPA2-PSK encryption. I never thought this may cause problem. How come that iMac is so bad on this?

    My new router can set up a guest wifi. I set up the guest wifi with WEP and the main wifi still the same.

    It works very well now on all my devices.

    Thanks a lot Kris!


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