I am trying to use the Default User, first via a customized install CD, and

then via the domain logon script folder, to automate some new machine

installs. We have 7 physical printers in house, and 6 of them have two

variations of settings (post script and non-PS, double sided/stapled and not,

etc. 13 printers to set up in all, for each of 30 users. And no time to do

it.

Even though the shared printer on the server is configured correctly, when

adding a printer on the client, only default settings come over. Thus, I had

hoped to build all the printers in the Default User, so when new users are

created based on that template, they would have all their printers done.

Unfortunately, I can't get anything to stick. even on a machine with printers

set up, I see nothing in the Printhood folder (or the Nethood folder for that

matter), and new users based on the Default User have no printers.

Anyone have any suggestions, even going down a totally different road (with

the exception of WMI, which I would not be able to learn before next weeks

roll-out).

Best,

Gordon

Creating default printer settings in a default profile(which I have never heard of being done) is not a good idea.. what if you modify the device? ie add a 3rd printer try.

What type of printers are you working with. How are you setting the device properties up.

have you tried disconnecting all printers on startup script before connecting them

IE: what i do in my printer logon scripts is disconnect the printers first in my script then re-add them in the same script to make sure that they download the latest drivers and updates when the printer get added.

another option might be to use the 'ms printer migrator', set up printers on one, backup, then restore on the other PCs...

http://www.microsoft.com/windows2000/techn...nt/download.asp

You could add the printers as Local printers then any user that logs into the machine will pick them up. Just remeber and uncheck the box that says "automatically detect and install my plug and play printer"