Many thanks Patrick
-----Original Message-----
Gotta love complicated documentation, huh? The registry
change for adding a user defined inf file is done on the
TS, NOT the client. I have a sample inf file & reg file
you can download here:
http://www.workthin.com/NTPrintSub.zip
The port mapping change for DOT4 and other non-standard
ports only needs to be change for client printers that
show something other than USB, LPT or IP_Address as the
port the printer is using.
Make sure your clients are using the latest Remote
Desktop Client (5.1 or 5.2), available here:
http://www.workthin.com/tsdown.htm
If you have time, read the chapter on Printing from Brian
Madden's book that's available on:
http://www.workthin.com/tsp.htm
I wish this were available to me 4 years ago...
The basic steps to troubleshooting auto-creation problems are:
1. Check event log for 1111 errors
2. Create mapping via inf file for the printer that's
not being autocreated, using suggested mappings on
http://www.printingsupport.com/matrix.htm
3. Have user logon and test printer.
4. If printer is auto-created, but can't print then the
mapping you made is to an incompatible print driver. (try
another)
5. If printer is NOT autocreated, check your registry
entry & inf file for correct spelling and syntax and check
the event log for 1111 errors.
6. If trial & error does not allow the printer to work
via inf mapping, you either have to load the driver on the
server (can be dangerous), purchase a printing product
like triCerat ScrewDrivers or get a different printer.
Patrick Rouse
Microsoft MVP - Terminal Server
http://www.workthin.com
----- Bob Showalter wrote: -----
Patrick,
Thanks for the quick reply. I have one other
question: I assume from the wording that the registry
change is to be made on the Terminal Server. Is that
correct?
Also, the Microsoft KB article referenced says to
change the port mapping on remote system system from DOT4
to LPT. Is that true even if it as USB port that is being
used by the multifunction device.
