0
I have a Windows 7 Pro 64-bit machine that acts as a host for several remote Windows 7 Pro machines that connect to the host machine using the Windows 7 Remote Desktop Connection client that ships with Windows 7 Pro. I have enabled printer redirection for the remote machines and it's working perfectly. HOWEVER, every time a remote machine connects with RDC, those printers installed on the remote machine that don't have a matching printer driver installed in the host machine's Print Management sub-system generate a 1111 Error in the host machine's System log. This is a GIANT PITA because these messages are generated EVERY time a remote machine connects to the host machine using RDC! The 1111 Error messages are really beginning to pile up. I'm worried about filling up the System log on the host machine with useless error messages.
Has anyone found a way to deal with this problem besides, 1.) Disabling printer redirection - which I can't do, or 2.) Installing printer drivers for every printer installed on every remote machine that connects to the host machine? This seems like something that Microsoft would have fixed LONG ago, but I can't find ANY solution.
1Microsoft did fix the problem long ago, beginning with Windows Server 2008. Windows 7 isn't a server operating system and isn't intended to be used as such. Use the right tool (OS) for the job. – joeqwerty – 2015-06-04T05:55:22.360