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

Cannot access Windows 7 Shares from a Windows XP Machine

Scenario:
Windows 7 Machines x 4 (1 x Acting as a server)
Windows XP Machines x 3
10/100/1000Mbps Network.

So I replaced a Windows XP server with a Windows 7 one and there was me thinking this was going to be easy...

From the XP machines I could ping the 'server' but couldn't get onto it, both by UNC or IP paths. I believe the error was "The specified server could not perform this action" or something to that affect.

I did recall having an issue similar tp this with Windows7 in the past and turns out the resolution is the same. You have to disable SMB version 2 so 7 support back compatibility with XP Clients. (You also sometimes get the problem with Windows SBS 2008 and XP machines.)

In regards to how SMB is designed to work see below:
  • When a Windows Server 2008/Vista "client" connects to a Windows Server 2008/Vista "server", SMB 2.0 is used.
  • When a Windows Server 2008/Vista "client" connects to a Windows 2000/XP/2003 "server", SMB 1.0 is used.
  • When a Windows 2000/XP/2003 "client" connects to a Windows Server 2008/Vista "server", SMB 1.0 is used.
  • When a Windows 2000/XP/2003 "client" connects to a Windows 2000/XP/2003 "server", SMB 1.0 is used.

Resolution
To try disabling SMB2 (which is perfectly safe) enter regedit and navigate to the following key:

HKLM\System\CurrentControlSet\Services\LanmanServer\Parameters

Add a new REG_DWORD key with the name of "Smb2" (without quotation mark)
Value name: Smb2
Value type: REG_DWORD
0 = disabled
1 = enabled

A REBOOT IS REQUIRED FOR THIS TO WORK....


Did I solve your problem? Buy me a virtual beer by clicking on a Google ad :). Thanks!
Love to know how many other people this helps...

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