Product documentation
Profile Management
Current Release 2607 LTSR 2511 2507 LTSR 2503 2411 2407 2402 LTSR 2311 2308 2305 2303 2212 2209 2206 2203 LTSR 1912 LTSR 7.15
View PDF

Limit profile synchronization during logoff

November 4, 2025
Contributed by: 
C

The Limit number of user stores synced at logoff policy helps improve logoff performance in environments with multiple user stores. This policy lets you control how many user stores synchronize during logoff, helping reduce logoff duration and optimize performance.

Note:

This policy is supported in Citrix Profile Management version 2503 and later.

How it works

By default, Profile Management synchronizes profile data to all configured user stores during logoff. In environments with multiple stores or large profiles, this behavior can cause delays.

The Limit number of user stores synced at logoff policy lets you specify how many stores (1–8, including the main store) synchronize during logoff. The behavior differs depending on whether the environment is persistent or non-persistent.

Persistent environments

In persistent environments (where operating system changes persist across reboots):

  • During logoff: The main user store and up to the configured number of additional stores (1–8 total) synchronize during logoff.
  • After logoff: Any remaining stores synchronize asynchronously in the background after logoff completes.

Result: Logoff completes faster while all stores eventually synchronize. No data loss occurs.

Example: If five user stores are configured and you set the limit to 2:

  • The main store and one additional store synchronize during logoff.
  • The remaining three stores synchronize in the background after logoff.

Non-persistent environments

In non-persistent environments (where operating system changes don’t persist, such as pooled virtual desktops that reset after logoff):

  • During logoff: Only the main user store and up to the configured number of additional stores (1–8 total) synchronize.
  • After logoff: Stores beyond that limit do not synchronize during this logoff.
  • Next logon: All outdated stores synchronize from the main store, ensuring consistency.

Result: Users experience faster logoff times, but some user stores might temporarily contain stale data.

Example: If five user stores are configured and you set the limit to 2:

  • The main store and one additional store synchronize during logoff.
  • The remaining three stores remain outdated until the next logon.

Configure the policy

  1. Open the Group Policy Management Editor.
  2. Go to Computer Configuration > Administrative Templates > Citrix Components > Profile Management > Advanced settings.
  3. Locate and double-click Limit number of user stores synced at logoff.
  4. Select Enabled, and specify the number of stores to synchronize during logoff (1–8, including the main store).
  5. Click OK to save the configuration.
  6. Run gpupdate /force on the affected machine to apply the changes.
  7. Log off and log back on to ensure that the policy takes effect.

Note:

This policy takes effect only when the Replicate user stores policy is enabled.

Best practices

General recommendations:

  • Evaluate requirements: Determine the minimum number of stores that must synchronize during logoff to maintain critical data availability.
  • Combine with other optimizations: Use this policy with features such as Profile streaming, Folder streaming, or Accelerate folder mirroring to further improve performance.
  • Monitor results: Review the Profile Management logs at C:\Windows\System32\LogFiles\UserProfileManager or use the Profile Management health check to monitor and assess the impact of this policy on logoff and subsequent logon performance.
  • Test first: Validate the configuration in a non-production environment before deployment.

Persistent environments

  • Configure higher limits (for example, 3–5 stores) to allow background synchronization without blocking logoff.
  • Ensure sufficient network bandwidth for background synchronization.
  • Monitor background synchronization threads for any performance impact on the system.

Non-persistent environments

  • Configure lower limits (for example, 1–2 stores) to prioritize logoff speed.
  • Include critical or frequently accessed stores within the synchronization limit.
  • The next logon might take longer because all stores resynchronize from the main store.
  • In high-availability configurations, plan for temporary data staleness in non-synchronized stores.

Troubleshooting

If logoff performance doesn’t improve or synchronization issues occur:

  • Confirm that the policy is applied (gpupdate /force) and verify its effect in the Citrix Profile Management logs.
  • Ensure that all user stores are accessible and properly permitted.
  • Check for network interruptions that might delay or prevent synchronization.
  • In persistent environments, verify that background synchronization threads start as expected.
  • In non-persistent environments, if users report outdated data, increase the number of stores synced at logoff.
Limit profile synchronization during logoff
November 4, 2025
Contributed by: 
C
November 4, 2025
Contributed by: 
C

In this article

Site feedback | Your privacy choices footer linkYour Privacy Choices | Privacy and legal terms | Cookie preferences | Consent settings | docs.cloud.com
© 1999- Cloud Software Group, Inc. All rights reserved.