On Thu, Apr 22, 2010 at 12:55 PM, tony patton <[email protected]> wrote: > We used to/still do use a similar naming convention, ie: claims_8000_038, > which was department, model and last octet of the IP.
I name Windows printer objects after department, and if needed, generic type. So "Accounting", "Sales", "SalesColor", etc. If the model is changed out for a different model, I just change the print driver while keeping the Windows printer object name the same. For the most part, that means things transparently keep working for the users. (Small org. If we were bigger, I'd prefix with the site name or something.) Printers themselves have network names and IP addresses independent of the above. Basically, I try to make them into queues, which represent logical functions, not physical printers, which are interchangeable parts. I liked how NetWare did printing: Printers and print queues were distinctly separate objects. You could assign multiple printers to one queue, or multiple queues to one printer. The *nix way also has advantages: Everything is a print queue. A print queue can have an arbitrary number of filters, and can hand off to another local queue, or to a port, or to a queue on a remote host. You can have multiple queues that set different print defaults without duplicating anything. Like most of *nix, it's cryptic and complex, but powerful once you figure it out. -- Ben ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
