Publishing RDS RemoteApps as SDE vApps
The article explains how Windows administrators can publish applications like Word and Excel as RemoteApps in an RDS collection, allowing them to appear as one-click tiles in SDE Remote. It includes steps for setup, values needed, and testing.
For the client's Windows administrators: publish Word, Excel or a line-of-business app in the RDS collection, then hand us three values so it appears as a one-click tile in SDE Remote.
1. How it works
A RemoteApp vApp is an RDP connection to the RDS farm that asks for one published program instead of a desktop. From the SDE Remote app it opens as a normal window on the user's taskbar (seamless), and several RemoteApps open side by side in one session. In a browser it opens in the tab. Traffic goes through the SDE gateway, as for desktops; nothing on the RDS farm is published to the internet.
2. On the RDS farm
- In Server Manager → Remote Desktop Services → Collections → <collection> → RemoteApp Programs → Publish RemoteApp programs, publish the program. Or in PowerShell:
New-RDRemoteApp -CollectionName "Office" -DisplayName "Word" -FilePath "C:\Program Files\Microsoft Office\root\Office16\WINWORD.EXE" -ConnectionBroker rdcb.corp.local - Note the program's alias (Properties → General → Alias, or
Get-RDRemoteApp -CollectionName Office | ft DisplayName, Alias), e.g.WINWORD. - Make sure the users (or their group) are allowed on the collection (User Groups).
- Profiles: use FSLogix or User Profile Disks; Office needs a persistent profile.
3. Microsoft Office
- Install Microsoft 365 Apps with Shared Computer Activation (users' licences must include it: E3/E5, Business Premium, A3/A5), or Office LTSC volume licensing.
- RDS Client Access Licences (per user or per device) are needed for every user.
4. Values for the SDE administrator
| Value | Example | Where to find it |
|---|---|---|
| RD Connection Broker (or a single session host) | rdcb.corp.local | Server Manager → RDS → Overview |
| Load-balance info (routing token) | tsv://MS Terminal Services Plugin.1.Office | The collection's .rdp file from RD Web Access (loadbalanceinfo:s:) |
| Alias of each program | WINWORD, EXCEL | Step 2 |
| Domain (NetBIOS) | CORP | |
| The AD group(s) that should get each app | Office-Users |
5. Creating the vApp (SDE administrator)
sde-vapps admin page → vApps → New vApp → RDS RemoteApp: RDS farm = the Connection Broker, RemoteApp alias = ||WINWORD, load-balance info, RDP domain, sign-in = their own account (AD), NLA, who gets it. One vApp per program. USB redirection is available from the SDE Remote app.
6. Testing
- From a Windows PC inside the network,
mstscwith the collection's RemoteApp.rdpfile opens Word (proves the farm side). - The vApp's tile in a browser opens Word in the tab.
- From the SDE Remote app, Word opens as its own window; opening Excel too gives a second window in the same session.
- Office shows the user as signed in and licensed (Shared Computer Activation).
person people found this useful.
