Forum Discussion
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:
When connecting via the Windows client, she gets this:
As far as I know, she is the only member of staff who gets this. She's using Windows 10 Home on a laptop, has tried multiple browsers and is using a DSL ISP (Sky in this instance).
I've tried running "Get-RdsDiagnosticActivities" but it comes back with "There were no activities found"
Any ideas?
Thanks,
Ian
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
Hi,
I was able to solve the problem by removing the virtual machine from the domain and adding it again after the reboot.Hope this helps.
I had the same error from one of my user and found out that Virtual PC was not connected or dropped out of our domain. We ended up reconfiguring VDI for that user. Norphus
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
same , trying to connect to newly deployed host pool based on 2004 win 10 (
connnection to old host pool (same tenant, same domain same upn ) goes well
(( not sure how to troubleshhot this
Miguel680603Microsoft
Same issue, but at the beginning everythig was OK with the first Hoospool, and now I can´t connect. I created two more pool and with the same result
I had a similar issue today in my 2004 lab environeemnt, but i only had to reboot my DC and RDSH server.
I would suggest you to check UPNs in your DC and check the rights.
(Rights are per apps in 2019 deployment types, so if you created a new pool you need to add the same users to the new pool).
Once i did re-subscribed the connection worked.
Hope it help.
- Click Start, click Administrative Tools, and then click Computer Management.
- In the console tree, click the Local Users and Groups node.
- In the details pane, double-click the Groups folder.
- Double-click Remote Desktop Users, and then click Add.
- In the Select Users dialog box, click Locations to specify the search location.
- Click Object Types to specify the types of objects that you want to search for.
- In the Enter the object names to select (examples) box, type the name you want to add.
- Click Check Names.
- When the name is located, click OK.
hello norphus
i also have the same problem now
if you solve your problem can you tell us the solutionregards
It happens to us as well. I add the user through Graph API. The user can't access it for up to 40 minutes. Then the user is able to log in to the WVD.
I have the same issue and users are in local AD synced with Azure AD connect.
- DavidBelanger
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):4Hi, we're facing this issue as we want our admins to connect to their administrative machines through AVD by using cloud-only admin accounts and then AD accounts for RDP. Is it possible to disable this function of AVD where it tries to add users to the local Remote Desktop Users group?
- DavidBelanger
Thanks for the feedback. Any thoughts on what could be different for those user's devices?
For reference, I filed the tracking item for investigation:
Item 25683128 : Reports of error 0x3000047 when connecting to WVD
same issue both via web and client
AndreadG same issue and I have used the Spring 2020 ARM.
The funny thing is that with my account , global administrator, with MFA enabled I can login. Users in member of the group assigned to the Application Group in WVD they cannot enter.
other difference is that I have M365 E5 and they have M365 E3
Hi, i'm literally facing the same issue:
n error occurred while Remote Desktop Connection was accessing this resource. Retry the connection or contact your system administrator.[Expanded Information]
Error code: 0x3000047
Extended error code: 0x0
Activity ID: AB903267-6E4A-42F5-8087-8F0CB8C10000
