Skip to main content
cau-ifi-ts
cau-ifi-ts
Participant
March 3, 2026
Question

Adobe Acrobat Pro requires re-login when switching between load-balanced servers (FSLogix profile sync). How to avoid that?

  • March 3, 2026
  • 1 reply
  • 95 views

Dear Adobe community,

I have a problem with a Windows server setup in which users have to re-login to Adobe Acrobat Pro because of profile synchronization issues. The setup is the following: We have a Windows server environment (Windows Server 2022) with two servers behind a load balancer where user profiles are synchronized using FSLogix. On the servers, we run Adobe Acrobat Pro and every of the 19 users has its own personal named license which allows simultaneous logins on two devices.

The setup should be as follows: Users should remain logged into Adobe Acrobat Pro on both servers, so switching between them via the load balancer doesn't require re-authentication. This unfortunately does not work. When a user works on Server A, they stay logged in across multiple sessions. However, when the load balancer routes them to Server B, Adobe prompts them to log in again. This happens on every server switch. It seems like the already authenticated session on this server is invalidated by the profile synchronization. How can we avoid that?

We already attempted to exclude AppData\Local\Adobe\OOBE from FSLogix synchronization using Redirections.xml:

<?xml version="1.0" encoding="UTF-8"?>
<FrxProfileRedirection ExcludeCommonFolders="false">
  <Excludes>
    <Exclude Copy="false">AppData\Local\Adobe\OOBE</Exclude>
  </Excludes>
</FrxProfileRedirection>

This unfortunately had no effect. Are there additioinal paths we should exclude from FSLogix sync or where exactly does Adobe Acrobat Pro store session/authentication data that sync should not overwrite? Or do we have to exclude the synchronization of the credential manager?

Any guidance would be appreciated!

    1 reply

    A
    Community Manager
    Anshul_NautiyalCommunity Manager
    Community Manager
    March 3, 2026

    Hi ​@cau-ifi-ts 

    Thank you for reaching out and for sharing the details of your setup.
    Based on your description, the behavior you’re experiencing is expected in load‑balanced, multi‑server environments when using Adobe Acrobat Pro with Named User licensing, even when user profiles are synchronized with FSLogix.
    Although FSLogix correctly roams the Windows user profile between servers, Adobe Acrobat still validates the signed‑in session against the specific session host (server) the user is connected to. When the load balancer routes a user from Server A to Server B, Acrobat interprets this as a new device context and may prompt the user to sign in again. This can occur even if the user profile is mounted successfully and the user remains signed in on the original server.
    To ensure the environment is correctly configured, please verify that User‑Specific Licensing and Identity are enabled on all session hosts by confirming the following registry keys are present:

    [HKEY_LOCAL_MACHINE\SOFTWARE\Adobe\Licensing\UserSpecificLicensing]
    "Enabled"="1" (REG_SZ)

    [HKEY_LOCAL_MACHINE\SOFTWARE\Adobe\Identity\UserSpecificIdentity]
    "Enabled"="1" (REG_SZ)

    For best results, Adobe recommends installing Acrobat Pro using the Enterprise installer with roaming identity and licensing enabled. This helps Acrobat handle user‑based authentication more effectively in virtualized and load‑balanced environments. Check this doc:

    https://www.adobe.com/devnet-docs/acrobatetk/tools/AdminGuide/licensing.html#named-user-deployment

    It’s also important to be aware that, due to product design limitations, occasional re‑authentication may still occur in environments where users frequently switch between session hosts. This behavior is not caused by FSLogix misconfiguration but by how Named User licensing validates active sessions.

    Please let me know if you’d like help reviewing your current Acrobat installation method or if you need any additional guidance.


    Regards,
    ^AN

      cau-ifi-ts
      cau-ifi-tsAuthor
      Participant
      March 11, 2026

      Thanks for the detailed and promising answer! I forwarded your instructions to the corresponding administrator and will keep you updated / ask for further guidance if needed.

      Terms & ConditionsAccessibility statement
      Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices