Deploying RDS 2012 using Standard Deployment


This post shows you how to deploy  RDS using the standard deployment option in Add Roles and Features Wizard.

You can add multiple servers to the configuration but for this demonstration I will be using a single server.

This shows how to install a Session Based deployment which allows users to connect to session collections.

Deployment

PowerShell Deployment:

Load the RemoteDesktop PowerShell Module

import-module RemoteDesktop

Deploy Server Roles via PowerShell

New-SessionDeployment [-ConnectionBroker] <string> [-WebAccessServer] <string> [-SessionHost] <string>
New-SessionDeployment -ConnectionBroker <Server FQDN> -WebAccessServer <Server FQDN> -SessionHost <Server FQDN>

List Servers & Server Roles installed in the RDS deployment:

The following lists all servers and Server Roles in RDS Deployment:

Get-RDServer

The following shows which roles are installed on a single server:

Get-RDServer -ConnectionBroker <Server FQDN>

GUI Deployment

Within the Server Manager, select Add Roles and Features Wizard.

standard deployment1

standard deployment2

Select a session based desktop installation or a virtual machine based desktop deployment.

I have selected a Session based deployment for this demonstration.

standard deployment3

standard deployment4

Select the servers you wish to be Connection brokers and Add the servers from the server pool.

You will need to create a server pool before adding multiple servers.

standard deployment5

standard deployment6

standard deployment7

standard deployment8

standard deployment9

You can now see a basic RDS configuration with the following roles installed, RD connection Broker , Session Host, and RD Web Access.

5 thoughts on “Deploying RDS 2012 using Standard Deployment

  1. I am trying to setup a “classic” style of RDS/Terminal Server, where users will log into the remote desktop and have the applications available to them there (not through Web Access).

    The issue I am running into, is that the WebApps are shown, but when I try to RDP to the DNS Round Robbin (configured to the Brokers/Web Access Hosts) or Single Broker Server, I am not being directed to the Session Hosts and getting not authorized user on the RDP.

    The Domain Users are allowed on the Session Collection

      1. I believe it would be a Desktop Deployment:

        Setup:
        – RDSCB (broker and web access)
        – RDSH (session host)

        I have setup up the session collection with “Domain Users” being allowed access.

        With the setup, I am less concerned with WebApps, but I would like to setup a “classic” style of a Terminal Server (where the user RDP to the session host desktop). But with the setup I have listed above, my user is not able to RDP as he is not granted permissions (even though domain users group has access).

        Attempting to Setup
        RDP Process (users RDP to DNS Round Robbin or Broker name) –> redirect to the Session Host(s).

      2. If you are just wanting a session host with out the connection broker etc you can. have a look a the following article. this does demonstrate a none domain joined deployment but also works on domains as well. With regards to your question around permissions, i would check the permissions and also ensure that the remote desktop group has the users populated. Have you tried a different user to test to see if the issue lye’s with the user in question ?https://ryanmangansitblog.wordpress.com/2013/10/30/deploying-a-rdsh-server-in-a-workgroup-rds-2012-r2/

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s