Australian cloud for business software — built and run in Sydney since 2002

NetLeverage
NetLeverage

Remote Desktop printer redirection isn't working: redirected printers missing from the session

Technical article
Troubleshooting

About this article: This article is reviewed against the cited sources. This is source research, not lab validation. Check the stated versions and your own requirements before making changes.

Microsoft's page "Windows Server printer redirection isn't working" describes this case: printer redirection does not work, drive redirection does work, and no event IDs are logged. Its cause is a missing "AU" (Authenticated User) entry in the security descriptor of the Print Spooler service. When the entry is missing, the Remote Desktop service cannot open the spooler to read it.

Check the spooler's security descriptor first, with a command that only reads. Then work through Microsoft's other checks, which are a Group Policy setting for Easy Print, the Printers checkbox in the Remote Desktop client, and a policy on a Remote Desktop Gateway.

What the error means

There is no error text on screen. The symptom Microsoft states is: "Printer redirection isn't working. Drive redirection works. No event IDs are seen." Redirected printers are simply not in the session.

Microsoft's cause: "The spooler security descriptor must contain the "AU" (Authenticated User) ACL (Access Control List) which allows any authenticated user to open the spooler service for reading operations." The page adds: "since TS runs as a network service it relies on this ACL to be present in order to successfully open the spooler service." In its case, "that ACL was missing from the spooler security descriptor."

A separate Microsoft page, for Windows Server 2008 R2 only, lists the printer redirection events that the source Microsoft-Windows-TerminalServices-Printers can log. It is dated 2010-01-15 and states no later version. Where an event does appear on your server, it is worth matching against this list. Event 1102 reads "Driver %1 required for printer %2 is not installed on the server. Contact the administrator to install the driver before you log in again." Event 1116 reads "The printer %1 cannot be redirected by using Remote Desktop Easy Print. The client computer may not have a version of the Remote Desktop Connection client or Microsoft .NET Framework installed that supports this driver." Event 1124 reads "The number of printers per session limit was reached. The following print queue was not created:" followed by the printer and port.

Likely causes

Cause What you see How to confirm
AU entry missing from the Print Spooler service security descriptor Printers not redirected, drives are; no event IDs sc sdshow spooler shows no (A;;CCLCSWLOCRRC;;;AU) entry
Easy Print policy set the wrong way Printers missing from the session Group Policy: Use Remote Desktop Easy Print printer driver first
Printers box not ticked on the client No printers redirected for that user only Remote Desktop Connection, Local Resources tab; or redirectprinters:i:1 in the RDP file
Printer redirection disabled by policy on a Remote Desktop Gateway Only users connecting through the gateway lack printers Microsoft's page: "If you connect over RD Gateway, ensure that the policy that disables printer redirection is turned off."
Older client without the needed .NET Framework or client version Windows XP clients Microsoft's page: Windows XP clients need .NET Framework 3.5 SP1 and at least RDC 6.1
Per-session printer limit reached (2008 R2 page) Event 1124 Look for event 1124 in the System log on the session host

Prove the cause before changing anything

All of these only read.

On the server, show the current security descriptor of the Print Spooler service in an elevated command prompt:

sc sdshow spooler

Microsoft's page says an unaltered one "should look like this":

D:(A;;CCLCSWLOCRRC;;;AU)(A;;CCDCLCSWRPWPDTLOCRSDRCWDWO;;;BA)(A;;CCLCSWRPWPDTLOCRRC;;;SY)

The one that matters is the entry for AU. Microsoft notes the output you see may differ "depending on the permissions set on the spooler", so look for the AU entry, not for an exact string.

Then check Microsoft's other items:

  1. Group Policy at Computer Configuration, Administrative templates, Windows Components, Remote Desktop Services, Remote Desktop Session Host, Printer Redirection. Microsoft's page: the setting "Use Remote Desktop Easy Print printer driver first" must be "Enabled" for Easy Print redirection and "Disabled" for Legacy Print, and "For "Not configured", Easy Print is chosen by default."
  2. On the client, in the Remote Desktop Connection window, check the Printers box on the Local Resources tab. The matching RDP file setting is redirectprinters:i:1.
  3. If the connection goes through an RD Gateway, check that the gateway policy that disables printer redirection is off.
  4. If the server is also a domain controller, Microsoft's page points to its page on installing the Remote Desktop Session Host role service without the Connection Broker role service.

Example (illustrative): at contoso.com.au, users of the session host rds01 find that their local printers do not appear in the session, while their local drives do. The System log has no printer redirection events. On rds01, sc sdshow spooler returns D:(A;;CCDCLCSWRPWPDTLOCRSDRCWDWO;;;BA)(A;;CCLCSWRPWPDTLOCRRC;;;SY), which has the BA and SY entries and no AU entry. This matches Microsoft's cause.

Fix

If the AU entry is missing

Before you change it, save the current descriptor to a new file whose name includes today's date. Do not overwrite an earlier copy. Create C:\Temp first if it does not exist.

sc sdshow spooler > C:\Temp\spooler-sd-before-2026-11-22.txt

Risk: the next command replaces the whole security descriptor of the Print Spooler service on this server. If the string is wrong, other accounts can lose the right to start, stop or read the spooler, and printing for every user can fail until it is corrected.

Microsoft's fix is to put the AU entry at the start of the existing string, after D:, and keep every other entry. The command below is Microsoft's printed example, exactly as the page prints it, including the AU entry twice and the space after D:. Replace the trailing entries with whatever your own sc sdshow spooler showed, in the same order. Microsoft's sc sdset page gives the syntax as sc [<ServerName>] sdset <ServiceName> <ServiceSecurityDescriptor> and says <ServiceSecurityDescriptor> "Specifies the service descriptor in SDDL."

sc sdset spooler D: (A;;CCLCSWLOCRRC;;;AU)(A;;CCLCSWLOCRRC;;;AU)(A;;CCDCLCSWRPWPDTLOCRSDRCWDWO;;;BA)(A;;CCLCSWRPWPDTLOCRRC;;;SY)

Microsoft's page says this keeps "the old ACLs" and adds the missing one for authenticated user.

To undo it: put the saved string back. Open C:\Temp\spooler-sd-before-2026-11-22.txt (use the date of your own save), copy the string, and run the command below with that string in place of the placeholder. This does not overwrite the saved file.

sc sdset spooler <string from the saved file>

Run the undo only after the sc sdset command above has run. Run sc sdshow spooler again afterwards to confirm the output matches the saved file.

If a policy or client setting is the cause

Before you change the Easy Print policy, note its current state (Not configured, Enabled or Disabled).

Risk: the next steps change the Easy Print policy for every session on the servers that the Group Policy Object applies to. Microsoft's page ties Enabled to Easy Print redirection and Disabled to Legacy Print, so a wrong setting changes how every user's printers are redirected.

Make this change only if the policy is currently set the opposite way from what you want. In the Group Policy Management Editor, open Computer Configuration, Administrative templates, Windows Components, Remote Desktop Services, Remote Desktop Session Host, Printer Redirection, open "Use Remote Desktop Easy Print printer driver first" and set it to Enabled for Easy Print, or Disabled for Legacy Print, then apply the policy.

To undo it: return the setting to the state you noted.

For the client, first note whether the Printers box on the Local Resources tab is ticked, and if the connection uses an RDP file, note whether it contains redirectprinters:i:1.

Risk: the next step changes the connection settings for one user's Remote Desktop connection. Local printers are then offered to the remote session on every connection made with those settings.

Tick the Printers box on the Local Resources tab before connecting.

To undo it: clear the Printers box, or restore the RDP file setting you noted.

Confirm the fix

  • Run sc sdshow spooler again. The AU entry is present.
  • A user signs off and connects again. The redirected printers appear in the session.
  • If event 1116 or 1102 appeared before the change, check that it no longer repeats for that user.

What to watch afterwards

  • The spooler's security descriptor. Microsoft's page does not say why the AU entry went missing in its case, so run sc sdshow spooler again after any change to the server and compare it with your saved copy.
  • Printers per session. Event 1124 means the per-session limit was reached and the page gives no figure, so check the event, not the number.
  • The Easy Print policy after any Group Policy change.

Risks and limits

These commands have not been run or lab-tested.

Microsoft's sc sdset and sc sdshow pages list "Applies To" versions that end at Windows Server 2012. Microsoft's printer redirection page says "Supported versions of Windows Server" with no version list, and its events page is for Windows Server 2008 R2. Microsoft's pages do not say which fix applies to your server without the checks above, and they give no figure for the per-session printer limit. Editing a service security descriptor affects every user of the server: take the saved copy first, and test the change on one server.

Sources