How Can I Bulk Update Manually Configured Printer IP Ports on Windows?

For directly attached TCP/IP printers, PowerShell is probably the most practical option. You can enumerate printers with Get-Printer, inspect their current ports, create replacement ports with Add-PrinterPort, and then point each printer to the new port with Set-Printer. Test the mapping carefully first, especially if several printers use similar names. Deploying the script through a computer startup script or a narrowly scoped Group Policy can handle the clients in batches. For the future, use DNS hostnames instead of hard-coded addresses whenever possible.

If the printers are connected through a print server, the migration may be much easier. Client printers should reference a shared path such as \PrintServerPrinterName rather than a local IP port. You can migrate or recreate the shared queues and deploy the connections through Group Policy. If the server’s DNS records are updated to follow the printers’ new addresses, clients may not need any changes at all. Direct-IP installations are the ones that require local port updates.

I’d avoid changing every machine at once. Build a script that records each printer’s name, current port, and driver, then maps the old address range to the new one. Have it create the new standard TCP/IP port, switch the printer to that port, and log success or failure. Pilot it on a few test computers through a filtered Group Policy, verify printing and default-printer behavior, and then expand the scope. If possible, use the network change as an opportunity to introduce a print server or DNS-based printer names.