Terminal Server Printer Redirection Wizard: Step-by-Step Setup GuidePrinter redirection lets users in remote desktop sessions use printers attached to their local workstations as if those printers were connected directly to the terminal server. The Terminal Server Printer Redirection Wizard simplifies deploying and managing redirected printers for Remote Desktop Services (RDS) and other terminal-server environments. This guide explains prerequisites, configuration options, step‑by‑step setup, troubleshooting, and best practices for reliable, secure redirected printing.
Overview: what printer redirection does and why it matters
Printer redirection maps local client printers into a user’s remote session so applications running on the server can print to the client’s physical or virtual device. Benefits include:
- User convenience — no need to install every client printer on the server.
- Centralized app management — desktop apps can print as though the printer is local.
- Reduced server admin overhead — automated mapping cuts manual driver installation and maintenance.
Common use cases: call centers, remote/hybrid workers, VDI setups, and SaaS-hosted Windows applications.
Prerequisites and environment checks
Before running the wizard, confirm:
- Server role: Remote Desktop Services or Terminal Services is installed and properly licensed.
- Network: stable connectivity between clients and server; sufficient bandwidth for print jobs.
- Client OS & RDP version: modern RDP clients (Windows, macOS, Linux) support printer redirection; older clients may not.
- User rights: users must have permission to connect via RDS and to install printer drivers if driver installation is required.
- Print driver strategy: determine whether to use universal drivers, client-side drivers, or server‑installed drivers.
- Group Policy: review policies that affect redirection (see next section).
- Print spooler health: ensure the Print Spooler service is running on the server.
Related Group Policy settings to review
Printer redirection behavior is often controlled by Group Policy. Key settings:
- “Do not allow client printer redirection” — set to Disabled to permit redirection.
- “Redirect only the default client printer” — enables mapping only the client default.
- “Use Remote Desktop Easy Print printer driver first” — when Enabled, prioritizes Easy Print (no server-side driver needed).
- “Allow printer redirection” — same purpose in newer ADMX templates.
- Permissions for driver installation via “Allow non-administrators to install drivers for these device setup classes” (if driver install is necessary).
If you use Easy Print (recommended where possible), ensure the .NET Framework and Remote Desktop Easy Print driver are available; Easy Print uses client-side drivers and the RDP channel to render print jobs, reducing driver installation issues on the server.
Step‑by‑step: preparing the server
- Install Remote Desktop Services (if not already installed).
- Update Windows with the latest patches to ensure RDP/Easy Print updates are applied.
- Ensure Print Spooler service is set to Automatic and running:
- Services → Print Spooler → Startup type = Automatic → Start.
- Confirm or install printer drivers if you plan to use server‑side drivers (see driver strategy).
- Configure Group Policy:
- Open Group Policy Management Console (GPMC).
- Edit the policy applied to your RDS servers or OU.
- Navigate to Computer Configuration → Administrative Templates → Windows Components → Remote Desktop Services → Remote Desktop Session Host → Printer Redirection.
- Set “Do not allow client printer redirection” = Disabled.
- Configure “Use Remote Desktop Easy Print printer driver first” = Enabled (recommended).
- Optionally, enable “Redirect only the default client printer” if desired.
- Reboot RDS servers or run gpupdate /force.
Step‑by‑step: running the Terminal Server Printer Redirection Wizard
Note: exact wizard screens vary by vendor or Windows version; this generic flow applies to the built-in wizard and many third-party helpers.
- Launch the Wizard:
- On the RDS server, open Server Manager or the printer management console and start the Terminal Server Printer Redirection Wizard.
- Select target servers:
- Choose the RDS host(s) or server farm where redirection should be enabled.
- Choose redirection method:
- Select between “Easy Print / client-side first” or “Server-side driver mapping.”
- Recommended: choose Easy Print for most environments to avoid driver deployment.
- Configure driver mapping (if using server-side drivers):
- Map common client printer model names to an available server printer driver.
- Use universal drivers (e.g., Microsoft Universal Print Class Driver, vendor universal drivers) when possible.
- Set policy options:
- Decide whether to redirect all client printers or only defaults.
- Configure session-level defaults and security settings for which users/groups this applies to.
- Test redirection settings:
- The wizard may provide a test option; otherwise, connect with a client and verify redirected printers appear in Devices and Printers inside the RDS session.
- Apply changes and close the wizard.
- If changes were made to drivers or policies, users may need to log off and back on (or you may restart the RDS host).
Client configuration checklist
- Ensure client RDP settings allow printer redirection: In Remote Desktop Connection → Local Resources → Printers checked.
- For macOS/Linux RDP clients, enable printer redirection in the client app preferences and ensure any required helper drivers or cups printer sharing are configured.
- Install local printer drivers on the client (as usual); Easy Print reduces server driver requirements but client drivers must exist for local printing.
Testing and verification
- Connect from a test client with a local printer attached.
- Open Devices and Printers in the remote session — redirected printers typically appear as “PrinterName (redirected X).”
- Print a test page from a simple app (Notepad, WordPad) and verify the job reaches the client printer.
- On the server, use the Print Management console to observe incoming print jobs and spooler behavior.
Troubleshooting common issues
- Redirected printer not appearing:
- Confirm RDP client “Printers” option is enabled.
- Check Group Policy for “Do not allow client printer redirection.”
- Verify Print Spooler is running on both client and server.
- Driver mismatch or errors:
- Switch to Easy Print to avoid server-side driver problems.
- Install matching universal drivers on the server when necessary.
- Slow logon times:
- Large numbers of redirected printers can delay session startup. Use Group Policy to redirect only default printer or limit exponential mapping.
- Use printer driver optimization and disable unnecessary printer features.
- Print job stuck in spooler:
- Restart Print Spooler, clear stuck jobs, and update drivers.
- Permissions errors installing drivers:
- Allow non-admin driver installations via Group Policy or preinstall drivers centrally.
Security considerations
- Limit which users/groups can redirect printers if sensitive documents are printed on unmanaged client devices.
- Consider network segmentation for RDS hosts handling sensitive workloads.
- Use Easy Print to avoid installing numerous third‑party drivers on the server, reducing attack surface.
- Ensure the RDS environment is patched and monitored for vulnerabilities.
Performance and scalability tips
- Use Easy Print whenever possible to avoid heavy driver loads on the server.
- Avoid mapping large numbers of client printers — redirect only the default or a curated list.
- Monitor spooler memory and CPU usage; distribute print load across print servers when necessary.
- For heavy print environments, consider a dedicated print server that receives redirected jobs from terminal servers.
Example: enabling Easy Print via Group Policy (concise)
- Open GPMC and edit the policy for RDS servers.
- Navigate to: Computer Configuration → Administrative Templates → Windows Components → Remote Desktop Services → Remote Desktop Session Host → Printer Redirection.
- Enable: “Use Remote Desktop Easy Print printer driver first.”
- Disable: “Do not allow client printer redirection.”
- Apply and run gpupdate /force on targets.
Maintenance checklist
- Keep Windows and RDP client versions up to date.
- Review and prune driver inventory on servers regularly.
- Audit Group Policy settings annually or when requirements change.
- Maintain a documented driver mapping list if using server‑side drivers.
Conclusion
The Terminal Server Printer Redirection Wizard simplifies bringing local printers into remote sessions. Favor Remote Desktop Easy Print to reduce complexity and driver churn. Combine correct Group Policy settings, a clear driver strategy, and proactive monitoring to ensure reliable, secure redirected printing across your RDS farm.
Leave a Reply