Hey everyone, I'm currently in the process of migrating our printers from Windows Server 2012R2 to 2022. The initial migration went smoothly on a server that had about 40 printers—I used the printer migration tool, imported the configurations, and changed the server name to match the old one without any problems. However, now I'm trying to migrate a different print server that has around 80 printers, and I'm running into an issue. When I import the migration file, it brings in the printers and drivers but skips the IP ports, defaulting to 'Print to file'. The event viewer shows an error that says it might be due to incomplete port data in the backup file or compatibility issues with the Windows version. Has anyone faced this problem before? I didn't have to create TCP/IP ports manually in my last migration, so this is puzzling.
3 Answers
For me, printer migrations have always been a chance to update drivers and tweak print settings. With only 40 printers, you could knock that out in an afternoon. But since you're dealing with 80 now, I get the hesitation. Just wondering, why do you think the ports didn't come over like before? That’s usually a reliable part of the migration if everything's compatible!
If you’re looking to simplify your printer management, I recommend checking out PrinterLogic. It can really streamline things by removing the need for print servers altogether. You might want to consider this for future upgrades!
I’ve had this issue pop up too! It might be related to the printers using a special port instead of a standard IP. Try installing the relevant printer drivers on the new server first; sometimes that ensures all the right port types get recognized during the migration.
Related Questions
Can't Load PhpMyadmin On After Server Update
Redirect www to non-www in Apache Conf
How To Check If Your SSL Cert Is SHA 1
Windows TrackPad Gestures