Moving printers to consolidate servers without interrupting users [Windows 2003 to 2003]

Question

Greetings! 
How do I go about moving network printers served from ServerA to ServerB, decommission/shutdown ServerA, and be completely transparent to users without causing them the need to remap printers?
My company is still at Active Directory level Windows 2003 SP2, and has all of our printers on several Windows 2003 SP2 servers. I am in the midst to decommission several old servers and consolidate print servers and then upgrade the domain to Server 2012
levels.
Right now, a user may have a network printer setup so that it is listed as "Printer1 on ServerA"
I want it so that when I move the printers to ServerB, users can still use their already setup "Printer1 on ServerA", instead of having to map them with "Printer1 on ServerB". Although, any new printers added from the consolidation point
forward to a users PC would be "Printer1 on ServerB".
My plan is to use my Windows 7 PC to:
Use Print Management to migrate/export ServerA printers to a file.
Use Print Management to migrate/import that ServerA printers file into ServerB. Using "Keep existing printers" in Import mode and "List All Printers" for List in the directory. [That would add ServerA's printers to
ServerB while keeping ServerB's printers. But I'm a little unclear which option to use for List in the directory.]
Shut down ServerA.
In our AD DNS, delete ServerA's A record and then either (a) add an A record for ServerA using ServerB's IP address, or (b) add a CN record for ServerA to point to ServerB's FQDN. [I think (a) is the better option, right?]
And then after the DNS refresh, the jobs should just come out of Printer1 on ServerA (as already listed/setup on my workstation) even though Printer1 now resides on ServerB.
I tried that plan last night, and things just didn't quite work out. My workstation said Printer1 on ServerA was Offline and I couldn't print to Printer1 on ServerA (which was imported onto ServerB) even though my DNS had ServerA with ServerB's IP.
For now I brought ServerA back online and people are working.
What am I missing or should be doing differently? Any issue with local security that would prevent one server to not accept commands directed to another servername? Thanks for your input!
Visual nutshell:
Printer1/ServerA ---> shutdown ServerA ---> Printer1/ServerB while those with Printer1/ServerA definitions on their workstations would still print.

Answer 1

When I last went from 2003 to 2008 R2, I did things a bit different.  I brought up the new server and migrated all printers.  I then had both servers running at the same time with the same configuration but all the clients
were pointing to the old server.  To move the clients I deployed this vbs script to all users using group policy as a logon script:
http://gallery.technet.microsoft.com/scriptcenter/20428e3a-12c6-4354-bddf-d748367fca72#content.  I left both servers running for some
time until all users were redirected.  I frequently then checked the old servers event logs for any print jobs until I no longer saw any and then shutdown the old server.  Hope that makes sense.
+1, I kinda do it that way too. (except I didnt know that script, as I used GPP to erase all printer connected & I was re-doing the printer connection after with GPP too)
Regards, Philippe
Don't forget to mark as answer or vote as helpful to help identify good information. ( linkedin endorsement never hurt too :o) )
Answer an interesting question ? Create a
wiki article about it!