LAN_Win2KXP_v10_PV/APPS/SETUP/PUSH/WIN2K/pushw2k.txt Driver File Contents (LAN_WIN2KXP_V10_PV.EXE)

Driver Package File Name: LAN_WIN2KXP_V10_PV.EXE
File Size: 16.5 MB

Push Install Instructions for Microsoft Windows* 2000 

- Introduction  

- Setting up an install directory on the file server

- Instructions for Creating Teams and VLANs (Optional) 

- Deployment methods 

- Microsoft documentation for unattended installations of Windows 2000 

- Sample unattend.txt file for Windows 2000 

- Directory structure for unattended installation files 

--------------------------------------------------------------------------------

Introduction

A "Push", or unattended installation of Windows 2000 provides a means for 
network administrators to easily install Windows 2000 on similarly equipped 
systems. The network administrator can create a bootable diskette that 
automatically logs into a central server and installs the operating system from 
an image of the Windows 2000 installation directory stored on that server. This 
document provides instructions for a basic unattended installation of 
Windows 2000 that includes the installation of drivers for the Intel(R) PRO/100 
and Intel(R) PRO/1000 adapters.

NOTE: Installation of Intel(R) PRO/100 and Intel(R) PRO/1000 drivers requires Windows 2000 Service Pack 4.

As part of the unattended installation, you can create teams and VLANs. If you 
wish to create one or more teams/VLANs as part of the unattended installation, 
you must also follow the instructions denoted in this page as "Instructions 
for Creating Teams/VLANs (Optional)".

The elements necessary for the Windows 2000 unattended installation are:

- A Windows 2000 Server with a shared image of the \I386 directory from the 
  Windows 2000 installation CD (Service Pack 4 is required). 
- If you want to create teams/VLANs as part of the unattended installation, you 
  need to create a configuration file with the team information in it. To 
  create this file, you need a sample system that has the same type of adapters 
  that will be in the systems receiving the push installation. On the sample 
  system, use Intel(R) PROSet for Windows Device Manager to set up the adapters 
  in the teaming/VLAN configuration you want. This system could also be the 
  Windows 2000 Server mentioned above. For clarity, this system is referred 
  to in this page as the configured system. 
- An unattended installation configuration file that provides Windows 2000 
  setup with information it needs to complete the installation. The name of 
  this file is UNATTEND.TXT. 
- A DOS boot diskette that contains Microsoft Network Client software for 
  connecting to the Windows 2000 server and AutoExec commands to 
  automatically start the Windows 2000 installation. 

-------------------------------------------------------------------------------

Setting up an install directory on the file server

The server must be setup with a distribution folder that holds the required 
Windows 2000 files and which clients can reach when connecting via TCP/IP or 
IPX.

For illustration purposes, the examples on this document use the network share 
D:\PUSHW2K. To create this share, 

1) Create a directory on the server, (EX: D:\PUSHW2K).  
2) Use the My Computer applet in Windows 2000 to locate the D:\PUSHW2K folder.  
3) Right-click the folder and select Sharing.  
4) Select Share this folder. Give it a share name (EX: PUSHW2K). This share 
   name will be used to connect to this directory from the remote target 
   systems.  By default, the permissions for this share will be for Everyone to have 
   Full Control.  
5) Adjust permissions as necessary and click OK.  

To prepare the distribution folder:

1) Copy the \I386 folder from the Windows 2000 CD to D:\PUSHW2K. Use Windows 
   Explorer or XCOPY to maintain the same directory structure as on the 
   Windows 2000 CD. When the copy is complete, the Windows 2000 installation 
   files should be in the D:\PUSHW2K\I386 directory. 
2) Copy Unattend.txt from the Intel CD (found in \APPS\SETUP\PUSH\WIN2K) into 
   the shared directory D:\PUSHW2K\I386.  
3) Edit the Unattend.txt file with Notepad or another text-editor to include 
   your customizations. At a minimum you should change the items in the 
   [UserData] section of the file.   For server installations the [LicenseFilePrintData] section
   should be used to specify the server type and number of users (for PerServer type).
4) Create the driver install directory structure and copy the driver files 
   to it. 

NOTE: The PUSHCOPY.BAT file provided with the drivers in the \APPS\SETUP\PUSH 
directory copies the appropriate files for the installation. PUSHCOPY also 
copies the components needed to perform the automated installations contained 
in the [GuiRunOnce] section of the sample UNATTEND.TXT file. These include an unattended installation of Intel(R) PROSet
for Windows Device Manager. 

Example: From a Windows 2000 command prompt where e: is the drive letter of 
the CD-ROM drive:
e: 
cd \APPS\SETUP\PUSH 
	(you must be in the \APPS\SETUP\PUSH\ directory to run PUSHCOPY)
pushcopy D:\PUSHW2K\I386 w2k

The above command creates the $OEM$ directory structure and copies all the 
necessary files to install the driver and Intel(R) PROSet for Windows Device 
Manager. However, Intel(R) PROSet for Windows Device Manager is not installed 
unless the line: 

; Command0="%systemdrive%\WMIScr\Install.bat"

is uncommented from unattend.txt.

See the "Directory structure for unattended installation files" section of
this document for more information about the directory structure and file 
layout of the $OEM$ directory.

-------------------------------------------------------------------------------

Instructions for Creating Teams and VLANs (Optional)

1) Copy SavResDX.vbs from the Intel CD to the configured system. The file is 
   located in the APPS\WMI\ directory on the Intel CD. 
2) Open a command prompt on the configured system and navigate to the 
   directory containing SavResDX.vbs. 
3) Run the following command: cscript SavResDX.vbs save. A configuration file 
   called WmiConf.txt is created in the same directory. 
4) On the Windows 2000 Server, create a directory in the $OEM$\$1 directory 
   called WMIScr. For example, on Windows 2000, the directory is 
   $OEM$\$1\WMIScr. 
5) Copy the SavResDX.vbs and WmiConf.txt files to the WMIScr directory.
6) Locate the batch file, Install.bat, in $OEM$\$1\WMIScr.  Edit the batch file by removing the comment the preceeds the second START command.
   The file should look like the follow when finished:
   
   Start /wait %systemdrive%\drivers\net\INTEL\APPS\ProsetDX\2KXPWS03\DxSetup.exe /i /qw  /li %temp%\dxsetup.log ANS=1
   REM Uncomment the next line if VLANs or Teams are to be installed.
   Start /wait /b cscript %systemdrive%\wmiscr\SavResDX.vbs restore %systemdrive%\wmiscr\wmiconf.txt > %systemdrive%\wmiscr\output.txt
   exit

--------------------------------------------------------------------------------

Deployment Methods

Make sure that you have a copy of a network bootable MS-DOS floppy that will 
connect to the Z:\PUSHW2K directory, use it to boot the destination system 
(the one you want to push install to), and connect to this shared network 
directory.

Run the command at the \\Server\PUSHW2K\i386 prompt: 
	winnt /u:Z:\I386\unattend.txt /s:Z:\I386 /t:c 
where Z: equals mapped drive.

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

If you installed teams/VLANs as part of the unattended installation, view the 
results of the script execution in the output.txt file. This file is in 
the same directory as the SavResDX.vbs file.

--------------------------------------------------------------------------------

Microsoft documentation for unattended installations of Windows 2000

For a complete description of the parameters supported in Unattend.txt see 
the UNATTEND.DOC document in the DEPLOY.CAB cabinet file on the Windows 2000 CD. 
To obtain the document, use Internet Explorer 5.0 or greater to open DEPLOY.CAB 
in the \SUPPORT\TOOLS directory on the Windows 2000 CD.

For deployment suggestions using a Windows 2000 RIS server and PXE boot see the 
Boot Agent User's Guide.

To configure and install the driver set on the RIS Server see the knowledge 
base article Q246184 on Microsoft's support site at: 
http://support.microsoft.com/default.aspx?scid=kb;en-us;246184

General information on how to preinstall an OEM driver set for Windows 2000 
can be found in knowledge base article Q254078: 
http://support.microsoft.com/default.aspx?scid=kb;en-us;254078

--------------------------------------------------------------------------------

Sample Unattend.txt file for Windows* 2000

[Unattended]
UnattendMode=FullUnattended
OemSkipEula=Yes
OemPreinstall=Yes
OemPnPDriversPath = "\drivers\net\INTEL\PRO100\WS03XP2K;\drivers\net\INTEL\PRO1000\WS03XP2K;\drivers\net\INTEL\APPS\INTELAMT\DRIVERS\WS03XP"
TargetPath=\WINNT
DriverSigningPolicy=Ignore
Filesystem=LeaveAlone
OverwriteOemFilesOnUpgrade=No

[GuiUnattended]
AdminPassword=*
AutoLogon=Yes
AutoLogonCount=1
OEMSkipRegional=1
TimeZone=4
OemSkipWelcome=1

; At a minimum you should update the [UserData] section.

[UserData]
FullName=Name
OrgName=Organization
ComputerName=ComputerName
ProductID=xxxxx-xxxxx-xxxxx-xxxxx-xxxxx

; For Server installations, this section specifies the Server Type and number of 
; users if the Server Type is PerServer

[LicenseFilePrintData]
;    Set up the licensing type for the server.  
 
;     AutoMode=xxxxxxxx
;             Possible AutoMode values are PerSeat and PerServer

;     AutoUsers=xxxx
;             Number of users if AutoMode = PerServer.

[GuiRunOnce]

; Command to install Intel(R) PROSet for Windows* Device Manager - uncomment to install it after push install
; This command will call the batch file during Windows 2000 installation and sequentially install Intel(R) Proset for Windows Device Manager followed by installing any Teams or VLANs.

;    Command0="%systemdrive%\WMIScr\Install.bat"

[Identification]
JoinWorkgroup=WORKGROUP
; Use the following for a domain installation
; JoinDomain-MYDOMAIN
; CreateComputerAccountInDomain=Yes
; DomainAdmin=Installer

[Networking]
InstallDefaultComponents=Yes

--------------------------------------------------------------------------------
Directory Structure For Unattended Installation Files

The following directory structure is created by PUSHCOPY.BAT to place the 
files necessary for the installation of the driver and Intel(R) PROSet for 
Windows Device Manager. The directory D:\PUSHWS03 refers to the location 
of the files from the Windows 2000 installation CD.

D:\PUSHW2K\I386\$oem$\$1\drivers\net\INTEL

(From the \PRO100\WS03XP2K directory of the Intel CD)
D:\PUSHW2K\I386\$oem$\$1\drivers\net\INTEL\PRO100\WS03XP2K\ASFSTUP.DLL
D:\PUSHW2K\I386\$oem$\$1\drivers\net\INTEL\PRO100\WS03XP2K\E100A325.INF
D:\PUSHW2K\I386\$oem$\$1\drivers\net\INTEL\PRO100\WS03XP2K\E100ANT5.INF
D:\PUSHW2K\I386\$oem$\$1\drivers\net\INTEL\PRO100\WS03XP2K\E100B325.CAT
D:\PUSHW2K\I386\$oem$\$1\drivers\net\INTEL\PRO100\WS03XP2K\E100B325.DIN
D:\PUSHW2K\I386\$oem$\$1\drivers\net\INTEL\PRO100\WS03XP2K\E100B325.INF
D:\PUSHW2K\I386\$oem$\$1\drivers\net\INTEL\PRO100\WS03XP2K\E100B325.SYS
D:\PUSHW2K\I386\$oem$\$1\drivers\net\INTEL\PRO100\WS03XP2K\E100BMSG.DLL
D:\PUSHW2K\I386\$oem$\$1\drivers\net\INTEL\PRO100\WS03XP2K\E100BNT5.DIN
D:\PUSHW2K\I386\$oem$\$1\drivers\net\INTEL\PRO100\WS03XP2K\E100BNT5.SYS
D:\PUSHW2K\I386\$oem$\$1\drivers\net\INTEL\PRO100\WS03XP2K\INTELNIC.DLL
D:\PUSHW2K\I386\$oem$\$1\drivers\net\INTEL\PRO100\WS03XP2K\NCS2SETP.DLL
D:\PUSHW2K\I386\$oem$\$1\drivers\net\INTEL\PRO100\WS03XP2K\PROUNSTL.EXE

(From the \PRO1000\WS03XP2K directory of the Intel CD)
D:\PUSHW2K\I386\$oem$\$1\drivers\net\INTEL\PRO1000\WS03XP2K\ASFSTUP.DLL
D:\PUSHW2K\I386\$oem$\$1\drivers\net\INTEL\PRO1000\WS03XP2K\E1000MSG.DLL
D:\PUSHW2K\I386\$oem$\$1\drivers\net\INTEL\PRO1000\WS03XP2K\E1000NT5.DIN
D:\PUSHW2K\I386\$oem$\$1\drivers\net\INTEL\PRO1000\WS03XP2K\E1000NT5.SYS
D:\PUSHW2K\I386\$oem$\$1\drivers\net\INTEL\PRO1000\WS03XP2K\E1000325.CAT
D:\PUSHW2K\I386\$oem$\$1\drivers\net\INTEL\PRO1000\WS03XP2K\E1000325.DIN
D:\PUSHW2K\I386\$oem$\$1\drivers\net\INTEL\PRO1000\WS03XP2K\E1000325.INF
D:\PUSHW2K\I386\$oem$\$1\drivers\net\INTEL\PRO1000\WS03XP2K\E1000325.SYS
D:\PUSHW2K\I386\$oem$\$1\drivers\net\INTEL\PRO1000\WS03XP2K\ETCOINST.DLL
D:\PUSHW2K\I386\$oem$\$1\drivers\net\INTEL\PRO1000\WS03XP2K\INTELNIC.DLL
D:\PUSHW2K\I386\$oem$\$1\drivers\net\INTEL\PRO1000\WS03XP2K\NCSSETP.DLL
D:\PUSHW2K\I386\$oem$\$1\drivers\net\INTEL\PRO1000\WS03XP2K\PROUNSTL.EXE

(From the \APPS\PROSETDX\2KXPWS03 directory of the Intel CD)
D:\PUSHW2K\I386\$oem$\$1\drivers\net\INTEL\APPS\PROSETDX\2KXPWS03\DMIX32.CAB
D:\PUSHW2K\I386\$oem$\$1\drivers\net\INTEL\APPS\PROSETDX\2KXPWS03\DX32*.CAB	;International language files
D:\PUSHW2K\I386\$oem$\$1\drivers\net\INTEL\APPS\PROSETDX\2KXPWS03\DxHlp*.CAB	;International language files
D:\PUSHW2K\I386\$oem$\$1\drivers\net\INTEL\APPS\PROSETDX\2KXPWS03\DxRes*.DLL	;International language files
D:\PUSHW2K\I386\$oem$\$1\drivers\net\INTEL\APPS\PROSETDX\2KXPWS03\DxSetup.exe
D:\PUSHW2K\I386\$oem$\$1\drivers\net\INTEL\APPS\PROSETDX\2KXPWS03\License.cab
D:\PUSHW2K\I386\$oem$\$1\drivers\net\INTEL\APPS\PROSETDX\2KXPWS03\OemVer.reg

(From the \APPS\PROSETDX\2KXPWS03\DRIVERS directory of the Intel CD)
D:\PUSHW2K\I386\$oem$\$1\drivers\net\INTEL\APPS\PROSETDX\2KXPWS03\DRIVERS\ANSM2KXP.INF
D:\PUSHW2K\I386\$oem$\$1\drivers\net\INTEL\APPS\PROSETDX\2KXPWS03\DRIVERS\ANSP2KXP.INF
D:\PUSHW2K\I386\$oem$\$1\drivers\net\INTEL\APPS\PROSETDX\2KXPWS03\DRIVERS\IANS2KXP.CAT
D:\PUSHW2K\I386\$oem$\$1\drivers\net\INTEL\APPS\PROSETDX\2KXPWS03\DRIVERS\IANSMSG.DLL
D:\PUSHW2K\I386\$oem$\$1\drivers\net\INTEL\APPS\PROSETDX\2KXPWS03\DRIVERS\IANSW2K.SYS
D:\PUSHW2K\I386\$oem$\$1\drivers\net\INTEL\APPS\PROSETDX\2KXPWS03\DRIVERS\IANSWXP.SYS
D:\PUSHW2K\I386\$oem$\$1\drivers\net\INTEL\APPS\PROSETDX\2KXPWS03\DRIVERS\INTELNIC.DLL
D:\PUSHW2K\I386\$oem$\$1\drivers\net\INTEL\APPS\PROSETDX\2KXPWS03\DRIVERS\PRONTOBJ.DLL

(From the \APPS\SETUP\SETUPBD\W98-WS32 directory of the Intel CD)
D:\PUSHW2K\I386\$oem$\$1\drivers\net\INTEL\APPS\Setup\SetupBD\W98-WS32\INST98.DLL
D:\PUSHW2K\I386\$oem$\$1\drivers\net\INTEL\APPS\Setup\SetupBD\W98-WS32\NETINST.DLL
D:\PUSHW2K\I386\$oem$\$1\drivers\net\INTEL\APPS\Setup\SetupBD\W98-WS32\SETBDRES.DLL
D:\PUSHW2K\I386\$oem$\$1\drivers\net\INTEL\APPS\Setup\SetupBD\W98-WS32\SETUPBD.DIN
D:\PUSHW2K\I386\$oem$\$1\drivers\net\INTEL\APPS\Setup\SetupBD\W98-WS32\SETUPBD.EXE
D:\PUSHW2K\I386\$oem$\$1\drivers\net\INTEL\APPS\Setup\SetupBD\W98-WS32\SETUPBD.INI

(From the \APPS\Tools directory of the Intel CD)
D:\PUSHW2K\I386\$oem$\$1\drivers\NET\INTEL\APPS\Tools\DIAGS.EXE
D:\PUSHW2K\I386\$oem$\$1\drivers\NET\INTEL\APPS\Tools\DIAGS.TXT
D:\PUSHW2K\I386\$oem$\$1\drivers\NET\INTEL\APPS\Tools\IDADAPT.EXE
D:\PUSHW2K\I386\$oem$\$1\drivers\NET\INTEL\APPS\Tools\IDADAPT.TXT

(From the \APPS\SETUP\PUSH\WIN2K directory of the Intel CD)
D:\PUSHW2K\I386\$oem$\$1\drivers\NET\INTEL\UNATTEND.TXT
D:\PUSHW2K\I386\$oem$\$1\drivers\NET\INTEL\PUSHW2K.TXT
D:\PUSHW2K\I386\$oem$\$1\drivers\NET\INTEL\INSTALL.BAT

(From the \APPS\INTELAMT\DRIVERS\WS03XP directory of the Intel CD)
(*Files are copied only if they exist on the CD*)
D:\PUSHW2K\I386\$oem$\$1\drivers\net\INTEL\APPS\INTELAMT\DRIVERS\WS03XP\IAMT03.SYS
D:\PUSHW2K\I386\$oem$\$1\drivers\net\INTEL\APPS\INTELAMT\DRIVERS\WS03XP\IAMT.CAT
D:\PUSHW2K\I386\$oem$\$1\drivers\net\INTEL\APPS\INTELAMT\DRIVERS\WS03XP\IAMT.INF
D:\PUSHW2K\I386\$oem$\$1\drivers\net\INTEL\APPS\INTELAMT\DRIVERS\WS03XP\IAMTXP.SYS
D:\PUSHW2K\I386\$oem$\$1\drivers\net\INTEL\APPS\INTELAMT\DRIVERS\WS03XP\IRESOL.CAT
D:\PUSHW2K\I386\$oem$\$1\drivers\net\INTEL\APPS\INTELAMT\DRIVERS\WS03XP\IRESOL.INF

; To activate the Intel(R) PROSet for Windows Device Manager installation 
; once the above directories have been created and populated, uncomment 
; the line:

;    Command0="%systemdrive%\WMIScr\Install.bat"
;  in the [GuiRunOnce] section of Unattend.txt
server: web1, load: 0.99