Shulou(Shulou.com)05/31 Report--

This article introduces what is the deficiency of Windows Server 2012 RDS, the content is very detailed, interested friends can refer to, hope to be helpful to you.

Most desktop virtualization administrators will find that Windows Server 2012 Remote Desktop Services (RDS) is the latest version, but there are still some shortcomings.

Microsoft Windows Server 2012 RDS has made some major improvements in the system core platform and its management capabilities, including better virtual desktop distribution and stateless pooling mechanism. In addition, the release of RemoteFX has brought significant improvements to the desktop performance and graphics display capabilities provided through WAN.

But like other platforms, it is important to be aware of some of its shortcomings before deploying RDS 2012 or upgrading the existing stable Windows Server 2008 R2 environment.

Deficiency 1 of RDS 2012: rewriting the remote control function

Since the release of RDS, a very useful feature has been remote control (Remote Control, also known as shadowing if you are more familiar with Citrix). This feature supports remote control of user sessions to complete troubleshooting.

Before including RDS 2008, it followed a very simple logic. The administrator needs to be located at the server to which the user is connected, establish a RDP session on the same server, then right-click the user session on the list of connected users and select Remote Control. Enterprises rely on this feature to troubleshoot user sessions, and even independent software vendors use the same mechanism to provide remote support when users connect to their own tools (such as 2X ApplicationServer, Citrix XenApp, etc.).

With the release of RDS 2012, Microsoft has stripped the feature from the platform, and the official replacement is RA (Remote Assistance). Even if RA does work, its implementation logic for remote control of user sessions is quite different. Under RA, users need to initialize the remote control protocol themselves, which requires some training to complete the creation of the connection.

RDS 2012 deficiency II: the implementation of Connection Broker HA brings new requirements

Another thing to note is the new Connection Broker of RDS 2012 and its highly available HA modules. Connection Broker brings some new features, such as the dual active cluster model to achieve high availability, but you also need to be aware of some of the new requirements.

Remote Desktop Connection Broker for Windows Server 2012 requires SQL database support, as well as appropriate authentication and load balancing mechanisms to support highly available implementations.

RDS 2012 deficiency III: the user interface has changed

You may know that today's Windows 8 uses a fragmented user interface, eliminating the start menu that users have been used to since the days of Windows 95.

Window Server 2012 uses the same interface, which is a challenge for users, including IT personnel. In addition, some features, such as Aero Glass, have been removed from the new interface. If this is a necessary feature for your remote desktop, the deployment and implementation of Windows Server 2012 also faces additional issues that need to be addressed.

RDS 2012 under IV: add-on products may not be compatible

If you run some additional products on RDS, such as 2X Application Server, Citrix XenApp, Ericom WebConnect, or similar products, check the compatibility of RDS 2012 before installing. As of April 2013, most of these products were not compatible with the latest RDS version.

On the shortcomings of Windows Server 2012 RDS what is shared here, I hope the above content can be of some help to you, can learn more knowledge. If you think the article is good, you can share it for more people to see.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.