How to Automate SNMP Installation

Last reviewed: January 21, 1996
Article ID: Q142159
The information in this article applies to:
  • Microsoft Windows NT Workstation versions 3.5 and 3.51
  • Microsoft Windows NT Server versions 3.5 and 3.51
  • Microsoft Resource Kit for Windows NT version 3.5

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:

  1. 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"}

  2. (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

  1. Copy the \I386 directory from the Windows NT compact disc to your hard drive.

  2. Expand i386\OEMNXPTC.IN_ to OEMNXPTC.INF. The Expand.exe file is located in the %SystemRoot%\SYSTEM32 directory.

  3. 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.

  1. Modify i386\OEMNXPTC.INF:

    ; 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.
    
    

  2. Expand i386\Oemnxpsn.in_ to Oemnxpsn.inf. The Expand.exe file is located in the %SystemRoot%\System32 directory.

  3. 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.

  1. Modify i386\Oemnxpsn.inf using Step 2 in the Computer Profile Setup section.


Additional reference words: 3.51
KBCategory: kbsetup kbhowto
KBSubcategory: ntreskit ntsetup


THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: January 21, 1996
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.