Microsoft Rewards
Make your journey to modern management even easier with partner solutions that complement Microsoft Managed Desktop: Certified modern devices End-user support Line-of-business (LOB) app management Customer readiness Deployment support Value-added services. Oct 03, 2018 With Windows Admin Center integration, it is easy to consolidate all local and remote server management into a single pane. We have brought several Windows Defender optimizations for multi-session to give you more confidence in bringing a secure, scalable and cost-effective desktop experience to end users. The Remote Desktop Services Management Pack helps you manage your computers that are running Remote Desktop Services on Windows Server 2012 by monitoring the health of all Remote Desktop Services role services.
Windows Remote Management is one component of the Windows Hardware Management features that manage server hardware locally and remotely. These features include a service that implements the WS-Management protocol, hardware diagnosis and control through baseboard management controllers (BMCs), and a COM API and scripting objects that allow you to write applications that communicate remotely through the WS-Management protocol. For more information about the public specification for WS-Management protocol, see Web Services for Management (WS–Management).
Components of WinRM and Hardware Management
The following is a list of components and features that are supplied by WinRM and hardware monitoring:
Microsoft Terminal Services Manager
This scripting API enables you to obtain data from remote computers using scripts that perform WS-Management protocol operations.
Winrm.cmd
This command–line tool for system management is implemented in a Visual Basic Scripting Edition file (Winrm.vbs) written using the WinRM scripting API. This tool enables an administrator to configure WinRM and to get data or manage resources. For more information, see the online help provided by the command line Winrm/?.
Winrs.exe
This command line tool enables administrators to remotely execute most Cmd.exe commands using the WS-Management protocol. For more information, see the online help provided by the command line Winrs/?.
Intelligent Platform Management Interface (IPMI) driver and WMI provider
Hardware management through the Intelligent Platform Management Interface (IPMI) provider and driver enables you to control and diagnose remote server hardware through BMCs when the operating system is not running or deployed.
For more information, see the IPMI Provider.
WMI service
The WMI service continues to run side-by-side with WinRM and provides requested data or control through the WMI plug-in. You can continue to obtain data from standard WMI classes, such as Win32_Process, as well as IPMI-supplied data. For more information about configuration and installation required for WinRM, see Hardware Management Introduction.
WS-Management protocol
WS-Management protocol, a SOAP-based, firewall-friendly protocol, was designed for systems to locate and exchange management information. The intent of the WS-Management protocol specification is to provide interoperability and consistency for enterprise systems that have computers running on a variety of operating systems from different vendors.
WS-Management protocol is based on the following standard web service specifications: HTTPS, SOAP over HTTP (WS-I profile), SOAP 1.2, WS-Addressing, WS-Transfer, WS-Enumeration, and WS-Eventing. For more information about the current draft of the specification, see the Management Specifications Index Page.
Working with WinRM
For more information about writing WinRM scripts, see Using Windows Remote Management.
The following table lists topics that provide information about the WS-Management protocol, WinRM and WMI, how to specify management resources such as disk drives or processes.
| Topic | Description |
|---|---|
| Installation and Configuration for Windows Remote Management | The WinRM listener requires configuration on both client and server computers. |
| Windows Remote Management Architecture | Diagram that illustrates the components of WinRM and which components are found on client and server computers. |
| WS-Management Protocol | Description of the public standard WS-Management protocol for remotely sending and receiving management data to any computer device that implements the protocol. |
| Scripting in Windows Remote Management | The WinRM scripting API is similar to the actions of the WS-Management protocol. Data retrieved by scripts is formatted in XML, not objects. |
| Authentication for Remote Connections | WS-Management protocol maintains security for data transfer between computers by supporting several standard methods of authentication and message encryption. |
| Windows Remote Management and WMI | Because WinRM is integrated with Windows Management Instrumentation (WMI), you can obtain WMI data with scripts or applications that use the WinRM Scripting API or through the Winrm command-line tool. |
| Resource URIs | A resource URI is an identifier for a management operation or value. For example, disk drives represent a type of resource. |
| Remote Hardware Management | The IPMI Provider supplies classes and data that describe the baseboard management controller (BMC) hardware management domain, the BMC computer systems in the domain, and the BMC sensors. Other objects represent the BMC System Event Log (SEL) and the messages in the log. |
| Events | You cannot obtain events through WinRM scripting, but you can use the Wevtutil.exe command-line tool to view Event Collector events. |
Applies To: Windows Server 2012 R2, Windows Server 2012
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.
Did you mean…
Did you know that Microsoft Azure provides similar functionality in the cloud? Learn more about Microsoft Azure virtualization solutions. Create a hybrid virtualization solution in Microsoft Azure: |
Role description
The Remote Desktop Services role 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.
Practical applications
Remote Desktop Services allows workers to work anywhere. Some of the key benefits of Remote Desktop Services include:
Unified administration experience – Administer your session and virtual desktop collections, configure your RemoteApp programs, manage your virtual desktops, and add servers to the deployment from one centralized console.
User personalization – User profile disks allow you to preserve user personalization settings across session collections and pooled virtual desktop collections.
Less expensive storage – Pooled virtual desktops can use local storage live migration between host computers. Personal virtual desktops can use storage located on network shares.
Automated pooled virtual desktop management – Deploy and manage pooled virtual desktops centrally by using a virtual desktop template. Any changes, such as application installation or security updates, are installed on the virtual desktop template, and the pooled virtual desktops are then recreated from the virtual desktop template.
New and changed functionality for Windows Server 2012 R2
In Windows Server 2012 R2, 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
For more information about new features and functionality, see What's New in Remote Desktop Services in Windows Server.
New and changed functionality for Windows Server 2012
Remote Desktop Services enables the mobile work force to connect to desktop and applications from anywhere. In Windows Server 2012, Remote Desktop Services includes enhancements in the following areas:
Simplified Virtual Desktop Infrastructure (VDI) deployment and management
Simplified Session Virtualization deployment and management
Centralized resource publishing
Rich user experience with Remote Desktop Protocol (RDP)
The user experience has been enhanced for Remote Desktop Services in Windows Server 2012 in the following ways:
Rich Windows desktop remoting experience
Smooth audio and video playback experience
Rich graphics and video user experience over a WAN
Enhanced device remoting support with USB Redirection for Session Virtualization and VDI
True Multi-Touch and gesture remoting
Email name discovery and subscription to administrator supplied remote resources
RemoteFX virtualized GPU provides DX 11 support
In addition to these areas of enhancement, Remote Desktop Services in Windows Server 2012 introduces a new management console for managing the majority of Remote Desktop Services-related tasks. For more information about new features and functionality, see What's New in Remote Desktop Services in Windows Server.
New Microsoft Remote Desktop Clients
You can use the Microsoft Remote Desktop client to connect to a remote PC and your work resources from almost anywhere. Experience rich interactivity using a remote desktop client designed to help you get your work done wherever you are. For example, you can connect to your work PC and have access to all of your apps, files, and network resources as if you were sitting right in front of your work PC. You can leave apps open at work and then see those same apps using the RD client.
For information about these new features and functionality for Android, iOS, and Mac, see Microsoft Remote Desktop Clients.
Removed or deprecated functionality
For a list of deprecated features, see Features Removed or Deprecated in Windows Server 2012 R2 and Features Removed or Deprecated in Windows Server 2012.
Hardware requirements
Remote Desktop Services requires that the Windows Server 2012 R2 or 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.
Note
Without a RemoteFX virtualized GPU, applications that require DirectX will still work using a built in Hyper-V specific GPU.
Server Manager information
Remote Desktop Services is a server role that consists of several role services. In Windows Server 2012 R2 and Windows Server 2012, the following Remote Desktop Services role services can be installed with this role:
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):
|
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. |
See also
The following table provides additional resources for evaluating Remote Desktop Services.
Content type | References |
|---|---|
Product evaluation | |
Community resources | |
Related technologies |