1Y0-204 · Question #234
Scenario: A Citrix Administrator has been advised that additional Windows users will need to access the on-premises Citrix Virtual Apps and Desktop Site. The Site utilizes Citrix Profile Management…
The correct answer is D. When the new users initiate their first logon to a Virtual Delivery Agent (VDA) machine. Typically, the migration of existing profiles to a new profile management system occurs during the user's first logon after the policy has been applied, as this is when the user's profile is first accessed and can be migrated.
Question
Scenario: A Citrix Administrator has been advised that additional Windows users will need to access the on-premises Citrix Virtual Apps and Desktop Site. The Site utilizes Citrix Profile Management for all users. The new users have been using Windows Roaming Profiles and will need their existing profile information when they use the Citrix Site. The administrator enables the Profile Management policy setting for 'Enable Migration of Existing Profiles'. At which stage will the new users' Roaming Profiles be migrated to the existing Profile Management store?
Options
- AWhen the new policy is updated automatically in Active Directory after 90 minutes
- BWhen the new users initiate their first domain authentication
- CWhen the Virtual Delivery Agent (VDA) machines configured with the new policy are restarted
- DWhen the new users initiate their first logon to a Virtual Delivery Agent (VDA) machine
How the community answered
(25 responses)- A12% (3)
- B4% (1)
- C8% (2)
- D76% (19)
Explanation
Typically, the migration of existing profiles to a new profile management system occurs during the user's first logon after the policy has been applied, as this is when the user's profile is first accessed and can be migrated.
Topics
Community Discussion
7
Giselle K.May 28, 2026D is correct. The "Enable Migration of Existing Profiles" setting kicks in at first logon to a VDA, which is when Profile Management hooks into the session, detects the incoming Windows Roaming Profile, and copies it into the CPM store before the desktop finishes loading.
Dervla O.May 30, 2026That sequence is right, though worth flagging that the copy only happens if no CPM profile already exists for that user, so on a second VDA logon the migration step is quietly skipped.
Ola B.May 25, 2026Good catch on option B being a trap here. Domain authentication happens at the network level before any VDA session is even involved, so the profile store has no opportunity to intercept and migrate anything at that point. Profile Management only gets to do its work during the logon process on the VDA itself, which is when it reads the policy, checks whether a CPM profile already exists for the user, and if it does not, pulls from the existing Windows Roaming Profile and copies it into the store. So D is the right pick, and the best way to cement this is to spin up a lab VDA, add a test user with a roaming profile, enable that migration policy, and watch what happens the first time that user logs on versus the second time.
Dervla O.Jun 21, 2026Option B is the trap here, because "domain authentication" sounds plausible if you're thinking of group policy processing, but profile migration in Citrix Profile Management is a logon-time event tied to the VDA session, not to a DC handshake. The migration happens at first VDA logon (D), when the Profile Management service on the VDA detects no existing CPM profile and pulls in the roaming profile at session setup.
Yusuf A.Jun 10, 2026At first I thought it was B, because "first domain authentication" sounds like it would be the trigger since that is when Windows normally picks up roaming profile data. But then I remembered that Profile Management does not run at domain auth time, it runs as a Citrix service on the VDA itself, so the migration can only happen once a session actually starts on that machine. Option D makes sense because the first logon to a VDA is exactly when Citrix Profile Management kicks in, detects no existing CPM store for that user, sees the roaming profile, and copies it over before the desktop loads. A senior admin on my team put it this way: the migration is basically an import that happens at session launch, not at login to the domain controller, and not from a policy refresh cycle like A suggests.
Dervla O.Jun 13, 2026Yusuf's framing is solid, and the "import at session launch" analogy holds up well, but worth flagging for anyone reading that this one-time copy only triggers if the CPM store is genuinely absent, so users who already have a partial store from a previous failed migration can get stuck and need manual remediation before that first-logon import will fire.
Fatima Z.Jun 15, 2026Okay I will be honest, I almost bubbled B on this one because "first domain authentication" sounds so logical, like the moment you knock on the door is when the moving truck shows up with your old stuff. But here is the thing that snapped me out of it: domain authentication happens at the network level and Citrix Profile Management is not even in the room yet at that point, it is just Windows and a domain controller having a chat. CPM only gets to act when a user actually touches a VDA, so the migration trigger lives at VDA logon, not at domain logon. My hook for this is LOG ON FIRST, MOVE YOUR STUFF, and I picture a new employee showing up at a Citrix office and the movers only unload the boxes once the person actually walks through the VDA door, not when they badged into the parking lot. The answer is D every time.