If for some reason you had to install a 3rd party driver, i.e. to acheive specific functionality than only the manufacturers driver provides, see if the manufacturer offers a "corporate" driver, which is just the driver and not the utlilties, i.e. the junk that comes up in the notification area (system tray)
Also good to verify that the driver is certified (or compatible) with terminal services or Citrix
Patrick Rous
Microsoft MVP - Terminal Serve
http://www.workthin.co
-----
(E-Mail Removed) wrote: ----
Patrick - yes I had added the 3rd party drivers to the TS
I read somewhere that's what you need to do. Have since
read the article you suggest and will remove the Canon
driver and remap with new inf file to a compatible MS
driver
Thanks for hel
Gerain
>-----Original Message----
>The problem is that someone probably installed this
driver on the terminal server, instead of mapping it to a
built in driver using an inf file. Most 3rd party
printers are not made to run on Terminal Services. I'd
suggest removing the drivers for this model, then follow
the directions on this page to map this printer to a built
in driver
>>http://www.workthin.com/tsp.ht
>>You may want to do this during non-peak hours so you
don't interrupt the end-users work, as they won't be able
to print (to this specific printer) while you're making
the changes. You could even setup the inf file & registry
entries before removing the canon software so there's no
downtime
>>Patrick Rous
>Microsoft MVP - Terminal Serve
>http://www.workthin.co
>> ----- Geraint wrote: ----
>> I have set up client printing from our Win 2K
Terminal
> Server with no problems
> A couple of our clients however have a Canon LBP-810
> printer that insists on loading up Print Monitoring
> Software each time they connect and start a new
session.
> The problem is that when this software is loaded a
message
> is displayed on the Terminal Server, Admin login
screen to
> say that the software is successfully installed.
The
> client never sees this message, and unless the admin
spots
> it and clicks OK the client does not get their
printer
> mapped to their session as the default. There is no
way
> to disable this monitoring software without removing
the
> driver
> Has anyone else come across this or can suggest a
way to
> get around it please
>> Gerain
>>
>