Discussion Locked

Automate TCP/IP Print Svc Installation?

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

Hello,
We are running Windows NT 4.0 Workstation with SP6a installed. Does anyone know of a way to automate the installation of services, specifically the MS TCP/IP Print Services? We are receiving new Xerox Docushare printers that we will be configuring the workstations to use a TCP/IP port configured for each printer, so if you know of a way to automate the installation/configuration of the ports also that will help. Mainly, I need to install the TCP/IP Print service on 2500 workstations and would like to automate the task. The service installation creates binding information in the registry related to the installed NIC, so using the repackage option in SMS Installer is not the way we'd like to go. I'd like for the actual installation (just as if the users were installing from Network Services on their system) to be automated. We will be using SMS 2.0 to deploy since our users do not have administrative rights required to install services and configure local printers. Thanks for any information on this one.

Arlo McCalla
arlo.mccalla

8 replies

by schitzoid

if you take a typical machine and open regedit, select HKLM\SYSTEM\CurrentControlSet and the choose file>export you'll have all the reg keys for you exiting drivers.
if you open a command line at c:\winnt and type dir system32 /s >filename.txt you have a text file of all your sytem and driver files.
make all the changes to the machine and do it again, giving the .reg and .txt files different names.
use the FC.exe utility to find the difference in the old and new files, piping this to a text file also ( fc /l file1 file2 >filediff.txt)
now to have a text file you can copy and paste from to write your login scripts for both updating regkeys, and copying driver files.
such as: regupdate.reg
REGEDIT4

[HKEY_LOCAL_MACHINE\SYSTEM\...]
"KeyNam"=dword:

And fileupdate.cmd

echo updating your system
xcopy \\server\share\files\ %systemroot%\ /s
shutdown /l /r /t:20 "your machine will now restart in 20sec"

use a second typical machine and test that everything worksby running the scripts.

by arlo mccalla

You pretty much described the SMS Installer's Repackage functionality, but by using a manual method. Very interesting as I never tried that manually, but it's still not going to work for us as the system I'm exporting this configuration from may not be the same as the system receiving the configuration. We have multiple configurations and are looking for a way for the installation of the service to create the registry keys for us, depending on the NIC installed and the configuration of it. Using the method you mentioned will be a static configuration and not work on all our different systems. Thanks for the response though. FYI, I've even opened a call with MS Premier Support a few days ago and they are still researching the issue. It appears it may be something that can't be automated the way I am requesting, we'll see what they say. I'll post their answer up here once they give me one, unless a tech-republic member comes up with it first. Either way, I'm happy :)

by gijoe

I don't think you'll be able to find a way to totally automate this, simply because of all the variables in hardware/software and probably printers that staff use.

by arlo mccalla

Microsoft finally gave up and said the only way to do it is to write your own application using the NT API calls, so we installed manually. We are upgrading to Win2K currently, so it's not an issue any longer. Thanks for your response!

Arlo

by ann777

Can't you choose which computers in SMS you wish to deliver the packages to? I know you can do this. You just need to setup so that each computer's current printer info is not overwritten.

by arlo mccalla

Yes, it is possible to send to systems based on many variables, such as network card installed, etc. We have so many configurations, we didn't want to go through setting up a package for each system type, and then the port settings (IP's) wouldhave to be set on the systems depending on their physical location in our building, so we decided installing manually was the best way to go. We're upgrading to Win2K currently, so it's not an issue any longer. Thanks for the response though!

Arlo

This discussion is closed to new replies.