Memory hook: Replace the host; preserve the profile.
Must remember
- Maintain a versioned golden image with required OS updates, applications and agents. Azure VM Image Builder automates supported builds; Azure Compute Gallery distributes image versions to target regions.
- Generalize and validate images according to the supported process. Keep production release rings and rollback versions; an image update does not automatically patch all existing hosts.
- FSLogix Profile Containers attach a user profile stored in a VHD/VHDX on supported shared storage. ODFC containers can isolate Office-related data for applicable scenarios; application masking controls visibility, not licensing.
- Choose Azure Files or Azure NetApp Files from performance, identity, protocol, availability and cost requirements. Configure both share-level access and filesystem permissions correctly.
- Cloud Cache supports multiple profile storage locations with local caching and its own performance/failure considerations. It is not permission-free replication or a replacement for tested backups.
- Monitor profile attach time, capacity, IOPS, locks and concurrent access. Keep profiles separate from disposable session-host disks and test restores without corrupting active user state.
Choose under exam pressure
| Requirement | Choice and reason |
|---|---|
| Users lose settings when moving between pooled hosts | Implement correctly permissioned FSLogix profile containers. |
| Need consistent host replacements across regions | Versioned images in Azure Compute Gallery with tested regional availability. |
Traps
- A user can pass AVD sign-in and still fail profile storage authentication.
- Copying an actively mounted profile is not automatically a consistent backup.
Active recall
1. What persists a pooled user’s desktop settings?
The correctly attached profile container rather than local host state.
2. Why preserve old image versions?
Controlled rollback and reproducible replacement hosts.
3. Which two permission layers often matter for Azure Files?
Share-level authorization and filesystem ACLs.
4. What can cause temporary profiles?
Failed container access, locks, storage performance or FSLogix configuration issues.
5. Does application masking grant a software license?
No; it controls visibility/access behavior and licensing remains separate.