Default printer change upon RDP re-connection to terminal server

Ronald Torr 0 Reputation points
2026-04-17T09:53:54.58+00:00

Hi

I have the problem below can anyone help?

When initially connecting to the terminal server with RDP, the printer is correctly set as the default. However, when the client disconnects (not sign out, just closing the RDP session) the default printer changes and must be manually set as default again. So the catch is, that we'd need a solution that isn't based on user login, but instead upon re-connection to the server.

Server 2019 Terminal Server.

Thanks in advance

Windows for business | Windows Server | User experience | Remote desktop services and terminal services

4 answers

Sort by: Oldest
Most helpful Newest Oldest

  1. AI answer

    2026-04-17T09:54:07.6233333+00:00

    The behavior is tied to how Remote Desktop printer redirection and defaults are managed per session. There is no built‑in Windows Server 2019 feature that automatically re‑applies a specific default printer on reconnection only; instead, this is normally handled either:

    • By the client’s own default printer and Easy Print redirection, or
    • By logon‑time scripts or Group Policy preferences.

    To keep the desired printer as default after disconnect/reconnect, use one of these supported approaches:

    1. Use Easy Print and control the default on the client
      Ensure the RD Session Host is using Easy Print so that the client’s default printer is honored and stays consistent:
      • On the RD Session Host, configure Group Policy:
        Computer Configuration → Administrative Templates → Windows Components → Remote Desktop Services → Remote Desktop Session Host → Printer Redirection
        Set Use Remote Desktop Easy Print printer driver first to Enabled (for Easy Print) or Disabled (for legacy print). For Not configured, Easy Print is chosen by default.
      • On the client, set the correct local default printer. When the user reconnects, Easy Print should redirect that printer and keep it as the default in the session.
    2. Force a specific default printer via Group Policy (per user)
      If the same default printer must always be used on the terminal server regardless of client defaults, configure a user‑scoped Group Policy Preference (Printers) or a logon script that sets the default printer each time the user signs in. This does not trigger on reconnect, but it guarantees the correct default after each sign‑in.
    3. Use a logoff script to clean redirected printers (if stale sessions cause wrong defaults)
      If the default is changing because stale redirected printers accumulate across sessions, use the documented script approach to clean redirected printers at logoff:
      • Create delprinter.vbs with the provided script that deletes session printers from:
        • HKCU\Software\Microsoft\Windows NT\CurrentVersion\Devices
        • HKCU\Software\Microsoft\Windows NT\CurrentVersion\PrinterPorts
      • Create a Group Policy that applies to all users at LOG OFF and calls a batch file (for example \\yourdomain.com\NETLOGON\delprint.bat) which runs cscript delprinter.vbs. This keeps redirected printers from persisting incorrectly between sessions, which can help prevent the default from switching to an invalid or stale redirected printer after reconnect.

    If the issue persists even with Easy Print and clean redirected printers, configure a small reconnection script (for example, triggered by a third‑party RDS session manager or by users manually running it) that calls rundll32 printui.dll,PrintUIEntry to set the desired printer as default; Windows does not provide a native “on reconnect” trigger in Group Policy.

    References:

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

  2. HLBui 13,420 Reputation points Independent Advisor
    2026-04-17T10:52:00.03+00:00

    Good day Ronald Torr

    It’s a common quirk with RDP sessions on Server 2019. When a user disconnects (without signing out), the session state is preserved, but the default printer mapping doesn’t always stick. On reconnect, Windows sometimes re‑evaluates printer assignments and ends up picking another printer as default. That’s why you’re having to manually reset it each time.

    One way to tackle this is by using Group Policy Preferences to enforce the default printer at the machine or user level. That way, even if the session is reconnected, the policy reapplies and sets the right printer back as default. Another option is to use a logon script or reconnect script that runs RUNDLL32 PRINTUI.DLL,PrintUIEntry or PowerShell’s Set-Printer to reset the default printer whenever the session resumes.

    Since you don’t want it tied to login only, you’ll need to hook into session reconnect events. Tools like Task Scheduler can be configured to trigger on reconnect/disconnect events and run a script to reset the default printer. That usually solves the “disconnect but not sign out” scenario.

    Also, double‑check that printer redirection policies aren’t conflicting sometimes RDP printer redirection overrides the default printer setting on reconnect. If you don’t need redirection, disabling it can help stabilize things.

    So in short: enforce the default printer via GPO or script, and tie it to reconnect events rather than just login. That way, users won’t have to keep fixing it manually.

    I hope this information can help you solve the problem and feel free to click “Accept Answer” so we know we’re heading in the right direction and let me know if you need any assistance. Thank you!

    Was this answer helpful?

    0 comments
  3. HLBui 13,420 Reputation points Independent Advisor
    2026-04-20T09:14:43.8066667+00:00

    Hi Ronald Torr

    Just checking to see how is everything. Please feel free to let me know if you need any assistance

    Was this answer helpful?

    0 comments
  4. 2FAQu 0 Reputation points
    2026-08-22T01:23:51.0166667+00:00

    If you have RDSSH with FSLogix, you need the Reg RoamIdentity for FSLogix.

    1. Path: HKEY_LOCAL_MACHINE\SOFTWARE\FSLogix\Profiles
    2. DWORD32: RoamIdentity
    3. Value: 1
    4. Sign in and out

    If you dont have FSLogix:

    1. Path: HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Print\Providers\Client Side Rendering Print Provider
    2. DWORD32: RemovePrintersAtLogoff
    3. Value: 0
    4. Restart Spooler
    5. Sign in and out

    Was this answer helpful?

    0 comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.