Printing from changing workstations.

Archived from groups: microsoft.public.windowsnt.terminalserver.client (More info?)

Setting the default printer is easiest done within the users
logon script. It helps if you have a naming scheme for your
clients which reflects their location (and thereby most likely the
preferred default printer).

You'll need some sort of utility to do this:
Defprint.exe controls local printers (local to the TS),
Con2prt.exe controls network printers, or use a KiXtart script.

Examples (check for correct syntax!)

if %Clientname% == CLIENT01 DefPrint.exe /d "HP OfficeJet"

if %clientname% == CLIENT01 con2prt.exe \\PrintServer\printer01

if %clientname% = "CLIENT01"
SetDefaultPrinter ("\\TS\printer01" )
endif

Defprint.exe can be downloaded here:
http://www.dcug.de/phpnuke/html/modules.php?
name=Downloads&d_op=MostPopular

con2prt.exe is part of the NT Resource Kit.
KiXtart can be downloaded from http://www.kixtart.org

--
Vera Noest
MCSE,CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
*----------- Please reply in newsgroup -------------*

"=?Utf-8?B?TWF0dGhldyBXaWxsaWFtcw==?=" <Matthew
Williams@discussions.microsoft.com> wrote on 14 okt 2004:

> I've got a school with a mixed environment of Win98/2K/XP ,
> Macs, and Dumb Terminals, which is a PC with a bootable network
> card. The students are mostly using the Dumb Terminals, with
> the teachers using 'Smart' Terminals.
>
> The problem I'm having is printer mapping with the students.
> They jump onto different machines from class-to-class. I would
> like to setup a default printer according to the system they
> logon to. It wouldn't be so bad if they were all 'Smart'
> Terminals, but the students are going through the Terminal
> Server.
>
> They currently have access to all the printers, then have to
> choose which one to print to. There are about 30 printers, so
> that's no fun. I've looked into applying permissions to various
> printers, but the majority of the students need access to
> multiple printers.
>
> I'm thinking the solution is going to be a mixture of a script
> and Group Policy. Any suggestions will be helpful.
>
> Thanks in Advance.
>
> Matthew Williams