Question Locked

Changing client printers after an IP Schema change

0 helpful
4 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

The network printers at our location are installed as local printers using the Standard TCP/IP port. The printer connection is not scripted, and to my knowledge they didn't publish the printers using a DNS name, only IP. When we add a printer, it's done at the client machine using "add local printer, TCP/IP port, choose driver, name printer, etc etc etc"

We are preparing to change our entire IP schema and are looking for a way to automate the change at the clients' PCs, so we don't have to manually touch each one to reflect the update.

Is this even possible?

Please don't kill the messenger regarding the setup, it's been like this since I started working here and efforts to change to a print server or other, better methodology have fallen on deaf ears...

thanks for any help you guys can offer!

4 replies

by smileyginger

thanks, Peconet.

I just downloaded and installed it - this looks like a per client app - am I right? or did I miss something.

looking for something to perform the changes on an enterprise-wide scale. about 900 workstations for the various installed printers.

by ic-it

There is a registry key for each printer. You might write a startup script to read the IP address in the key and then based on the finding(s) replace the IP address for each found printer.

Here is the key give it a look and have fun.

HKLM\Software\Microsoft\windows NT\CurrentVersion\Print\Printers\local name used

edited to add; the IP address will be in the printer name key and in the sub-key(s) DSpooler and sometimes (default?) PrinterDriverData
The IP also appears in HKLM\System\ControlSet\Control\Print\Monitors\Standard TCP/IP Ports\(Actual IP address)

It's in all controlset numberings but you should be ok with the main one.

This discussion is closed to new replies.