Auto-Create printers

[Cary Shultz]

Hello NG,

My question: if there is no known driver for a printer
then it will not \ can not be added to a TS session via
the Auto-Create functionality. Correct? Well, not
without a little massaging. But that 'massaging' should
not be anything that a regular user could do.

We have a Terminal Server ( WIN2000 SP4 ) running Citrix
MetaFrame 1.8 SP3. The Auto-Create printer functionality
was disabled. Obviously there was a problem somewhere
that caused this to be disabled.

I thought that if there was no known driver for
printerABC
then printerABC could not / would not be added to the
Citrix connection. By 'no known driver' I mean that the
drivers for that particular printer do not exist on the
WIN2000 Server CD ( or, better said, in the ntprint.inf
file on the TS ) -AND- we have not mapped printerABC to
anything in the substitute .inf file. NOTE: The
substitute .inf file was the 'massaging' that I mentioned
earlier.

For example, I have a Lexmark printer ( USB connection to
my computer - it is the default printer on my local
system ) and before Auto-Create was disabled if I were to
create a Citrix connection and then look in the Event
Viewer | System Log I would see that the attempt to add
my
Lexmark printer to my Citrix connection failed - as
expected. Since Auto-Create was disabled, that 'failure'
is no longer logged - also as expected.

I am simply trying to become clear in my mind that if
known drivers do not already exist for printerABC (
either
natively or via the substitute .inf file ) then
printerABC
CAN NOT be added to the TS / Citrix connection via the
Auto-Create functionality. I thought that I was clear on
this but someone else is of the opinion that this is not
correct.

Thanks all,

Cary


PS. I have done a good deal of reading and this is
pretty
clear to me but....Patrick, your web site is really very
nice. The links are also very useful. If I had a couple
of extra printers available I would do the testing myself
in my lab but 'testing' in a production environment is
not
really anything for which I have any interest.

 

[Cary Shultz]

Patrick,

Understood. I simply used the ntprint.inf /
substitute .ing file used by RDP as this was more fresh
in my mind. You have given me the wtsuprn.inf file
before but I could not - off of the top of my head - come
up with the file used by Citrix.

Thank you,

Cary

-----Original Message-----
Citrix does NOT use this "user defined inf file" but

rather the wtsuprn.inf, which has the same syntax. IN
MetaFrame XP & 3.0 this mapping is handled by the GUI,
instead of directly editing the wtsuprn.inf file.

 

[Guest]

Cool

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

----- Cary Shultz wrote: ----

Patrick

Understood. I simply used the ntprint.inf /
substitute .ing file used by RDP as this was more fresh
in my mind. You have given me the wtsuprn.inf file
before but I could not - off of the top of my head - come
up with the file used by Citrix

Thank you

Car

-----Original Message----
Citrix does NOT use this "user defined inf file" but

rather the wtsuprn.inf, which has the same syntax. IN
MetaFrame XP & 3.0 this mapping is handled by the GUI,
instead of directly editing the wtsuprn.inf file