Forum Discussion

Norphus's avatar
Norphus
Copper Contributor
Mar 20, 2020
Solved

Error when connecting to MVD - 0x3000047

I have recently deployed WVD thanks to the current global crisis. It is working well for most of our users, apart from one. When she tries to connect to WVD via the web client, she gets this: ...
  • DavidBelanger's avatar
    DavidBelanger
    Mar 24, 2020

    serge I think you are on the right track. Here's what we see internally:

     

    Client gets an Error during Orchestration. 
    Orchestration failed. Code=0x80075a1e, symbolicCode: E_PROXY_ORCHESTRATION_UNKNOWN_ERROR, message: Failed to add user = ≤USERNAME REMOVED≥ to group = Remote Desktop Users. Reason: Win32.ERROR_NO_SUCH_MEMBER, target: (null):4

BogdanGrozoiu's avatar
BogdanGrozoiu
Copper Contributor
Jun 08, 2020

AlexTBigAl I had something similar when I redeployed the 2004 VMs.

(I'm using the Windows-10-Enterprise-multi-session-with-Office-365-ProPlus-2004 GalleryImageSKU)

 

If you've redeployed them with the same hostname, make sure you de-registered the "old" ones from the host pool.

 

Do you see a recent heartbeat from the 2004 hosts in the hosts pool?

AlexTBigAl's avatar
AlexTBigAl
Copper Contributor
Jun 08, 2020

BogdanGrozoiu 

 

Thanks for your response. These had been deployed with new hostnames and with a new hostpool.

 

I had tried from Gallery as well as custom Shared Image Gallery using the new April 2020 ARM WVD.

 

Using the same process I successfully deployed both Gallery Windows-10-Enterprise-multi-session, Version 1909 + Office-365-ProPlus , as well as a custom image

 

TIA

 

 

  • jjensen1818's avatar
    jjensen1818
    Copper Contributor
    Jun 09, 2020
    Same issue. just created a brand new AADDS. New Hostpool using custom win 10 2004 and office pro plus image. Cannot login.

    Created another hostpool and chose gallery image win 10 1909 with office pro plus. No issues.

    Must be related to win10 2004?
    • jjensen1818's avatar
      jjensen1818
      Copper Contributor
      Jun 09, 2020
      Apparently there is a bug.

      https://techcommunity.microsoft.com/t5/windows-virtual-desktop/investigating-issue-with-windows-10-enterprise-multi-session/m-p/1431813

      You can fix it by running this registry add

      Windows Registry Editor Version 5.00

      [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\rdp-sxs]
      "fReverseConnectMode"=dword:00000001

      I did it by running the powershell command on the VM directly in Azure.

      New-ItemProperty -Path "HKLM:\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\rdp-sxs" -Name "fReverseConnectMode" -Value "1" -PropertyType "Dword"

      After a reboot it works!

      Regards
      Jacob
      • Vu_Hoang's avatar
        Vu_Hoang
        Copper Contributor
        Aug 14, 2023

        jjensen1818 

        Thanks for the tips.
        This is really a bit of a mystery occurrence, however.
        Tried various fixes suggested from Microsoft forums and from other sites, including this registry fixes that worked for a couple (on top of removing it from host pool, rejoin domain, uninstalled all RDAgents software, re-register with new token, etc.), but then it does not for a few others.

        But then next day or so, things are ok again for all affected VMs without any other fixes added.

        Would really love to know the root cause of this to better support the mass audience.

Resources