Memory hook: Publish the right app; redirect only what is needed.
Must remember
- Choose desktop versus RemoteApp delivery according to the user workflow. Create application groups, publish applications and assign users deliberately; verify the executable and dependencies on each eligible host.
- Install applications in the image, deploy with management tooling or use supported App attach packages. App attach separates supported application packaging from the base image but still needs package compatibility and access.
- Microsoft 365 Apps, OneDrive and Teams require supported multi-session configuration. Use the current Teams optimization/media components for the client and session-host combination rather than assuming any desktop installer is sufficient.
- Client choice affects features and transport. Configure device, clipboard, drive, printer and multimedia redirection according to security and usability requirements; Universal Print solves a different layer from arbitrary local printer redirection.
- Use Intune or Group Policy for supported user/session settings. Host-pool RDP properties, session timeouts and personal-desktop assignment influence experience and resource use.
- Start VM on Connect starts an eligible host when needed; it does not replace a complete capacity/scaling strategy. Test the experience with actual client versions and realistic profiles.
Choose under exam pressure
| Requirement | Choice and reason |
|---|---|
| One application is required without a full desktop | Publish a RemoteApp through an assigned application group. |
| Sensitive desktops must not export local files | Restrict appropriate redirection paths and test the actual client behavior. |
Traps
- An app installed on one host is not available on every pooled host.
- Start VM on Connect does not guarantee unlimited immediate capacity.
Active recall
1. What does App attach separate?
Supported application delivery from the base session-host image.
2. Why test Teams optimization?
Media performance depends on supported client, host and optimization components.
3. What controls idle sessions?
Appropriate session timeout and disconnect/logoff policies, coordinated with user requirements.
4. Why distinguish client capabilities?
Redirection, authentication and media features vary by client/platform/version.
5. How verify application publication?
Sign in as an assigned test user and launch the app on representative hosts.