Skip to content

How to Create an RDS Session Collection with PowerShell Print

  • 0

Applies to: Windows Server 2019, 2022 and 2025.

A session collection groups Session Hosts and defines the user desktop environment. Build it only after Connection Broker and Session Host roles are healthy.

RDS deployments require Windows Server licensing, the correct RDS CAL model and secure access design. Administrative RDP sessions are not a replacement. Review managed RDS hosting at managed Windows VPS hosting.

Prerequisites

  • Deploy RD Connection Broker.
  • Join Session Hosts to the domain and RDS deployment.
  • Create an authorized AD access group.
  • Confirm licensing and profile design.

Procedure

Step 1: Load the module

Use an RDS management server.

Import-Module RemoteDesktop

Step 2: Review deployment

List role servers.

Get-RDServer -ConnectionBroker 'rdcb01.corp.example'

Step 3: Create collection

Replace server and collection names.

New-RDSessionCollection -CollectionName 'Business Applications' -SessionHost 'rdsh01.corp.example' -ConnectionBroker 'rdcb01.corp.example'

Step 4: Set access group

Assign an approved domain group through collection properties or supported cmdlets.

Step 5: Configure session limits and profiles

Define idle, disconnected, redirection and profile settings.

Verification

Query collections and session hosts.

Get-RDSessionCollection -ConnectionBroker 'rdcb01.corp.example'
Get-RDSessionHost -CollectionName 'Business Applications' -ConnectionBroker 'rdcb01.corp.example'

Rollback

Drain users, remove Session Hosts and use Remove-RDSessionCollection only after RemoteApps and profile dependencies are removed.

Licensing and security notes

Collection design is separate from CAL licensing and from application vendor licensing.

Official references

For a hosted environment with setup and onboarding, explore our managed Windows VPS plans.


Was this answer helpful?

« Back