installling printer driver to many pc of LAN

[t123456789]

Hi all

Now I have got 1 Click printer driver installer that include customs setting.

I want to know how to install the driver to many PCs (workgroup).

Help me plzz. (I don't know it can be?)

[schooltech]

Your 1 click installer should allow you to create a "rip" and push it out to whichever clients you want to.

Before you rip it, make sure the driver has all proper accessories picked, like finisher, hole punch, etc, and then 'image' that driver to the other machines on the network.

Other than that, you'll have to follow the destructions of the program, but most of these are pretty straightforward.

[TheOwl]

If you have installed your print driver on a server and shared it out, a simple way to install the driver on everyone's PC is to send out a link via email to the UNC path of the printer share.

\\servername\printsharename

All your clients have to do is click on the link and then click yes. No extra software required.

[schooltech]

Yeah, and then you're putting the responsibility in the hands of the end users. Some people should always stand 10 feet back from a machine!!!!


I think he just wants to push it out to the clients without having them do anything, but he didn't give too much information, so I may be reading it wrong. I'm not sure exactly what software he is using, as I've only messed with a few management console programs.

[TheOwl]

OK, so if no user interaction is what is wanted here then there is one other thing that could be done if the driver is installed on a Windows server.

For each user that logs on, you can set a logon script which will map network drives and so on. You can get the logon script to install the printer when the users logon.

This can be rather handy. Imagine for a second that the users PC gets re-imaged, you don't have to worry about reinstalling the queue as it will install again once the PC is joined to the domain and the user logs on,

[schooltech]

Yeah, we reimage about 2500 machines each summer in our school district. We run logon scripts for mapping of network drives, but elected to not have scripts for printer installs. We also found that pushing out more than one print driver, for those who have multiple printers installed throughout the year, sometimes causes the rip to not work properly because of default printers on their profiles, etc. So, the management console just rips out a single driver that will be the default, and we end up adding any additional drivers as need be. We also have certain profiles deleted upon restart, kind of a quasi "deep-freeze" setup. It works pretty well overall.

I think that because we don't know his environment, we're just throwing stuff out there and see what sticks. His environment might not be that involved, and running scripts and management consoles still might not be what he needs; he just may be looking at it as a convenient way to do it, yet it may be more involved than we are aware of.