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
RD Web support for non-IE browsers?
A great summary on all that is new on RDS in Windows Server 2012 !
Excellent improvements for the new RDS of Windows Server 2012!
Looking forward to start using it!
Yes, in Windows Server 2012 end users can access the desktops and applications published as a web page by Remote Desktop Web Access role service via various browsers where, in Windows Server 2008 R2 only IE was supported.
-Klaas Langhout, RDS Team
Remote Desktop can be a lifesaver for fixing problems on servers at remote sites, but what if you forgot to enable the feature before you shipped the server out to Kalamazoo? Enabling Remote Desktop is easy if the server is in front of you: just log on as an administrator, open System in Control Panel, select the Remote tab, and under Remote Desktop select the checkbox labeled "Allow users to connect remotely to this computer."
In W2K8R2, a certificate was required to allow single-sign when using the RDS Connection Broker. When making a connection from a RDP client, a revoke check is performed on the server certificate. When the revoke check is not possible (or fails for whatever reason), an error is shown and the connection is denied.
Has this serious problem been resolved in RDS 2012?
Jon, thanks for the clarification!
How can customers download the Windows Server 2012 pre-release that you mentioned?
@tclark. All the details on how to get the beta are in the blog post from March 1st. blogs.technet.com/.../windows-server-8-beta-available-now.aspx
Hope this helps,
Senior Comminity Lead - Server and Cloud
Could you shed some light on physical GPU usage in RD Session Host?
Is physical GPU supported at all?
How to configure and verify it's working (dxdiag?)?
Alldetails on how to get the beta are in the blog post from March 1st.blogs.technet.com/.../window-server-8-beta-availabal-now.aspx
This is so awesome!