User Profiles, App Layering, and Image Management
This domain tests how user state, applications, and images are separated so desktops can be replaced without losing data. It covers FSLogix profiles, profile shares, app layering, golden images, and Frame image versions.
Core rules
- Non-persistent desktops need external profile storage. FSLogix Profile Containers and Office Containers on Nutanix Files SMB shares are common; grant share and NTFS permissions to users and computer accounts as required.
- Size profile shares for concurrent logons and container growth; exclude VHDX/VHD containers from antivirus scanning that locks them; monitor share latency.
- App layering separates the base OS from applications. Validate the layering product with the broker, AHV, and antivirus; test composited images before broad rollout.
- Maintain a golden-image pipeline: patch, generalize, test, version, canary, promote. In Frame, use sandboxes and stack image versions; keep the previous version for rollback.
- Persistent desktops still need backup and patching. Persistence is not a backup strategy.
- Document which data lives in the image, profile, app layer, and user home share; ambiguity causes data loss.
Worked example
A 250-user pool uses FSLogix. Create a Nutanix Files share, set share and NTFS permissions, apply GPO for profile and Office containers, install the FSLogix agent in the golden image, and test with a pilot pool. Update the image in a Frame sandbox, publish a new version, test logon and OneDrive, then promote. Reasoning: profiles stay outside the disposable VM; image versions provide rollback.
Traps
Saving profiles on the desktop system disk; granting Everyone full control; forgetting computer-account permissions; layering an app that conflicts with the base image; updating production without a canary; treating a persistent desktop as backed up.