windows server 2012 r2 remote desktop services web access

#WINDOWS SERVER 2012 R2 REMOTE DESKTOP SERVICES WEB ACCESS WINDOWS#

Here we see the VM's named, and added to hyper-v.

This process can take quite some time and is determinate upon how many VM's were chosen to create.īelow we see our Collection has been created, and 2 Virtual desktops added. 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. On the Confirmation summary screen click Create. Since we have a single server solution, we have stored them on one of our local hard drives. User profile disks store profile settings and data in a central location. We have also opted to have their states roll back to their original state when the user logs off. Here we have selected to store them on the RD Host they are created on. The Virtual Desktop Storage is simply where the generated VM's will be physically stored. Specify desired information and click Next. We also need to specify how many Virtual Desktops we want to be generated, and the prefix and suffix for naming convention. Here we select the User Groups we wish to allow to connect to the VM collection we are creating. Select the domain, and OU if desired, and click Next. It is important that the permissions needed for the specified OU are added for the user creating this collection. The VM's will be automatically joined to the domain selected below. 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. For this demonstration we will simply provide the information needed. Here we may provide an answer-file for configuration if desired. 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 select our virtual-machine template that we made available earlier. Leave ' Automatically create and manage virtual desktops' Checked and click Next. įor this collection we will do a Pooled virtual desktop collection. Any changes that a user made while logged on are lost. 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. 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. The capabilities offered by each are also different. Personal virtual desktops are different in that users are assigned to specific machines. Pooled virtual desktops are essentially a group of virtual machines that users are dynamically assigned to use. Here we are given two choices for collection type: This may or may not be utilized in your deployment. The collection name will only be displayed to users coming through Remote Desktop Web Access. To create a session collection click ' Create session collections' from Server Manager > Remote Desktop Services DHCP scope configured to point clients to the AD DNS server.A SYSPREP generalized, 'Generation 1' Hyper-V virtual machine, added to Hyper-V to be used for the template.

At least one RD Session Host that is available to be added to the collection.

A user or user group already existing in Active Directory that you want to have access.

#WINDOWS SERVER 2012 R2 REMOTE DESKTOP SERVICES WEB ACCESS WINDOWS#

A Windows Server 2012 Remote Desktop Services Virtual-machine based deployment.This information is not necessarily found in in the 'Before You Begin' section as we will see below. This is a list of requirements to successfully create a collection. Virtual machine-based Session CollectionsĪ session collection consists of one or more Remote Desktop Session Host servers. This is a guide to configuring Remote Desktop virtual machine-based session collections in Windows Server 2012 & 2012 R2.

Windows server 2012 r2 remote desktop services web access