Your Guide to the Latest Windows Server Product Information
The other day I was in a conversation where I drew the distinction between reliable and robust. I hadn’t really thought about it precisely but when asked to articulate the distinction I said that robust was “reliable across a wide range of conditions”. A lot of what Klaas describes in his blog about RDS reminds me of that definition. Remote Desktop Services in Windows Server 2012, is reliable across a much wider range of conditions. It works better across a wide range of networking configurations, it works better across a wide range of hardware devices and configurations (physical or virtual) and it works better across a wide range of administrative scenarios. Oh yeah, it also adds a bunch of great new features. I think you are going to enjoy what you see here.Klaas Langhout, a Director of Program Management in our RDS team, wrote this blog.--Cheers! Jeffrey
For Windows Server 2012 we listened to our customers and partners and added the most desired features and resolved the top pain points in Remote Desktop Services (RDS). Following a description of RDS, I’ll summarize some of the many dramatic improvements we have made. For those people that are not familiar with 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 to perform their job from the variety of devices that the employee uses. This provides “work anywhere from any device” while ensuring that your control and compliance needs are met. In the previous release, we received consistent feedback that:
Windows Server 2012 addresses each of these issues. For Windows Server 2012 we have made RemoteFX dramatically better over a WAN as well as balancing between scale (host side cost) and reduced bandwidth. Specific improvements include:
The second main improvement area is in overall infrastructure simplification and cost reduction. Cost and complexity is a major roadblock for Virtual Desktop Infrastructure (VDI) and hosted desktop deployments of all sizes. In Windows Server 2012 we made many improvements to address this problem, such as:
The third and final focus area for improvements made in RDS has been in overall management simplification. This is targeted at improving the E2E management experience as well as enabling partner solution creation. Improvements include:
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, Pooled virtual desktop collection, Personal virtual desktop collection to reduce the cost appropriate to the needs of the user. The administration is simplified and platform hooks are provided for partner extension to provide additional value and solutions.Customers are excited about RDS with Windows Server 2012 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 blogs posts to come at the RDS Blog.
- The Entire Remote Desktop Virtualization Team
And how about security improvements? Anything there? Thanks!
Have any changes been made to improve printing in RDS? It's been an issue we've brought up with MS Product support a few times and they have had no answers for us.
A physical GPU can be used in a RD Session Host (RDSH) but can only be used by user sessions where they are using DirectX applications that are not running in full-screen exclusive mode. Given the multi-user nature of RDSH, full-screen exclusive mode DirectX applications are not allowed. This has not changed since Windows Server 2008 R2.
Also, given the multi-user nature of RDSH, it is recommended to configure a physical GPU on RDSH only if all the applications in use by the user sessions are 3D – if there is a mix of GDI, 2D, and 3D applications in the workload (e.g. Office apps are in the mix), you will get better overall server scale/density by continuing to use the default software GPU on the RDSH. As a best practice, it is recommended to test your particular workload with multiple simultaneous users on the RDSH with and without physical GPU to decide which mode to deploy.
To switch the RDSH over to use the physical GPU, please enable the following group policy:
Path: Local Computer Policy\Computer Configuration\Administrative Templates\Windows Components\Remote Desktop Services\Remote Desktop Session Host\Remote Session Environment
Title: Use the hardware default graphics adapter for all Remote Desktop Services sessions
And to verify it is working, you can use dxdiag in the remote session.
Lead Program Manager - RemoteFX, RDS Team
Regarding the question on printing improvements: there are no specific updates to printing in Windows Server 2012 around EasyPrint that was updated in 2008 R2. For more information on EasyPrint see blogs.msdn.com/.../using-remote-desktop-easy-print-in-windows-7-and-windows-server-2008-r2.aspx
Yes, there are new security features made available to Remote Desktop Services administrators in Windows Server 2012. We have plans to blogs in detail about each of them, but for now here are the two highlights:
1) Single sign-on no longer requires a certificate, which greatly simplifies the deployment steps.
2) Clients connecting through Remote Desktop Gateway can now use Kerberos when authenticating to corporate Remote Desktop resources. This enables smart card authentication of remote clients that want to connect via the Gateway to machines requiring Network Level Authentication.
Tristan Scott, RDS Team Program Manager
How easy is it to have 2008R2 session hosts as the backend to a 2012 front end. ie. Use the benefits of the 2012 gateway , connection broker, single sign on etc, but the users running environment is a 2008R2 session host?
Will you need to be running a Windows 8 client to be able to use USB redirection without a GPU in the host? Or will the current RDP clients in Win & XP now work with it?
at our customer site, 3dsmax and autodesk is used. They are very interested in remoteFX which enables vGPU however the games they develop donot perform well on remoteFX.
There are two main challenges a) Performance and 2nd) Compatibility of vGPU WDDM device which is not reconginised by most of the graphic packages.
Performance is in fact disappointing check to see the benchmarks where it lies almost at the bottom: www.videocardbenchmark.net/video_lookup.php
I hope calista technologies acquired by MS to develop this remoteFX is working on increasing it's power further in the upcomming 2012 version.
Any insights on this would be apprecated.
I'm trying to access a Windows Server 2012 RC install via an existing RD Gateway but it just won't connect. All the other 2008 servers are accessible so I guess there's a "gotcha" with the new version that I'm not aware of, nor can I find anything.....any ideas?
Cheers for now
It would great to know which new capabilties work with Windows 7 clients (e.g., single-sign on)
Hey, thanks for this excellent blog, but a question please: Has USB device support been enhanced. Because, even with Windows Server 2008 R2 SP1 with RemoteFX, there's some devices that cannot be redirect like ALL-IN-ONE printers ?
You mention Hyper-V integration. Is there an additional cost for the Hyper-V functionality that provides extra RDS features or is that functionality already included in the OS cost ?
Also, have you reduced prices on RDS CALS (one of the things which prevented our rollout of Terminal Serices/RDS was signficant costs of CALs.)?