|
Deploying Printer Setups Across the Network
|
Login/Create an Account
| Top
| 5 comments
|
Search Discussion
|
|
|
|
The Fine Print:
The following comments are owned by whoever posted them.
We are not responsible for them in any way.
|
 |
|
|
|
|
by
Anonymous Coward
on Thursday July 05, @12:10AM (#119056)
|
|
|
|
|
|
We manage users, passwords, crons, printers, etc. with CF Engine.
http://www.onlamp.com/pub/a/onlamp/2004/04/15/cfen gine.html
|
|
|
|
|
|
|
|
|
|
by
Anonymous Coward
on Thursday July 05, @06:30AM (#119061)
|
|
|
|
|
If the macs are bound to an OS X Server, you can manage client printers using Workgroup Manager. You could also manage printers/print queues/etc. using Server Admin, again on OSX Server.
This may not provide granular enough control for you, however. For our machines, I've built an installer package that removes the old printer configurations and installs whatever files are needed. By pushing this package out to desktops using Apple Remote Desktop, and then using ARD's Task Server feature to get the laptops, the process can be pretty painless.
Good luck!
|
|
|
|
|
|
|
|
|
|
|
|
|
|
By far the best printer management suite out there is by Novell. Their iPrint print server allows for map based printer and driver management. For each printer configuration change, you can simply create/modify the printer settings at the server and they will be pushed out to the Windows/Linux/OS X print clients the next time they connect.
|
|
|
|
|
|
|
|
|
|
by
Anonymous Coward
on Thursday July 05, @11:12AM (#119067)
|
|
|
|
|
|
MacOSX uses CUPS, doesn't it? Couldn't you use that to keep the the printer setups up to date dynamically?
|
|
|
|
|
|
|
|
|
|
|
by
Anonymous Coward
on Thursday July 05, @03:20PM (#119072)
|
|
|
|
|
|
I once wrote a shell script to add printers and deployed it using Apple remote desktop all at once. Worked a treat for about 80 macs
|
|
|
|
|
