What Powershell Command Did You Utilize In Install Print And Document Services?

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

How to Migrate Impress Server from Windows Server 2012 R2 to 2016 Cadre using Printbrm?

The impress server migration procedure is performed using the Printer Migration Wizard tool. Y'all tin can run it through the MMC Print Management snap-in or using the Printbrm.exe command line utility. Yous can run the migration magician 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 Cadre, the Printbrm.exe migration wizard is not bachelor.

The Migration Magician tool allows you lot to consign all the drivers, printer settings, print queues to the export file that can exist 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 manner all clients will go along printing without irresolute its settings. If information technology is not possible to assign the same name and IP address to the target server, then later 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 fashion, you demand to perform its bones configuration using the sconfig utility:

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

Install-WindowsFeature Print-Services

Now you can starting time the print spooler service:

Set-Service -Name "Spooler" -StartupType automated  Start-Service -Name "Spooler"

To allow remote management of Cadre 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 Direction"  Enable-NetFirewallRule -DisplayGroup "Remote Book 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"

Additional. If the target server must back up LPR, IPP or WSD, so yous must install and configure the appropriate components.

Exporting the Settings of the Source Impress Server to a File

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

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

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

Select choice Consign printer queues and drivers to a file.

Enter the proper noun of a new print server.

Review the list of objects to export.

Select consign file.

Await until the export is complete. The size of the export file tin can be quite large. In our case, 80 printers and about lx drivers were installed on the print server. The file size was well-nigh one.iv GB.

Importing Data From File to Target Server

Before you start importing printers, you lot demand 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 Issue ID 71 from PrintBRM.

Beginning the Migration Wizard again.
Choose option Import printer queues and printer drivers from a file.
Specify the server name and path to the data file.
Next select Import mode: Overwrite existing printers, List in the directory: Don't list any printers
Since in this instance printers are already published in Active Directory, we will not re-publish them to avoid making duplicates.

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

Switching Users to New Print Server

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

Rename the source server then that yous can assign its name to the new server. After renaming, you tin publish printers of the new impress server in AD:

This was the concluding pace to migrate print server. Hope this was useful!

Author
Recent Posts

I enjoy applied science and developing websites. Since 2012 I'm running a few of my own websites, and share useful content on gadgets, PC administration and website promotion.