Push Installation for Windows

General Information: additional push installation information and setup files located in the \Push folder on the Intel CD.

Component Installer (Setup.exe) Information. Read this section if you are installing advanced features in Windows unattended mode.

A note about computer names in Microsoft networks

It is important to not have two computers with the same network name on the network at the same time, or being installed at the same time. Consequently you cannot use these files by themselves to deploy Windows 95/98 on multiple computers, without manually changing the computer name value.

Different configuration managers exist to overcome this hurdle in enterprise OS deployments. For more information on deploying Windows 95/98 in an enterprise network, consult the Windows 95/98 resource kit.

Setting up an Install Directory on the file server

Note: The network share Z:\PUSH is used here as an example path to the distribution folder. The distribution folder is where the setup files for Windows 95/98 reside. During the first step of the install, the client will connect to the distribution folder with IPX or TCP/IP.

Before an unattended server based setup of Windows 95/98 can occur a directory needs to be prepared.

1. Copy the Win9x setup folder from the CD to Z:\PUSH. Use Explorer, Winfile or XCOPY in order to maintain the same 
directory structure as on the CD.

2. From the Configuration and Drivers CD provided with the adapter, copy the following files and directories into Z:\PUSH:

          Note: drive D below represents your CD-ROM drive letter. Yours may be different.

          D:\8255xNDI.DLL              -->     Z:\PUSH\8255xNDI.DLL
          D:\8255xDEL.EXE              -->    Z:\PUSH\8255xDEL.EXE
          D:\E100B.CAT                 -->      Z:\PUSH\E100B.CAT
          D:\E100B.DOS                 -->     Z:\PUSH\E100B.DOS
          D:\E100B.SYS                 -->     Z:\PUSH\E100B.SYS
          D:\E100BNT.SYS               -->    Z:\PUSH\E100BNT.SYS 
          D:\E100BNT5.SYS              -->    Z:\PUSH\E100BNT5.SYS 
          D:\E100BODI.COM              -->   Z:\PUSH\E100BODI.COM
          D:\NET82557.INF              -->     Z:\PUSH\NET82557.INF
          D:\NET82557.DIN             -->      Z:\PUSH\NET82557.DIN
             D:\PROMON.EXE                -->     Z:\PUSH\PROMON.EXE
          D:\PROSETP.CNT               -->     Z:\PUSH\PROSETP.CNT
          D:\PROSETP.CPL               -->     Z:\PUSH\PROSETP.CPL
          D:\PROSETP.HLP               -->     Z:\PUSH\PROSETP.HLP 
          D:\WOL558.VXD                -->     Z:\PUSH\WOL558.VXD

          D:\WIN9X\PUSH\CUSTOM.INF     -->     Z:\PUSH\CUSTOM.INF
          D:\WIN9X\PUSH\MSBATCH.INF    -->     Z:\PUSH\MSBATCH.INF

3. Review the copy of MSBATCH.INF within the Z:\PUSH directory, make any changes needed to customize the install for your network.

Deployment Methods

There are many ways to perform an unattended installation or upgrade including but not limited to:

- Setting up a login script that executes a setup statement when each user logs in

- Inserting an object in an email message that runs setup when the user clicks it

- Using Microsoft SMS server to run Windows 9x Setup

- Inserting a floppy that shares a drive on the network and runs setup from the shared drive

- Copying the files to a local drive and then running an unattended setup from there

In the end each Network Administrator will find the easiest way to accomplish this goal for his or her own network.

To avoid possible areas where an unattended installation might be halted we recommend you use one of the following setup command lines for Windows 95 or Windows 98, respectively:

Windows 95:
SETUP /IS /IW /IM

Windows 98:
SETUP /IS /IM /IE /IW

Where to get help

The Windows 95 and Windows 98 Resource kit contains detailed information on unattended setups and deploying Windows 95/98 in an enterprise environment.

Microsoft's support web site is also a good place to look: 

http://www.microsoft.com/Support/

Windows 2000

Introduction

The PUSH installations of Network Adapter drivers on windows 2000 is achieved by setting the options in the Unattend.txt file. This and other files are located in the \PUSH folder on the Intel CD.

Setting up an Install Directory on the file server

Note: The network share Z:\PUSH2K is used here as an example path to the distribution folder. The distribution folder is where the setup files for Windows 2000 reside. During the first step of the install, the client will connect to the distribution folder with IPX or TCP/IP.

Before an unattended server based setup of Windows 2000 can occur a directory needs to be prepared.

1. Copy the \I386 folder from the CD to Z:\PUSH2K. Use Explorer, Winfile or XCOPY in order to maintain the same directory structure as on the CD.

2. Make folders beneath \i386 as follows:
\$OEM$\$$\Help
\$OEM$\$$\System32
\$OEM$\$1\Drivers\Net\e100b

3. From the Configuration and Drivers Diskette provided with the adapter, copy all the files into Z:\PUSH2K\i386\$OEM$\$1\Drivers\Net\e100b directory and copy Unattend.txt from the Diskette into the shared directory Z:\PUSH2K. Make sure that Unattend.txt has the latest changes you made for customizing the push installation.

Deployment Method

1. Make sure that you have a copy of network bootable MS-DOS floppy and the boot the system which you want to push install with this floppy and connected to the shared network directory.

2. Run the command as :

\\Server\PUSH2K\i386\winnt /u:\\Server\PUSH2K\Unattend.txt /s:\\Server\PUSH2K /t:C

Important Note:
By adopting the above procedure, the setup runs the installation in unattended mode and also detects the plug and play network adpaters. All driver files are copied from the shared directory to the target system directories and continues installation of the OS and Network Adapters without user intervention.

The sample Unattend.txt file used for the above installation is as follows:


[Unattended]
Unattendmode = FullUnattended
OemPreinstall = YES
TargetPath = WINNT
Filesystem = LeaveAlone
NoWaitAfterTextMode = 1
NoWaitAfterGUIMode = 1
OemSkipEula = Yes
OemPnpDriversPath="drivers\net\e100b"

[UserData]
ProductID=xxxx-xxxx-xxxx-xxxx-xxxx
FullName = "DMI2"
OrgName = "Intel"
ComputerName = "COMPUTER1"

[GuiUnattended]
TimeZone = "004"
AdminPassword = *
OemSkipWelcome = 1
AdvServerType = SERVERNT

[LicenseFilePrintData]
AutoMode = PerSeat

[Display]
BitsPerPel = 16
XResolution = 800
YResolution = 600
VRefresh = 60

[Identification]

JoinWorkGroup = Workgroup
; *Use the following for a domain installation
; JoinDomain=DMI2
; CreateComputerAccountInDomain=Yes
; DomainAdmin=Installer
; DomainAdminPassword=install

[Networking]
InstallDefaultComponents=Yes

Windows NT 4.0

Instructions for Windows NT 4.x Unattended Install (Push)

The main objective of the Push Installation is to get the client properly connected to the Windows NT server before the installation begins using the NDIS2 driver, and to keep the same client connected using the NDIS4 driver after the Windows NT Workstation is installed without any end user action.

The main difficulty is that the list of supported adapters on the Windows NT 4.0 CD-ROM is restricted and thus special steps must be performed to update the Installation source files and modify the scripts to automate the process (for the adapters not on the list).

The main steps of the process are:

1. Create a Network Installation Startup disk from the Windows NT Server and modify it for your adapter.

2. Create a shared directory for the Windows NT Workstation Installation files on the Windows NT Server.

3. Modify the UNATTEND.TXT installation script to automate the procedure and add the proper adapter installation and configuration information.

The sample UNATTEND.TXT file provided below shows how to override default registry parameters for the adapter in the [E100BParameters] section. Override parameters should not be used unless the default 
parameters will not work properly for a specific installation. The sample parameters are commented out.

4. Integrate the adapter driver files into the Windows NT installation source files.

5. Perform the Unattended Setup booting with the prepared setup disk from the client system.

The Procedure:

1. Prepare a Windows NT 4.0 server:

a) Create a folder on the server's hard disk for the installation files (e.g., "NT40.INS"). Make this folder shared (e.g., with shared name "NT40.INS").

b) Create a user (e.g., "USERID" with a password "password") and granted read and view rights for the NT40.INS folder.

2. Use a CD-ROM drive at the Windows NT server and copy the i386 folder with Windows NT 4.0 installation files to the shared folder NT40.INS on this server (e.g., using the NT Explorer).

3. Create / Modify the installation answer file UNATTEND.TXT as required by your specific system and desired Windows NT configurations. Note that UNATTEND.TXT may be read-only and may need to be made write-able before editing (e.g., attrib -r unattend.txt). A sample UNATTEND.TXT file with comments is included at the end of this document.

The best place to put this file is in the root of your install disk, but the real requirement is just to specify the full path to this file in the AUTOEXEC.BAT for the WINNT command (see 6b) and 6m) below).

4. Create the \E100B directory: NT40.INS\i386\$OEM$\Net\E100B.

5. Copy driver installation files: Xcopy the Intel Configuration and Drivers Disk to the proper place under Adapter Device Driver folder (NT40.INS\i386\$OEM$\Net\E100B folder on the Windows NT server). This enables the installation program to find the same file structure as on the Drivers disk. Be sure to use the /s /e switches on xcopy.

6. On the Windows NT server, prepare the Microsoft Client Installation disk using the Windows NT Network Client Administrator:

a) Prepare a system diskette (e.g., DOS 6.22: format a: /s). Do not use the Windows NT system disk.

b) Copy UNATTEND.TXT from \NT40.INS\i386 to the diskette as specified in 3) above (preferably to the root (a:\)).

c) Use the Windows NT Administrative Tools (Common), start Network Client Administrator and choose "Make Network Installation Startup Disk".

d) Set "Existing Path" to use the previously installed software for MS Client or, if it is the first time, create the shared directory on the server's hard drive, using the Windows NT 4.0 Server CD-ROM as a source (e.g., by copying from \client on the CD-ROM to c:\client).

e) Choose "Network Client v3.0 for MS-DOS and Windows".

f) Choose any of the Network Adapters from the list (e.g., NE2000 compatible).

g) Set Computer name, User name, Domain and Network protocol when prompted.

h) Select OK and wait while files are copied to the disk.

i) Copy the proper ndis2 dos driver (E100B.DOS) to this disk in the \NET directory. E100B.DOS can be found in \DOS on the Intel Configuration and Driver Disk.

j) Modify A:\NET\SYSTEM.INI : netcard = E100B.DOS

k) Modify A:\NET\PROTOCOL.INI : drivername = E100B$

l) Add a line: CACHEFLUSH = 1 just after the "drivername = E100B$" line.

m) Verify or modify A:\AUTOEXEC.BAT to have the following commands:

NET USE W:\\PST\NT40.INS W:\i386\WINNT /s:W:\i386 /u:a:\unattend.txt

Note that W is an example for the logical drive mapped to the share on the Windows NT server.

n) Remove the invocation of setup.exe from A:\AUTOEXEC.BAT.

7) Boot up your DOS client with the disk prepared above installed. After connecting to the network:

a) Input "USERID" as a User name when prompted.

b) Input "password" as a password when prompted.

OR

c) Modify the NET START line in the AUTOEXEC.BAT to
NET LOGON USERID PASSWORD /YES

Sample Templates

1) PROTOCOL.INI

[network.setup]
version=0x3110
netcard=ms$ne2clone,1,MS$NE2CLONE,1
transport=ms$ndishlp,MS$NDISHLP
transport=ms$netbeui,MS$NETBEUI
lana0=ms$ne2clone,1,ms$netbeui
lana1=ms$ne2clone,1,ms$ndishlp

[ms$ne2clone]
drivername = E100B$
CACHEFLUSH = 1
; CACHEFLUSH line is required ONLY IF NDIS2 does not shut down
; properly

;INTERRUPT=3
;IOBASE=0x300
;SlotNumber=1

[protman]
drivername=PROTMAN$
PRIORITY=MS$NDISHLP

[MS$NDISHLP]
drivername=ndishlp$
BINDINGS=ms$ne2clone

[ms$netbeui]
drivername=netbeui$
SESSIONS=10
NCBS=12
BINDINGS=ms$ne2clone
LANABASE=0

2. SYSTEM.INI

[network]
filesharing=no
printsharing=no
autologon=yes
computername=COMPUTERNAME
lanroot=A:\NET
username=Administrator
workgroup=DOMAIN
reconnect=no
directhost=no
dospophotkey=N
lmlogon=0
logondomain=DOMAIN
preferredredir=full
autostart=full
maxconnections=8

[network drivers]
netcard=E100B.DOS
transport=ndishlp.sys,*netbeui
devdir=A:\NET
LoadRMDrivers=yes

[Password Lists]
*Shares=a:\net\Share000.PWL
USERID=A:\NET\USERID.PWL

3. AUTOEXEC.BAT

path=a:\net
a:\net\net start
rem a:\net\net logon userid password /yes
net use W: \\133\nt40.ins
W:
cd i386
winnt /s:W:\i386 /u:a:\unattend.txt

4. UNATTEND.TXT

[Unattended]
OemPreinstall = yes
NoWaitAfterTextMode = 1
NoWaitAfterGUIMode = 1
FileSystem = LeaveAlone
ExtendOEMPartition = 0
ConfirmHardware = no
NtUpgrade = no
Win31Upgrade = no
TargetPath = winnt
OverwriteOemFilesOnUpgrade = no
OemSkipEULA = yes

[GuiUnattended]
OemSkipWelcome = 1
OEMBlankAdminPassword = 1
TimeZone = "(GMT-08:00) Pacific Time (US & Canada)"

[UserData]
FullName = "Userid"
OrgName = "Organization"
ComputerName = COMPUTER
ProductId = "xxx-xxxxxx"

[Display]
ConfigureAtLogon = 0
BitsPerPel = 8
XResolution = 640
YResolution = 480
VRefresh = 60
AutoConfirm = 1

[Network]
InstallAdapters = SelectedAdaptersSection
InstallProtocols = ProtocolsSection
InstallServices = ServicesSection
JoinWorkgroup = workgroup

[SelectedAdaptersSection]
E100B = E100BParameters, ..\$OEM$\Net\E100B\

[E100BParameters]
;MemoryAddress = 0x0C000000 ; sample parameter only
;InterruptNumber = 11 ; sample parameter only
;Bus = 4 ; sample parameter only

[ProtocolsSection]
TC = TCParamSection

[TCParamSection]
DHCP = yes

[ServicesSection]


REFERENCES:

1. Microsoft Windows NT Resource Kit - Microsoft Press 19NT
2. Microsoft TechNet CD-ROM, April 1997
3. Microsoft support web page at http://support.microsoft.com/support

    Article ID : Q155197, Q156795

Component Installer (Setup.exe) Information

When installing advanced features in Windows unattended mode, use the following command line guidelines for advanced features.

Procomp.exe /<Component-Name> [TARGET_PATH=<path> ERROR_PATH =<path> /s /u]

· Component-Name Is one of the following: [PROSet | PriorityPacket]

· TARGET_PATH Specifies the target install directory

· ERROR_PATH Specifies the target error file path name

· /s silent mode

· /u uninstall

Packet Protect:

Unattended install is not available for Packet Protect software.