Which THREE actions are performed by Citrix Profile Management when a user logs off a virtual desktop? (Choose three.)
Trap 1: Rebooting the VDA
Rebooting the VDA is a task performed by the Citrix Machine Creation Services or Provisioning Services, not by the profile management agent. Profile Management focuses exclusively on user data and settings, and triggering a reboot would be disruptive to other users sharing the same host server.
Trap 2: Updating group policy objects
Group Policy updates are handled by the Windows Group Policy Client service and typically occur at logon or background refresh intervals. Profile Management has no authority to modify or update central Active Directory Group Policy Objects, as that would pose a significant security risk to the domain environment.
- A
Uploading modified files to the User Store
Uploading changes to the User Store is the primary task of the logoff process. This ensures that any files created or modified during the session are persisted. Without this step, the user's work and configuration changes would be lost, negating the benefits of a roaming profile solution.
- B
Rebooting the VDA
Why it fails: Rebooting the VDA is a task performed by the Citrix Machine Creation Services or Provisioning Services, not by the profile management agent. Profile Management focuses exclusively on user data and settings, and triggering a reboot would be disruptive to other users sharing the same host server.
- C
Deleting the local user profile folder
Deleting the local profile after a logoff is standard practice in non-persistent VDI. It prevents the accumulation of temporary data on the VDA, which would eventually lead to disk space exhaustion. This cleanup ensures that the next user logging onto that VDA starts with a clean slate.
- D
Updating the registry hives in the User Store
Registry settings modified during the session must be merged back into the user's NTUSER.DAT file stored within the network User Store. This ensures that personal customizations to the Windows environment, such as display settings and application configurations, remain consistent when the user logs into a different machine.
- E
Updating group policy objects
Why it fails: Group Policy updates are handled by the Windows Group Policy Client service and typically occur at logon or background refresh intervals. Profile Management has no authority to modify or update central Active Directory Group Policy Objects, as that would pose a significant security risk to the domain environment.