Event ID 1111 - Terminal Services Printer Redirection

I came across an issue with a remote user on a Mac that had a local printer attached and was trying to use printer redirection across rdp to our Win2k8 terminal server and rdp'ing from there to her office pc.  At one point it was working but then "stopped" all of a sudden.  Both x86 and x64 drivers were installed correctly on the ts box and her workstation.  Nothing stood out in the ts event viewer, but on her workstation I was getting a ton of event 1111 termservdevices errors like the one below:

Curious that her printer, the MFC7840W, was looking for an HP 4350 PS driver.  After reading more about the ntprintsubs.inf file and about the PrinterMappingINFName registry key, I was lead to theTerminal Server Printer Redirection Wizard Tool at MS kb239088.

Overview

The Terminal Server Printer Driver Redirection Wizard will help you troubleshoot and replace print drivers that were unsuccessfully redirected. This tool automates the process found in the Microsoft Knowledge Base article KB239088 entitled “Windows 2000 Terminal Services Server Logs Events 1111, 1105, and 1006” http://support.microsoft.com/?id=239088.

This tool will scan a server’s System Event Log and detect all events with Event ID 1111 and Source ‘TermServDevices.’ The tool will then scan the server’s registry for installed Version 3 MINI drivers, and prompt you to substitute an installed Version 3 MINI driver for each of the printers that failed printer redirection. Any changes will be written to a file named NTPrintSubs.inf which is where custom redirected printer mappings are stored.

Since the issue appeared to be her office workstation and not the terminal server, I extracted the package to a local folder on her pc and ran it.  After a few seconds of scanning the registry it found the issue with incorrect printer driver mappings between the HP 4350 PS and the MFC-7840W.  After a quick reboot, she was able to redirect her print jobs to her remote printer.  Good resource to know.

Cannot start Microsoft Office Outlook. MapI32.DLL is corrupt or the wrong version.

Office 2003 is compatible with Windows 7. However since you are having problems, try the following:

Rename MSMAPI32.dll to MSMAPI32.old.
Then try and start Outlook again.

The file path is C:\Program Files\Common Files\System\MSMAPI\1033 or do a search for MAPI32.dll.

If the rename doesn't help, then run fixmapi.exe - it's in one of the office folders or use search (use
advanced options for looking in hidden files and folders).