Forum Discussion
Error when connecting to MVD - 0x3000047
- 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
same issue here - 0x3000047 for W10 2004 - based custom image. Will try 1909 base next week.
Same problem - created from an Image Gallery - used the same process with an shared Image Gallery using (1909 with 365) with no problems.
Just now trying to deploy a WVD using MarketPlace image v2004 with 365 Gen1 - get the same error code
Has anybody got this to work correctly?
TIA
- BogdanGrozoiuJun 08, 2020Copper Contributor
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?
- AlexTBigAlJun 08, 2020Copper Contributor
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
- jjensen1818Jun 09, 2020Copper ContributorSame 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?