Skip to main content
A
ac15557395
Participant
July 14, 2026
Answered

Acrobat Server 2025 RDS RemoteApp

  • July 14, 2026
  • 1 reply
  • 20 views

I'm having ongoing issues running Adobe Acrobat on a Windows Server 2025 RDS server using Published RemoteApp.

Environment:

  • Windows Server 2025 with Published RemoteApp (not full desktops)
  • Named User Licensing
  • Application published: ERP Business software (uses Adobe for PDF generation during workflows)
  • Multiple users connect from Windows 11 workstations

Issues:

  • AcroTray.exe repeatedly tries to access paths in other users' profiles (e.g. C:\Users\production\AppData\...) resulting in many NAME NOT FOUND errors.
  • PDF printing via Microsoft Print to PDF often fails on one specific workstation when connected to the new server (works fine on the old Server 2016 server).
  • Occasional licensing/session conflicts ("another connection was made").

What we've tried:

  • Clearing NGL licensing folders
  • Registry tweaks for virtualization
  • Reinstall attempts on the server

Has anyone successfully deployed Acrobat (especially with Named User Licensing) on Server 2025 in an RDS/RemoteApp environment? Any recommended deployment method or known issues with Acrobat + Server 2025 RDS?

Any guidance would be appreciated.

    Correct answer Anand Sri Bhattacharya

    Hello @ac15557395,


    I hope you are doing well, and thanks for reaching out. We're sorry for the trouble you had.


    I’d suggest testing in this order:

    1. Validate the same workflow on a documented server OS, preferably Windows Server 2022, to determine whether the issue is specific to Server 2025.

    2. Test in a full RDS desktop session instead of Published RemoteApp to see whether the issue is specific to RemoteApp isolation/windowing/session behavior.

    3. Test with a clean Windows profile and one concurrent user, then retest with multiple concurrent users.

    4. Launch Acrobat directly once in each affected user session, sign in, and confirm it remains activated after closing/reopening.

    5. Test PDF creation directly in Acrobat using Menu > Create > PDF from file before testing through the ERP application.

    6. Check Credential Manager, TLS 1.2, Adobe licensing endpoints, and antivirus/EDR allowlisting as documented by Adobe.

    7. If Microsoft Print to PDF fails only from one Windows 11 workstation, isolate whether that failure occurs with non-Adobe applications too, because Microsoft Print to PDF is an OS printer component rather than the Adobe PDF printer.


    Also, as this is an Enterprise licensing, the recommendation is to contact the Enterprise support team from the Admin console and create a support ticket. The dedicated team will help you with the custom requirements.


    I hope this information helps. Let us know if you need any assistance.

    Regards,

    Anand Sri.



    1 reply

    Anand Sri Bhattacharya
    Community Manager
    Anand Sri BhattacharyaCommunity ManagerCorrect answer
    Community Manager
    July 14, 2026

    Hello @ac15557395,


    I hope you are doing well, and thanks for reaching out. We're sorry for the trouble you had.


    I’d suggest testing in this order:

    1. Validate the same workflow on a documented server OS, preferably Windows Server 2022, to determine whether the issue is specific to Server 2025.

    2. Test in a full RDS desktop session instead of Published RemoteApp to see whether the issue is specific to RemoteApp isolation/windowing/session behavior.

    3. Test with a clean Windows profile and one concurrent user, then retest with multiple concurrent users.

    4. Launch Acrobat directly once in each affected user session, sign in, and confirm it remains activated after closing/reopening.

    5. Test PDF creation directly in Acrobat using Menu > Create > PDF from file before testing through the ERP application.

    6. Check Credential Manager, TLS 1.2, Adobe licensing endpoints, and antivirus/EDR allowlisting as documented by Adobe.

    7. If Microsoft Print to PDF fails only from one Windows 11 workstation, isolate whether that failure occurs with non-Adobe applications too, because Microsoft Print to PDF is an OS printer component rather than the Adobe PDF printer.


    Also, as this is an Enterprise licensing, the recommendation is to contact the Enterprise support team from the Admin console and create a support ticket. The dedicated team will help you with the custom requirements.


    I hope this information helps. Let us know if you need any assistance.

    Regards,

    Anand Sri.



    Firefly Community Gallery
    Adobe Firefly

    Remix with Firefly Community Gallery

    Thousands of free creations to fall in love with and remix in Firefly.

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