Exporteren (0) Afdrukken
Alles uitvouwen
EN
Deze inhoud is niet beschikbaar in uw taal, maar wel in het Engels.

What's New in Remote Desktop Services in Windows Server

Published: June 21, 2013

Updated: May 28, 2014

Applies To: Windows Server 2012, Windows Server 2012 R2



This topic describes the Remote Desktop Services functionality that is new or changed in Windows Server 2012 R2 and Windows Server 2012.

In this topic:

In Windows Server 2012 R2, Remote Desktop Services offers enhanced support in the following areas:

In Windows Server 2012 R2, Session Shadowing enables you to remotely monitor or control an active session of another user on a Remote Desktop Session Host (RD Session Host) server. The current version includes integration with Server Manager and Remote Desktop Connection (mstsc.exe).

In Windows Server 2012 R2 the Data Deduplication feature, released in Windows Server 2012, can be used with actively running personal desktop collections when the desktop virtual hard disks (VHDs) are stored on a file server running Windows Server 2012 R2 and accessed by using Server Message Block (SMB). Storage capacity requirements can be dramatically reduced by using the Data Deduplication feature. Data Deduplication on the SMB server caches frequently accessed data, allowing performance improvements on many read-intensive operations, including parallel remote client boot.

In Windows Server 2012 R2 RemoteApp programs are one step closer to the look and feel of local applications by including support for transparency, live thumbnails, and seamless application move that allows the application content to remain visible while the application is moved on screen.

In Windows Server 2012 R2 Quick Reconnect improves connection performance enabling users to reconnect to their existing virtual desktops, RemoteApp programs, and session-based desktops more quickly. The connection process for RemoteApp programs has been redesigned for Windows® 8.1 and Windows Server 2012 R2 clients, to be more informative and user friendly.

Windows Server 2012 R2 improves performance on the Windows Server 2012 remote experience, by using codecs that enable better compression, delivering bandwidth savings (for example video content delivery over a WAN utilizes up to 50% less bandwidth compared to Windows Server 2012).

In Windows 8.1 and Windows Server 2012 R2 support has been added for display changes on the client to be automatically reflected on the remote client. This translates to seamless device rotation, and monitor addition and removal (for example connecting to a projector or docking a laptop) for both remote sessions and RemoteApp programs.

The RemoteFX vGPU in Windows Server 2012 R2 includes support for DX11.1 on systems that have DX11.1 capable GPU cards. Graphics intensive applications that rely on DX11.1 features can be virtualized and run in a virtualized environment on Windows 8.1 and Windows Server 2012 R2. Windows Server 2012 R2 introduces the following functionality:

  • Non-Uniform Memory Access (NUMA) support: RemoteFX running on NUMA-based platforms will experience improved scaling capabilities.

  • Video RAM (VRAM) changes: Adding system memory, to the server running Hyper-V, will allow for a dynamic increase in virtual machine VRAM which can improve performance for applications.

Windows 8.1 and Windows Server 2012 R2 support a new remote desktop option to connect in RestrictedAdmin mode. When connecting using RestrictedAdmin mode, the user’s credentials are not sent to the host by the remote desktop client. Using this mode with administrator credentials, the remote desktop client attempts to interactively logon to a host that also supports this mode without sending credentials. When the host verifies that the user account connecting to it has administrator rights and supports Restricted Admin mode, the connection is successful. Otherwise, the connection attempt fails. Restricted Admin mode does not at any point send plain text or other re-usable forms of credentials to remote computers.

noteNote
Once connected to a host in RestrictedAdmin mode, the user will not be able to seamlessly access other network resources from that host using the credentials they provided to the remote desktop client.

To connect using RestrictedAdmin mode requires

  • Windows 8.1 or Windows Server 2012 R2 for the remote desktop host

  • Windows 8.1 or Windows Server 2012 R2 for the remote desktop client

Remote Desktop Services is a server role that consists of several role services. In Windows Server 2012 R2, Remote Desktop Services consists of the following role services:

 

Role service name Role service description

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.

The Remote Desktop Services server role in Windows Server 2012 provides technologies that enable users to connect to virtual desktops, RemoteApp programs, and session-based desktops. With Remote Desktop Services, users can access remote connections from within a corporate network or from the Internet.

In Windows Server 2012, Remote Desktop Services offers enhanced support for the following scenarios:

Remote Desktop Services introduced a VDI deployment in Windows Server 2008 R2. In Windows Server 2012, Remote Desktop Services includes new ways to efficiently configure and manage your virtual desktops. Some of the enhancements include:

  • Unified central experience – Deploy VDI quickly, and then manage your pooled and personal virtual desktop deployments through a new unified central experience.

  • Automated and simple single-image management – Take advantage of automated ways to deploy and manage pooled virtual desktops with a virtual desktop template.

  • User personalization – Preserve user personalization settings for pooled virtual desktop deployments by using user profile disks.

  • Less expensive storage – Use inexpensive local storage with live migration functionality between host computers for pooled virtual desktops. Personal virtual desktops can use the less expensive SMB central storage.

In Windows Server 2012, Session Virtualization deployment in Remote Desktop Services includes new ways to efficiently configure and manage your session-based desktops. In earlier versions of Remote Desktop Services, ongoing management of the RD Session Host servers is performed at a per server level. By using a Session Virtualization deployment scenario, centralized management and installation is enabled. Session Virtualization in Windows Server 2012 offers the following benefits:

  • Unified central experience – In Windows Server 2012, you can deploy Session Virtualization quickly and manage your deployments through a new unified central experience.

  • Simplified and centralized deployment – Simple scenario-based installations allow you to create an entire session collection at one time.

  • User personalization – User profile disks allow you to preserve user personalization settings for your session collections.

  • Centralized and unified management – Manage all of the RD Session Host servers in your session collection from a single location.

  • Fairshare experience – For a predictable user experience in Windows Server 2012 and to ensure that one user does not negatively impact the performance of another user’s session, the following features are enabled by default on RD Session Host servers:

    • Network Fairshare – Dynamically distributes available bandwidth across sessions based on the number of active sessions to enable equal bandwidth utilization.

    • Disk Fairshare – Prevents sessions from over utilizing disk usage by equal distribution of disk I/O among sessions.

    • CPU Fairshare – Dynamically distributes processor time across sessions based on the number of active sessions and load on these sessions. This was introduced in Windows Server 2008 R2 and has been improved for heavier loads in Windows Server 2012.

A Session Virtualization deployment consists of RD Session Host servers along with infrastructure servers, such as RD Licensing, RD Connection Broker, RD Gateway, and RD Web Access servers.

A session collection (referred to as a farm in earlier versions of Windows Server) is a grouping of RD Session Host servers for a given session. A session collection is used to publish one of the following resources:

  • Session-based desktops

  • RemoteApp programs

Session Virtualization is a scenario-based installation within Server Manager that allows you to install, configure, and manage RD Session Host servers from a central location. With the Session Virtualization deployment scenario, you’re presented with two deployment types:

  • Quick Start: Installs all the necessary Remote Desktop Services role services on one computer to enable you to install and configure Remote Desktop Services role services in a test environment.

  • Standard deployment: Allows you to flexibly deploy the various Remote Desktop Services role services on different servers.

In Windows Server 2008 R2, publishing and managing applications on both pooled and personal virtual desktops is a very time-consuming and costly process. Because RemoteApp programs only partially integrate with the native Windows® experience, they add to the management cost since there is no way to organize published RemoteApp programs to users.

Remote Desktop Services in Windows Server 2012 enables you to publish and manage resources, such as RemoteApp programs, session-based desktops, and virtual desktops, from a centralized console. Using this new publishing feature, you can get an historic view of resources assigned to end users, change published resources for any given collection, and edit properties of published resources.

In addition to the centralized console, you can now configure a RemoteApp and Desktop Connection URL by using Group Policy, and then give users access to the URL automatically through an email address.

Centralized resource publishing provides end users with an experience that can replace locally installed applications.

Windows Server 2008 R2 with Service Pack 1 and Windows 7 with Service Pack 1 introduced Microsoft RemoteFX, which enables the delivery of a full Windows user experience to a range of client devices, including rich clients, thin clients, and ultrathin clients. Windows Server 2012 builds on this platform to enable a richer and more seamless experience on all types of networks and devices. Specifically, Remote Desktop Protocol (RDP) enables a consistent user experience when connecting to centralized workspaces even on networks where bandwidth is limited and latency is high.

Following are the key benefits for end users and IT professionals in using RDP in Windows 8 for their centralized workspace deployments.

 

RDP key benefits to end users

RDP key benefits to IT professionals

  • Rich end user experience

  • Access to corporate desktop and applications from anywhere by using any device

  • Secure, managed, and fully supported desktops and applications

  • Flexible deployment options

    • Virtual desktops

    • Session-based desktops

    • RemoteApp programs

    • Full desktop clients

    • Thin clients

    • Corporate networks

    • Branch offices

  • Diverse workforce support

    • Roaming users

    • Telecommuters

    • Bring your own computer

  • Keep costs down

Windows Server 2008 R2 with Service Pack 1 and Windows 7 with Service Pack 1 introduced Microsoft RemoteFX vGPU support, a set of technologies for a rich PC-like experience for virtual desktops. Windows Server 2008 R2 with Service Pack 1 introduced the following functionality:

  • Host-side remoting

  • Render-capture-encode pipeline

  • Highly efficient GPU-based encode

  • Throttling based on client activity

  • DirectX-enabled virtual graphics processing unit (vGPU)

Windows Server 2012 builds upon this platform and implements support for the vGPU from DX9 to DX11. The user experience is also improved including support for additional monitors at higher resolutions. As hardware acceleration proliferates to more applications like the web browser, the vGPU enables applications to run higher levels of DirectX within Remote Desktop Virtualization Host (RD Virtualization Host).

Maximum monitor resolution for virtual machines per Windows Version:

 

Maximum resolution Monitors per virtual machine for Windows 7 with SP 1 Monitors per virtual machine for Windows 8

1024 x 768

4

8

1280 x 1024

4

8

1600 x 1200

3

4

1920 x 1200

2

4

2560 x 1600

-

2

Remote Desktop Services is a server role that consists of several role services. In Windows Server 2012, Remote Desktop Services consists of the following role services:

 

Role service name Role service description

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 by using RemoteApp and Desktop Connection.

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.

Vindt u dit nuttig?
(1500 tekens resterend)
Bedankt voor uw feedback

Community-inhoud

Toevoegen
Weergeven:
© 2014 Microsoft