Bulk reply here. - Printers are just an object in the directory of class printQueue. There is no SID or anything like that attached to them. - The printer object needs to go away, eventually because it has the UNC path to the share on it - If you go to View>Show Objects as Containers (or something like that) in ADUC, and browse to your print server, you'll find all the printQueue objects under there.
- Mapping printers for people via GPO is completely unrelated to this publishing functionality. - FWIW, I usually argue against the concierge approach with GPOs - Old printQueue objects will automatically get pruned over time by AD. - Since you're republishing the printers on a new server, and it sounds like your customer population is leveraging this feature, I would use the above mentioned ADUC feature to go and just shift-click all the old printQueue objects and delete them once your old server is offline - In the event you bring your old server back up, the objects will be recreated Thanks, Brian Desmond br...@briandesmond.com w - 312.625.1438 | c - 312.731.3132 -----Original Message----- From: Michael Leone [mailto:oozerd...@gmail.com] Sent: Wednesday, February 13, 2013 8:06 AM To: NT System Admin Issues Subject: Replacing a print server - publishing printers in directory? So I need to replace one of my current print servers (Win2003, 32bit) with a new VM (Win2008 R2, 64bit). Some of you may recall my emails about this recently. Anyway, I have the new server ready, all printers defined on it (with the same names as the current production printers). My question is about actually cutting over to the new server. Before I do that, do I need to unlist the printers from the directory on the old production print server and unshare the printers *before* changing it's name and IP? That's a bit of a pain, because there are 93 printers, and I haven't found a way to do that as a batch, so I'd have to change each printer definition manually.I don't know how printers are treated in the directory - do they have a unique SID like a computer object, and so just creating a new printer with the same name on a server with the same name does not mean that it will just work? Once I unlist and unshare, I should be able to change the name and IP of the old server; re-assign them to the new printer; list all the new printers in the directory. And then all should Just Work. Is that right? Am I missing a step? Do I have a step wrong? Thanks ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe ntsysadmin ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe ntsysadmin
