The goal of the Unattended Setup or Push Installation is to allow system administrators to automatically install and configure Windows 95* throughout an organization. Both new and upgrade Windows 95 installations can be done using the same procedure. Microsoft's recommendation is to use this strategy if there are 50 or more computers to be installed in a company. In this document, only the Unattended Setup of the Windows 95 operating system will be discussed, but the method is applicable also for Windows Applications installation and software upgrades from the common source throughout the organization.
From the LAN Adapter manufacturer's prospective, the main objective regarding the Push Installation is to get the client connected to the Windows NT* server properly before the installation begins using the NDIS2 driver and to keep the same client connected using the NDIS3 or NDIS4 driver after Windows 95 is installed without any end user's actions. The main difficulty is that the list of supported adapters on the Windows 95 and Windows NT CD-ROMs is limited. Special steps must be performed to update the Installation Image on the Server and modify the scripts that automate the installation process for the adapter(s) which are not on the list.
The procedure described below is addressed to System Administrators and/or the Technical Support staff. It requires the following knowledge and experience:
- Managing user accounts on the Windows NT Server.
- Preparing a shared image of the Microsoft Client on the Windows NT Server.
- Understanding of the Windows 95 regular installation procedure.
- Installing and configuring network adapters for Windows 95.
Once the Installation Image on the Windows NT Server and the Setup Disk are prepared by a qualified engineer, the end user can run the Unattended Setup for different systems and even modify some parameters in the installation script.
- Create a Network Installation Startup disk from the Windows NT Server and modify it for your board.
- Create a Windows 95 Installation Image on the Windows NT Server using NETSETUP.
- Modify the MSBATCH.INF installation script to automate the procedure and include the proper network adapter installation and configuration.
- Integrate the adapter into the Windows 95 HCL using the INFINST.
- Boot up the client system with the prepared setup disk inserted.
||EtherExpress™ PRO/100 ISA
||Installed in all new Clients|
|NDIS2 real mode|
NDIS3 protected mode
||Windows NT Server 4.0
|| With a CD-ROM drive|
|| DOS 6.2x
||formatted HDD, no files|
|| DOS 6.2x
||formatted HDD, no files|
- Prepare a Windows NT 4.0 server:
- Create a shared folder on the server's hard disk for the installation files (i.e. "W95setup" ).
- Create a user (i.e. Pushuser with a password Pushuser) and grant read and view rights for the W95setup folder
On the Windows NT Server, prepare the Microsoft Client Installation disk (Setup Disk).
- Prepare a system diskette (i.e. DOS 6.22). Do not use the Windows 95 system disk!
- Using the Windows NT Administrative Tools (common), start Network Client Administrator and choose "Make Network Installation Startup Disk".
- Set "Existing Path" to use the previously installed MS Client share on the Windows NT Server's hard drive.
* assumed that the shared image on the server's hard drive has been created already *
** if not use the NT 4.0 Server CD-ROM as a source and follow the standard procedure described in the Windows NT 4.0 Server User manual to create this share **
- Choose "DOS / Windows for Workgroups Client 3.0".
- Choose any of the Network Adapters from the list (i.e. NE2000 Compatible ).
- Set Computer: nameany name (i.e. Client1)
Set User name: Pushuser
Set Domain: the Logon domain configured at the NT Server (i.e. CA_TEST_ENG)
Set Network protocol: choose from the list. IPX compatible is recommended.
- Select OK and wait while files are copied to the disk.
- Copy the proper driver (E100ISA.DOS) to this disk in the \NET directory.
- Modify A:\NET\SYSTEM.INI : netcard=E100ISA.dos
- Modify A:\NET\PROTOCOL.INI : drivername=e100is$
- Verify/modify A:\AUTOEXEC.BAT to have the following commands:
NET LOGON pushuser /y
NET USE W: \\PST\W95setup
Now your Setup Disk is ready.
Use an existing Windows 95 client system with a CD-ROM drive:
- Connect to the Windows NT server.
- Map a logical drive (i.e. J: ) to the Windows NT server's shared folder W95setup
( i.e. using the Windows Explorer).
- Insert the Windows 95 CD-ROM and start ADMIN\NETTOOLS\NETSETUP\NETSETUP.
Input the parameters:
- Set path to the mapped logical drive ( in our example J:\ ).
- Choose the second option, "Local hard drive".
- Click the "Install" button.
- Choose "Create Default".
- Set "Setup" option to "Do not allow user input".
- Set "Install Directory" option (i.e. C:\WIN95).
- Set "Install Verification" on.
- Set other options as required by your system and network setup. The default name of the script is MSBATCH.INF. You need to modify this script later.
- Input the "Product ID" (your Windows 95 registration number).
NETSETUP will copy installation files to the Windows NT server and then change the attributes of the copied files to "Read-only".
Create / Modify the installation script MSBATCH.INF as required by your specific system and desired Windows 95 configuration. See the recommended example of this file at the end of this document. By default, this file is stored in the root of the Installation Image on the server, but you can put it any place (for example on the Setup Disk) and put the full path to this script in AUTOEXEC.BAT for the SETUP command.
Use Windows 95 CD-ROM and start ADMIN\NETTOOLS\NETSETUP\INFINST.
- Insert the PRO/100 ISA adapter installation disk #1 into your floppy drive
(i.e. A: ).
- Set path J:\ as a destination.
- Click the "Install INF" button.
- Choose A:\NETE100.INF when prompted for the source.
- The files will be copied to the proper place on the server and the adapter will be integrated to the Windows 95 HCL by adding it to the LAYOUT.INF.
On the New Client system, boot up with the Setup Disk installed. You will be automatically connected to the network as Pushuser. Input the password when prompted and the Windows 95 setup begins. No more questions will be asked during the installation if the attached example of MSBATCH.INF is used. Don't forget to take the Setup Disk out of the floppy drive when rebooting the first time. Either way, the installation starts from the very beginning again. Windows 95 will be installed with the EtherExpress PRO/100 ISA adapter configured and supported by the NDIS3 driver.
Multiple system models
If different models of PCs are used in the company and require different configurations, then different installation scripts and different Setup Disks could be prepared. The script files may have any names, i.e. MSBAT1.inf, MSBAT2.inf etc. The proper script name must be indicated as a parameter for SETUP in the last command of the proper AUTOEXEC.BAT on the Setup Disk:
Example: w:\setup w:\msbat1.inf
The recommendation is to label these Setup Disks with information to match the appropriate clients.
If different LAN adapters are used in the company and require different configurations, then different installation scripts and different Setup Disks could be prepared. To do this, repeat the steps 6 - 10 for every type of adapter to integrate the appropriate INF file to the Installation Image and prepare the specific MS Client Setup Disks.
System Administrators can automate upgrades of the common software for all clients using the SMS (System Management Server). The set-up upgrade script can be run as a mandatory job for all clients. This method requires the SMS agents to be installed on the all involved client systems.
a:\net\net initialize a:\net\nwlink
net use w: \\PST\W95setup /* PST is the name of the NT 4.0 server containing the shared image */
echo Running Setup...
w:\setup w:\msbatch.inf /* call of Windows 95 setup program with the prepared installation script */
[SETUP] /* COMMENTS */
Express=1 /* do not allow user input, use settings from MSBATCH.inf only */
InstallType=1 /* Typical type of installation */
Devicepath=1 /* adds the installation source folder to the path for finding INFs;
forces Setup to rebuild HCL after any updates of the disk image */
Verify=0 /* default */
EBD=0 /* do not create an emergency Startup Disk */
ProductID=240-0001977 /* the original Windows 95 product ID */
TimeZone=Pacific /* the time zone to be set on the computer */
Name="JoeI" /* full user name for this installation */
Org="Intel" /* the registered organization */
Display=0 /* do not display the Name and Organization dialog box */
WorkstationSetup=0 /* allow a standard setup (local files) */
DisplayWorkstationSetup=0 /* do not display the user interface */
HDBoot=1 /* start from the hard disk and run from the network */
RPLSetup=0 /* do not do a remote setup */
Display=0 /* do not display the network interface */
Clients=vredir,nwredir /* install MS clients for Windows and NetWare */
Protocols=netbeui,nwlink /* install NetBEUI and IPX/SPX compatible protocols */
NetCards=* E100ISA /* install PRO/100 ISA - internal name is used */
ComputerName="PC28" /* the computer's network name */
Workgroup="ca_test_eng" /* sets the workgroup for the computer */
Description="AST P5-133" /* the description for the computer */
[*E100ISA_ID] /* this group was added for the PRO/100 ISA */
CardBrand=Intel /* the adapter's manufacture name */
INFfile=nete100i.inf /* the name of appropriate INF file */
ValidatedLogon=1 /* Client for MS Networks logons validated on an NT domain */
LogonDomain="ca_test_eng" /* Windows NT domain name */
FrameType=4 /* default: Auto detection of the IPX/SPX frame type */
NetBIOS=1 /* install NetBIOS support for IPX/SPX */
[Printers] /* no parameters means that the printer won't be installed
For additional information, refer to the following:
- Microsoft Windows 95 Resource Kit, Microsoft Press, 1995
- Microsoft Windows NT 4.0 Server Resource Kit, Microsoft Press, 1997
- Microsoft TechNet CD-ROM, April 1997
This applies to: