Memory hook: Measure logon, manage capacity, recover profiles.
Must remember
- AVD Insights uses Azure Monitor/Log Analytics with required diagnostics and host data collection. Inspect connection success, logon duration, profile attach, host utilization and application responsiveness.
- Scaling plans schedule and adjust supported host-pool capacity. Coordinate breadth/depth-first behavior, session limits, drain mode and user notifications; do not remove hosts with unhandled active sessions.
- Optimize from peak concurrency and application demand. Low average CPU does not prove spare memory, disk or profile-storage performance.
- Patch images and hosts through staged rollout, drain and replacement/update procedures. Preserve a tested prior image and verify user applications after each change.
- DR includes alternate-region host capacity, replicated/available images, profile/data recovery, identity, DNS and assignments. A globally managed control plane does not make a single-region session-host fleet region-resilient.
- Back up profiles, personal desktop data and required images/configuration with suitable policies. Test restore and user reconnection against the RPO/RTO.
Choose under exam pressure
| Requirement | Choice and reason |
|---|---|
| Morning logons are slow | Correlate host capacity, profile storage, identity and logon telemetry. |
| Reduce overnight cost | A tested scaling plan that respects active sessions and minimum required capacity. |
Traps
- A session-host backup alone does not protect profiles stored elsewhere.
- Deallocating hosts saves compute but retained disks and storage still incur cost.
Active recall
1. What does drain mode do?
Prevents new sessions on a host while existing sessions can be handled deliberately.
2. Why measure profile attach time?
Storage/identity problems can dominate perceived logon performance.
3. What must regional DR include besides VMs?
Images, profiles/data, identity, networking, assignments and validated user access.
4. How safely update a pool?
Stage a tested image, control session placement, replace/update hosts and verify before wider rollout.
5. What proves a backup strategy?
Successful recovery of a representative user environment within the target window.