RDS encompasses the roles formerly known under the Terminal Services workload as well as a new role service to manage and automate access to virtual desktops based on Hyper-V technology for a Virtual Desktop Infrastructure (VDI). Combined, these services are now called Remote Desktop Services.
RDS provides technologies that enable users to access session-based desktops, VM-based desktops, or applications in the data center from within a corporate network or from the Internet. RDS enables a full-fidelity desktop or application experience and efficiently connects remote workers from managed or unmanaged devices.
Key Feature - Support for Virtual Desktop Infrastructure (VDI)
One of the key new features of RDS is the ability to provide users with a VM-based remote desktop, or virtual desktop. Virtual desktops run client operating systems hosted on Hyper-V–based servers located in a data center. With RDS and VDI, users can experience rich and individualized desktops with full administrative control over the desktop and the applications. Administrators have the ability to configure dedicated personal desktops that will provide a consistent desktop experience for users that is similar to the experience of using a dedicated desktop or portable computer. Alternatively, VDI desktops can be pooled and dedicated to a specific set of applications.
- What's New & Changed in Windows Server 2008 R2 RDS?
- Remote Desktop Session Host
Client experience configuration page
Per-user Remote App filtering
Fair Share CPU scheduling
Windows Installer RDS compatibility
Roaming user profile cache management
Remote Desktop IP virtualization
- Remote Desktop License Management Changes
Automatic license server discovery no longer supported for RD Session Host servers
In Windows Server 2008 R2, you must specify the name of a license server for the RD Session Host server to use by using Remote Desktop Session Host Configuration.
However, for Windows Server 2008, Windows Server 2003, or Windows 2000 Server, you must specify a discovery scope when you install the RD Licensing role service, which determines how the Remote Desktop license server is automatically discoverable by terminal servers that are running these earlier operating systems.
The Manage RDS CALs Wizard allows you to migrate RDS CALs from one license server to another, and also allows you to rebuild the RD Licensing database.
- Remote Desktop Connection Broker
Remote Desktop Connection Broker (RD Connection Broker), formerly Terminal Services Session Broker (TS Session Broker), is used to provide users with access to RemoteApp and Desktop Connection. RemoteApp and Desktop Connection provides users 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, Remote Desktop sessions, and RemoteApp programs accessed by using RemoteApp and Desktop Connection. RD Connection Broker also aggregates RemoteApp sources from multiple Remote Desktop Session Host (RD Session Host) servers that may host different RemoteApp programs.
To configure which RemoteApp programs and virtual desktops are available through RemoteApp and Desktop Connection, you must add the RD Connection Broker role service on a computer running Windows Server 2008 R2, and then use Remote Desktop Connection Manager (RD Connection Manager).
- Remote Desktop Gateway
Configurable idle and session timeouts
Background session authentication and authorization
System and logon messages
Device redirection enforcement
Network Access Protection (NAP) remediation
Pluggable authentication and authorization
- Remote Desktop Web Access Changes
Per user RemoteApp program filtering
Single sign-on between RD Session Host and RD Web Access
Public & provate computer option.
- New Role: Remote Desktop Virtualization Host
Remote Desktop Virtualization Host (RD Virtualization Host) is a new Remote Desktop Services role service included with Windows Server 2008 R2. RD Virtualization Host integrates with the Hyper-V™ role to provide virtual machines that can be used as personal virtual desktops or virtual desktop pools by using RemoteApp and Desktop Connection. User accounts can be assigned a unique personal virtual desktop or be redirected to a virtual desktop pool where a virtual desktop is dynamically assigned. RD Virtualization Host is an important component to the Virtual Desktop Infrastructure (VDI) solution offered by Microsoft.
What does Remote Desktop Virtualization Host do?
An administrator can make personal virtual desktops or virtual desktop pools available to users by using either RemoteApp and Desktop Connection or Remote Desktop Web Access (RD Web Access). These virtual desktops are virtual machines hosted on a computer that is running Windows Server 2008 R2 on which Hyper-V and RD Virtualization Host are also installed.
With a personal virtual desktop, a user is assigned a personal virtual desktop in Active Directory Domain Services (AD DS). A personal virtual desktop can be assigned to only one user account. All customizations that the user does to their personal virtual desktop are saved and available to them when they log on to the personal virtual desktop again.
A virtual desktop pool requires that virtual machines are identically configured and should not already be assigned to a user as a personal virtual desktop. Because the virtual machines are identically configured, the user will see the same virtual desktop, regardless of which virtual machine in the virtual desktop pool the user connects to by using RemoteApp and Desktop Connection. Also, you can configure virtual desktop pools to roll back to a previous state when a user account logs off from the computer.
Note: RD Virtualization Host requires that Hyper-V be installed on the same computer on which RD Virtualization Host is installed.
- RemoteApp and Desktop Connection
In Windows Server 2008, Terminal Services introduced RemoteApp programs, which are programs that are accessed remotely through Remote Desktop Services and appear as if they are running on the end user's local computer. In Windows Server 2008 R2, Remote Desktop Services provides administrators the ability to group and personalize RemoteApp programs as well as virtual desktops and make them available to end users on the Start menu of a computer that is running Windows® 7. This new feature is called RemoteApp and Desktop Connection.
RemoteApp and Desktop Connection provides a personalized view of RemoteApp programs, session-based desktops, and virtual desktops to users. When a user starts a RemoteApp program or a session-based desktop, a Remote Desktop Services session is started on the Remote Desktop Session Host (RD Session Host) server that hosts the remote desktop or RemoteApp program. If a user connects to a virtual desktop, a remote desktop connection is made to a virtual machine that is running on a Remote Desktop Virtualization Host (RD Virtualization Host) server. To configure which RemoteApp programs, session-based desktops, and virtual desktops are available through RemoteApp and Desktop Connection, you must add the Remote Desktop Connection Broker (RD Connection Broker) role service on a computer that is running Windows Server 2008 R2, and then use Remote Desktop Connection Manager.
In Windows 7 and Windows Server 2008 R2, you configure RemoteApp and Desktop Connection by using Control Panel. After RemoteApp and Desktop Connection is configured, RemoteApp programs, session-based desktops, and virtual desktops that are part of this connection are available to users on the Start menu of their computer. Any changes that are made to RemoteApp and Desktop Connection, such as adding or removing RemoteApp programs or virtual desktops, are automatically updated on the client and on the Start menu.
- Remote Desktop Client Experience Changes
The Remote Desktop Connection client experience has been enhanced for computers running Windows 7 that are connecting to a Remote Desktop Session Host (RD Session Host) server running Windows Server 2008 R2.
The following changes are available in Windows Server 2008 R2:
Audio and video playback. In Windows Server 2008 R2, audio and video content, played back by using Windows Media Player, is redirected from the RD Session Host server to the client computer in its original format and rendered by using the client computer's resources. Other multimedia content such as Silverlight and Windows Presentation Foundation are rendered on the server. The bitmaps are then compressed and sent over to the client.
Multiple monitor support. Remote Desktop Connection (RDC) 7.0 and Windows Server 2008 R2 enable support for up to 16 monitors. This feature supports connecting to a remote session with any monitor configuration that is supported on the client computer. Programs function just like they do when they are running on the client computer.
Desktop composition is not supported on an RD Session Host session with multiple monitors.
Audio recording redirection. RDC 7.0 and Windows Server 2008 R2 redirect audio recording devices, such as microphones, from the client computer to the remote desktop session. This may be useful for organizations that use voice chat or Windows Speech Recognition.
Desktop composition. RDC 7.0, Windows 7, and Windows Server 2008 R2 support Windows Aero within an RD Session Host session.
Desktop composition is not supported in a remote session from Windows Vista® to Windows 7, or in a remote session from Windows 7 to Windows Vista even if the RDC 7.0 client is installed. You must be using Windows 7 or Windows Server 2008 R2 to take advantage of the desktop composition feature.
Language bar redirection. In RDC 7.0 and Windows Server 2008 R2, you can use the language bar on the client computer to control the language settings within your RemoteApp programs.