Jump to content

New features coming to Remote Desktop Services

Arthur

By Arthur
in Windows Server 2016

 Share

Recommended Posts

FN-GM

FN-GM

Posted
Posted
It looks great!

It works really well on the internal network.

 

All I get from outside is "Oops, we couldn't connect to ...."

 

I am using a Sophos UTM 9

 

I have a feeling it is something to do with websockets and the UTM not handling them well. Or at all.

 

I have the same errors on all the versions i have tried, 0.8.x - 0.9.x

 

Normal RdWeb works just fine.

 

Any ideas?

 

Does anyone have it working on other firewalls?

 

Regards

 

BoX

 

We get the same issue but not using Sophos.

 

Are you using a reverse or web application proxy of some kind?

box_l

box_l

Posted
Posted

Yes, it is called Web Application Firewall in the sophos UTM. (Astaro)

 

I think i will try an ipFire install maybe.

 

Just to see if a simple Http/Https Allow rule is a viable alternative.

Simcfc73

Simcfc73

Posted
Posted

Guess I am going to have to wait a bit to use it in my setup.

 

Important

The web client does not currently support using Azure Application Proxy and does not support Web Application Proxy at all. See Using RDS with application proxy services for details.

Arthur

Arthur

Posted
  • Author
Posted

Remote Desktop web client now generally available

 

Today, we are announcing the general availability of the Remote Desktop web client for Windows Server 2016 and Windows Server 2019 Preview. With a few simple PowerShell cmdlets, the client can be added to an existing Remote Desktop Services deployment, side by side with the RDWeb role.

 

This first release of the web client contains a core set of features to get you started in providing a simple, no-install, consistent cross-platform solution to end users who don’t need some of the more advanced features from a native client.

 

The following features are currently available:

 

  • Access desktops and apps published through a feed
  • Single sign-on
  • Print to PDF file
  • Audio out
  • Full screen and dynamic resolution
  • Copy/paste text using Ctrl+C and Ctrl+V
  • Keyboard and mouse input support
  • Localized in 18 languages

The web client is supported on Edge, IE11+, Chrome, Firefox, and Safari browsers for desktop platforms like Windows, macOS, Chromebook, and Linux.

  • Thanks 2
FN-GM

FN-GM

Posted
Posted
There seems to be some kind of bandwidth saving system and it makes the desktop shortcuts and menus in SIMS blurred until you use them. Does anyone know how to turn this off please?
  • 4 weeks later...
FishCustard

FishCustard

Posted
Posted
Just FYI: if you set this up with self-signed certs for testing, and then swap them for proper SSL certificates later you'll need to re-run the 
Import-RDWebClientBrokerCert <.cer file path>

command again, pointing to the new certificate. Otherwise you'll get "unexpected server certificate" errors when you try to connect.

  • Thanks 1
  • 7 months later...
robk

robk

Posted
Posted

Has anyone got this working in server 2016? can't install 2019 due to a VMware issue, and can't tell if I should be able to install the html 5 plug in on server 2016 full or not...

 

I know server core is a none starter for the remote desktop components.

gshaw

gshaw

Posted
Posted
Was going to turn this on last week then read it doesn't work with Azure AD Application Proxy, sort it out Microsoft [emoji58]
FishCustard

FishCustard

Posted
Posted
Has anyone got this working in server 2016? can't install 2019 due to a VMware issue, and can't tell if I should be able to install the html 5 plug in on server 2016 full or not...

 

I know server core is a none starter for the remote desktop components.

 

Yep, we have it running on 2016 just fine. :)

robk

robk

Posted
Posted
Yes. It works fine on 2016 (with DE).
Yep, we have it running on 2016 just fine. :)[/quote @FishCustard which server build are you using?

 

I am either on the wrong build or missing some updates as the install instructions I have didn't work...

DrCheese

DrCheese

Posted
Posted
Was going to turn this on last week then read it doesn't work with Azure AD Application Proxy, sort it out Microsoft [emoji58]

 

Ya, this does baffle me - I won't setup any new services that don't allow us to use Azure AD now, as we have 2fa active. For now, we're still using our ericom accessnow solution for staff (HTML5) & one of my staff wrote an Azure AD wrapper for it.

  • Thanks 1
box_l

box_l

Posted
Posted (edited)

They do say that it is on the roadmap.

 

It does appear that the websocket bits are the issue.

 

Add your vote and maybe it will happen sooner!

 

Check the last post and provide feedback. [email protected]

 

https://feedback.azure.com/forums/169401-azure-active-directory/suggestions/33918046-support-remote-desktop-web-client-html5-on-azure-a

 

 

Has anyone managed to publish the webclient with a reverse proxy or open ports?

 

All the solutions i have tried fail with the websockets.

Edited by box_l
box_l

box_l

Posted
Posted

I presume that is a reference to a microsoft KB?

I have that installed already where required.

 

Just to clarify, I have no issues with the webclient on the internal network, it works just fine.

It is the publishing of it externally.

gshaw

gshaw

Posted
Posted
They do say that it is on the roadmap.

 

It does appear that the websocket bits are the issue.

 

Add your vote and maybe it will happen sooner!

 

Check the last post and provide feedback. [email protected]

 

https://feedback.azure.com/forums/169401-azure-active-directory/suggestions/33918046-support-remote-desktop-web-client-html5-on-azure-a

 

 

Has anyone managed to publish the webclient with a reverse proxy or open ports?

 

All the solutions i have tried fail with the websockets.

 

Just emailed them as we're big fans of AAD Application Proxy here

FishCustard

FishCustard

Posted
Posted
I presume that is a reference to a microsoft KB?

I have that installed already where required.

 

Just to clarify, I have no issues with the webclient on the internal network, it works just fine.

It is the publishing of it externally.

No, that's the Windows build I'm running - @robk wanted to know

  • Thanks 1
free780

free780

Posted
Posted
@gshaw I'm also chasing this with fasttrack and the product team. I currently have Ericom going through the Azure App Proxy but it does mean staff have to logon twice. I couldn't get accessnow to SSO using AzureAD. Ericom solution is very complex and another cost.
  • Thanks 1
gshaw

gshaw

Posted
Posted
@free780 I had a response from the AAD Feedback team, pretty much mirrored the statement on the web page "Yes, this feature is on our roadmap and we are keen on making this integration happen"
DrCheese

DrCheese

Posted
Posted
@gshaw I'm also chasing this with fasttrack and the product team. I currently have Ericom going through the Azure App Proxy but it does mean staff have to logon twice. I couldn't get accessnow to SSO using AzureAD. Ericom solution is very complex and another cost.

 

We couldn't avoid this either - My guy was able to pull through the username but not the password, so staff have to enter their password again. Not ideal but no one's really complained.

free780

free780

Posted
Posted (edited)

I did get the webclient to work through AzureAD but not the app proxy. You have to use the myapps browser extension.

At least users won't store credentials in their Google account or similar.

Edited by free780

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share
Go to topic listing


×
×
  • Create New...