Re: 3rd party print monitors
Absolutely! Take them one at a time: uninstall the 3rd party driver
and map it to a windows driver. Test from a client to verify that
the printer is redirected, using the windows driver (check the
EventLog, make sure that informational printer messages are enabled
on the TS, in Printers and Faxes - File - Server settings -
Advanced), then take the next driver.
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting:
http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___
=?Utf-8?B?cmljaGFyZA==?= <richard@discussions.microsoft.com> wrote
on 12 nov 2007 in microsoft.public.windows.terminal_services:
> Vera,
> Can I test this on the system by removing selected
> drivers and it
> won't affect the other. Just want to get the format correct.
>
> "Vera Noest [MVP]" wrote:
>
>> Completely uninstall all 3rd party printer drivers, and map
>> printers to a native windows printer driver by creating a
>> custom ntprintsubs.inf file.
>>
>> Details are explained here (valid for 2003 as well):
>>
>> 239088 - Windows 2000 Terminal Services Server Logs Events
>> 1111, 1105, and 1106
>> http://support.microsoft.com/?kbid=239088
>> _________________________________________________________
>> Vera Noest
>> MCSE, CCEA, Microsoft MVP - Terminal Server
>> TS troubleshooting: http://ts.veranoest.net
>> *----------- Please reply in newsgroup -------------*
>>
>> =?Utf-8?B?cmljaGFyZA==?= <richard@discussions.microsoft.com>
>> wrote on 12 nov 2007:
>>
>> > I have a terminal that users print locally from terminal
>> > server farm. 3rd party print monitor are hanging the login.
>> >
>> > Is there a way to delete the 3rd party print monitors from
>> > terminal server and have the autocreate use winprint rather
>> > then hp, dell, lexmark etc print monitor.