Microsoft KB Archive/142159

= How to Automate SNMP Installation =

Article ID: 142159

Article Last Modified on 11/1/2006

-

APPLIES TO


 * Microsoft Windows NT Workstation 3.5
 * Microsoft Windows NT Workstation 3.51
 * Microsoft Windows NT Server 3.5
 * Microsoft Windows NT Server 3.51
 * MSPRESS Microsoft Windows NT Resource Kit 3.5

-



This article was previously published under Q142159



SUMMARY
When you run Unattended or Computer Profile Setup (CPS), the SNMP protocol is not installed to target computers (by default). However, you can accomplish automated installation of SNMP by modifying setup files.



MORE INFORMATION
WARNING: Modification of INF files may cause serious, system-wide problems before and after Setup and may require you to reinstall Windows NT to correct them. Microsoft cannot guarantee that any problems resulting from the modification of INF files can be solved. Make INF modifications at your own risk. Corporate Network Systems does not support the modification of INF files. For more information on INF files, refer to the Programmer's Guide included in the Windows NT DDK or contact Microsoft Consulting Services or a Solution Provider.

Computer Profile Setup
On the distribution server, make these necessary modifications:

 In the Defaults.inf file, change the third parameter of

!TCPIpServiceMask in the [TCPIPServices] section to 1.

[TCPIPServices]

!TcpIpServiceMask = {"1","1","1","0","0","0","0","0"}  (Optional) Modify the script fragment in Oemnxpsn.inf so that the SNMP configuration dialog box is not displayed. With this modification, Setup will not allow you to configure SNMP, so it will be installed with default values.

Code fragment before modification:

LibraryProcedure Result, $(!TCPCFG_HANDLE), CPlSnmp, $(!STF_HWND) ifint $(Result) == 0 set CommonStatus = STATUS_REBOOT else-ifint $(Result) == 1 set CommonStatus = STATUS_REBOOT else set RegistryErrorIndex = $(Result) goto fatalregistry endif

Code fragment after modification:

ifstr(i) $(!STF_GUI_UNATTENDED) == "YES" Set Result = 0 else LibraryProcedure Result, $(!TCPCFG_HANDLE), CPlSnmp, $(!STF_HWND) endif

ifint $(Result) == 0 set CommonStatus = STATUS_REBOOT else-ifint $(Result) == 1 set CommonStatus = STATUS_REBOOT else set RegistryErrorIndex = $(Result) goto fatalregistry endif 

Uattended Setup
 Copy the \I386 directory from the Windows NT compact disc to your hard drive. Expand i386\OEMNXPTC.IN_ to OEMNXPTC.INF. The Expand.exe file is located in the %SystemRoot%\SYSTEM32 directory. Rename i386\OEMNXPTC.IN_ to OEMNXPTC.BK_. WARNING: Modification of Setup files can cause serious, system-wide problems before and after Setup and may require you to reinstall Windows NT tocorrect them. Microsoft cannot guarantee that any problems resulting from the modification of Setup files can be solved. Make Setup file modifications at your own risk.

  Modify i386\OEMNXPTC.INF: <pre class="fixed_text">  ; Original line below ;                set InstallList = {"1","1","0","0","0","0","0","0"} ; Modified line below set InstallList = {"1","1","1","0","0","0","0","0"}

NOTE: It is not necessary to rename Oemnxptc.inf to Oemnxptc.in_. Windows NT Setup does not require the file to be compressed or named with an .in_ extension. </li> Expand i386\Oemnxpsn.in_ to Oemnxpsn.inf. The Expand.exe file is located in the %SystemRoot%\System32 directory.</li> Rename i386\OEMNXPSN.IN_ to OEMNXPSN.BK_. WARNING: Modification of Setup files can cause serious, system-wide problems before and after Setup and may require you to reinstall Windows NT to correct them. Microsoft cannot guarantee that any problems resulting from the modification of Setup files can be solved. Make Setup file modifications at your own risk.

</li> Modify i386\Oemnxpsn.inf using Step 2 in the Computer Profile Setup section.</li></ol>

Keywords: KB142159

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.