Posts

Showing posts from January, 2019

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

Activation error DISM on Windows Server - could not activate

Ever tried to activate an Eval download of Windows Server and got an activation failure? Or got an error 50? The command most commonly referred to online and in Microsoft guides is as below: Firstly, make sure your version is actually genuine and you're licensing the right version too. Run the following command: DISM /online /Get-TargetEditions This will reveal what you can upgrade Eval too, in a majority of cases we'll use Server Standard as an example but this refers to datacenter too. Run the below to license your server: DISM /online /Set-Edition:ServerStandard /ProductKey:XXXXX-XXXXX-XXXXX-XXXXX-XXXXX /AcceptEula If this still doesn't work, something that I spent hours of my life one evening figuring out... is that a command window that isn't elevated will produce an error 50, unknown error and/or a activation couldn't be completed. Yes, its truly that simple! Elevate Command Prompt and try again, 9/10 this will fix the issue for you!