After following the threads related to TS client printing
issues, and trying the fixes suggested, I still have the
following problem.

I have 2 of 7 PC's using the current RDP, that when
connecting to the TS try to create a print session and
attach a printer to it. I have turned off the switch on
the clients RDP to not connect the local printer. The
PC's all connect to printers mapped on the TS. I want to
have each client connect to a specific zoned printer when
logging on.

The other issue is 3 thin clients (Neoware Capio's) have a
local printer attached that uses a custom driver. I get
the error 1111. When the user logs on, it attaches itself
to the proper printer, but the printer port changes for
that to that of one of the other thins. I can manually go
on to the TS and assign the proper port to the printer and
all is well, until the person shuts down his thin. I have
tried to follow the suggestion to "In the user's account
uncheck "Default to main client printer" but the problem
remains. I have also tried the MS kb on how to map a
native driver, but I must admit I don't know if I have the
syntax correct.

Setting the default printer is easiest done within the users
logon script. You'll need some sort of utility to do this:
Defprint.exe controls local printers, Con2prt.exe controls
network printers, or use a KiXtart script.

Examples (check for correct syntax!)

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

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

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


Mapping the printers manually to a specific port leads to the
problems that you describe. Documented here:
317780 - Print Jobs That Are Sent to Terminal Services Redirected
Printers May Print on Another Client's Printer
http://support.microsoft.com/?kbid=317780

I assume that you have read this article:
239088 - Windows 2000 Terminal Services Server Logs Events 1111,
1105, and 1106
http://support.microsoft.com/?kbid=239088

What part of the syntax is not clear to you? i.e. from the example
given in the article:
"HP DeskJet 720C Series v10.3" = "HP DeskJet 722C"

"HP DeskJet 720C Series v10.3" is the name of the driver on the
client
"HP DeskJet 720C Series v10.3" is the native driver on the server

--
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
--- please respond in newsgroup, NOT by private email ---

"Mike" <(E-Mail Removed)> wrote in
news:13cb101c41b18$6af1c0d0$(E-Mail Removed):

> After following the threads related to TS client printing
> issues, and trying the fixes suggested, I still have the
> following problem.
>
> I have 2 of 7 PC's using the current RDP, that when
> connecting to the TS try to create a print session and
> attach a printer to it. I have turned off the switch on
> the clients RDP to not connect the local printer. The
> PC's all connect to printers mapped on the TS. I want to
> have each client connect to a specific zoned printer when
> logging on.
>
> The other issue is 3 thin clients (Neoware Capio's) have a
> local printer attached that uses a custom driver. I get
> the error 1111. When the user logs on, it attaches itself
> to the proper printer, but the printer port changes for
> that to that of one of the other thins. I can manually go
> on to the TS and assign the proper port to the printer and
> all is well, until the person shuts down his thin. I have
> tried to follow the suggestion to "In the user's account
> uncheck "Default to main client printer" but the problem
> remains. I have also tried the MS kb on how to map a
> native driver, but I must admit I don't know if I have the
> syntax correct.

Using prnmngr.vbs seems to be the way to go, however, I
have Win2K server, not Win2003.
Where can I locate the script itself?


>-----Original Message-----
>I have sample inf & registry files available here:
>
>http://www.workthin.com/tsp.htm
>
>You can dynamically connnect users to specific network
printers via logon script using prnmngr.vbs:
>http://www.microsoft.com/resources/d...tion/windows/x
p/all/proddocs/en-us/prnmngr.mspx
>
>
>Patrick Rouse
>Microsoft MVP - Terminal Server
>http://www.workthin.com
>
> ----- Mike wrote: -----
>
> After following the threads related to TS client
printing
> issues, and trying the fixes suggested, I still have
the
> following problem.
>
> I have 2 of 7 PC's using the current RDP, that when
> connecting to the TS try to create a print session
and
> attach a printer to it. I have turned off the
switch on
> the clients RDP to not connect the local printer.
The
> PC's all connect to printers mapped on the TS. I
want to
> have each client connect to a specific zoned printer
when
> logging on.
>
> The other issue is 3 thin clients (Neoware Capio's)
have a
> local printer attached that uses a custom driver. I
get
> the error 1111. When the user logs on, it attaches
itself
> to the proper printer, but the printer port changes
for
> that to that of one of the other thins. I can
manually go
> on to the TS and assign the proper port to the
printer and
> all is well, until the person shuts down his thin.
I have
> tried to follow the suggestion to "In the user's
account
> uncheck "Default to main client printer" but the
problem
> remains. I have also tried the MS kb on how to map
a
> native driver, but I must admit I don't know if I
have the
> syntax correct.
>
>.
>