In the previous release, we received consistent feedback that: This provides “work anywhere from any device” while ensuring that your control and compliance needs are met. 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.
Following a description of RDS, I’ll summarize some of the many dramatic improvements we have made.įor 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. Klaas Langhout, a Director of Program Management in our RDS team, wrote this blog.įor 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). I think you are going to enjoy what you see here. Oh yeah, it also adds a bunch of great new features. 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. Remote Desktop Services in Windows Server 2012, is reliable across a much wider range of conditions.
A lot of what Klaas describes in his blog about RDS reminds me of that definition. 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”. (Get-WmiObject -class Win32_OperatingSystem).The other day I was in a conversation where I drew the distinction between reliable and robust. Write-Host -ForegroundColor Green "You are running the following Operating System:" It only checks for the presence of the infrastructure roles and the updates that belong to them.
Here is the script you can use to check your infrastructure roles. It should be reproducable today with fully patched Windows Server 2012 R2 servers. Somehow the behaviour documented in the table at the end of this blog might change with future updates. I had to make a few test rounds and installed the updates on three different servers in my lab to get only the updates that are needed. With a fully patched system the Rollups and Updates listed below are already installed (so forget about them): After that I ran my script and checked what is already installed and what not. I have a fully patched Windows Server 2012 R2 server available for my test with all RDS roles installed on it (without the virtualization role because it cannot be installed side by side with the Session Host role on the same system). The attached script will help you find the installed and missing updates for every RDS role. But if you feel like something is not working as expected go through the updates and the descriptions and check if you could resolve one of your issues by installing the specific update. If everything is running fine, forget this article. You should try to avoid installing all of these updates if you don´t have problems with RDS in your environment. Here are the Microsoft Knowledge Base Articles you need to know if you have RDS running: This blog won´t cover the client updates, just Windows Server 2012 R2. Therefore I´m writing this blog to get you through it and to give you an fast overview of what needs to be installed for every specific infrastructure role. In my eyes it´s not an easy process as it should be. I don´t know if you ever tried to dig into these articles and get all the necessary information.
There are two Knowledge Base articles available for RDS at Microsoft that explain the prerequisites and necessary steps to install these updates. If you are running a Remote Desktop Services Infrastructure (RDS) with Citrix XenApp, VMware View or doesn´t use any third party extension at all you will have to install a bunch of Updates to resolve the most bugs you could run into from a Operating System perspective.