What's changed: Created AZ-140 Chapter 4 (Domain 3: FSLogix (Profile Container/ODFC/Cloud Cache/app masking); user experience and client settings (clients/device-multimedia redirection/Teams WebRTC Redirector/Universal Print/Intune/RDP properties/session timeouts/Start VM on Connect/personal-desktop assignment); app delivery (application groups desktop/RemoteApp, user assignment, M365 Apps SCA, OneDrive multi-session, App attach dynamic delivery)).
4.2User experience and client settings
Understand choosing/deploying AVD clients, device/multimedia redirection, printing and Universal Print, user settings via Intune/Group Policy, RDP properties, session timeouts, Start VM on Connect, and personal-desktop assignment.
User experience is shaped by which client connects, how local peripherals pass into the session, and what printing/settings/timeouts apply.
4.2.1Clients and redirection
Choose an AVD client (Windows/Web/macOS/mobile) and deploy via Intune, etc. Device redirection passes local drives/clipboard/USB/camera into the session (allow/restrict via host pool RDP properties); multimedia redirection decodes video/calls locally for smoothness. Microsoft Teams should use Teams optimization (media optimization) via the Remote Desktop WebRTC Redirector Service to process audio/video locally for quality.
4.2.2Printing, settings, and connection control
Printing uses Universal Print (cloud print infrastructure, no print server) to print directly from session hosts. Distribute user settings via Intune policies or Group Policy. Tune the experience with RDP properties (redirection/display) and session timeouts (disconnect/logoff grace). Start VM on Connect powers on a stopped session host only when a user connects, cutting idle cost (a separate feature from autoscaling—its purpose is on-demand power-on at first connect). For personal host pools, personal-desktop assignment (automatic/direct) pins users to hosts.
Cues: "local peripherals into the session" = device redirection (controlled by RDP properties). "Teams audio/video optimization" = WebRTC Redirector (Teams media optimization). "cloud printing without a print server" = Universal Print. "power on host only at connect" = Start VM on Connect. Settings via Intune/Group Policy.
Watch the mix-ups: (1) Start VM on Connect (on-demand power-on at connect) vs autoscaling (schedule/load-based scaling). (2) Teams needs WebRTC Redirector optimization, not just installation. (3) Universal Print is cloud printing replacing on-prem print servers. (4) Redirection allow/restrict is set via host pool RDP properties.
4.2.3Section summary
- Device/multimedia redirection via RDP properties; Teams optimized via WebRTC Redirector
- Universal Print = serverless cloud printing; settings via Intune/Group Policy
- Start VM on Connect = power on host at connect to cut idle cost (distinct from autoscaling)
Sign in to track progress — Log in.
Quick check
(just a quick review)Q1. You want better Microsoft Teams audio/video quality in AVD by processing media locally. Which is best?
Q2. You want to print from session hosts via the cloud without an on-prem print server. Which is best?
Q3. You want stopped session hosts to power on only when a user connects, cutting idle cost. Which is best?
Q4. You want to control whether local clipboard/drives pass into the session, per host pool. Which is best?
Q5. You want to centrally distribute user settings (policies) to AVD session hosts via cloud management. Which is best?
Keep track of your progress
The full study guide is free to read. Sign up free to practice with the question bank, track what you have read, review your mistakes, and highlight passages.