How to Disable Remote Desktop Easy Print in Windows Server (2016-2025)
Remote Desktop Easy Print is the default driver Windows uses to map local client printers into a remote session. While convenient, it strips away advanced printer features (like stapling, tray selection, or custom formatting) and can cause frustrating formatting issues for users.
If you need your users to access the full native capabilities of their printers over RDP, you must disable the Easy Print feature and force the server to rely on native print drivers. Here is how to configure this policy across modern Windows Server deployments.
Prerequisites Before You Begin
- You must have Domain Administrator or Local Administrator privileges on the Session Host.
- CRITICAL: You must install the exact matching native printer drivers directly onto the RD Session Host server before proceeding. If Easy Print is disabled and the server lacks the native driver, the printer will fail to map entirely.
-
Open the Group Policy Editor
Log into your RD Session Host (or Domain Controller if applying globally). Press the Windows Key + R, type
gpedit.msc(orgpmc.mscfor domain-level), and hit Enter.
-
Navigate the Policy Tree
In the left-hand pane, drill down through the following path:
Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Printer Redirection.
-
Locate the Easy Print Policy
In the right-hand pane, find the policy named Use Remote Desktop Easy Print printer driver first. Double-click it to open the configuration window.
-
Disable the Driver Preference
Change the radio button at the top from "Not Configured" to Disabled. Click Apply and OK.
(Note: Setting this to "Disabled" tells the server to look for the native driver first. It will only fall back to Easy Print if the native driver is missing.)
-
Update Group Policy
To apply the changes immediately, open Command Prompt as an Administrator and run the command
gpupdate /force. Wait for the success confirmation message.
-
Reconnect to Your Server
For the mapped printers to pick up the new native drivers, you must restart the spooler. Open Services (
services.msc), right-click the Print Spooler service, and select Restart. Alternatively, users can simply log off and log back into their remote sessions.
Admin Note on Driver Matching:Ensure the names of the print drivers on the local client machine and the RD Session Host match exactly character-for-character. If the names differ slightly (e.g., "HP Universal Printing PCL 6" vs "HP Universal Printing PCL6"), the server will not map the printer.
Is Your RDS Environment Properly Authorized?
Configuring printers is only half the battle. Every user or device connecting to your Session Host must be covered by an authentic Remote Desktop Client Access License. Secure your infrastructure and ensure uninterrupted access for your workforce today.
Author Bio
Vijayan
Related Posts
Understanding RDS CAL Downgrade Rights
Home – Understanding RDS CAL Downgrade Rights Understanding RDS CAL Downgrade Rights When managing a Remote Desktop Services environment, hardware and software upgrades rarely happen all at once. You might purchase new Client Access Licenses (CALs) today, but still need them to authorize connections to older servers running in your datacenter. Microsoft accommodates this reality…
How to Create a Remote Desktop User in Windows Server (2016, 2019, 2022 & 2025)
Home – How to Create a Remote Desktop User in Windows Server (2016, 2019, 2022 & 2025) How to Create a Remote Desktop User in Windows Server (2016, 2019, 2022 & 2025) Provisioning remote access for a new employee requires more than just creating a standard Windows account. To securely connect to a Session Host,…
How to Fix the CredSSP “Encryption Oracle Remediation” RDP Error
Home – How to Fix the CredSSP “Encryption Oracle Remediation” RDP Error How to Fix the CredSSP “Encryption Oracle Remediation” RDP Error If you are managing Windows Servers, you have likely encountered this terrifying error message when trying to connect via Remote Desktop: “An authentication error has occurred. The function requested is not supported… This…
How to Configure the RDS “Startup Environment” in Server 2016, 2019, 2022 & 2025
Home – How to Configure the RDS “Startup Environment” in Server 2016, 2019, 2022 & 2025 How to Configure the RDS “Startup Environment” in Server 2016, 2019, 2022 & 2025 If you recently upgraded your infrastructure, you likely noticed a glaring omission: Microsoft removed the Environment, Sessions, and Remote Control tabs from the Active Directory…