Step-by-Step: Migrating Print Servers from Windows Server 2008 to Windows Server 2012
When we talk about migrating to a new OS we always have to think about each workload supported by the OS where looking at migrating. In this post we will look at migrating the Print and Document Services role from a Windows 2008 R2 server (W2K8R2-1) to the destination Windows Server 2012 server (PRNT-SRV)
To follow along:
- Download the evaluation of Windows Servers 2012
- Use the info in this post to setup your own lab
To manage the migration process, use one of the following:
- The Printer Migration Wizard, which you access through Print Management, a snap-in in Microsoft Management Console (MMC).
- The Printbrm.exe command-line tool.
Before you can start the migration process, you must ensure the Print and Document Services role is installed on the destination server (PRNT-SRV in our case).
1- Backup the source server (our 2008 R2 server) using the Printer Migration Wizard
From our Windows Server 2012 we will use the Print Management console to perform the Migration.
1- Open Server Manager, click Tools, and then click Print Management.
2- Right Click Print Management, and select Migrate Printer
3- Select “Export printer queues and printer drivers to a file” and click Next
4- Provide the Server name from which you want to extract to printer queues and drivers. and click next.
5- Review the list and click Next
6- Provide a location and a file name to save the extracted data and click Next
7- When the export is complete click Finish.
2- Restore printers to the destination server (PRNT-SRV) using the Printer Migration Wizard
1- Right-click Print Management, and then click Migrate Printers to open the Printer Migration Wizard. Select Import printer queues and printer drivers from a file, and then click Next
After selecting the file we created when we exported the Print Queues and drivers, click Next
2- Review the printers to be imported and click Next.
3- Select “This Print Server ( \\PRNT-SRV ) ” if you are running the Print Management console from the target server, or select the appropriate server in your domain by selecting “A print server on the network”
4- Set the import options and click Next
Wen the wizard completes, ensure that you do not have any errors, test the printers,
- View event log messages about the migration.
- Manually check the destination server for each printer migrated from the source server.
- Verify that the printer associated with each printer queue is online
- Confirm that a printer queue’s special settings, permissions, or drivers were preserved during the migration
- Check the properties for each queue on the destination server and verify that any special settings are still applicable.
- If the driver installs any non-standard settings that have been altered as a result of the migration, verify those as well
- Make any necessary changes, such as adding a port monitor or a new driver
If you are using Active Directory Domain Services (AD DS) to publish printers, do not publish printers to AD when you restore printers. This prevents duplicate printers from being displayed by AD DS before the destination server configuration is verified.
On the source server, you must unpublish printers before renaming the source server. To do this, select all printers in the Print Management snap-in, right-click the selected printers, and then click Remove from Directory. This prevents printers from being published twice to AD when the source server is renamed.
After renaming the destination server to the source server’s original name, you can publish all printers on the destination server to AD DS. To do this, select all printers in the Print Management snap-in, right-click the selected printers, and then click List in directory.
You can find more info about the Migration process here.
Cheers!
Pierre Roman, MCITP, ITIL | Technology Evangelist
Twitter | Facebook | LinkedIn
Comments
Anonymous
June 17, 2013
Pierre, Just wanted to say thanks for posting this. This covers a few points in the Windows 2012 Certification rather well. Just book marked this as an academic resource.Anonymous
June 17, 2013
Hey Steven, I'm glad you're finding these of value. Let us know if there are any other scenarios you'd like us to cover. PierreAnonymous
June 17, 2013
There are almost a half dozen typos in the text. Copy the text into word. You'll see the typos.Anonymous
June 18, 2013
Thanks Ed. I took care of those. It's what happens when you write an article at 2:00am. Thanks PierreAnonymous
July 11, 2013
What about upgrading the OS on a single print server from 2008R2 to 2012? Any specials concerns for the Print Management role?Anonymous
July 12, 2013
Hello Brachus, Good point! I have not gone through the process, but let me look into that. We are planning on more "upgrade" scenarios as part of our Step-By-Step series. Cheers PierreAnonymous
December 15, 2016
John Boehle found this article helpful but I had to force him to use it! Thanks Pierre!Alo