Microsoft Print Migrator Server 2008
Jul 02, 2010 This article is the step-by-step process from migrating printers from Windows Server 2003 to Windows Server 2008 R2 x64 using the Printer Migration Wizard. Oct 17, 2008 Why PrintMig 3.1 is Retired. In Windows Vista and Windows Server 2008, the Print Migration Wizard within the new Print Management Console is.
Free Migration Tools to Windows 2008 R2. Print Server Migration: tools and a step by step guide is provided to help with the migration of existing print.
. If necessary, enable the Administrative Tools menu, which is hidden by default on Windows-based client operating systems. Right-click Start, and then click Properties. The Start Menu and Taskbar Properties dialog box opens. On the Start Menu tab, click Customize. The Customize Start Menu dialog box opens.
Under System Administrative Tools, select Display on the All Programs menu or Display on the All Programs menu and the Start menu. In the Administrative Tools menu, click Print Management. If you are migrating from the x86-based architecture of Windows Server 2003 or Windows Server 2008 to the x64-based architecture of Windows Server 2012, you should install x64-based drivers on the source server before creating the backup file. The migration process copies all installed drivers from the source server to the destination server.
It recreates the printer queues on the destination server if the printer settings file contains the x64-based drivers. Verify that each print queue on the source server has a driver installed for the operating system on the destination server before creating the printer settings file. For example, if you are migrating an x86-based source print server to an x64-based destination print server, verify that each print queue has an x64-based driver installed before you create the printer settings file.
Microsoft Print Server 2012
Any print queue that does not have a cross-architecture driver installed will not be migrated to the destination server. To install cross-architecture drivers for a printer, you can use:.
The Add Printer Driver Wizard, which is available in the Print Management snap-in. The Printer Properties dialog box, which is available through the Printers folder in the Control Panel. As a best practice, you need to install a driver with the same name as the native architecture. To add the x86-based driver to the x64-based destination server, use the x86-based client to remotely open the x64-based server using Windows Explorer and navigate to the remote printer folder and add the driver. To install an x64-based driver on the x86-based source server, use the x64-based client to remotely open the x86-based server using Windows Explorer and navigate to the remote printer folder and add the driver.
Microsoft Print Server Setup
Tip In many cases, it can take you a long time to update all the print drivers for all your print queues. To save time, you may want to update just the most used print queues first, and gradually update the others when you have time. To save time, you can set the existing print queues to the Generic/Text Only driver for migration and later switch them to the OEM driver at your convenience. Most printers allow basic printing using the Generic Text driver. For more information, see at the Microsoft TechNet Blogs web site. Simple system-to-system migrations require no preparation for the source server.
However, additional preparation is required for cross-architecture migrations. If performing the migration as quickly as possible is a priority, remove unused drivers, ports, and queues before starting the migration to improve its speed after verifying with users that the items to remove are no longer in use. In general, however, minimize changes to the source server environment to ensure you can roll back to this environment if necessary.
Print Migrator
Note You should delete native print drivers that are not currently associated with a print queue because these drivers increase the size of the printer settings file unnecessarily. The print spooler will not allow a native print driver that is currently associated with a print queue to be deleted. The Print Spooler service will use non-native drivers. It routes these drivers to the Print Server service when a non-native client connects to a print queue and has to download a driver.
You should remove any unused drivers and print queues. Do not delete a non-native driver with a corresponding native print driver that is associated with a print queue. In this instance, the Print Spooler service will not prevent the non-native driver from being deleted. If the non-native driver's architecture matches the destination server's architecture, then you must block the driver's deletion. Cross-architecture drivers will never appear to be loaded by the Print Spooler service. Administrators should only delete them after confirming the drivers are no longer needed.