This object monitors the redirection of Remote Desktop Services printers.
Summary
Remote Desktop Services provides printer redirection, which routes printing jobs from a server to a printer that is attached to a client computer or to a shared printer that is available to the client computer. When a user establishes a remote session with an RD Session Host server, the redirected printer will be available to applications running in the remote session.
By default, an RD Session Host server, that is running Windows Server 2008 or newer, first tries to use the Remote Desktop Services Easy Print driver. If the client computer does not support this driver, the RD Session Host server looks for a matching printer driver installed on the RD Session Host server. You can either install a matching printer driver on the RD Session Host server, or you can create a custom printer mapping file.
Resolutions
To resolve this issue, check the event ID, and then view the troubleshooting information for that event in the sections below.
Resolution steps for the following event IDs: 1103, 1100
To resolve this issue, enable the Remote Desktop Device Redirector Bus. If you cannot enable the Remote Desktop Device Redirector Bus, replace the existing Rdpdr.sys file. If the problem persists, replace the RDPDR registry subkey.
To perform these tasks, refer to the following sections.
Enable the Remote Desktop Device Redirector Bus
To perform this procedure on the RD Session Host server, you must have membership in the local Administrators group, or you must have been delegated the appropriate authority.
To enable the Remote Desktop Device Redirector Bus on the RD Session Host server:
1. On the RD Session Host server, open Device Manager. To open Device Manager, click Start, click Run, type devmgmt.msc, and then click OK.
2. If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Yes.
3. Expand System devices.
4. Right-click Remote Desktop Device Redirector Bus, and then click Properties.
5. On the Driver tab, click Enable.
6. Restart the computer so that the changes take effect.
7. Start Device Manager, and then view the properties of the Remote Desktop Device Redirector Bus. In Device status, ensure that the message This device is working properly appears.
Replace the existing Rdpdr.sys file
If the Rdpdr.sys file is missing or corrupted, copy the Rdpdr.sys file from the Windows Server installation media into the %systemroot%\system32\drivers folder on the RD Session Host server, (where %systemroot% is the folder in which the operating system is installed, which is, by default, c:\windows).
To perform this procedure on the RD Session Host server, you must have membership in the local Administrators group, or you must have been delegated the appropriate authority.
To copy the Rdpdr.sys file:
1. Insert the installation media.
2. On the RD Session Host server, click Start, click Run, type expand source destination, where source is the path to the file that you want to expand on the installation disk, and destination is the path to the location where you want to save the file, and then click OK.
3. Restart the RD Session Host server.
Replace the RDPDR registry subkey
If copying the Rdpdr.sys file does not resolve the problem, the RDPDR registry subkey may be corrupted.
To resolve this issue, use either of the following methods.
To perform these procedures, you must have membership in the local Administrators group, or you must have been delegated the appropriate authority.
Method one
Replace the RDPDR registry subkey.
To replace the RDPDR registry subkey:
Caution: Incorrectly editing the registry might severely damage your system. Before making changes to the registry, you should back up any valued data.
1. On a working RD Session Host server, open Registry Editor. To open Registry Editor, click Start, click Run, type regedit, and then click OK.
2. If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Yes.
3. Locate the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\Root\RDPDR registry subkey.
4. Right-click RDPDR, click Export, and then save the .reg file. Copy the .reg file to the RD Session Host server that is having the problem.
5. On the RD Session Host server that is having the problem, double-click the .reg file that you created in the previous step.
6. If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Yes.
7. Click Yes, and then click OK.
8. After the registry subkey is imported, start Device Manager, expand System devices, and then click Remote Desktop Device Redirector Bus.
9. On the Action menu, click Scan for hardware changes.
10. Right-click Remote Desktop Device Redirector Bus, and then click Properties. In Device status, make sure that the message This device is working properly appears.
Note: You might have to restart the RD Session Host server for the changes to take effect.
If this method does not work, uninstall and then reinstall the Remote Desktop Session Host role service.
Method two
Uninstall and then reinstall the Remote Desktop Session Host role service by using Server Manager. For more information about uninstalling and reinstalling the Remote Desktop Session Host role service, see the Remote Desktop Session Host Help in the Windows Server Technical Library ( http://go.microsoft.com/fwlink/?LinkId=177721).
Important: If you uninstall and then reinstall the Remote Desktop Session Host role service, you may have to reinstall existing applications.
Resolution steps for the following event IDs:1111, 1102
To resolve this issue, do either of the following:
To perform these tasks, refer to the following sections.
Install or reinstall the printer driver on the RD Session Host server
If the printer driver installed on the client computer is an OEM driver, and a driver is available from the printer's manufacturer, replace the OEM driver with the driver that is available from the printer manufacturer. If you are installing a third-party driver, make sure that the driver is a Windows Hardware Quality Labs (WHQL) signed driver.
Important: After you install the printer driver, RD Session Host clients must log off from and then log on to the RD Session Host server before the printer driver changes take effect.
To install the printer driver, use either of the following methods.
To perform these procedures, you must have membership in the local Administrators group, or you must have been delegated the appropriate authority.
Method one
Run the printer's Setup program to install the printer driver .inf file on the RD Session Host server.
Method two
Install the printer driver by using the Add Printer Driver Wizard.
To install the driver:
1. On the RD Session Host server, click Start, click Run, type control printers, and then click OK.
2. On the File menu, click Server Properties.
Note: If the File menu is not visible, right-click an empty area of the Printers dialog box, and then click Server Properties.
3. Click the Drivers tab.
4. Click Add, and then follow the instructions in the Add Printer Driver Wizard to install the printer driver .inf file.
Create or modify a custom printer mapping file
You can create or modify an existing custom printer mapping file to define mappings from client-side to server-side drivers on the RD Session Host server.
To perform this procedure on the RD Session Host server, you must have membership in the local Administrators group, or you must have been delegated the appropriate authority.
To use a custom printer mapping file:
Caution: Incorrectly editing the registry might severely damage your system. Before making changes to the registry, you should back up any valued data.
1. On the RD Session Host server, open Registry Editor. To open Registry Editor, click Start, click Run, type regedit, and then click OK.
2. If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Yes.
3. Locate the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\Wds\rdpwd registry subkey.
4. Add the following values:
Name: PrinterMappingINFName
Type: String (REG_SZ)
Value data: Name of the .inf file to which you want to redirect lookups.
Example: c:\windows\inf\ntprintsubs.inf
Name: PrinterMappingINFSection
Type: String (REG_SZ)
Value data: Name of the section in the .inf file to which you want to redirect lookups.
Example: Printers
After you add the new registry values, create or modify the .inf file that you specified in the PrinterMappingINFName registry entry to include the user-defined mappings from the client-side to server-side drivers. Follow the format used in the following example:
;NTPRINTSUBS.INF
;Printer mapping file for client-side to server-side drivers
[Printers]
"OEM Printer Driver Name" = "Windows Server 2008 Driver Name"
For example:
"HP DeskJet 720C Series v10.3" = "HP DeskJet 722C"
The left side of the equation is the exact name of the printer driver associated with the client-side print queue that is being redirected to the server. The exact name of the printer driver appears on the General tab, next to Model when you view the printer properties on the client computer. (You can also click the Advanced tab and view the driver name in the Driver list.) The right side of the equation is the exact name of the server-side driver equivalent that is installed on the RD Session Host server.
Important: You must restart the Print Spooler service on the RD Session Host server for the changes to take effect.
To perform this procedure on the RD Session Host server, you must have membership in the local Administrators group, or you must have been delegated the appropriate authority.
To restart the Print Spooler service:
1. On the RD Session Host server, open the Services snap-in. To open the Services snap-in, click Start, point to Administrative Tools, and then click Services.
2. If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Yes.
3. In the Services pane, right-click Print Spooler, and then click Restart.
4. Confirm that the Status column for the Print Spooler service displays Started.
Resolution steps for the following event ID: 1115
To resolve this issue, ensure that the Print Spooler service is running on both the client computer and the RD Session Host server. If restarting the Print Spooler service does not resolve the issue, the printui.dll drive file on the RD Session Host server might be corrupted. To resolve this issue, reinstall the printer driver on the RD Session Host server.
To perform these tasks, refer to the following sections.
Start the Print Spooler service
To perform this procedure, you must have membership in the local Administrators group, or you must have been delegated the appropriate authority.
To start the service:
1. Open the Services snap-in. To open the Services snap-in, click Start, type services.msc, and then click OK.
2. If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Yes.
3. In the Services pane, right-click Print Spooler, and then click Properties.
4. On the General tab, ensure that Startup type is set to Automatic. If it is not, click Automatic, and then click Apply.
5. Under Service status, click Start.
6. Click OK to close the Print Spooler Properties dialog box.
7. Confirm that the Status column for the Print Spooler service displays Started.
Reinstall the printer driver on the RD Session Host server
If the printer driver installed on the client computer is an OEM driver, and a driver is available from the printer's manufacturer, replace the OEM driver with the driver that is available from the printer manufacturer. If you are installing a third-party driver, make sure that the driver is a Windows Hardware Quality Labs (WHQL) signed driver.
Important: After you install the printer driver, RD Session Host server clients must log off from and then log on to the RD Session Host server before the printer driver changes take effect.
To install the printer driver, use either of the following methods.
To perform these procedures, you must have membership in the local Administrators group, or you must have been delegated the appropriate authority.
Method one
Run the printer's Setup program to install the printer driver .inf file on the RD Session Host server.
Method two
Install the driver by using the Add Printer Driver Wizard.
To install the driver:
1. On the RD Session Host server, click Start, click Run, type control printers, and then click OK.
2. On the File menu, click Server Properties.
Note: If the File menu is not visible, right-click an empty area of the Printers dialog box, and then click Server Properties.
3. Click the Drivers tab.
4. Click Add, and then follow the instructions in the Add Printer Driver Wizard to install the printer driver .inf file.
Resolution steps for the following event ID: 1123
To try to resolve this issue, the user should disconnect the Remote Desktop Services session, and then reconnect.
Resolution steps for the following event ID:1124
To resolve this issue, create or modify the MaxPrintersPerSession registry entry to ensure that the maximum number of printers per session limit is not reached. By default, the maximum number of printers per session limit is 20.
To perform this procedure on the RD Session Host server, you must have membership in the local Administrators group, or you must have been delegated the appropriate authority.
To change the registry entry:
Caution: Incorrectly editing the registry might severely damage your system. Before making changes to the registry, you should back up any valued data.
1. On the RD Session Host server, open Registry Editor. To open Registry Editor, click Start, click Run, type regedit, and then click OK.
2. If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Yes.
3. Locate the HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services registry subkey.
4. Right-click Terminal Services, point to New, and then click DWORD (32-bit) Value.
5. Type MaxPrintersPerSession as the entry name, and then press ENTER.
6. Right-click MaxPrintersPerSession, and then click Modify.
7. In the Value data box, type the maximum number of printers that you want to allow per session, and then click OK.
8. Close Registry Editor.
For the settings to take effect, do either of the following:
Have the user log off from the session, and then start a new session.
Restart the Remote Desktop Services UserMode Port Redirector service on the RD Session Host server.
Use the following procedure to restart the Remote Desktop Services UserMode Port Redirector service on the RD Session Host server.
To perform this procedure on the RD Session Host server, you must have membership in the local Administrators group, or you must have been delegated the appropriate authority.
To restart the service:
1. On the RD Session Host server, open the Services snap-in. To open the Services snap-in, click Start, point to Administrative Tools, and then click Services.
2. If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Yes.
3. In the Services pane, right-click Remote Desktop Services UserMode Port Redirector, and then click Restart.
4. Confirm that the Status column for the Remote Desktop Services UserMode Port Redirector service displays Started.
Resolution steps for the following event ID:1108
This issue can typically be ignored. The default configuration will be applied to the printer queue when it is created.
Resolution steps for the following event ID:1105
To resolve this issue, first ensure that the Print Spooler service is running on the RD Session Host server. If the Print Spooler service is running, ensure that the print queue that is specified within the client session exists.
Ensure that the Print Spooler service is running
To perform this procedure, you must have membership in the local Administrators group, or you must have been delegated the appropriate authority.
To check the service:
1. On the RD Session Host server, open the Services snap-in. To open the Services snap-in, click Start, type services.msc, and then click OK.
2. If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Yes.
3. In the Services pane, right-click Print Spooler, and then click Properties.
4. On the General tab, ensure that Startup type is set to Automatic. If it is not, click Automatic, and then click Apply.
5. Under Service status, click Start.
6. Click OK to close the Print Spooler Properties dialog box.
7. Confirm that the Status column for the Print Spooler service displays Started.
Ensure that the print queue that is specified within the client session exists
If the client's print queue does not exist, the RD Session Host server cannot apply the printer's access control list (ACL) when it tries to make the printer available from within the session.
To ensure that the print queue that is specified within the client session exists, exit the Remote Desktop Services session on the client computer and then try to connect to the printer. If you cannot connect to the printer, verify the printer settings on the print server.
If the printer no longer exists, right-click the printer in the Printers tool (or the Printers and Faxes tool depending on the operating system version), click Delete, and then click Yes to confirm the printer deletion.
Resolution steps for the following event ID: 1114, 1112, 1107
To resolve this issue, start the Print Spooler service.
To perform this procedure, you must have membership in the local Administrators group, or you must have been delegated the appropriate authority.
To start the service:
1. On the RD Session Host server, open the Services snap-in. To open the Services snap-in, click Start, point to Administrative Tools, and then click Services.
2. If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Yes.
3. In the Services pane, right-click Print Spooler, and then click Properties.
4. On the General tab, ensure that Startup type is set to Automatic. If it is not, click Automatic, and then click Apply.
5. Under Service status, click Start.
6. Click OK to close the Print Spooler Properties dialog box.
7. Confirm that the Status column for the Print Spooler service displays Started.
Resolution steps for the following event ID:1116
To resolve this issue, the following components must be installed on the client computer:
Note: The RDC 6.1 (6.0.6001) client and the RDC 7.0 client support Remote Desktop Protocol 6.1.
Refer to the following sections to check which version of the components is currently installed on the client computer. If you need to download a newer version of either of the required components, see the Microsoft Download Center Web site ( http://go.microsoft.com/fwlink/?LinkId=102026).
Check the version of Remote Desktop Connection
To check the version of Remote Desktop Connection on the client computer:
1. On the client computer, click Start, click Run, type mstsc.exe, and then click OK.
2. Click the icon in the upper-left corner of the Remote Desktop Connection dialog box, and then click About.
3. The version will be listed in the About Remote Desktop Connection dialog box. If RDC 6.1 is installed, the version number will appear as 6.0.6001.
Check the version of .NET Framework
To perform this procedure, you must have membership in the local Administrators group, or you must have been delegated the appropriate authority.
To check the version of .NET Framework on the client computer:
Caution: Incorrectly editing the registry might severely damage your system. Before making changes to the registry, you should back up any valued data.
1. On the client computer, open Registry Editor. To open Registry Editor, click Start, click Run, type regedit, and then click OK.
2. If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue.
3. Locate and then click the following registry subkey:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP\v3.0\Setup
4. Locate the Version entry, and then view the value for the entry in the Data column. The value should be at least 3.0.04506.620.
5. If the value is less than 3.0.04506.620 or the v3.0 registry subkey does not exist, .NET Framework 3.0 SP1 is not installed on the client computer.
Resolution steps for the following event IDs: 1110, 1501
To resolve this issue, run the printer driver Setup program again to reinstall the printer driver .inf file. If the issue still occurs, and you use a custom printer mapping file to define mappings from client-side to server-side drivers, ensure that the custom printer mapping file is correctly configured by checking the following:
The correct printer mapping .inf file name is specified in the PrinterMappingINFName registry entry.
The custom printer mapping file contains entries.
The custom printer mapping file contains correct syntax.
To perform these tasks, refer to the following sections.
Install or reinstall the printer driver on the RD Session Host server
If the printer driver that is installed on the client computer is an OEM driver, and a driver is available from the printer's manufacturer, replace the OEM driver with the driver that is available from the printer manufacturer. If you are installing a third-party driver, make sure that the driver is a Windows Hardware Quality Labs (WHQL) signed driver.
Important: After you install the printer driver, RD Session Host server clients must log off from and then log on to the RD Session Host server before the printer driver changes take effect.
To install the printer driver, use either of the following methods.
To perform these procedures, you must have membership in the local Administrators group, or you must have been delegated the appropriate authority.
Method one
Run the printer's Setup program to install the printer driver .inf file on the RD Session Host server.
Method two
Install the printer driver by using the Add Printer Driver Wizard.
To install the driver:
1. On the RD Session Host server, click Start, click Run, type control printers, and then click OK.
2. Click a printer, and then click Printer server properties.
3. Click the Drivers tab.
4. Click Add, and then follow the instructions in the Add Printer Driver Wizard to install the printer driver .inf file.
Change the custom printer mapping file
To perform this procedure on the RD Session Host server, you must have membership in the local Administrators group, or you must have been delegated the appropriate authority.
To change the custom printer mapping file:
Caution: Incorrectly editing the registry might severely damage your system. Before making changes to the registry, you should back up any valued data.
1. On the RD Session Host server, make sure that the .inf file name that you specified in the PrinterMappingINFName registry entry of the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\Wds\rdpwd subkey is correct.
2. To verify the value of the registry entry:
3. On the RD Session Host server, open Registry Editor. To open Registry Editor, click Start, click Run, type regedit, and then click OK.
4. If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Yes.
5. Locate and then click the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\Wds\rdpwd subkey.
6. Locate the PrinterMappingINFName entry, and then view the value for the entry in the Data column.
7. If the file name is incorrect, right-click PrinterMappingINFName, click Modify, type the correct file name in Value data, and then click OK.
Open the printer mapping .inf file that is specified in the PrinterMappingINFName registry entry. Ensure that the file contains at least one mapping in its printer name mapping section. Also, ensure that the syntax is correct. The mappings should use the following syntax:
"OEM Printer Driver Name" = "Windows Server 2008 Driver Name"
The left side of the equation is the exact name of the printer driver associated with the client-side print queue that is being redirected to the server. The exact name of the printer driver appears on the General tab, next to Model when you view the printer properties on the client computer. (You can also click the Advanced tab and view the driver name in the Driver list.) The right side of the equation is the exact name of the server-side driver equivalent that is installed on the RD Session Host server.
Restart the Print Spooler service on the RD Session Host server for any changes to take effect.
To perform this procedure on the RD Session Host server, you must have membership in the local Administrators group, or you must have been delegated the appropriate authority.
To restart the service:
1. On the RD Session Host server, open the Services snap-in. To open the Services snap-in, click Start, point to Administrative Tools, and then click Services.
2. If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Yes.
3. In the Services pane, right-click Print Spooler, and then click Restart.
4. Confirm that the Status column for the Print Spooler service displays Started.
Resolution steps for the following event ID: 1113
To resolve this issue, increase the amount of available memory on the RD Session Host server. One way to increase the amount of available memory is to determine if there are any programs or processes running on the RD Session Host server that can be closed. Use Task Manager to determine which processes are using the most memory, and to end those processes.
To perform this procedure, you must have membership in the local Administrators group, or you must have been delegated the appropriate authority.
To free up memory on the RD Session Host server:
1. On the RD Session Host server, right-click an empty area of the taskbar, and then click Start Task Manager.
2. Click the Processes tab.
3. Make sure that the User Name and Memory (Private Working Set) columns appear. If they do not appear, on the View menu, click Select Columns, select the User Name and the Memory (Private Working Set) check boxes, and then click OK.
4. At the bottom of the tab, select the Show processes from all users check box.
5. If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Yes.
6. To sort the processes by memory usage, click the Memory (Private Working Set) column header.
7. Determine if you can end any of the memory-intensive processes.
8. To end a process, click the process name, and then click End Process.
9. Click End Process to confirm that you want to end the process.
If you cannot free up memory by using Task Manager, or if this issue still occurs after you try to free up memory, restart the RD Session Host server.
Resolution steps for the following event ID: 1122
To resolve this issue, stop and then start the Print Spooler service.
To perform this procedure, you must have membership in the local Administrators group, or you must have been delegated the appropriate authority.
To stop and then start the service:
1. On the RD Session Host server, open the Services snap-in. To open the Services snap-in, click Start, point to Administrative Tools, and then click Services.
2. If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Yes.
3. In the Services pane, right-click Print Spooler, and then click Properties.
4. On the General tab, ensure that Startup type is set to Automatic. If it is not, click Automatic, and then click Apply.
5. Under Service status, click Stop, and then click Start.
6. Click OK to close the Print Spooler Properties dialog box.
7. Confirm that the Status column for the Print Spooler service displays Started.
Resolution steps for the following event ID:1109
This issue can typically be ignored. This condition often occurs even though the default printer was set correctly.
Note: This condition might appear in situations where the Remote Desktop Services client has more than one redirected printer queue and the client is doing the following:
Disconnecting. When the client disconnects from a Remote Desktop Services session, the RD Session Host server will remove the redirected printer queues. The RD Session Host server might not remove the redirected printer queues in the same order in which it created them. If the RD Session Host server tries to restore a redirected printer queue that has already been removed, the default printer may not be set correctly.
Reconnecting. When the client reconnects to a Remote Desktop Services session, the Print Spooler service on the RD Session Host server enumerates the list of printers for the session. If the Print Spooler service does not correctly enumerate the printers that are in a disconnected state, the default printer may not be set correctly.
Home
ENU