Unsolved WIn 2k3 print server moving to a Win 2k12 print server with a different IP and name. What to do?

---

Here is my senario:

lets say We have a server named Server01, Server01 is a Windows 2003 file server that also serves printers.

Now we are standing up a new server which lets call it Server02 and will have a different IP address which will replace Server01 and act as the new print server.

Now once we take down server01 all the printers will have broken the connection. Once I have installed all the shared printers, I am looking for the easiest way to push out all the printers and avoid having to go to all the windows clients and reinstall manually.

Any guidance is much appreciated.

I believe this can be accomplished with group policy; I would rather not get moving and find a solution that works than go through the research and figure it out. We have to get this accomplished in little time.

@joshua-bingham,

I asked Don about this: "It depends on how the clients are mapped. If the clients map to the old IP, then the best bet is to use a GPO or login script to change the registry key that stores the IP of the printer. If the clients map to the name then you can use the SETSPN command to add the older server's name as a secondary name to the new server. Just update the DNS records and you are done."

@ronnie-wong The old server is going away, so I would not want to use SETSPEN, would I?

@joshua-bingham,

If you want it to appear "seamless" as you're replacing the old with the new, then you should use SETSPN.

I learned with Microsoft. Export the print server items out and keep the same name for print server unless you want to break everything and have to redo your workstations. Microsoft has easy export tools for it. I export print management out of the old server. Shut it down. Rename the new server to same name. Reboot it. Import print management back in. Your done.