Migrating printers between servers used to be accomplished using a free add-on tool from Microsoft called PRINTMIG.EXE but as of Server 2008, the tool is built in. These instructions assume you are moving from something older to Server 2012 but roughly the same process was followed when I migrated printers from Windows Server 2003 to Windows Server 2008:
Add the PRINT SERVICES role
Open Server Manger (in Server 2012)
click MANAGE, ADD ROLES AND FEATURES
click NEXT throught the first few screens (and yes, it is a ROLE BASED FEATURE)
on the SERVER ROLES screen, select PRINT AND DOCUMENTATION SERVICES
accept the defaults to the end
in my case a reboot was required
Launch PRINT MANAGEMENT (i.e. on the tiles screen, click PRINT MAN and it will show)
Right click on the PRINT MANAGEMENT section head and select MIGRATE PRINTERS
Select EXPORT
Select A PRINT SERVER ON THE NETWORK, and browse to what will be your old print server
Name the export file (this single file will house ALL the drivers, ports and print queue)
Follow the wizard’s remaining obvious steps
Right click on the PRINT MANAGEMENT section head and select MIGRATE PRINTERS
Select IMPORT
Browse to the file you just created
Follow the wizard’s remaining obvious steps
This process will take a few minutes so don’t panic and take note that some errors are to be expected. For instance if you have TYPE 2 drivers, they will not be imported because Server 2012 ONLY supports Mode 3 and Mode 4 drivers.
Note that this tool works just fine (and is supported) between 32bit and 64bit servers.
Can you please share the script to delete all of the old printers and install new ones on our clients Win 7 machines. Also can we create an SCCM collection of the script and run it on our win 7 machines?
Thanks
I'm sorry, but we have no residual Win7 PC's left to test on. Our clients and our offices are all 100% Windows 10 now.
Does this create the corresponding TCP/IP ports on the destination server, or do they need to be created individually first?
please share the script so i can add it to the group policy to point to the new printers.
my email add is woundeddove09@gmail.com
Is this what you are looking for:
@Title = Correct Printer Share Names
@rem delete all printers with ports named IP_ - i.e. all network printers
rundll32 printui.dll,PrintUIEntry /dn /n "\\XXXX-fs1\Sams3380-BW-Act"
msg %username% Your printer name has been corrected.
following the wizar you get all the printers in the new server, but what happens with the workstations? do I need to go one by one migrating the end user to point to the same printer in the new server?
Yes, that is correct. I have a script I use to delete all of the old printers and install new ones. A link to the script can be emailed to staff so they can run it at will OR you could just add it to their login script. If you are interested, I will dig the script out an post it for you.
i need to configure a new printers location on each station?
I am sorry but I do not understand what you are asking. If you can rephrase it, I will take a crack at answering it.
Hey IAN,
You Rocks Man....
Your steps did it great...
and My New Print Server is Working Flawlessly now...
Thanks Alot For Your Support,
Keep It Up
AuRuM...
Will users still be able to connect to printers from the old server once the migration is complete
Yes they will... until you shut down the old server.
Ian thanks for the response. The tool worked except, I cant all the printers to migrate to the new server. All of the drivers are there but the printers on an old 2003 print server are still being stubborn. Any advice?
excellent
thanks for article ..
it worked
now how to migrate users to point to new serevr !!!
regardss
Nice guide for migrating print server into Windows 2012.
View Comments
Hi Ian,
Can you please share the script to delete all of the old printers and install new ones on our clients Win 7 machines. Also can we create an SCCM collection of the script and run it on our win 7 machines?
Thanks
I'm sorry, but we have no residual Win7 PC's left to test on. Our clients and our offices are all 100% Windows 10 now.
Does this create the corresponding TCP/IP ports on the destination server, or do they need to be created individually first?
please share the script so i can add it to the group policy to point to the new printers.
my email add is woundeddove09@gmail.com
Is this what you are looking for:
@Title = Correct Printer Share Names
@rem delete all printers with ports named IP_ - i.e. all network printers
rundll32 printui.dll,PrintUIEntry /dn /n "\\XXXX-fs1\Sams3380-BW-Act"
@rem install new printers
rundll32 printui.dll,PrintUIEntry /in /n "\\XXXXX-fs2\Sams3820-BW-Act" /q
rundll32 printui.dll,PrintUIEntry /y /n "\\XXXX-fs2\Sams3820-BW-Act" /q
msg %username% Your printer name has been corrected.
following the wizar you get all the printers in the new server, but what happens with the workstations? do I need to go one by one migrating the end user to point to the same printer in the new server?
Yes, that is correct. I have a script I use to delete all of the old printers and install new ones. A link to the script can be emailed to staff so they can run it at will OR you could just add it to their login script. If you are interested, I will dig the script out an post it for you.
i need to configure a new printers location on each station?
I am sorry but I do not understand what you are asking. If you can rephrase it, I will take a crack at answering it.
Hey IAN,
You Rocks Man....
Your steps did it great...
and My New Print Server is Working Flawlessly now...
Thanks Alot For Your Support,
Keep It Up
AuRuM...
Will users still be able to connect to printers from the old server once the migration is complete
Yes they will... until you shut down the old server.
Ian thanks for the response. The tool worked except, I cant all the printers to migrate to the new server. All of the drivers are there but the printers on an old 2003 print server are still being stubborn. Any advice?
excellent
thanks for article ..
it worked
now how to migrate users to point to new serevr !!!
regardss
Nice guide for migrating print server into Windows 2012.