How To Install Web Deploy On Windows Server 2012

How to install Microsoft RDS in Windows Server 2012

When yous're set to install Microsoft RDS, keep an heart on each component. Some are mandatory in Windows Server 2012 and others aren't.

If yous desire to apply Microsoft RDS to give users remote admission to desktops and applications, you must know how to install information technology.

Installing Microsoft Remote Desktop Services (RDS) starts with understanding each of its components. In part 1 of this series, I explained the RDS roles and what each of them does. Before breaking downwards how to install RDS, let's review the components:

Remote Desktop (RD) Virtualization Host: Hosts virtual machines

RD Session Host (RDSH): Hosts RemoteApp published applications or session-based desktops.

RD Connection Banker (mandatory): Connects and reconnects users to virtual desktops, RemoteApp published applications and session-based desktops. Distributes load among RD Session Host servers in a session collection.

RD Web Access (mandatory): Allows users to admission RemoteApp and desktop connection via the Start menu on Windows 8, Windows vii or via the Web browser.

RD Gateway (optional): Provides Internet-connected devices access to virtual desktops, RemoteApp published apps and session-based desktops on internal network.

RD Licensing (mandatory): Manages licenses required to connect to RD Session Host collections or virtual desktop collections.

Choosing an RDS installation method

You tin install all the roles from a unmarried server using the Microsoft RDS tool via the new Server Managing director in Windows Server 2012. Here'south how:

Open the Server Manager Console and select option iii: "Add other servers to manage"
Add the servers you lot want to deploy Remote Desktop Services to
In the Server Manager Console, select option two: "Add roles and features"
Select "Remote Desktop Services installation"

And then, install RDS in one of two ways:

Standard deployment. With this method, you deploy Microsoft RDS roles to multiple servers. For typical production deployments, choose a standard deployment that allows y'all to install each role service separately on separate servers if desired.

If you select a Standard deployment, you will be prompted to cull which server(south) you would similar to deploy the RDS role services to. For a typical RDS installation where high availability and security are of import, you should deploy each component to a dedicated server.

Quick Offset. With Quick Showtime, you install RDS role services onto a unmarried server. This road is unremarkably reserved for proof-of-concepts or very small deployments.

If yous cull Quick Start, you lot volition be asked for 1 server to deploy the RD roles to.

Determining your deployment blazon

The side by side step is to select the type of RDS deployment you want to practise. Here's where the first 2 RDS roles come in. In that location are virtual machine (VM) based deployments (RD Virtualization Host) and session-based desktop deployments (RDSH).

To deploy Windows 7 virtual desktops, for instance, choose the VM-based deployment, and the wizard will install the Virtualization Host. To deploy RemoteApp published application or session-based desktops, choose the session-based desktop deployment, and the wizard will install the RDSH.

You can deploy both components, but the wizard only allows you to choose one or the other at 1 time. You will have to run the wizard over again to install both RDSH and RD Virtualization Host.

Based on which installation method you chose, the following function services are and so deployed to their servers: RD Connexion Broker, RD Web Access, and either RD Virtualization Host or Remote Desktop Session Host.

After the installation is consummate, you lot can choose to add RD Gateway and RD Licensing roles to the environment through the Overview screen of the Microsoft RDS Console.

You can also use that screen to install more RDS roles after the initial wizard is complete within the Windows Server 2012 Server Manager console. Right-clicking on whatsoever of the components allows you to add or remove additional roles or servers for high availability.

For loftier availability with RD Web Access and RD Gateway, add two or more servers and apply DNS round robin, Windows Network Load Balancing or a third-party load balancing tool. High availability for the RD Connexion Broker is also improved in Windows Server 2012 Remote Desktop Services.

Next Steps

Role one: Breaking down RDS roles

What'due south remote access?

Simplifying VDI deployment with RDS

What a VMware pro thinks of RDS and RemoteFX

Quiz: How much do you lot know nearly Windows Server 2012 RDS?

Dig Deeper on Virtual desktop delivery tools

Remote Desktop Session Host (RDSH)

Past: Margaret Jones
Windows Server 2019 RDS updates a benefaction for remote work needs

Past: Dan Franciscus
Remote Desktop Services (RDS)

By: Jack Madden
Clear the confusion around Microsoft RDS

By: Robert Sheldon