Networking Connectivity
Network Connectivity
Unattended Installation of Windows NT* 4.0 Workstations

Basics
Version A - Simple Version
Version B - More Complicated Version
Tested Adapters and Specifics
UNATTEND.TXT File without Adapter Section
UNATTEND.TXT File with Adapter Section

NOTE:  This document describes a generic unattended install process. It is intended for the adapters listed in the "This applies to" section below. Specific instructions are included on the distribution CD or diskette for some models, and those instructions should be followed if they apply to your adapter.

For all Intel network adapters based on 82557, 82558 or 82559 LAN controllers (the PRO/100B, PRO/10+ PCI and the Intel PRO/100+ line of adapters) please follow the custom procedure described in the document NTPUSH.TXT. This file is in the directory \INFO\MS\ on the software and drivers CD distributed with your adapter. This file is also included in the latest driver download for these products.

This information is provided solely as a convenience to Intel customers. If you have questions about Microsoft Windows NT* or the unattended installation process, consult your Windows NT documentation or contact Microsoft for assistance.

Back to Top

Basics
All unattended installations start with creating a directory on a network drive called \I386 and copying all the files from the \I386 directory of the install CD to that network directory. If the server is a Windows NT 4.0 server, create a share for that directory. If the server is a NetWare* server, assign the appropriate rights to the person who will be logged into the server doing this installation and map a drive to the \I386 directory. There are several ways to do an unattended install successfully. The more complicated version (called Version B in this document) is necessary if, during the installation, the workstation must join a domain. The simple version (Version A in this document) can be used most of the time.

Back to Top

Version A - Simple Version

Preparation

  1. Copy the \I386 directory and all it's files and subdirectories from the Windows NT 4.0 installation CD to a directory on the server.

  2. Change to the \I386 directory on the server.

  3. Create a subdirectory of \I386 called $OEM$. You should now have this directory on the server:

    \I386\$OEM$

  4. Create a subdirectory of \I386\$OEM$ called NT. You should now have this directory on the server:

    \I386\$OEM$\NT

  5. Copy the files from the \NT directory on the LAN driver diskette into the \I386\$OEM$ directory AND into the \I386\$OEM$\NT directory. If there is an OEMSETUP.INF in the \NT directory of the driver diskette, do not copy the one at the root of the driver diskette. If there is an OEMSETNT.INF in the \NT directory of the driver diskette, copy it and change its name to OEMSETUP.INF. If the only OEMSETUP.INF is the one at the root of the driver diskette, copy it. Also copy the adapter's .INF file.

  6. Create an answer file (UNATTEND.TXT). Use the sample at the end of this document and make the appropriate changes.

  7. Copy the UNATTEND.TXT you just created into the \I386 directory. See Microsoft's documentation for parameters that may be used in the answer file.

  8. Install the LAN adapter into the target workstation and log onto server. You may use a floppy boot disk or you may prepare the hard drive and boot from it.

Installation

  1. Change to the \I386 directory. It is important that, if the target workstation needs to reconnect to the server during the install, the setup program can find the \I386 directory. This means that you should create a mapping that will exist when the machine reboots. If you are installing from a NetWare server, just use the default network drive. If you are installing from a Windows NT 4.0 server, map Z: to the share.

  2. Change to the mapped drive you just created and execute the installation command line as follows:

    winnt /s:<drive>: /x /b /u:<drive>:\unattend.txt

    If you booted to a floppy disk, remove the boot disk from the machine as soon as the installation begins.

Back to Top

Version B - More Complicated Version

Criteria
If you are assigning static IP addresses during the installation and/or joining a domain during the installation and Version A with the \$OEM$ directory is not working, try this version.

Preparation

  1. Copy the \I386 directory and all it's files and subdirectories from the Windows NT 4.0 installation CD to a directory on the server.

  2. Change to the \I386\DRVLIB.NIC directory on the server.

  3. Create a directory for the adapter drivers. You may call the directory anything you want. Make a subdirectory in it called \NT.

  4. From the LAN adapter driver diskette, copy the files from the \NT directory, and the OEMSETUP.INF and the network adapter's .INF from the root into the \I386\DRVLIB.NIC\ADAPTER_DIRECTORY directory AND to the \I386\DRVLIB.NIC\ADAPTER_DIRECTORY\NT directory. If there is an OEMSETNT.INF, copy it instead of the OEMSETUP.INF and rename it OEMSETUP.INF.

  5. Edit the OEMSETUP.INF (or the OEMSETNT.INF) from the drivers diskette and collect the following information:

    [OptionsTextEng] ____________________________________

    [PlatformsSupported] _________________________________

    If you cannot find this information in the .INF file, it is probably not designed for Windows NT 4.0. You may have to follow the simple version and make appropriate changes after the install is finished.

  6. Using the Windows NT 4.0 CD with the \I386 directory on it, use the extract utility on the CD to extract \I386\OEMNADZZ.IN_ from the CD to the \I386 installation directory on the server.

  7. You will need to edit the OEMNADZZ.INF and add the adapter information you collected above to the appropriate sections. If you look at the file you will notice that there are 3 sections for each bus type--- Options, Filename and OptionsTextEng. You are supposed to add the appropriate information to the appropriate sections and it must appear in the same position in each list. In other words, you are supposed to add the information to the top of each list. It has been shown that this does not always work. To avoid conflicts, remove all information from all bus type sections and replace them with only the pertinent information. Be careful not to change any of the program instructions that appear after the bus information. Do not remove the section headings. The following example is based on the Intel PRO/10+ ISA adapter:

    [PCIOptions]
    [PCIFilename]
    [PCIOptionsTextENG]
    [MCAOptions]
    [MCAFilename]
    [MCAOptionsTextENG]
    [ISAOptions]
    EPRO[ISAFilename]
    DRVLIB.NIC\EPRO\OEMSETUP.INF
    [ISAOptionsTextENG]
    EPRO = "Intel EtherExpress(TM) PRO/10 or PRO/10+ ISALAN Adapter"
    [EISAOptions]
    [EISAFilename]
    [EISAOptionsTextENG]
    [Jazz-Internal BusOptions]
    [Jazz-Internal BusFilename]
    [Jazz-Internal BusOptionsTextENG]

    Note:  If the adapter is being installed in an EISA machine, the information must appear in the EISA section also. It does not matter if the adapter is not an EISA adapter.

  8. Change to the \I386\DRVLIB.NIC directory on the server. Create a subdirectory for the adapter there, using the adapter's name as indicated in the OEMSETUP.INF file [OptionsTextEng] section. If a subdirectory with that name already exists, delete all the files in that subdirectory. Make another subdirectory of the adapter subdirectory called \NT. If, for example, you were installing an Intel EtherExpress™ PRO/100 EISA LAN Adapter, your directory structure would look like this:

    \I386\DRVLIB.NIC\E100EXP\NT

  9. Copy all the files from the \NT directory of the drivers diskette for Intel adapter to both the adapter subdirectory and the \NT subdirectory. Following the above example, you would copy the files to \I386\DRVLIB.NIC\E100EXP AND \I386\DRVLIB.NIC\E100EXP\NT.

  10. Create an UNATTEND.TXT file. Use the sample at the end of this document and make the appropriate changes. Any changes to the UNATTEND.TXT file must follow the Microsoft guidelines, found in the Windows NT 4.0 Resource Kit.

  11. Copy the UNATTEND.TXT you just created into the \I386 directory, replacing any UNATTEND.TXT file that may already be there.

  12. Install the LAN adapter into the target workstation and log onto the server. You may use a floppy boot disk or you may prepare the hard drive and boot from it. See special notes about boot configuration.

Installation

  1. Change to the \I386 directory. It is important that, if the target workstation needs to reconnect to the server during the install, the setup program can find the \I386 directory. This means that you should create a mapping that will exist when the machine reboots. If you are installing from a NetWare server, just use the default network drive. If you are installing from a Windows NT server, map Z: to the share.

  2. Change to the mapped drive you just created and execute the installation command line as follows:

    winnt /s:<drive>: /x /b /u:<drive>:\unattend.txt

    If you booted to a floppy disk, remove the boot disk from the machine as soon as the installation begins.

Back to Top

Tested Adapters and Specifics

  • EtherExpress PRO/100 ISA adapter
    Version A only.

  • EtherExpress PRO/100A PCI adapter
    Version B only. You must use the drivers in the 100ANT40.EXE archive and you must use the revised OEMSETUP.INF (attached). You must include a speed parameter or the installation will stop at the time the adapter is activated and you will be required to supply a speed setting. Speed may be set at 0 (auto detect), 10 or 100.

  • EtherExpress PRO/100B adapter
    Follow the instructions in the file \INFO\MS\NTPUSH.TXT in the latest driver download (100PDISK.EXE).

  • EtherExpress PRO/100+ adapter
    Follow the instructions in the file \INFO\MS\NTPUSH.TXT in the latest driver download (100PDISK.EXE).

  • EtherExpress PRO/10+ ISA adapter
    Version B only.

  • EtherExpress PRO/10+ PCI adapter
    Follow the instructions in the file \INFO\MS\NTPUSH.TXT in the latest driver download (100PDISK.EXE).

Back to Top

UNATTEND.TXT File without Adapter Section (Windows NT 4.0 will detect adapter)

[Unattended]
OemPreinstall = yes
NoWaitAfterTextMode = 1
NoWaitAfterGUIMode = 1
FileSystem = LeaveAlone
ExtendOEMPartition = 0
ConfirmHardware = no
NtUpgrade = no
Win31Upgrade = no
TargetPath = \winnt
OverWriteOemFilesOnUpgrade = no
OemSkipEula = yes [UserData]
FullName = "YOUR_NAME_HERE"
OrgName = "YOUR_ORGANIZATION_NAME_HERE"
ComputerName = YOUR_COMPUTER_NAME_HERE
ProductId = "YOUR_PRODUCT_ID_NUMBER_HERE" [GuiUnattended]
OemSkipWelcome = 1
OEMBlankAdminPassword = 1
TimeZone = "(GMT-08:00) Pacific Time (US & Canada);
Tijuana" [Display]
ConfigureAtLogon = 0
BitsPerPel = 8
XResolution = 800
YResolution = 600
VRefresh = 60
AutoConfirm = 1 [Network]
DetectAdapters = ""
InstallProtocols = ProtocolsSection
InstallServices = ServicesSection
JoinWorkgroup = WORKGROUP_NAME [ProtocolsSection]
TC = TCParamSection [TCParamSection]
DHCP = yes [ServicesSection]

Back to Top

UNATTEND.TXT File with Adapter Section (using the OEMNADZZ.INF)

[Unattended]
OemPreinstall = yes
NoWaitAfterTextMode = 1
NoWaitAfterGUIMode = 1
FileSystem = LeaveAlone
ExtendOEMPartition = 0
ConfirmHardware = no
NtUpgrade = no
Win31Upgrade = no
TargetPath = \winnt
OverWriteOemFilesOnUpgrade = no
OemSkipEula = yes [UserData]
FullName = "YOUR_NAME_HERE"
OrgName = "YOUR_ORGANIZATION_NAME_HERE"
ComputerName = YOUR_COMPUTER_NAME_HERE
ProductId = "YOUR_PRODUCT_ID_NUMBER_HERE" [GuiUnattended]
OemSkipWelcome = 1
OEMBlankAdminPassword = 1
TimeZone = "(GMT-08:00) Pacific Time (US & Canada); Tijuana" [Display]
ConfigureAtLogon = 0
BitsPerPel = 8
XResolution = 800
YResolution = 600
VRefresh = 60
AutoConfirm = 1 [Network]
InstallAdapters = AdaptersSection
InstallProtocols = ProtocolsSection
InstallServices = ServicesSection
JoinWorkgroup = YOUR_WORKGROUP_NAME [AdaptersSection]
ADAPTER_NAME = ADAPTER_NAMEParamSection, \$OEM$
;substitute your adapter name for ADAPTER_NAME [ADAPTER_NAMEParamSection]
;substitute your adapter name for ADAPTER_NAME [ProtocolsSection]
TC = TCParamSection [TCParamSection]
DHCP = yes [ServicesSection]

Operating System:

Windows NT 4.0*

This applies to:

Intel® InBusiness™ 10/100 Adapter
Intel® PRO/100 Intelligent Server Adapter
Intel® PRO/100 ISA Adapter
Intel® PRO/100 M Desktop Adapter
Intel® PRO/100 PCI and EISA Adapters
Intel® PRO/100 S Desktop Adapter
Intel® PRO/100 S Dual Port Server Adapter
Intel® PRO/100 S Management Adapter
Intel® PRO/100 S Server Adapter
Intel® PRO/100 Smart Adapter
Intel® PRO/100 VE Desktop Adapter
Intel® PRO/100 VM Network Connection
Intel® PRO/100+ Adapter
Intel® PRO/100+ Dual Port Server Adapter
Intel® PRO/100+ Management Adapter
Intel® PRO/100+ Server Adapter
Intel® PRO/100B Adapter

Solution ID: CS-009706
Last Modified: 13-Mar-2014
Date Created: 26-Feb-2004
Back to Top