Remote Desktop Services (RDS) is a collection of role services in Windows Server that allow users to remotely access graphical desktops and Windows applications. Windows Server 2016 will bring some key changes to improve graphics performance and pen input options.

News in RDS 2016:

  • Windows 10-like experience (App Compatibility) – It looks exactly like Windows 10. Most apps (that works in windows 10) will also work in RDS 2016.

 

  • Pen remoting support – In previous version pen was treated like a mouse. In RDS 2016, the pen is now a first class input method, at the same level as your mouse, keyboard and touch

 

  • Personal session desktops – This option allows us  to assign personal desktops to end-users based on Windows Server 2016 in the Guest VM instead of Windows Client OS. We can create a new type of session collection where each user is assigned to their own personal session host with administrative rights.

 

  • Windows Multipoint Services – This option was available as a separate product but now included in Windows Server 2016. Windows MultiPoint Server is a Microsoft product originally developed for educational institutions and classrooms. MultiPoint allows multiple users, each with their own independent Windows experience, to simultaneously share one computer.

 

  • RD Connection Broker –  improved connection handling and performance. Connection Broker is now able to handle over 10,000 concurrent logon requests. We are able to build large Desktop-as-a-Service solutions.

 

  • Generation 2 VM Support – In Windows Server 2016 we are able to use any type of generation as base for personal session based desktops. There is no additional configuration required.

 

  • Edge and Office 2016 support
  • RemoteFX Improvements
  • Azure SQL Database – the new database for your highly available environment
  • RDP 10 – new capabilities built into the protocol

 

Remote Desktop Components

RD Session Host (RDSH) – hosts Windows-based programs or the full Windows desktop for Remote Desktop Services clients. Users can connect to an RD Session Host server to run programs, to save files, and to use network resources on that server.

RD Gateway (RDG) – enables compatible devices to securely connect over the Internet to RD Session Host servers or RD Virtualization Host servers behind a corporate firewall. A RDG is to be placed at the edge of a corporate network to filter out incoming RDS requests by referencing criteria defined in a designated Network Policy Server (NPS). With a server certificate, RDG offers secure remote access to RDS infrastructure.

RD Web Access (RDWA) – provides users with a customizable web portal for accessing session-based desktops, virtual desktops, and RemoteApp programs. To start, a user will access a RDS webpage by specifying an URL where RDS resources are published to.

RD Connection Broker (RDCB) – provides a single, personalized, and aggregated view of RemoteApp programs, session-based desktops, and virtual desktops to users. RD Connection Broker supports load balancing and reconnection to existing sessions on virtual desktops, session-based desktops, and RemoteApp programs. RDCB knows which is where, whom to talk to, and what to do with a RDS request.

RD Licensing – manage the Remote Desktop Services client access licenses that are required for each device or user to connect to session-based desktops.

RD Virtualization Host (RDVH)– RD Virtualization Host integrates with Hyper-V to provide virtual machines that can be used as personal virtual desktops or virtual desktop pools.

 

RDS 2016 DEPLOYMENT TYPE

  • STANDARD – It is the best practice deployment and you would choose this deployment type in the production environment. 3 core roles Connection Broker, RDWeb, and RDSH will be deployed on 3 different servers. When you choose Standard deployment Collections, Remote Apps and configuration will need to be configured manually. All installation, configuration, and management of the RDS session deployment should be done from the Connection Broker.

 

  • QUICK START – is the second option in RDS deployment and it is similar to Standard but when you choose quick start all components will be deployed on 1 server. Quick Start is a fast track for getting RDS up and running in a matter of minutes. Collection and remote app will be auto-configured. This deployment type is not recommended for production but if you are setting RDS up for a lab or a small environment then a all-in-one setup would save you hardware resources.

 

  • MULTIPOINT SERVICES – This is a new deployment option in RDS 2016. MPS was originally built for use in the classrooms and educational institutions. User stations can be consist of only monitor, keyboard, mouse (zero clients) and be connected to MPS through usb hubs, video cables or through LAN. If clients are not zero, for example, laptops, thin clients MPS uses some of the RDS services (by default): RD Session Host and RD Licensing Server.

 

Thanks for reading!

Cheers,

Nedim