Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion GroupsWindows Server 2003Windows 2000Windows NTSmall Business ServerVirtual ServerExchange ServerIISHost Integration ServerISA ServerSMSWSUSMOMWindows Media ServerSecurityCertification
Related Topics
SQL ServerMS WindowsMS OfficePC HardwareMore Topics ...

Windows Server Forum / Windows 2000 / Terminal Services / February 2004

Tip: Looking for answers? Try searching our database.

Printing to Client printer

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Deb - 28 Feb 2004 16:43 GMT
What do I need to do in order for a person logged onto
terminal services to be able to print those files to his
home printer
Bj?rnar Bols?y - 28 Feb 2004 17:39 GMT
> What do I need to do in order for a person logged onto
> terminal services to be able to print those files to his
> home printer

1. You need the latest RDC client (5.1) for the home user.
2. You need to enable the "local devices\printer" option
   on his RDC icon.
3. You need to set up his home printer with a printerdriver
   that -matches- the printer driver name on the Terminal
   Server he logs into.

So when the user logs on, the TS printer picks up his local
printer, automagically sets up the printerque and redirects
the printerjobs to the local printer.

Step 3 is the tricky one. If you are lucky the users printer
is supported natively by the Terminal Server and you simply
install the correct driver. If not, you -might- want to obtain
an OEM driver from the manufacturer (say HP) and install it
on the TS server. But, although rare in my experience, you
run the risk of bugs and incopatibility problems.

A simpler solution would be to simply use an older, but
compatible driver on the users home PC (and install the same
driver on the TS server). Finding a compatible driver isn't
always straight forward, but you can be sure every HP printer
runs fine on the standard LaserJet or LaserJet Series II driver
(bear in mind that a printers advanced functions might not
be available).


Something to be aware of are the new multifunction USB printers
that are so popular today. They are not really suited for a
TS setup, although they will usually run quite well. The problem
is that the printjobs for these printers are, well, big compared
to more professional printers because they for instance don't
have a dedicated printjob processor and have to send fontdata
as part of the printjob. A simple black/white document print
can easily produce a 1-2MB printjob, as oposed to maybe 200-300KB
for a standard HP LaserJet office printer.

That's something to keep in mind when the user calls and
complains about "slow screen updates" now and then, even if
he's on a DSL broadband.

Regards...

 
Patrick Rouse [MVP] - 29 Feb 2004 23:36 GMT
There's actually a Remote Desktop Client newer than 5.1, i.e. 5.2.3790 that came with Windows Server 2003.  It's not much different that 5.1 but has some improvements

It can be downloaded here
http://www.workthin.com/tsdown.ht

More printing info here
http://www.workthin.com/tsp.ht

As Bjørnar said, if you're lucky you're printer has a built-in driver on the server, otherwise you have to go the route of adding a substitute inf file, as detailed on the URL above

Patrick Rous
Microsoft MVP - Terminal Serve
http://www.workthin.co

   
    ----- Bjørnar Bolsøy wrote: ----
   
    "Deb" <anonymous@discussions.microsoft.com> wrote in
    news:3adb01c3fe19$ecfd0bf0$a301280a@phx.gbl
   
    > What do I need to do in order for a person logged onto
    > terminal services to be able to print those files to his
    > home printe
   
   
     1. You need the latest RDC client (5.1) for the home user
     2. You need to enable the "local devices\printer" optio
        on his RDC icon
     3. You need to set up his home printer with a printerdrive
        that -matches- the printer driver name on the Termina
        Server he logs into
   
     So when the user logs on, the TS printer picks up his loca
     printer, automagically sets up the printerque and redirect
     the printerjobs to the local printer
   
   
     Step 3 is the tricky one. If you are lucky the users printe
     is supported natively by the Terminal Server and you simply
     install the correct driver. If not, you -might- want to obtai
     an OEM driver from the manufacturer (say HP) and install i
     on the TS server. But, although rare in my experience, you
     run the risk of bugs and incopatibility problems
   
     A simpler solution would be to simply use an older, but
     compatible driver on the users home PC (and install the same
     driver on the TS server). Finding a compatible driver isn't
     always straight forward, but you can be sure every HP printer
     runs fine on the standard LaserJet or LaserJet Series II driver
     (bear in mind that a printers advanced functions might not
     be available)
   
   
     Something to be aware of are the new multifunction USB printer
     that are so popular today. They are not really suited for
     TS setup, although they will usually run quite well. The proble
     is that the printjobs for these printers are, well, big compare
     to more professional printers because they for instance don'
     have a dedicated printjob processor and have to send fontdat
     as part of the printjob. A simple black/white document print
     can easily produce a 1-2MB printjob, as oposed to maybe 200-300K
     for a standard HP LaserJet office printer
   
     That's something to keep in mind when the user calls and
     complains about "slow screen updates" now and then, even i
     he's on a DSL broadband
   
   
   
     Regards..
   
   
   
     
   
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2009 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.