Since we just created this collection, it defaults to Remote Desktop for the resource type. In the Properties section we can view and edit the properties of the collections. Go ahead and highlight the new collection and let’s take a look at our options. On the confirmation screen, confirm your settings and click create.īack in Server Manager, we now see our collection. Stay tuned for an upcoming article on Profile Disks. Uncheck the Enable user Profile Disks checkbox and hit next. For this example we will disable Profile Disks. On the User Profile Disks screen, we can enable and configure Profile Disks for the collection. The group is called demolab\RemoteApp Office Apps. Since I’ve already created a specific security group for this collection, we will go ahead and add the group. For this example, you can leave domain users. As a good practice, a specific security group should be created and assigned for each of the collections. To make things easy, it defaults to Domain users. We will now need to add the user group(s) which will have access to the collection. For this example, we will be adding RDSH01. On the Specify RD Session Host servers screen, we can add RD session host servers which will be part of our collection. On the next screen, we will name the new collection. On the Before you Begin screen, click next. Highlight “Collections”, then on the right hand side, click on the “tasks” drop down and select the option “Create Session collection”. In the following steps, we will go through the process of creating a new collection and publishing some RemoteApp programs. The published desktop will require its own collection.
#CANNOT FIND THE MIXER PROGRAM SNDVOL32 R WINDOWS 7 KEYGEN#
One thing to note is you cannot publish a desktop to an existing collection which has already been configured for RemoteApps. You would simply create a new collection, add the servers which will be providing the session desktop and publish them to the proper user group(s). This is the same if you wanted to provide users with a session host desktop. If we wanted to publish the Office applications across the 5 RD session host servers, we would first create a collection that included all 5 servers and publish the Office apps accordingly. For instance, let’s say we had a group of 5 RD session host servers which all have Office 2013 installed and are configured the same way.
So think of collections as something similar to an application silo. These can be RemoteApp programs or Session Host and VDI desktops. Collections give you the ability to group a set of RD Session Host servers with a common set of applications and publish them to users.
On the left column you will see a new node called Collections. Let’s open Server Manager and look at our farm. Now with the farm built, let’s take a look at the changes and the process of publishing RemoteApp programs and session-based desktops in Server 2012 / 2012 R2. In a previous article, we went through the steps of deploying a 2012 / 2012R2 Remote Desktop Services (RDS) farm.
0 kommentar(er)
