Installing Network Components Without the Control Panel

 Last reviewed: December 4, 1997
Article ID: Q162771
The information in this article applies to:
  • Microsoft Windows NT Server versions 3.51 and 4.0
  • Microsoft Windows NT Workstation versions 3.51 and 4.0

SUMMARY

In order to install network components (for example, network adapters, network protocols or network services), you must use the Protocols, Services, or Adapters tab in Control Panel and then click Add to install the proper network component.

This article is aimed at providing a way to install any network component from a batch file, assuming you know the INF file name and the option. This information can be applied to install network components that are shipped with Windows NT, or to install any third-party component as soon as an Oemsetup.inf file is provided.

WARNING: The solution provided in this article doesn't compute the bindings. Therefore, if the bindings need to be done after the installation of a network component, the user will have run the Network Control Panel tool manually.

MORE INFORMATION

CAUTION: The solution included in this article has not been extensively tested in large installations. Microsoft cannot guarantee that modification of network components as recommended herein will accomplish the objective described in this article under all circumstances and in all configurations.

The Network Control Panel tool (loaded from a file called Ncpa.cpl) takes control over all setup of network components. When you add a network component through the interface, Ncpa.cpl tells Setup.exe to call Ncpashel.inf with specific parameters.

Instead of using the Network Control Panel tool, it is possible to call Setup.exe with the following parameters:

SETUP.EXE /f /i%systemroot%\system32\ncpashel.inf 

          /T NTN_InstallMode = Install
          /T NTN_Origination = install
          /T NTN_Infname = OEMSETUP.INF
          /T NTN_SRCPATH = D:\I386
          /T NTN_Infoption = OPTION
The command line above must be entered as a single line. Here is a description of all the parameters: 

/f                 = Turns off blue background
/T NTN_InstallMode = Install, Remove, Update, Configure or Bind 
                     This option is identical to the GUI interface
/T NTN_Origination = Install (= NCPA when setup issued by NCPA.CPL) 
/T NTN_Infname     = Name of the INF file name
/T NTN_SRCPATH     = Path to the distribution files
/T NTN_Infoption   = Name of the option. To figure out which option has
                     to be installed, open the INF file and search for the
                     section [Options].  You should find the name of the
                     option to setup.
For example, you may install Microsoft TCP/IP Printing with a batch file including the following commands (it is assumed below that D: is your CD- ROM drive):

cd %systemroot% setup /f /i%systemroot%\system32\ncpashel.inf 

      /T NTN_InstallMode = Install
      /T NTN_Origination = install /T NTN_Infname = .\OEMNSVTP.INF
      /T NTN_SRCPATH = D:\I386
      /T NTN_InfOption = TCPPRINT
Oemnsvtp.inf is the INF file that directs installation of the Microsoft TCP/IP Printing component. It contains the following section:

[Options] 

    TCPPRINT

Keywords          : ntsetup NTSrvWkst kbsetup
Version           : WinNT:3.51,4.0
Platform          : winnt
Issue type        : kbinfo

================================================================================

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: December 4, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.