Remote Desktop orchestration error

Problem Statement – Not Able to Connect to AVD

• Logon to//rdweb.wvd.microsoft.com/arm/webclient/index.htmlwith Azure AD user name and password.
• Click theRemote Desktop Session hostavailable.
• Log in to Remote Desktop with the same Azure user name and password used above.

We couldn’t connect because there are currently no available resources. Try again later or contact tech support for help if this keeps happening.

Error 0x3000046

Extended Error Code 0x0

How to fix RD Client iOS error code 0x3000015 for Windows Virtual Desktop

• Cloud, Endpoint Management, Modern Desktop, Modern Workplace, Windows Virtual Desktop
• 6

Many of you who tried out the new iOS Remote Desktop client app to connect to Windows Virtual Desktop might have encountered an error during subsequent attempts when adding a new workspace to your RD Client app.

0x3000015, a screen smasher for sure!

To avoid hitting the repair shop for a new screen, let me walk you through a couple of steps to fix this issue.

Setting the stage:

Starting with the screenshots below, I already have a workspace configured which points to 2 of my Windows Virtual Desktop tenants.

For the purpose of this demo and blog, I would like to setup a new workspace, so I can connect to another series of virtual desktops.

When pressing the “Edit” button, select “delete”

Press “delete” again in order to confirm and permanently delete that workspace.

Great so far, no workspaces to show:

Now let’s hit the “+” sign

And select “Add Workspace”

Enter the Windows Virtual Desktop webfeed url : “//rdweb.wvd.microsoft.com” and enter next

You’re then prompted to authenticate against your Azure Active Directory Tenant , so use your e-mail address or UPN [User Principal Name] that has access to a Windows Virtual Desktop workspace to login.

Awesome, here is my new workspace, and as you can see I have a session desktop available to launch.

Now, you would expect that if you select your session desktop, you’ll end up in your Windows 10 environment..

Guess again! 0x3000015, “we couldn’t connect to the remote desktop gatexway because of an internal error. If this keeps happening contact your network administrator for assistance.”

Now, let me be that network administrator for you today!

In order to resolve this issue, follow the steps below!

Fixing the issue

To start of with a clean sheet, close all open apps on your iOS device and navigate to the settings pane.

Scroll down through your apps until you reach the RD Client app.

Select the RD Client app.

And scroll down to the “WVD Security Tokens” setting. Slide this slider to the right and make sure it’s green and selected.

Enable “Delete on App Launch” in the “WVD Security Tokens” settings

Back to our Virtual Desktop

Now let’s navigate back to our Remote Desktop Client app.

And launch your previously added desktop

Enter your username and password

Woohoo! Here we have our rich Windows 10 experience on iOS provided by Windows Virtual Desktop.

Thank you!

Thank you for reading through this blog post, I hope I have saved you some time on researching the 0x3000015 error message.

If you encounter any new insights, feel free to drop me a comment or contact me via mail or other social media channels

Tags: apple ios rdclient remotedesktop windows10 WindowsVirtualDesktop WVD

Question: Q: Microsoft RDP client for Mac receiving "Unable to connect" error code 0x5000007 from Microsoft RD Gateway

We have an RD Gateway server setup and running well. All of our Windows clients can use MS RDP client from outside of the LAN, but Mac users continue to receive and error; "Unable to connect Your session ended because of a protocol error while communicating with the Remote Desktop Gateway. If this keeps happening, contact your network administrator for assistance."

I can successfully connect a Mac running MS RDP client to computers on the network, but fail when accessing from outside of the firewall, through the gateway server.

i'm so so so stuck. help please.

More Less

Posted on Apr 2, 2020 5:10 PM

Reply I have this question too[54] I have this question too Me too[54] Me too

Apr 3, 2020 4:17 AM in response to RichardVisageMe In response to RichardVisageMe

This forum is for Apple's Remote Desktop and therefore not for you. Microsoft's Remote Desktop forum is here:

//remotedesktop.uservoice.com/forums/287834-remote-desktop-client-for-mac

You should have a word with your network administrator and ask them the question. FWIW I think there's a certificate or a protocol setting that needs to be configured somewhere that will allow your Mac to 'pass-through'. This could be something built-in on a PC or pre-configured when your IT department roll out the setting to their PC clients. Be patient and persistent and don't let them fob you off simply because you're on a Mac and not a PC. They should be supporting you properly irrespective of platform. It's their job after all

More Less

Apr 3, 2020 4:17 AM

Reply Helpful

Thread reply - more options

• Link to this Post

Apr 3, 2020 1:43 PM in response to RichardVisageMe In response to RichardVisageMe

If you have a good rapport with your IT support team then ask them if you need to install an SSL certificate on your Mac. My understanding is the RD Gateway requires this for RD clients to connect successfully. The other aspect of this is whether you have to establish a VPN first. Now this may or may not be a requirement prior to using MRD but its worth asking.

I've had another look and found this:

//remotedesktop.uservoice.com/forums/925639-remote-desktop-beta-client-for-ios/suggestions/39205006-rd-gateway-error-0x3000066

Ask if TLS v1.2 is enabled and make sure you're on the latest macOS. Worth a try?

Good luck!

More Less

Apr 3, 2020 1:43 PM

Reply Helpful

Thread reply - more options

• Link to this Post