Forum Discussion
Error when connecting to MVD - 0x3000047
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
My setup worked fine with the default gallery image (Win10 multi-session with Office ProPlus). I then created a custom image and ran all the time into 0x3000047. Tried reboots and checked my UPN suffixes. All looked good, error persisted.
My custom image was with the brand new Windows 10 2004 with Office 365 ProPlus image. Not sure if it had any thing to do with it. Image was sysprepped, captured and published to the shared image gallery.
My observation was that the Session Host(s) created kept their original computer names. The machine was also joined to the domain with the original name, not rdsh-0 what I expected. I manually renamed the session host and rejoined, this did not help.
Finally decided to recreate my custom image based on Windows 10 1908 with Office. This time it worked fine.
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
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?
