On FusionAccess, if a full copy VM cannot be re-assigned after being unassigned, which of...

According to the Huawei HCIA-Cloud Computing technical guidelines for FusionAccess Service Provisioning, assignment types dictate the persistence and reusability of virtual desktops. The scenario described—where a VM cannot be re-assigned after being unassigned—points specifically to the "Assign a Computer to a User" (Single User/Static) assignment type.

In a "Single User" (1:1) assignment model, a permanent bond is created between a specific user and a specific Virtual Machine. This is the hallmark of Full Copy desktops used for persistent work environments. When an administrator "unassigns" a user from such a desktop, the VM is essentially "locked" to the user's previous data and profile settings to prevent data leakage or configuration contamination. In many Huawei VDI security policies, a VM that was once statically assigned to an individual contains personalized information that is not automatically wiped. Therefore, it cannot be simply "re-assigned" to another user without a manual cleanup or deletion and re-provisioning process.

In contrast, "Pooled" or "Multiple User" (1:N) assignments are designed for reusability. In those modes, once a user logs off or is unassigned, the VM returns to a common pool and is immediately available for the next user. The "Assign a Computer to a User" mode is prioritized for high-security or high-personalization roles where the desktop is treated like a physical PC. Huawei's documentation clarifies that for Full Copy VMs in a 1:1 relationship, the unassignment process typically signifies the end of that VM's specific lifecycle for that user. Understanding this behavior is crucial for administrators to avoid "resource stranding," where VMs remain in the system but cannot be assigned to new staff due to the persistence constraints of the 1:1 assignment model.

====================