Forum Discussion
Account Used To Logon needs to be different from Logged in Windows User - Help Please
UserA, AccountB, AccountC.
1-UserA logon to windows machine
2-Then UserA uses AccountB to subscribe to WVD ( https://rdweb.wvd.microsoft.com/api/arm/feeddiscovery).
3-the resources(feeds) show up on the WVD clients
4-UserA wants to use AccountC to connect to these WVD resources?
Hello, thank you for trying to understand better my situation. Thre are only two accounts to be clear.
Windows 10 dekstop PC login - Account A
Windows Virtual Desktop User - Account B
1- User A logs into domain joined PC.
2- User A opens Remote Desktop Client (WVD edition)
3- User A uses Account B credentials to subscribe to WVD
4- The resources for Account B show up in the Remote Desktop Client app.
5 - User A double clicks one of the RemoteApp programs (resources)
6- The RemoteDesktop connection begins, however the user is logged in using Account A, not Account B. The RemoteApp fails to open as Account A is not authorised for RemoteDesktop login on the server.
The issue being when account B is used to subscribe, it should also be used for the connection. Otherwise it could become very confusing.
- Soo Kuan TeoJul 31, 2020MicrosoftThanks for the information! Can you please file a feedback to us with feedbackhub? Feedbackhub will give us more info on your situation. Please do the following:
1. Reproduce your logon scenario once.
2. Open feedback hub, make sure you select category= apps\Remote Desktop
3. optional: "start repro" to reproduce your logon scenario, "stop scenario"
4. Click submit
5. After you submitted, wait for like 15 seconds. on the feedback hub ui, select Feedback->My feedback, you should see the feedback you just submitted. Click it, then Click Share, it will generate a link. Please share the link with us.- James_Randall_1978Aug 21, 2020Brass Contributor
Hello,
I have finally gotten around to doing what you have asked. Here is the link, sorry for the delay:
- Soo Kuan TeoSep 02, 2020Microsoft
James_Randall_1978 , Thanks for your feedback from feedbackhub, we identified the issue. we are working on the fix.
Thanks again.