Howard,
You are correct. Printers associated with computers not users. Yes, I caught your post about INI files read in, but don't think an INI with 300 sections would be an issue. If it becomes an issue, I could break it out so each WKSTA has its own INI.

I'd rather not manage and update 300 @WKSTA.kix files plus it would be more difficult to have an admin script auto-update them. INI file(s) would be easier to manage/update with an admin script.

With regard to your last post, If users add their own printers the individual files wouldl never get edited. I fear my coworkers may not follow up with a script edit either.

I think a script inventorying the printers and updating the INI(s) is the way to go. Whether I just rip them from the registry or use WMI as Jens suggests makes little difference.

Jens,
I run a 24/7 shop so nightly inventory is not the way to go. I'd probably trigger an admin script during logon as well as a scheduled one for those that never logoff. [Mad]
_________________________
Give a man a fish and he will be back for more. Slap him with a fish and he will go away forever.