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

Windows 7: "An unexpected network error has occured" when accessing Network Drives

a Very Very strange one on Windows 7, after logging onto the domain successfully accessing Mapped drives just gave the error "An unexpected network error has occured" there is nothing logged in Event Viewer or next to no diagnostics to run to figure out this problem.

After a little testing I found that you can access the server manually running its DNS name and then disconnect and re-map the drives you use and this clears the error.

Probably not the best fix - but a fix none the less,

If anyone has any other solutions feel free to post.

Comments

  1. Hey Man,

    We have the same problem here, happens on daily occurance, I havent had time to really investigate. doesnt make much difference mapping drives via Netbios name, hostname, FQDN.

    but very strange,

    Drives are Mapped at logon, :- Successful
    Accessing the Mapped Drive Root :- Successful
    Accessing a Subfolder :- Results in the same Error as you have.

    Also @ anypoint in the day a user will double click on a file to open, they receive this error on 1st time. if they immediatly double click again it opens?

    ReplyDelete
  2. In the Local Group Policy Editor,

    go to- Run --> gpedit.msc --> Local Computer Policy-> Computer Configuration-> Windows Settings-> Security Settings-> Local Policies-> Security Options

    Find the policy:

    Microsoft network client: Digitally sign communications (always)

    If this is enabled, change it to Disabled. Be sure and restart your machine for the change to take effect! Pressing the "Apply".

    After restart the system may be any pop will come just click on yes button

    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