Windows Server 2012 Remote Desktop Infrastructure

This course covers the redesigned Windows Desktop Infrastructure in Windows Server 2012. It prepares students to deploy Remote Desktop and study for the topics on the 70-415 exam.
Course info
Rating
(107)
Level
Intermediate
Updated
Jun 30, 2014
Duration
3h 35m
Table of contents
Creating a Session-based Deployment
Configuring Remote Desktop Collections
Configuring the Remote Desktop Client
Certificates
Installing Remote Desktop Gateway
Configuring Remote Desktop Gateway
Configuring Remote Desktop Web Access
Description
Course info
Rating
(107)
Level
Intermediate
Updated
Jun 30, 2014
Duration
3h 35m
Description

This course covers the new re-designed Remote Desktop infrastructure introduced in Windows Server 2012. The new installation procedure is covered in depth, along with the redesigned role of the Remote Desktop Connection Broker. We will go through the purpose and installation of the Remote Desktop Gateway, how to create and manage Collections along with Session properties, and configuring the Remote Desktop Client. There is a complete lecture on certificates to provide added insight into how to configure the certificates for multiple roles. The series also includes complete coverage of the Remote Desktop Web Access role including high availability and how to customize the web page.

About the author
About the author

Shadow Farrell has been a technical trainer for twenty years. He has worked in the field in enterprise environments such as AIG and Johnson & Johnson. Mr. Farrell holds many certifications from Microsoft as well as CompTIA and other vendors, and has worked as a Microsoft Certified Trainer for CompUSA, ComputerTraining.com and many other training centers.

Section Introduction Transcripts
Section Introduction Transcripts

Creating a Session-based Deployment
Welcome to Windows Server 2012 Remote Desktop Infrastructure. My name is Shadow Farrell, and in this module we're going to focus on creating a session-based deployment, which means we're going to be using Remote Desktop to connect up to a Remote Desktop Session Host and open a session, or we might choose to go through Web Access and use a remote app, but we're looking at a session-based deployment where users are actually using software on the RD Session Host.

Configuring Remote Desktop Collections
In this video, we're going to take a look at Configuring Remote Desktop Collections. The first thing we're going to take a look at before that is the deployment properties. And the first thing that we're going to see in deployment properties is the Remote Desktop Gateway and where we can set up the Remote Desktop Gateway settings. The purpose of the Remote Desktop Gateway is to act as a middleman. So if we look at a traditional Remote Desktop deployment, the external user would connect through the company's firewall to the connection broker. The connection broker then would refer the client to an RD Session Host. So the RD Session Host is really the first place that the client is going to be challenged for credentials to be authenticated. Well at that point they're already inside your network, which is not necessarily a good thing. So when we have a Remote Desktop Gateway, the client connects through an external firewall, normally the gateway would be positioned in a DMZ or perimeter network, the gateway is going to authenticate the user and make sure that they're allowed to come in through Remote Desktop, then they'll refer the user to the connection broker, which then will pass them on to the session host.

Configuring the Remote Desktop Client
In this module, we're going to take a look at Configuring the Remote Desktop Client. This is the client that comes built in to Windows, and we can tweak it a little bit to customize the user's experience. The first thing that we're going to take a look at is the Display tab. The Display tab lets us set up the display configuration and the color settings.

Certificates
In this module we're going to talk about certificates. Certificates are very important with Remote Desktop because they're used to secure the connection between the RD Gateway and the client. They're also used for the remote desktop web access, so you want to make sure that you have a good understanding of certificates so that you can make sure there won't be any problems with your clients trying to connect. Certificates are used for two purposes, identification and encryption. So let's take a look at identification first. Let's suppose I'm driving down the highway, and as I'm driving down the highway I get pulled over. So the first thing that the police officer is going to ask me for is identification, so I will provide my license, and the officer is going to take that back to the car. Now how does the police officer know that this is really my license? Well most licenses have something like a hologram or something like that, something that can't be duplicated, that's on that license. And the police officer would know, they'd shine their little light on it, they know that that particular hologram or whatever it is that can't be duplicated, means that in fact that license was issued by the state that it says it was issued by. So he's going to look at the hologram and say, yes, this really did come from the state of Rhode Island, and if I trust the state of Rhode Island I can verify that, in fact, this is John D. Pug, or this is Shadow Farrell, I can trust that this is accurate information, and now I've made a positive identification. So in a certificate that's called a digital signature, and a digital signature is some type of a unique mark on an electronic transmission that cannot be forged. So when the certificate is signed with a digital signature, as long as we can verify that signature, like the hologram, we know for sure that indeed this document did come from the source it says it came from. And in that sense, as long as we trust that source we can accept the certificate.

Installing Remote Desktop Gateway
In this module we're going to focus on installing Remote Desktop Gateway. Now Remote Desktop Gateway is important, because if we go with a traditional remote desktop scenario, the external user would connect through the firewall to the connection broker, which would then pass them on to the Remote Desktop Session Host, which means the first place the user gets challenged for credentials is at the Remote Desktop Session Host, at which point they're well inside the company network. So when we deploy Remote Desktop Gateway, this is a server that sits usually in a DMZ or a perimeter network that acts as a middle-man. The external user connects to the Remote Desktop Gateway. They are authenticated by the Gateway, and the Gateway makes sure that they have permissions to access internal resources. Then, once all that's been verified, the Remote Desktop Gateway passes the connection to the Remote Desktop Connection Broker, which in turn connects the client to the Remote Desktop Session Host.

Configuring Remote Desktop Gateway
Welcome to configuring Remote Desktop Gateway. In this module we're going to take a look at everything we really didn't take a look at in Installing. That would be SSL bridging, changing the ports that the RD Gateway uses, messaging, a little bit of a discussion of RD Gateway farms, NAP integration, and then a quick look at Group Policy for configuring the client.

Configuring Remote Desktop Web Access
Hi, my name is Shadow Farrell, and welcome to Configuring Remote Desktop Web Access. In this video we're going to talk about configuring SSL, Single Sign-on, high availability, and even tweaking the Remote Desktop Web Access web page to make it look the way you want it to look.