

- Server 2016 remote desktop services environment full#
- Server 2016 remote desktop services environment windows#
What worked for a few of my users was to have them log into the RDWEB site.
Server 2016 remote desktop services environment windows#
Server 2016 remote desktop services environment full#
I have not attempted, nor do I have a use case for Remote Apps, only the ability to allow the user to remote desktop via web into the same machine in question and have a full Remote Desktop experience, just via web.

It's my understanding that Remote Apps as well as Remote Desktops should be available here. However, it offers no options to actually launch anything.

So, it's deployed and appears to have at least the login bit correct. its for this reason that you can see the RD Connection Broker Hostname (or farm name in case you have RD Connection Brokers in HA environnement) when you connect to your remote desktop session or RemoteApp. It's not on a domain (workgroup mode), and has an existing RDP setup that works just fine for multiple (local) users using the downloaded and installed Microsoft Remote Desktop Client for Windows and macOS.įrom here, I've attempted to follow numerous sets of instructions that I've found while Googling, and I've been able to get to this state: RD Connection broker is also in charge of reconnecting remote users to their existing Remote Desktop Session. I do not have the ability to deploy more machines into our environment. My environment consists of a single Windows Server 2016 machine that I have administrative access to. The ultimate goal is to be able to visit and be able to do a full Remote Desktop session in the browser.
