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:. The first is that there have been a number of general improvements regarding the reporting and handling of error conditions during the backup and restore processes.
Beyond the error reporting improvements though, there are some key functionality pieces to be aware of. The first one is a Selective Restore feature only available via the command line that allows administrators to selectively restore printers and their related objects. The meaning of the switch does depend on whether it is used with the — R restore or — B switch.
The high level process looks like this:. In addition, there may be situations where restoring the security settings for print queues may not be desirable — for example moving the print server to a different domain. If you are interested, I will dig the script out an post it for you. I am sorry but I do not understand what you are asking. If you can rephrase it, I will take a crack at answering it. Will users still be able to connect to printers from the old server once the migration is complete.
Ian thanks for the response. The tool worked except, I cant all the printers to migrate to the new server. All of the drivers are there but the printers on an old print server are still being stubborn.
0コメント