Configure Remote Desktop Easy Print on Windows Server 2022/2025

6.6K

This tutorial shows how to configure Remote Desktop Easy Print on Windows Server to simplify remote printing. Easy Print was introduced in Windows Server 2008 and remains supported on modern Windows Server versions, including Windows Server 2022 and Windows Server 2025.

What is Remote Desktop Easy Print?

Remote Desktop Easy Print is a Windows Remote Desktop Services feature that allows you to easily print from a remote desktop session to a local printer.

Benefits of Easy Print for Remote Desktop Users

When printer redirection is enabled, Remote Desktop Services creates redirected printers that use the Remote Desktop Easy Print driver on the RD Session Host.

Remote Desktop Easy Print vs. Universal Print

Remote Desktop Easy Print is not the only printing option for modern remote desktop environments. Microsoft Universal Print provides a cloud-based printing service that can be used as an alternative to traditional printer redirection, particularly in Microsoft Entra ID, Microsoft 365, and Azure Virtual Desktop environments.

Unlike Easy Print, which redirects a printer from the user’s local device through the RDP session, Universal Print is a cloud-based print service. This can be useful when you want to reduce dependency on direct network connectivity between endpoints and session hosts and centrally manage printers through Microsoft cloud services.

For Azure Virtual Desktop, we recommend Universal Print as an alternative to RDP printer redirection.

Windows Ready Print and Windows Protected Print Mode

You should note that Windows printing is moving from traditional third-party printer drivers toward Windows Ready Print, which is based on modern printing technologies (such as Internet Printing Protocol (IPP) and Mopria-certified printers).

Windows Protected Print Mode (WPP) builds on Windows Ready Print and allows Windows to use only supported modern printing technologies instead of legacy third-party printer drivers. We recommend you to use Windows Protected Print Mode for environments where printer compatibility allows it.

This is important when using you are using Remote Desktop printer redirection. Easy Print can eliminate the need to install vendor-specific printer drivers on the RD Session Host, but it does not make legacy printer requirements on the client disappear.

In case a local printer depends on a third-party driver/vendor-specific printing functionality that is incompatible with Windows Protected Print Mode, you can prevent that printer from being used by enabling WPP. But keep in mind that this can affect specialized devices such as some label, receipt, barcode, and POS printers.

You should verify printer compatibility for enterprise environments with Windows Ready Print and Windows Protected Print Mode before standardizing on Easy Print for specialized printers.

For compatible printers, prefer Windows Ready Print/IPP-based printing where possible. You should use legacy driver-based printing only when required by the printer or application and where your security policy allows it.

Remote Desktop Easy Print: How Does It Work?

Easy Print Virtual Printer Explained

Remote Desktop Easy Print creates a virtual printer on the remote computer that represents the local printer you want to use. When you print a document from the remote session, it is sent to this virtual printer, which redirects the print job to the local printer.

The process works as follows:

1. When you connect to a remote desktop session, the Easy Print driver is automatically installed on the remote computer.
2. When you print a document from the remote session, the print job is sent to the virtual printer created by Easy Print.
3. The virtual printer converts the print job into XPS, which encapsulates the print job and settings that the local printer can understand. Keep in mind that Easy Print uses XPS rendering, and it may cause formatting differences/issues with a bunch of printer-specific features.
4. The print job is then redirected to the local printer via the Remote Desktop Connection.
5. After that, the local printer starts printing documents as if they were sent from the local machine.

Related article: How to Deploy Printers to Users or Computers via Group Policy?

Security Considerations for RDS Printing

Printer redirection and the Windows Print Spooler are security-sensitive components. You should enable printer redirection only when required, keep the RD Session Host fully patched, and avoid unnecessary third-party printer drivers.

Printer Driver Security

Windows restricts printer-driver installation by non-admins by default. You should keep Computer Configuration → Administrative Templates → Printers → Limits print driver installation to Administrators enabled (RestrictDriverInstallationToAdministrators) unless there is a documented requirement to change it.

If traditional Point and Print is used, you should also review Point and Print Restrictions and limit connections to trusted print servers where appropriate. Easy Print can reduce the need for vendor-specific drivers on the RD Session Host.

Windows Protected Print Mode

Windows Protected Print Mode (WPP) uses a modern IPP-based printing architecture and blocks third-party printer drivers, reducing the attack surface of the Windows print stack. Before enabling WPP, you should test compatibility with specialized printers that require vendor-specific drivers. In case of new deployments, refer Windows Ready Print/IPP-compatible printers where possible.

Configure Remote Desktop Easy Print Settings on the Server

You can configure the Remote Desktop Easy Print settings in two ways: via Group Policy or the Server Manager. These configuration methods apply to Windows Server 2012 and later, where the Remote Desktop Services role is installed.

But note that the settings deployed via Group Policy take precedence over the setting in Server Manager.

If you need to verify that the Remote Desktop Session Host role is installed, run the following command:

Get-WindowsFeature -Name RDS-RD-Server

The Install State column should show Installed.

Using Group Policy

1. Open the Group Policy Management Console on your domain controller:
   

   gpmc.msc

   
2. Create a new GPO or edit an existing one.
   

   

3. Navigate to the following policy:
   Computer Configuration\Policies\Administrative Templates\Windows Components\Remote Desktop Services\Remote Desktop Session Host\Printer Redirection
4. Enable the policy “Use Remote Desktop Easy Print printer driver first.”
   

   

   If this policy is enabled or not configured, the RD Session Host first attempts to use the Easy Print driver. If disabled, the server will try to match a native printer driver.
5. Close the Group Policy Management Editor and wait for the new policy to be applied.
6. Optionally, you can force the group policy to apply by running the following command in an elevated command prompt on the Remote Desktop Services server.
   

   gpupdate /force

Configure Easy Print with PowerShell

You can also config the Easy Print Group Policy setting using the Group Policy PowerShell cmdlets. This is useful for scripted/automated GPO deployment. The Use Remote Desktop Easy Print printer driver first policy corresponds to the following registry value:

HKLM\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services\fUseRDPPrinterEasyPrint

To enable the policy in an existing GPO, run the following command:

Set-GPRegistryValue -Name "RDS Printer Redirection" `
-Key "HKLM\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services" `
-ValueName "fUseRDPPrinterEasyPrint" `
-Type DWord `
-Value 1

In order to config the policy so that the RD Session Host prefers native printer drivers, use the command below:

Set-GPRegistryValue -Name "RDS Printer Redirection" `
-Key "HKLM\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services" `
-ValueName "fUseRDPPrinterEasyPrint" `
-Type DWord `
-Value 0

Replace RDS Printer Redirection with the name of the GPO you want to manage.

Disable Easy Print and Use Native Printer Drivers

In some environments, Remote Desktop Easy Print may not work correctly with specialized printers such as label printers, receipt/POS printers, barcode printers, or devices that require vendor-specific printing features. Before switching to a native vendor-specific printer driver, you need to check if the printer supports Windows Ready Print/IPP and whether it is compatible with Windows Protected Print Mode.

Note that Microsoft is phasing out servicing of legacy third-party v3/v4 printer drivers in favor of Windows Ready Print. This makes IPP/Windows Ready Print compatibility increasingly important when designing new Windows Server and RDS printing deployments.

To force the RD Session Host to use native printer drivers instead of Easy Print, follow the steps below:

1. Open the Group Policy Management Console.
2. Go to Computer Configuration\Policies\Administrative Templates\Windows Components\Remote Desktop Services\Remote Desktop Session Host\Printer Redirection
3. Open the policy Use Remote Desktop Easy Print printer driver first.
4. Set the policy to Disabled.
5. Apply the policy and run the command:
   

   gpupdate /force

When this policy is configured:

• Enabled or Not Configured — the RD Session Host attempts to use the Remote Desktop Easy Print driver first.
• Disabled — the RD Session Host attempts to use a matching native printer driver installed on the server.

Note. Using native printer drivers may be required for some specialized printers that do not work correctly with Easy Print or rely on vendor-specific printing features.

Using Server Manager

1. Login to the RDS server and open the Server Manager.
2. Navigate to Remote Desktop Services > Collections and edit the Session Collection.
   

   

3. Click Client Settings and check the following boxes:
   • Allow client printer redirection
     • Use the client default printing device
     • Use the Remote Desktop Easy Print printer driver first
       

       

If a group policy manages the printer redirection settings, you will get an error saying, “Could not set the appropriate properties on the servers. Ensure that all servers are available on the network, and the properties are not managed by Group Policy.”

When you get this error, ensure the Printer Redirection policies are not configured.

Confirm Remote Desktop Easy Print Driver is in Use

Remote Desktop printer redirection is supported by current Windows Remote Desktop clients when printer redirection is enabled and is not blocked by RDP/Group Policy settings.

You can use Remote Desktop Connection (mstsc.exe) for classic RDS deployments. For Azure Virtual Desktop and Windows 365, we recommend using the Windows App, which provides the current client experience for connecting to remote desktops and cloud PCs.

Keep in mind that the exact printer-redirection settings depend on the RDP client and deployment type. When troubleshooting, you should check both the client-side printer redirection setting and the server-side RDS policies.

Client Requirements

For Remote Desktop Easy Print to work correctly, your environment must meet the following client-side requirements:

• Printer redirection must be enabled in the Remote Desktop Connection client (mstsc) under Local Resources > Printers;
• A supported Remote Desktop Protocol (RDP) client must be used;
• The local printer must be properly installed and functioning on the client machine;
• The user must have permission to redirect local devices through the RDP session;
• Network connectivity between the client and the Remote Desktop Session Host must be stable.

Note. If printers are not redirected from the client machine, Remote Desktop Easy Print cannot create redirected printers in the remote session, regardless of the server-side config.

Checking Printer Properties in RDS

1. Open the Remote Desktop Connection app:
   

   mstsc

2. Enter the RDS server and credentials.
   

   

3. Switch to the Local Resources tab, check the Printers box, and click Connect.
   

   

4. Once logged in, open the Devices and Printers applet in Control Panel. Your local printers are listed on the server as redirected.
   

   

5. Right-click on the printer and click Printer properties.
   

   

6. Switch to the Advanced tab and confirm the driver is Remote Desktop Easy Print.
   

   

Now you need to check Easy Print policy config. Check that the expected Printer Redirection policies are applied to the RD Session Host with the commands:

gpresult /r

or

gpresult /h report.html

Azure Virtual Desktop and Windows 365 – Windows App

For Azure Virtual Desktop and Windows 365, you should use the Windows App where supported. In this case, printer redirection is configured through the connection settings in the Windows App rather than through the Local Resources tab of the classic mstsc.exe client.

However, the available redirection options depend on the platform and the RDP policies configured by your organization.

Check Event Viewer Logs

In case the printer redirection is enabled but redirected printers do not appear/printing fails, you should check the relevant Event Viewer logs on the RD Session Host. Open Event Viewer (eventvwr.msc) and review the following logs:

Applications and Services Logs → Microsoft → Windows → TerminalServices-Printers → Operational – events related to printer redirection in Remote Desktop Services.
Applications and Services Logs → Microsoft → Windows → PrintService → Admin – warnings and errors from the Windows printing subsystem.

These logs can help you determine if the problem is related to RDS printer redirection or to Windows printing and printer drivers.

As example, in case the redirected printer is not created at all, you should start with the TerminalServices-Printers/Operational log. If the printer is created but the print job fails, also check PrintService/Admin for spooler or driver-related errors.

For production troubleshooting, you should note the event timestamp and correlate it with the user’s RDP connection and the failed print attempt.

Common Easy Print Problems

Printers Do Not Appear in the Remote Session

If local printers are not redirected to the remote desktop session, you need to check the following:

• Make sure the Printers option is enabled on the Local Resources tab of the Remote Desktop Connection (mstsc) client;
• Verify that printer redirection is not disabled by Group Policy;
• Check the Session Collection Client Settings and confirm that Allow client printer redirection is enabled;
• Reconnect to the RDS session after changing any printer redirection settings.

Easy Print Driver Is Not Used

If redirected printers are using vendor-specific drivers instead of the Remote Desktop Easy Print driver:

• Verify that the Use Remote Desktop Easy Print printer driver first policy is enabled/not configured;
• Confirm that the RDP client version supports Easy Print;
• Check the printer properties on the RD Session Host and verify which driver is assigned to the redirected printer.

Printing is Slow

Remote Desktop Easy Print renders print jobs through the RDS printing pipeline and transfers the resulting print data through the RDP connection to the client. Large documents, high-resolution graphics, and complex print jobs can generate substantial amounts of print data. On slow/high-latency WAN/VPN connections, this can increase bandwidth consumption and printing latency.

For environments with frequent large/graphics-intensive print jobs, you should test Easy Print under realistic production conditions. In case performance or functionality is inadequate, you need to evaluate native/vendor-supported printing, Universal Print, or other supported printing architectures depending on the environment.

Wrapping up

Configuring Remote Desktop Easy Print on Windows Server 2022 can significantly improve the printing experience for remote users. Following the step-by-step instructions outlined in this blog post, you can ensure your users can easily print from their remote sessions. Easy Print can reduce the need to install vendor-specific printer drivers on RD Session Hosts, but printer compatibility still depends on the client, printer technology, RDP configuration, and any Windows printing security policies such as Windows Protected Print Mode.

With the proper configuration and setup, you can simplify the printing process and save time and frustration for both you and your users.