Share via

RDP printer redirection not working after migrating to Windows Server 2019

Hafiz Omar 0 Reputation points
2026-04-28T03:20:16.3966667+00:00

Hi, we are currently migrating our company's remote desktop setup to a new Windows Server 2019 box, and printer redirection has suddenly stopped working for our remote staff. On the old server, everything was fine, but even though we copied the same configs, shared the spooler drivers folder, and installed the same HP drivers, no local printers are showing up in RDP or RemoteApp sessions, which is really causing a headache for our support team. The users have high permissions and can connect just fine, but printer redirection doesn't seem to be happening - is there something we're missing in our settings or something different in Server 2019 that could be causing this?

Windows for business | Windows Server | Devices and deployment | Configure application groups
0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Jason Nguyen Tran 18,725 Reputation points Independent Advisor
    2026-04-28T04:12:50.58+00:00

    Hi Hafiz Omar,

    To clarify, Windows Server 2019 introduced some changes to Remote Desktop Services that can affect printer redirection. Even if you copied the same configs and drivers, the new server may require additional settings. First, please confirm that the “Printer Redirection” option is enabled in the Remote Desktop Session Host configuration and that Group Policy settings under Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Printer Redirection are not blocking redirection.

    Also, check that the Print Spooler service is running on the new server and that the drivers installed are Type 4 (v4) drivers, which are recommended for Server 2019. Legacy Type 3 drivers sometimes cause issues with redirection. If you are using RemoteApp, ensure that the RDP file settings allow printer redirection as well.

    Another common fix is to remove and reinstall the HP drivers using the latest Windows Server 2019‑compatible versions, rather than copying them from the old server. Finally, verify that user permissions are not restricted by Group Policy Objects that may have been reset during migration.

    I hope the response provided some helpful insight. If it addressed your issue, please consider marking it as Accept Answer so others facing the same problem can easily find the solution. If you need any further assistance, feel free to leave a comment.

    Jason.

    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.