wllmstwrt
asked on
push out software to client computers
we are receiving new copiers today and I would like to push out the driver. the problem is the driver file is a .exe file and not a .msi
What can I do?
AD is on server 2008 R2 client computers are mostly win7 64bit with some 32bit and xp machines.
What can I do?
AD is on server 2008 R2 client computers are mostly win7 64bit with some 32bit and xp machines.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Actually you can go one further on what s3e3 already posted.
Add the printer to the server, shared it out and publish it to AD. Then use a Group Policy to assign/add the printers to the client computer. The drivers will install automatically as long as you have all the correct/compatible drivers loaded on the server. No user intervention required.
Add the printer to the server, shared it out and publish it to AD. Then use a Group Policy to assign/add the printers to the client computer. The drivers will install automatically as long as you have all the correct/compatible drivers loaded on the server. No user intervention required.
I would change the wording "can go one step further" to "have to go one step further" as normal users cannot install published printers - so diggisaur's solution is the way.
For your original question about pushing exe setups, there are several ways. One is called MSI repackaging which can be done with tools like the free wininstall by scalable software.
Another is MSI wrapping which requires an exe that can use silent parameters for automation.
At last there is the scripted install using startup scripts, again the silent parameters are needed. If you look at the zap-solution it is similar.
If you are still interested, I would elaborate on your follow up question.
For your original question about pushing exe setups, there are several ways. One is called MSI repackaging which can be done with tools like the free wininstall by scalable software.
Another is MSI wrapping which requires an exe that can use silent parameters for automation.
At last there is the scripted install using startup scripts, again the silent parameters are needed. If you look at the zap-solution it is similar.
If you are still interested, I would elaborate on your follow up question.
Depending on what the exe offers, Patrick's solution will not work. This should be a split between Patrick and diggisaur who voted for using a print server solution with GPO deployment of printers in https://www.experts-exchange.com/questions/28323637/push-out-software-to-client-computers.html?anchorAnswerId=39733904#a39733904
This question has been classified as abandoned and is closed as part of the Cleanup Program. See the recommendation for more details.
Add the new copier to the print server, publish the printer in AD and have the users add the printers which will copy appropriate drivers to the workstation. No need to have them install a .exe or .msi driver package.