Nutanix Frame and Xi Frame Desktop-as-a-Service
This domain tests Frame/Xi Frame as Nutanix's desktop-as-a-service offering: terminology, tenancy, publishing workflow, entitlement, persistence, and operational boundaries. Xi Frame is the older brand; current material generally says Frame.
Core rules
- Frame Console is the administrative UI. A Frame account is the administrative and billing boundary; organizations can delegate administration; cloud accounts supply the compute credentials.
- A stack defines the image and runtime configuration. Pools publish stacks to users; a pool can be persistent or non-persistent and can autoscale.
- Users launch through Frame App or an HTML5 browser. The Frame Gateway brokers and streams; do not expose session hosts directly to the internet.
- Sandboxes are temporary test instances used to update an image. Publish a new image version, test it in a canary pool, then move production.
- Entitlements can come from local Frame users or identity-provider groups; use SSO/MFA at the IdP. Utility servers handle supporting roles, not user sessions.
Worked example
A department needs 80 Windows desktops only during business hours, with a new application next month. Create a stack from the current image, add the app in a sandbox, publish a new version, create a small test pool, validate logon and app behavior, then update the production pool. Set autoscale minimum/maximum and schedule shutdown outside hours. Reasoning: image changes are versioned; testing before production protects users; autoscale controls cost.
Traps
Editing a production image in place; publishing to all users before testing; confusing stacks with pools; forgetting cloud-account capacity limits; using persistent pools for transient task workers; assuming Frame removes the need for profile storage.