Print migrator windows 2003 download.Microsoft Print Migrator 3.1
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support. This includes cross-architecture and stand-alone migrations, as well as configurations for a server in a cluster. This document provides step-by-step instructions for migrating from old hardware to new hardware and consolidating print servers.
Print and Document Services enables print server tools and configures the server to act as a print server. Print and Document Services is not dependent on any other features or roles. However, some specific network configurations, clients, and hardware may require you to install additional features or enable certain services. This guide provides you with instructions for migrating an existing print server to a server that is running Windows Server This guide does not contain instructions for migration when the source server is running multiple roles.
If your server is running multiple roles, we recommend that you design a custom migration procedure specific to your server environment, based on the information provided in other role migration guides. Migration guides for additional roles are available in the Windows Server TechCenter.
If your source server is running multiple roles, some migration steps in this guide, such as those for computer name and IP configuration, can cause other roles that are running on the source server to fail.
As a best practice, run the Printer Migration Wizard or Printbrm. You can run these tools either locally on the server or remotely from any other computer running Windows Server or Windows 8. For more information about installing and using these tools, see Access the migration tools. The Print Management snap-in is not available in Windows Server For more information about migrating from Windows Server , see Preparing to Migrate. The Print Management snap-in and the Printbrm. For more information about migrating from a server running a Server Core installation, see Preparing to Migrate.
You can migrate Print and Document Services from the destination server or from any client with the following:. The Printer Migration Wizard provided that the client is running one of the supported operating systems listed in the Supported operating systems matrix.
This document is intended for IT administrators and other knowledge workers who are responsible for the operation and deployment of print servers in a managed environment. Recovering server information that was not properly saved prior to migration for in-place upgrades. You must have access to the Printer Migration Wizard to migrate print servers. For more information about supported scenarios and limitations, see Preparing to Migrate. The following table outlines the supported operating systems for migration covered in this guide.
The versions of operating systems shown in the preceding table are the oldest combinations of operating systems and service packs that are supported. Newer service packs, if available, are supported. The Foundation, Standard, Enterprise, and Datacenter editions of Windows Server are supported on full, Server Core, and MinShell installation options, as either source or destination servers.
All versions of Windows Server are xbased. Migrating to an xbased server is not supported. Both xbased and xbased migrations are supported for Windows Server and Windows Server All editions of Windows Server are xbased. You might prefer the migration process, rather than an upgrade, even when the hardware is native xbased. An example would be a case where there is increased use of the server and there is a server role split in which the source server has more than one server role —and you decide to separate the roles onto several additional xbased servers.
In this case, migration of individual server roles to other servers might be the best solution. The server administrator can choose which parts of an existing installation to migrate, but along with the server role, this usually includes configuration, data, system identity, and operating system settings.
Migration from a source server to a destination server that is running an operating system in a different system UI language that is, the installed language than the source server is not supported. For example, you cannot use Windows Server Migration Tools to migrate roles, operating system settings, data, or shares from a computer that is running Windows Server in the French language to a computer that is running Windows Server in the German language.
The system UI language is the language of the localized installation package that was used to set up the Windows operating system. Cross-architecture migration such as migrating from an xbased server to an xbased server is supported.
The source server must have print queue drivers installed for both the source and destination server architectures. If a print queue does not have a driver for the destination server architecture, then it will not be migrated.
Similarly, verify that the destination server contains drivers for each supported architecture. The Supported operating systems matrix provides a complete listing of the supported migration scenarios. Some migration scenarios require additional preparation.
There are several things you must consider when managing migrations using v3 print drivers. The first is that a print queue cannot function without the native printer driver for the server architecture x86 or x64 on which it exists.
Since Windows Server is a bit only operating system, it is important that you have bit drivers installed for all of your printers if you are migrating from a bit system.
The most difficult transition is from bit to bit servers in an organization with bit clients since it is common to have third-party bit printer drivers that do not have bit equivalents.
Install the xbased drivers on the source server so that you can determine if there any problems or conflicts before the migration process. If there are conflicts or problems on the destination server after the migration, roll back the migration.
You must enable or install these features before restoring the source print server configuration. Plug and play printers. However, plug and play printer drivers will be migrated.
Any system or print administrators, or permissions. If you want to retain the same system or print administrators on the destination server as on the source server, you will need to manually add these administrators to the destination server. While the original server is still running, use the Printer Migration Wizard or the Printbrm. Then, import or restore this backup image to a destination server running Windows Server that has been configured to run as a print server.
To migrate printers from a server running Windows Server or a Server Core installation to a server running Windows Server R2, you must use a computer running the Printer Migration Wizard to remotely manage the server running Windows Server or a Server Core installation. Using this computer, you can store the printer settings file containing information about the printers you want to migrate, such as settings, queues, and drivers from the server running Windows Server or a Server Core installation to a file share.
You can then use the Printer Migration Wizard to migrate the printers from the file share to the server running Windows Server R2. The Printing-Server Core role must be installed on a server running a Server Core installation from which you want to migrate.
Access the migration tools. Prepare the destination server. Prepare the source server. Back up the source server. The objective of the migration process is that the destination server is able to perform the same functions as the source server did, without client computers on the network being aware that the migration has taken place.
The following sections describe the impact of migration. The source server is not impacted by print server migration until the destination server takes over as the active server typically when the name or IP address of the source server is assigned to the destination server.
At that point, the source server no longer services print requests that target the print server. If the destination server replaces the source server in the network same name or IP address , then there should be no impact to other computers in the enterprise. If the destination server has a different name or IP address than the source server, then all clients with existing print connections must delete and recreate those print connections so that they target the destination server.
Administrative permissions are required on both the source print server and the destination print server. If the destination server replaces the source server in the network, then no permissions are required on other computers in the enterprise. If the destination server has a different name or IP address, then the permissions required on other computers may vary depending on Group Policy settings, Windows Update access, and driver availability.
The time required to migrate a print server will vary from server to server, depending on the following:. Migrating a single printer queue with a typical xbased and xbased driver can range from five seconds to several minutes, depending on the factors listed above. Because of this range, a typical migration can take anywhere from less than an hour to several hours.
Skip to main content. This browser is no longer supported. Table of contents Exit focus mode. Table of contents. Warning If your source server is running multiple roles, some migration steps in this guide, such as those for computer name and IP configuration, can cause other roles that are running on the source server to fail.
Note All commands in this guide are case-insensitive unless specifically noted. Note Both xbased and xbased migrations are supported for Windows Server and Windows Server Note The system UI language is the language of the localized installation package that was used to set up the Windows operating system.
Note The Printing-Server Core role must be installed on a server running a Server Core installation from which you want to migrate. Additional resources In this article.
