Your network contains an Active Directory Domain Services (AD DS) domain.

The Print Management migration wizard, built on printbrm.exe, documents that local bus printers, meaning printers connected through ports such as LPT or a locally attached USB-style port, are shown and processed during the backup step of the migration but are not successfully migrated to a working configuration on the destination server, because the physical port itself does not exist or map meaningfully on Server2. Printer1, connected through LPT1, and Printer2, connected through the similarly local, non-network Port1, both fall into this unsupported local-bus category and cannot be relied on to retain a working configuration after the move to Server2. Printer3, connected through a standard TCP/IP port pointing at a specific network address, is a fully network-addressable print queue whose port definition is meaningful on any print server, including Server2, so it migrates cleanly with its driver, queue settings, and configuration intact. Printer4, which uses the built-in FILE: port to print to a file rather than to physical hardware, is a virtual, hardware-independent port that is present identically on every Windows print server, so it too migrates without issue. Because printer drivers, queue settings, and port/configuration details only transfer meaningfully for ports that exist and behave identically on the target server, only Printer3 and Printer4 retain their current configuration after migrating to Server2.