How to Publish a Windows Application as RemoteApp
Applies to: Windows Server 2019, 2022 and 2025.
RemoteApp presents an approved program instead of a full desktop. The application must be installed consistently on every Session Host in the collection.
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 networkmanager.info.
Prerequisites
- Confirm application vendor supports RDS.
- Install the same version and path on every host.
- Create the RDS collection.
- Test dependencies, file associations and licensing.
Procedure
Step 1: Review collection
Confirm hosts and health.
Get-RDSessionCollection -ConnectionBroker 'rdcb01.corp.example'Step 2: Verify application path
Check the executable on each Session Host.
Test-Path 'C:\Program Files\BusinessApp\BusinessApp.exe'Step 3: Publish RemoteApp
Create a unique alias.
New-RDRemoteApp -CollectionName 'Business Applications' -DisplayName 'Business App' -FilePath 'C:\Program Files\BusinessApp\BusinessApp.exe' -Alias 'businessapp' -ConnectionBroker 'rdcb01.corp.example'Step 4: Assign users
Restrict collection access to approved AD groups.
Step 5: Test full workflow
Validate launch, printing, file access and sign-out from a standard client.
Verification
Query published applications and launch through RD Web or the approved feed.
Get-RDRemoteApp -CollectionName 'Business Applications' -ConnectionBroker 'rdcb01.corp.example'Rollback
Use Remove-RDRemoteApp for the collection and alias after confirming no feed or user workflow depends on it.
Licensing and security notes
Publishing does not change the application’s own named-user, device or concurrent licensing obligations.
