Enabling Modern Work Styles Using Remote Desktop Services in Windows Server 2012 R2
This post is a part of the nine-part series What’s New in Windows Server & System Center 2012 R2 that is featured on Brad Anderson’s In the Cloud blog. Today’s blog post covers Remote Desktop Services (RDS) & Virtual Desktop Infrastructure (VDI) solutions specific to the Windows Server 2012 R2 release and how it applies to Brad’s larger topic of “People-centric IT.” To read that post and see the other technologies discussed, read today’s post: Making Device Users Productive and Protecting Corporate Information.
Hi, I’m Klaas Langhout from the Remote Desktop Virtualization (RDV) team in Windows Server.
I’m happy to be able to provide a description of the key new value that we are bringing to Microsoft VDI and Remote Desktop Services specific to our Windows Server 2012 R2 release. The RDV team focused on areas that would help extend the functionality brought out in Windows Server 2012.
For those who are not familiar with Remote Desktop Services (RDS), it is the workload within Windows Server that enables users to connect to virtual desktops, session-based desktops, and RemoteApp programs. The key value that RDS provides is the ability to centralize and control the applications and data that employees need from the variety of devices that employees use, including bring-your-own-devices (BYOD). This provides “work anywhere from any device” functionality while ensuring that a company’s control and compliance needs are met at reasonable cost.
In Windows Server 2012 we invested in 1) enabling the Remote Desktop Protocol (RDP) to provide a great experience over wide area networks (WANs), 2) an easy-to-administer Remote Desktop and application solution, and 3) dramatic cost savings in the area of storage for a virtual machine-based or session-based desktop deployment.
For Windows Server 2012 R2 we focused on 1) further decreasing storage and network costs of desktop deployments, 2) decreasing the gap between a local app and RemoteApp program experience, and 3) solving specific administration pain points.
Our first focus area was to decrease storage and network-related costs:
Our second focus was improving the user experience by eliminating some of the remaining gaps we had between a RemoteApp program and a local app, and improving our modern Remote Desktop Connection (RDC) client. We have improved the experience when running RemoteApp programs (either from a session or virtual machine) by:
Our single pane of glass admin solution that focused on 1-500 users (PowerShell goes beyond that number) in Remote Desktop Services was made very easy in Windows Server 2012, but our third focus was to solve specific gaps that still existed in that experience:
Remote Desktop Services in Windows Server 2012 provides a single infrastructure, and consistently great remoting experience even over WAN while offering three deployment choices: session collection, pooled virtual desktop collection, and personal virtual desktop collection to allow the appropriate deployment to match user needs and reduce costs. The administration is simplified and platform hooks are provided for partner extension to provide additional value.
In Windows Server 2012 R2 we have further extended the value, focusing on lowering the cost of infrastructure, increasing fidelity of the end user experience (with lower bandwidth), and addressing specific administration requests that we received with Windows Server 2012.
Customers are excited about RDS in Windows Server 2012 R2, and some have already rolled out a pre-release version into production taking advantage of these new benefits! We are proud of the work we have done and look forward to providing more information as we drill into the specific features in blog posts to come in the RDS Blog.
- The Entire Remote Desktop Virtualization Team
To see all of the posts in this series, check out the What’s New in Windows Server & System Center 2012 R2 archive.
Where can I find the updated client for MAC that supports RD Gateway and SmartCard Auth?
On the previous question about an updated Mac RD client, we just announced recently a new Mac (and iOS, Android) client at : blogs.msdn.com/.../microsoft-remote-desktop-apps-for-ios-mac-os-x-and-android-available-for-download.aspx
Yes on RD Gateway support, no smart card on this version. We are tracking feedback provided in the store to determine where to invest.
do anybody know if an MS Windows 2012 Foundation Server could be run as an RD Server without beeing domain member? And if not, are there any options to run an RD server (without buying more windows servers)?
I have exactly the same question as robincm2.
Can you clarify whether or not Server 2012 R2 Remote Desktop Session Host can use a suitable GPU to offload video processing from the main CPU?
Or is there an other hardware can help with this?
We like to offer our users the best remoteFX experience, but without any decent Session Host offload this wil take a really high end CPU for every 2-4 users...
Apart from Windows Server 2012 R2, has anyone tried using other remote support tools such as logmein, GoSupportNow, RHUB, Bomgar etc.? I need to have reviews about it as planning to go-ahead with the best one.
Nice overview. Just one question at this point. We have a number of legacy apps that only run on WinXP or require a older version of Java. We'd like to provide these to our campus as RemoteApps (not appstreaming) so that people don't have to maintain a legacy system just to run one or two apps. Is this possible? To me the catch seems to be being able to offer a remote app that is running on WinXP to clients who are running Win7, Win8 or even MacOSX. Thx!
Oracle Sun Ray server offers Oracle Sun Ray ultra thin clients a Windows 2012 RDP session. With Windows 2012R2 the RDP connection is not established. Are there any backward compatibilty registry entries for Windows 2012R2 so that we can use the other Windows 2012R2 advantages with our Oracle Sun Ray infrastructure or is there any RDP (bind) authentication modification in Windows 2012R2 that can be adjusted to our environment?
Hi Klaas, in the beginning of your article you stated "... Remote Desktop Services (RDS), it is the workload within Windows Server that enables users to connect to virtual desktops, session-based desktops, and RemoteApp programs." by "session-based desktops" do you mean accessing the Windows Server directly using a RD session?
how can we find the( remote desktop session host ) in server 2012R2 plz tell me
Can we get back the client name field in the Connectinos pane? It is very useful when we have to shadow one of multiple sessions with the same username. 2008 server has it and it is a very useful feature for a helpdesk environment. We are replacing a 2003 based Citrix environment and this feature is missing from 2012R2 RDS.
We got the feedback regarding the client name field in the Connections pane - thank you for reporting it. We will consider for a future release.