A session collection consists of one or more Remote Desktop Session Host servers. This is a list of requirements to successfully create a collection. This information is not necessarily found in in the 'Before You Begin' section as we will see below. A Windows Server 2012 Remote Desktop Services Virtual-machine based deployment. The Remote Desktop Services Management Pack helps you manage your computers that are running Remote Desktop Services on Windows Server 2012 by monitoring the health of all Remote Desktop Services role services.

• Setup RD Licensing Role On Windows Server 2012 R2 - Virtually ...
• Installing Remote Desktop Services 2012 R2
• Cached
• Windows Server 2012 R2 Remote Desktop
• Setting Up Remote Desktop Services 2012 R2

Virtual machine-based Session Collections

A session collection consists of one or more Remote Desktop Session Host servers.

This is a list of requirements to successfully create a collection. This information is not necessarily found in in the 'Before You Begin' section as we will see below.

Requirements

• A Windows Server 2012 Remote Desktop Services Virtual-machine based deployment.
• A user or user group already existing in Active Directory that you want to have access.
• At least one RD Session Host that is available to be added to the collection.
• Hyper-V Role Installed
• A SYSPREP generalized, 'Generation 1' Hyper-V virtual machine, added to Hyper-V to be used for the template.
• DHCP scope configured to point clients to the AD DNS server.

Setup RD Licensing Role On Windows Server 2012 R2 - Virtually ...

To create a session collection click 'Create session collections' from Server Manager > Remote Desktop Services

Click Next.

The collection name will only be displayed to users coming through Remote Desktop Web Access. This may or may not be utilized in your deployment.

Specify the name you would like to use.

Click Next.

Here we are given two choices for collection type:

Pooled virtual desktops are essentially a group of virtual machines that users are dynamically assigned to use.

Personal virtual desktops are different in that users are assigned to specific machines.

The capabilities offered by each are also different.

For further reading see http://technet.microsoft.com/en-us/library/ee216741.aspx

Important: A virtual machine should not be both a member of a virtual desktop pool and assigned to a user as a personal virtual desktop.

Note: A virtual machine in a virtual desktop pool can be configured to be automatically restored to its original state after the user logs off. Any changes that a user made while logged on are lost. For more information, seehttp://go.microsoft.com/fwlink/?LinkId=143453.

For this collection we will do aPooled virtual desktop collection.

Leave 'Automatically create and manage virtual desktops'Checked and click Next.

Here we select our virtual-machine template that we made available earlier. Click Next.

Note: If the template selected is not a Generation 1 Hyper-V Virtual machine, or has not been sysprepped with the /generalize option, you will receive one of the following errors.

Here we may provide an answer-file for configuration if desired. For this demonstration we will simply provide the information needed.

Click Next.

Select the appropriate time zone to be used for the virtual machines in the pool, and the organizational unit you want them placed in Active Directory. The VM's will be automatically joined to the domain selected below. It is important that the permissions needed for the specified OU are added for the user creating this collection.

Select the domain, and OU if desired, and click Next.

Here we select the User Groups we wish to allow to connect to the VM collection we are creating. We also need to specify how many Virtual Desktops we want to be generated, and the prefix and suffix for naming convention.

Specify desired information and click Next.

The Virtual Desktop Storage is simply where the generated VM's will be physically stored. Here we have selected to store them on the RD Host they are created on.

We have also opted to have their states roll back to their original state when the user logs off.

Specify desired settings and click Next.

User profile disks store profile settings and data in a central location. Since we have a single server solution, we have stored them on one of our local hard drives. These may be stored on a network share.

Specify desired location and click Next.

On the Confirmation summary screen click Create.

The session collection will now be created, VM's or otherwise called Virtual Desktops will be generated and added to hyper-v as well as joined to the domain that was specified. This process can take quite some time and is determinate upon how many VM's were chosen to create.

Below we see our Collection has been created, and 2 Virtual desktops added.

Here we see the VM's named, and added to hyper-v. They can be managed as regular Hyper-V virtual machines as far as adding resources, etc..

Finally, if we open a web browser and connect to our server we will see our collection available for connection.

This can be done by typing https://SERVERNAME/RDWeb.

Remote Desktop Services (RDS) in Windows Server 2012 is Microsoft’s VDI (Virtual Desktop Infrastructure) offering. RDS formerly known as Terminal Services (TS) provides session-based virtual desktops, virtual-machine based virtual desktops and applications to end users. To be able to use these features, you must install Remote Desktop Services in Windows Server 2012 or 2012 R2. So, in this post I will show steps to install Remote Desktop Services in Windows Server 2012.

Install Remote Desktop Services in Windows Server 2012

The diagram below shows the scenario for this post. The network consists of one domain controller and one RDS server.

Log on to RDS server (MBG-RDS01). Open Server Manager. Click Add Roles and Features.

Click Next on Before you begin page. Choose installation type as Remote Desktop Services installation. Click Next.

As you can see below there are two ways of installing RDS services in Server 2012. They are quick or standard. In quick deployment option, three of the required RDS services are installed on single server. The three services are, RD Session Host, RD Connection Broker and RD Web Access. Similarly, the quick installation also creates a collection and publishes some RemoteApp programs. Here, I will install quick deployment option. If you wish to separate each RDS components then you can choose standard deployment option. Choose Quick Start as Deployment Type and click Next.

Deployment Scenario can also be either virtual machine-based or session-based. Here, I will choose session-based. Click Next.

Under Server Selection page, the current server will be automatically added as shown below. Click Next.

Review the installation options. Check, Restart the destination server automatically if required option. Click Deploy.

The installation will now begin. The server will reboot automatically. After the reboot, log back in, you can see the installation has completed successfully. Click Close.

Now, let’s verify the installation. Open Server Manager. Click Remote Desktop Services on the left pane. You can see the RDS deployment Overview as shown below. As we can see, RD Web Access, RD Connection Broker and RD Session Host have been installed. If you want applications or desktop sessions to be accessed from the Internet then you have to install RD Gateway. Similarly, You must install RD Licensing to activate RDS server.

You can also view installed applications. Under Collections, click QuckSessionCollection which is just a collection named created by Quick Deployment installation option. As you can see, calculator, paint and wordpad applications have been published.

To access those applications, open web browser and type URL of RD Web Access server. Type username and password and log on the server as shown below. You can also customize the look of RD Web Access page.

You can view the published applications below. Double-click to open any application. I have double-clicked calculator.

Accept the certificate warning. The application will open as shown below.

Installing Remote Desktop Services 2012 R2

So in this way you can install RDS in Windows Server 2012 using Quick Deployment option. You can now install certificates, publish required apps, publish session-based desktops, customize RD Web Access, and so on.

Cached

Windows Server 2012 R2 Remote Desktop

Setting Up Remote Desktop Services 2012 R2

• Install Exchange 2019 in Windows Server 2019 - November 28, 2020
• Why Backup your Microsoft Office 365 - November 27, 2020
• What’s New in VMware vSphere 7 - September 18, 2020