There are three options for migrating print servers from Windows NT 4.0 to Windows Server 2003. These options are:
· Manual
· Semi-automated
· Automated
Manual migration of print servers from Windows NT 4.0 Server to Windows Server 2003 is an option to exploit when all print clients have already been migrated to Windows 2000 Server or a more recent operating system. This option may be chosen so that kernel-mode drivers and unsupported port monitors can be completely removed from the print server.
This migration method, however, takes more time and is more prone to human error.
Semi-automated migration uses tools provided by Microsoft to speed up the process for migrating printers from the source Windows NT 4.0 server to the target Windows Server 2003 consolidated server.
Printers, drivers, and port configurations can be copied to the consolidated server using the tools provided. Some manual configuration is still required, but the bulk of the re-configuration is automated.
To manage driver-related issues, a command-line utility named fixprnsv.exe is provided with Windows Server 2003. This utility is available in the printers\fixprnsv directory of the Windows Server 2003 CD.
Fixprnsv.exe locates existing printer drivers that can replace older and unsuitable drivers. If a replacement driver is available for the printer, fixprnsv.exe replaces the problem driver with a driver provided by Microsoft. If it cannot find a replacement driver, it displays a message to check the Web site of the printer manufacturer for a new version of the driver. It only installs drivers for printers already configured on the print server.
Fixprnsv.exe from the Windows Server 2003 CD should be run on the Windows NT 4.0 print server to upgrade drivers that are blocked during the migration process. Microsoft maintains a list of troublesome printer drivers that cause server instability or failures. Windows blocks the drivers in this list from installation. For more information, search for “Printupg.inf” on the Windows Server 2003 hard drive or search for “Printupg.inf” at the following URL:
Print Migrator can back up and restore server configurations with minimal user intervention. It handles the migration of print queues, drivers, and printer ports. It is very useful when migrating and consolidating print servers. For more information on Print Migrator, refer to the following URL:
http://www.microsoft.com/printserver
Print Migrator does not change printer drivers or ports during server migration. It copies any kernel-mode drivers and the printer port configuration from the original Windows NT 4.0 server. Using Print Migrator, kernel-mode drivers are copied to the target print server to maintain the highest level of support for the existing Windows NT 4.0 print clients.
Print Migrator performs a backup and restore of only the port configuration (not the port monitors). If a port is being migrated to the new server, it needs to be installed on the target server before restoring the configuration from the backup.
In most cases, ports using non-Microsoft port monitors and unsupported ports need to be manually reconfigured to use the standard port monitor or LPR on the target computer. When restoring the printer configuration to the target server, Print Migrator provides the option of converting LPR ports to the higher performing standard port monitor; it does not convert other types of ports.
Print Migrator does not restore printers that have blocked printer drivers. Run fixprnsv.exe before backing up the source print server with Print Migrator. Note that fixprnsv.exe cannot update all blocked drivers. In some cases, it will prompt the administrator to download updated drivers from the printer hardware vendor Web site.
An in-place upgrade of Windows NT 4.0 to Windows Server 2003 is the most automated form of print server migration. Consider the following changes that may occur to existing print configurations during the upgrade:
· Windows NT 4.0 drivers that were shipped with the operating system are upgraded to the new version of these drivers in Windows Server 2003. The Windows NT 4.0 driver remains as an additional driver.
· If the name of an IHV driver explicitly matches the name of a driver that is shipped with Windows Server 2003, the installation will upgrade the driver to a Version 3 inbox driver (a driver that ships with Windows Server 2003). This upgrade occurs with no user intervention.
· Unstable drivers are blocked and printers that use these drivers are removed during the upgrade process. If the printer is connected directly to the computer and has a recognized Plug and Play ID, Windows searches for a suitable driver. If a suitable driver is found, the printer is installed during the upgrade as a new printer.
· Drivers that are not blocked and whose names do not match remain unchanged after the upgrade.
The in-place upgrade option is useful when the server hardware is suitable for a Windows Server 2003 print server and for one-to-one server migrations. However, when consolidating print servers, an in-place upgrade is only useful for migrating the first server that will become the consolidated server. All other printers need to be consolidated onto the consolidated server using Print Migrator or manual reinstallation of the printers.
Test the print servers to validate that each printer from the source environment exists, works, and is configured properly for all the client operating system versions identified during the assessment. Extensive reliability testing of the target print server is recommended if kernel-mode and monolithic drivers are installed.
浙公网安备 33010602011771号