Migrating printer from windows 2000 to Windows 2003 - How to make this transparent to users?

I am migrating all of our company's printers from a Windows 2000 server to Windows 2003 Server.  I am planning on using Print Migrator 3.1 to do this.  The 2 servers will not have the same name.  Is there any way that I can make this transparent to users so that they will not have to delete all their old printer mappings and add new?  A script perhaps?  
GDB IanAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Hi iburke666,

logon script deffinitely the best option

but seeing as how bad i am at scripting i can only point you in the direction

basically it is using this nice little peice of code

Set objWSHNetwork = CreateObject("WScript.Network")  'create network object
strConnectString = "\\server\printer"
strResult = objWSHNetwork.AddWindowsPrinterConnection(strConnectString)

Tony MassaCommented:
You will have to delete the old ones as well.  How many printers do you have?
Get the info on If Member here:  http://www.ss64.com/nt/ifmember.html
'    This is a script that will delete and then add printers, but you'll have to use group membership to decide
'     who gets what printers and what defaults, and you will also have to set a default printer for each user since when
'     delete all of the printers, Windows will choose a default printer for you
On Error Resume Next

strComputer = "."

Set objWMIService = GetObject("winmgmts:" _
    & "{impersonationLevel=impersonate}!\\" & strComputer & "\root\cimv2")

Set colInstalledPrinters =  objWMIService.ExecQuery _
    ("Select * from Win32_Printer")

For Each objPrinter in colInstalledPrinters
'  You will have to script the group membership checking...or you can just add all of
'  the printers and tell them to change the default printer themselves.  That would be easiest for small
'  numbers of users

   Set WshNetwork = CreateObject("WScript.Network")
   WshNetwork.AddWindowsPrinterConnection "\\SERVER-02\Printer Num1"
   WshNetwork.AddWindowsPrinterConnection "\\SERVER-02\Printer Num2"
   WshNetwork.AddWindowsPrinterConnection "\\SERVER-02\Printer Num3"
   WshNetwork.AddWindowsPrinterConnection "\\SERVER-02\Printer Num4"
   WshNetwork.SetDefaultPrinter "\\SERVER-02\Printer Num3"
always good when someone who knows what they are talking about posts!! cheers
Cloud Class® Course: Python 3 Fundamentals

This course will teach participants about installing and configuring Python, syntax, importing, statements, types, strings, booleans, files, lists, tuples, comprehensions, functions, and classes.

Are you planning on decommisioning the old 2000 sever?

If so, you can simply put a CNAME in DNS that points the old name to the new 2003 server.  Then the old "servername" would point to the new server too.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
GDB IanAuthor Commented:
We have about 30 printers and the old Windows 2000 server will be decommisioned.  How would I go about creating a cname to point from the old server name to the new?  Sorry for my ignorance.  thanks
I'll assume you are running windows 2003 DNS servers.

Inside DNS administration, in the forward lookup zone for that domain, right click the zone and choose New CNAME.  Then put in the name of the old server and point it to the new server.

Make sure the old server A record is out of DNS as well (do both of these after the old server is off).
Thanks for the points...

(BTW the other EE experts answers were right too, just they thought you really wanted to migrate to the new server name.  Be aware that unless you do actually change their settings locally you won't be able to get rid of that CNAME)
Tony MassaCommented:
Also don't forget to add a STATIC WINS record also if you have any downlevel (NT4) clients.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2003

From novice to tech pro — start learning today.