On Thu, Aug 28, 2014 at 12:20 PM, Gavin Wilby <[email protected]> wrote: > We have two print servers. > One is a 2003 server, one a 2012.
For this problem, the version of the print server isn't as relevant as what the print clients are running. If they're all running Vista/2008 or later, you're in better shape. XP/2003 or older printer clients complicate things. > There is also the problem that lots of users have old ghost printers, as > well as the fact that I need to get them. You're pretty much going to have to have something run for each user, then. Typically this is done at user logon (GPO and/or logon script). As noted previously, network printer connections are a property of the user, not the machine. > So if I have a user with two printers oldps\print1 and oldps\print2 > I need them to have newps\print1 and newps\print2. Is there any rhyme or reason to which printers which users need? If so, it's prolly easiest for you to create a GPO that removes *all* printer connections to the old server, and then other GPOs which add connections to the new server based on user membership in groups or whatever. If there's no rhyme or reason, is it viable to just add all printers to all users? This is brute force, but it works for some environments. If you need to be selective, your options are to script something, or buy a third-party product that will do it for you. I have no experience with the latter. For the former, I've used prnmngr.vbs to list existing printer connections, look for the old server, add the same on the new server, then remove the ones for the old server. -- Ben
