configure install windows print services

How to Migrate Print and Document Services from Windows Server 2012 R2 to Windows Server 2016 Core

This time we will take a closer look on how to migrate print server with the Print and Document Services role installed from Windows Server 2012 R2 to Windows Server 2016 Core. In our scenario, LPR (Line Printer Remote), IPP (Internet Printing Protocol) and WSD (Web Services on Devices) protocols are not used.

How to Migrate Print Server from Windows Server 2012 R2 to Windows Server 2016 Core?

The print server migration process is performed using the Printer Migration Wizard tool. You can run it through the MMC Print Management snap-in or using the Printbrm.exe command line utility. You can run the migration wizard either on the source server itself (if it is installed with a GUI), or on any other computer with the Print Management snap-in. On the Server Core, the Printbrm.exe migration wizard is not available.

The Migration Wizard tool allows you to export all the drivers, printer settings, print queues to the export file that can be imported to the target server. The final step is to decommission the source server and assign the target server the same name and IP address of the original server. This way all clients will continue printing without changing its settings. If it is not possible to assign the same name and IP address to the target server, then after the migration finish, it is necessary to reconfigure all clients (manually or using GPO) to use a new print server.

Configure Target Windows 2016 Core Server

After installing the OS in Server Core mode, you need to perform its basic configuration using the sconfig utility:

managing print service sconfig

After you have configured all the required server settings, install the Print and Document Services role by using the following PowerShell command:

Install-WindowsFeature Print-Services

install windows print services

Now you can start the print spooler service:

Set-Service -Name "Spooler" -StartupType automatic

Start-Service -Name "Spooler"

To allow remote management of Core server, enable a number of firewall rules:

Enable-NetFirewallRule -DisplayName "Windows Management Instrumentation (DCOM-In)"

Enable-NetFirewallRule -DisplayGroup "Remote Event Log Management"

Enable-NetFirewallRule -DisplayGroup "Remote Service Management"

Enable-NetFirewallRule -DisplayGroup "Remote Volume Management"

Enable-NetFirewallRule -DisplayGroup "Windows Firewall Remote Management"

Enable-NetFirewallRule -DisplayGroup "Remote Scheduled Tasks Management"

Enable-NetFirewallRule -DisplayGroup "Windows Management Instrumentation (WMI)"

Enable-NetFirewallRule -DisplayGroup "File and Printer sharing"

remote management print service server

Additional. If the target server must support LPR, IPP or WSD, then you must install and configure the appropriate components.

Exporting the Settings of the Source Print Server to a File

Before migrating, it is advisable to update the drivers on the source server to the Package-Aware versions (Package-aware printers have entries in their INF files that support point and print with packages).

Important. You should use the latest version of the migration wizard during the migration process. In this example, we use the migration wizard from the Print Management console (printmanagement.msc) on Windows 10. The Print$ share must be available on both servers.

Start Print Management console, right click on Print Management and select Migrate Printers.

print management console

Select option Export printer queues and drivers to a file.

managing print service migration

Enter the name of a new print server.

migrate print server

Review the list of objects to export.

printer migration server

Select export file.

printer migration export

Wait until the export is complete. The size of the export file can be quite large. In our case, 80 printers and about 60 drivers were installed on the print server. The file size was about 1.4 GB.

Importing Data From File to Target Server

Before you start importing printers, you need to create at least one printer. Otherwise, the print$ shared folder on the new server will not be created and the migration process will be interrupted with the error Event ID 71 from PrintBRM.

  1. Start the Migration Wizard again.
    migrate printers management
  2. Choose option Import printer queues and printer drivers from a file.
    printer migration import
  3. Specify the server name and path to the data file.
  4. Next select Import mode: Overwrite existing printers, List in the directory: Don’t list any printersprinter migration drivers
  5. Since in this case printers are already published in Active Directory, we will not re-publish them to avoid making duplicates.

After the import is completed, the wizard will prompt you to investigate the errors that have occurred during the import process. You can install problematic printers on the destination server manually.

Switching Users to New Print Server

After configuring all the printers on the target server, you can rename the source and target servers. But before you rename the source server, you need to delete the printer’s publications in Active Directory. In Print Management console select all printers, right click and select Remove from Directory.

printer queues

Rename the source server so that you can assign its name to the new server. After renaming, you can publish printers of the new print server in AD:

configure windows print services

This was the last step to migrate print server. Hope this was useful!

You may also like:

How to Migrate DHCP to Windows Server 2016 Migrating the DHCP service from the old server to the new Windows Server 2016 with saving of all the settings of the old server is quite easy. If the ...
Deploy Windows 10 with MDT 2013 and WDS In this article we will show you how to install and configure WDS role, MDT 2013 and Windows ADK on Windows Server 2012 R2 and use it to network PXE (...
Using IIS Manager for Remote Administration Managing multiple IIS servers over RDP can be quite inconvenient, especially if you need to administer dozens of such servers. It is much more conveni...
Print Job Stuck in Queue on Windows Server 2016/20... Print servers running Windows Server can have a large number of network printers connected. With a large number of devices, the Windows print queue ma...
Installing WebDAV client on Windows Server 2016 WebDAV (Web Distributed Authoring and Versioning) is an extension of the HTTP/1.1 protocol. The WebDAV protocol allows to access files on the remote s...

Add Your Comment