Create a Remote Desktop Services collection for desktops and apps to run
Applies To: Windows Server (Semi-Annual Channel), Windows Server 2016
Use the following steps to create a Remote Desktop Services session collection. A session collection holds the apps and desktops you want to make available to users. After you create the collection, publish it so users can access it.
Before you create a collection, you need to decide what kind of collection you need: pooled desktop sessions or personal desktop sessions.
- Use pooled desktop sessions for session-based virtualization: Leverage the compute power of Windows Server to provide a cost-effective multi-session environment to drive your users’ everyday workloads
- Use personal desktop sessions for to create a virtual desktop infrastructure (VDI): Leverage Windows client to provide the high performance, app compatibility, and familiarity that your users have come to expect of their Windows desktop experience.
With a pooled session, multiple users access a shared pool of resources, while with a personal desktop session, users are assigned their own desktop from within the pool. The pooled session provides lower overall cost, while personal sessions enable users to customize their desktop experience.
If you need to share hosted applications that are graphics-intensive, you can combine personal session desktops with RemoteFX vGPU configured for graphics accelerations. Alternatively, you can combine personal session desktops with the new Discrete Device Assignment (DDA) capability to also provide support for hosted applications that require accelerated graphics. Check out Which graphics virtualization technology is right for you for more information.
Regardless of the type of collection you choose, you'll populate those collections with RemoteApps - programs and resources that users can access from any supported device and work with as though the program was running locally.
Create a pooled desktop session collection
- In Server Manager, click Remote Desktop Services > Collections > Tasks > Create Session Collections.
- Enter a name for the collection, for example ContosoAps.
- Select the RD Session Host server you created (for example, Contoso-Shr1).
- Accept the default User Groups.
- Enter the location of the file share you created for the user profile disks for this collection (for example, \Contoso-Cb1\UserDisksr).
- Click Create. When the collection is created, click Close.
Create a personal desktop session collection
Use the New-RDSessionCollection cmdlet to create a personal session desktop collection. The following three parameters provide the configuration information required for personal session desktops:
- -PersonalUnmanaged - Specifies the type of session collection that lets you assign users to a personal session host server. If you don't specify this parameter, then the collection is created as a traditional RD Session Host collection, where users are assigned to the next available session host when they sign in.
- -GrantAdministrativePrivilege - If you use -PersonalUnmanaged, specifies that the user assigned to the session host be given administrative privileges. If you don't use this parameter, users are granted only standard user privileges.
- -AutoAssignUser - If you use -PersonalUnmanaged, specifies that new users connecting through the RD Connection Broker are automatically assigned to an unassigned session host. If there are no unassigned session hosts in the collection, the user will see an error message. If you don't use this parameter, you have to manually assign users to a session host before they sign in.
You can use PowerShell cmdlets to manage your personal desktop session collections. See Manage your personal desktop session collections for more information.
Publish RemoteApp programs
Use the following steps to publish the apps and resources in your collection:
- In Server Manager, select the new collection (ContosoApps).
- Under RemoteApp Programs, click Publish RemoteApp programs.
- Select the programs you want to publish, and then click Publish.
We'd love to hear your thoughts. Choose the type you'd like to provide:
Our feedback system is built on GitHub Issues. Read more on our blog.