These instructions describe how to migrate print services from Windows Server 2012 R2 to Windows Server 2016. Windows Server 2016 has built-in migration wizard.

Install Print Services on Server 2016

Step 1: Open the server manager. Click on the Add Roles and Features wizard.

Step 2: Click on Next.

Step 3: Choose Role-based or feature-based installation and click Next.

Step 4: Select a server from the server pool where you want to install print services. Click Next.

Step 5: Choose print and document services. Click on Add Features.

Step 6: Click on Next.

Step 7: Accept the default selections and click Next.

Migrate Windows Print Services

Step 1: Open the print management console.

Step 2: Right click print management and then click migrate printers.

Step 3: Choose export and click Next.

Step 4: Choose a print server from the network and enter the old print server name in this format \\<print server name>. You can also browse the old printer.

Step 5: Click Next.

Step 6: Name the file where you would like to place your exported data.

Step 7: Follow the wizard.

Step 8: Right click print management and then click migrate printers.

Step 9: Select import.

Step 10: Browse the file you just created in above steps.

Step 11: Follow the wizard till an end.

How to Migrate Print Services from Server 2012 to Server 2016

One thought on “How to Migrate Print Services from Server 2012 to Server 2016

  • Permalink

    In this article, I have documented the steps I took to update our two domain controllers to Server 2012 R2 from Server 2008 R2. While this can be considered a tutorial, it is more a reflection of what I did during my migration process. This guide assumes you have already made backups of your environment, all Windows Active Directory Domain Controllers in the forest are running Server 2003 or later, and we will be recycling (reusing) the same two servers you deployed. Last, Microsoft strongly recommends we do a clean install and not directly upgrade each server, so we will decommission a DC, reinstall windows, and then redeploy the DC until the entire environment has been upgraded.

    Reply

Leave a Reply

Your email address will not be published. Required fields are marked *

*