Microsoft Remote Desktop Services
Hi all and once again I am happy to inform you with some new configuration brought to you from Microsoft.
Before we begin configuring I would like to explain all their is to know before implementing the best Deployment for your scenario, Remote Desktops Services also known as Terminal Services.
Stay tuned in my next post I will upload configuration guide.
What is Remote Desktop Services
Remote Desktop Services accelerates and extends desktop and application deployments to any device, improving remote worker efficiency, while helping to keep critical intellectual property secure and simplify regulatory compliance. Remote Desktop Services enables virtual desktop infrastructure (VDI), session-based desktops, and applications, allowing users to work anywhere.
Remote Desktop Roles Explained
RD Virtualization Host – Remote Desktop Virtualization Host (RD Virtualization Host) integrates with Hyper-V to deploy pooled or personal virtual desktop collections within your organization.
RD Session Host – Remote Desktop Session Host (RD Session Host) enables a server to host RemoteApp programs or session-based desktops. Users can connect to RD Session Host servers in a session collection to run programs, save files, and use resources on those servers.
RD Connection Broker – Remote Desktop Connection Broker (RD Connection Broker):
- Allows users to reconnect to their existing virtual desktops, RemoteApp programs, and session-based desktops.
- Enables you to evenly distribute the load among RD Session Host servers in a session collection or pooled virtual desktops in a pooled virtual desktop collection.
- Provides access to virtual desktops in a virtual desktop collection.
RD Web Access – Remote Desktop Web Access (RD Web Access) enables users to access RemoteApp and Desktop Connection through the Start menu on a computer that is running Windows 8, Windows 7, or through a web browser. RemoteApp and Desktop Connection provides a customized view of RemoteApp programs and session-based desktops in a session collection, and RemoteApp programs and virtual desktops in a virtual desktop collection.
RD Licensing – Remote Desktop Licensing (RD Licensing) manages the licenses required to connect to a Remote Desktop Session Host server or a virtual desktop. You can use RD Licensing to install, issue, and track the availability of licenses.
RD Gateway – Remote Desktop Gateway (RD Gateway) enables authorized users to connect to virtual desktops, RemoteApp programs, and session-based desktops on an internal corporate network from any Internet-connected device.
Remote Desktop Services requires that the Windows Server 2012 operating system be installed. There are no additional hardware or software requirements for running Remote Desktop Services.
There are several hardware requirements that must be met when you deploy RemoteFX virtualized GPU to hardware accelerate your Windows client virtual desktops:
- SLAT-enabled processor. The processor on the RemoteFX server must support Second-Level Address Translation (SLAT).
- GPU. At least one graphics processing unit (GPU) that is capable of supporting RemoteFX is required on the RemoteFX server. The GPU driver must support DirectX 11.
So what’s new in 2012?
In Windows Server 2012 R2 Preview, Remote Desktop Services includes enhancements in the following areas:
- Monitor and control by using session shadowing
- Reduced storage requirements and improved performance accessing common data
- RemoteApp programs perform more like locally-based applications
- Improved reconnection performance for remote clients
- Improved compression allowing improved usage of network bandwidth
- Display resolution changes are automatically reflected on the remote client
- RemoteFX virtualized GPU supports DX11.1