This is because registration kiosks are used by multiple customers who do not need to personalize their desktops or applications, and who only need to perform a specific task such as registering or checking in. Non-persistent desktops can provide a secure and consistent user experience for these customers, and also reduce management overhead for the organization.

Comprehensive and Detailed Explanation From Exact Extract of Nutanix End User Computing documents:

According to Nutanix and Microsoft Best Practices for Non-Persistent VDI images:

Policy Setting: The Group Policy setting " Allow Automatic Updates immediate installation " should be set to Disabled .

Reasoning: In a non-persistent environment, desktops revert to their base state upon reboot. Allowing automatic updates to install immediately during a user session consumes system re sources (CPU/IOPS) and any changes made are discarded when the user logs off and the VM reboots.

Correct Management: Updates should be applied solely to the Master/Gold Image during a maintenance window. Once the master image is updated and sealed, it is redeployed to the pool. Disabling immediate installation prevents the " Windows Update " service from attempting to patch transient clones unnecessarily.

A mandatory profile is a type of roaming profile that is read-only and does not save any changes made by users during their sessions. A mandatory profile can be applied to a group of users who share a common desktop environment and do not need to customize their settings or preferences.

A mandatory profile can ensure that a group of base settings are applied to Citrix-based VDI users at each logon, regardless of any changes they make during their sessions. A mandatory profile can also improve performance, security, and consistency of the VDI environment.

To use a mandatory profile with Citrix Virtual Apps and Desktops, you need to create a template profile on a reference machine, rename its NTUSER.DAT file to NTUSER.MAN, and copy it to a network share.  Then you need to configure Profile Management policies or Active Directory settings to point to the network share location for your users 2 .

Nutanix Prism Central includes Behavioral Learning and Efficiency reporting tools designed to identify inefficient resource usage.7

To verify if VMs are " using less than their configured memory " (wasted resources), the administrator should view the Over-provisioned VMs list within the Efficiency widget. Nutanix defines an " Over-provisioned VM " as one that is sized with more resources (CPU/Memory) than it actually consumes based on historical performance data. 8 This list explicitly identifies these VMs, allowing the administrator to right-size them and reclaim cluster resources, whereas Task Manager (Option A) is manual/individual, and Capacity Runway (Option D) focuses on global cluster storage/resource exhaustion time rather than individual VM efficiency.

https://next.nutanix.com/community-blog-154/new-x-play-actions-in-prism-central-2021-7-40005

The Prism Central Playbook Action is a tool that allows you to automate tasks based on triggers, such as events, alerts, or webhooks. You can define a series of actions (called a playbook) that perform operations on your infrastructure, such as adding or reducing resources on a VM 2 .

To use the Playbook Action for VMs, you need to meet some prerequisites, such as:

The Prism Central version must be 2020.11 or later.

The AOS version must be 5.15 LTSR or later.

The hypervisor must be AHV or ESXi.

The VMs must have Nutanix Guest Tools (NGT) installed and enabled 3 .

One of the possible reasons why the Playbook Action is no longer being triggered is that  the virtual desktop CPU Usage alerts were not cleared . According to the Prism Central guide 3 , “If an alert has been triggered once and has not been cleared yet, then it will not trigger any action again until it has been cleared”. Therefore, if the CPU Usage alert remains active for a virtual desktop, it will prevent the Playbook Action from adding more vCPUs to it.

Comprehensive and Detailed Explanation From Exact Extract of Nutanix End User Computing documents:

Based on the provided exhibit and Nutanix Prism Central administration guides:

Interface Identification: The screenshot displays the Prism Central web console, indicated by the " Infrastructure " dropdown menu in the top navigation bar (Prism Element uses a different layout). The user is currently in the Images dashboard (Infrastructure > Compute > Images).

Updating Image Metadata: To rename an image (or modify its description/type) in Prism Central, the standard workflow is to select the target image (as shown with " Windows-11 " selected) and use the Actions menu.

The " Update " Action: Within the Actions dropdown menu, the correct option to modify existing settings is Update . Clicking Actions - > Update opens the " Update Image " dialog box, where the Name field is editable.

Incorrect Options:

A & D (CLI): These are incorrect because image renaming is fully supported in the UI; the CLI (acli or ncli) is available but not mandatory ( " must " is the error).

C (Clone): Cloning an image creates a duplicate copy. While this could result in a new image with a new name, it is an inefficient workaround rather than the direct solution for simply renaming an existing image.

To resolve issues with persistence (retaining settings) and login performance in a non-persistent VDI environment, the industry standard and Nutanix-recommended solution is to Enable a Virtual Disk-based profile solution (such as FSLogix Profile Containers or Citrix Profile Management containers).

Retaining Settings: Unlike local profiles (wiped on reboot) or mandatory profiles (read-only), containerized profiles capture all user writes and persist them to a VHD/VHDX file on a file share (e.g., Nutanix Files).

Speed: Microsoft Roaming Profiles (Option A) require copying files over the network at login, causing slowness. Virtual Disk-based solutions mount the profile disk instantly over the network, making the login process nearly as fast as a local profile while ensuring data persistence.

Frame  is a cloud-native desktop-as-a-service platform that delivers virtual apps and desktops from multiple public clouds 1 . Frame allows administrators to manage various components of their cloud accounts easily from the Frame console 1 .

A  cloud account  is a logical grouping of resources that are associated with a specific cloud provider (such as AWS, Azure, or Google) and region 1 . A cloud account can have multiple virtual networks, master images, and instance types that can be used to create and run virtual apps and desktops 1 .

To configure AWS, Azure, and Google accounts within Frame, an administrator needs to go to the  Cloud Accounts  section of the Frame console 1 . There, the administrator can add new cloud accounts or edit existing ones by providing the required credentials and settings for each cloud provider 1 2 .

https://docs.frame.nutanix.com/platform/infrastructure/byo/cloud-accounts/

Comprehensive and Detailed Explanation From Exact Extract of Nutanix End User Computing documents:

According to the installation guide for the Nutanix AHV Plug-in for Citrix :

Plugin Registration: The Nutanix AHV plug-in functions as a Hardware Compatibility Layer (HCL) plugin within the Citrix architecture. This allows the Citrix Provisioning (PVS) Streamed VM Setup Wizard to communicate with the AHV hypervisor.

Service Restart: After installing the plug-in on the PVS Console machine (or the DDC where the wizard is being run), the administrator must restart the specific Citrix services that load these HCL plugins. The Citrix Remote HCL Server service (often associated with the proxying of hypervisor calls in PVS/DDC environments) must be restarted to register the new Nutanix connection type.

Resolution: Without restarting this service, the PVS wizard cannot enumerate the Nutanix AHV connection or resources, rendering the integration unusable until the service reload picks up the new plugin dlls.