Push Install Instructions for Microsoft Windows* XP

- 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 XP 

- Sample unattend.txt file for Windows XP 

- Directory structure for unattended installation files. 

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

Introduction

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

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

The elements necessary for the Windows XP unattended installation are:

- A Windows XP server with a shared image of the Windows XP Installation CD. 
- If you wish to create VLANS as part of the unattended installation, you need
  to create a configuration file with the VLAN information in it.  To create
  this file you need a sample system that has the same of adapter(s) 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 VLAN configuration you want. This system could also be the Windows 
  XP system mentioned above. For clarity, this system is referred to in this 
  document as the configured system.
- An unattended installation configuration file that provides Windows setup 
  with information it needs to complete the installation. The name of this 
  file is UNATTEND.TXT 
- A DOS boot disk that contains Microsoft Network Client software, which is 
  used to connect to the Windows server. This disk also includes AutoExec 
  commands to automatically start the Windows installation. 

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

Setting up an install directory on the file server

The server must be setup with a distribution folder that holds the required 
Windows XP files. Clients must also be able to read this folder when connecting 
via TCP/IP or IPX.

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

1) Create a directory on the server, (EX: D:\PUSHXP).
2) Use the My Computer applet in Windows XP to locate the D:\PUSHXP folder.  
3) Right-click the folder and select Sharing. Select Share this folder. 
4) Give it a share name (EX: PUSHXP). 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 XP CD to D:\PUSHXP. Use Windows 
   Explorer or XCOPY to maintain the same directory structure as on the 
   Windows XP CD. When the copy is complete, the Windows XP installation 
   files should be in the D:\PUSHXP\I386 directory. 
2) Copy Unattend.txt from the Intel CD (found in \APPS\SETUP\PUSH\XP) into 
   the shared directory D:\PUSHXP\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. 
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 XP command prompt where e: is the drive letter of 
your CDROM drive: 
e:
cd \APPS\SETUP\PUSH 
	(you must be in the APPS\SETUP\PUSH\ directory to run PUSHCOPY)
pushcopy D:\PUSHXP\I386 XP

The above command creates the $OEM$ directory structure and copy 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" 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 XP Server , create a directory in the $OEM$\$1 directory 
   called WMIScr. For example, on Windows XP, the directory is 
   $OEM$\$1\WMIScr. 
5) Copy the SavResDX.vbs and WmiConf.txt files to the WMIScr directory.  Additionally, create a batch file and rename it to Install.bat.
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\PROSetDX.msi /qn /li %temp%\PROSetDX.log
   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 connects 
to the Z:\PUSHXP 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 from the \\Server\PUSHXP\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 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 XP

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

Other documents and utilities in the DEPLOY.CAB file provide details and tools 
for setting up a variety of unattended installation methods. 

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

Sample unattend.txt file for Windows XP
 
[Unattended]
UnattendMode=FullUnattended
OemSkipEula=Yes
OemPreinstall=Yes
OemPnPDriversPath = "\drivers\net\INTEL\PRO100\WS03XP2K;\drivers\net\INTEL\PRO1000\WS03XP2K;\drivers\net\INTEL\APPS\INTELAMT\DRIVERS\WS03XP2K"
TargetPath= *
DriverSigningPolicy=Ignore
Filesystem=LeaveAlone
OverwriteOemFilesOnUpgrade=No

; This switch prevents the user setup dialog from running when XP
; starts for the first time.
UnattendSwitch=Yes

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

[UserData]
FullName=Name
OrgName=Organization
ComputerName=Computer1
; PRODUCT ID is required for most installations.
ProductID="xxxxx-xxxxx-xxxxx-xxxxx-xxxxx"

; For Server Installations. The server License type must be specified.

[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 XP 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
; DomainAdminPassword=install

[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:\PUSHXP refers to the location of the files 
from the Windows XP installation CD. 

D:\PUSHXP\I386\$OEM$\$1\DRIVERS\NET\INTEL

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

(From the \PRO1000\WS03XP2K directory of the Intel CD)
D:\PUSHXP\I386\$oem$\$1\drivers\net\INTEL\PRO1000\WS03XP2K\E1E5032.DIN
D:\PUSHXP\I386\$oem$\$1\drivers\net\INTEL\PRO1000\WS03XP2K\E1E5032.SYS
D:\PUSHXP\I386\$oem$\$1\drivers\net\INTEL\PRO1000\WS03XP2K\E1E5132.CAT
D:\PUSHXP\I386\$oem$\$1\drivers\net\INTEL\PRO1000\WS03XP2K\E1E5132.DIN
D:\PUSHXP\I386\$oem$\$1\drivers\net\INTEL\PRO1000\WS03XP2K\E1E5132.INF
D:\PUSHXP\I386\$oem$\$1\drivers\net\INTEL\PRO1000\WS03XP2K\E1E5132.SYS
D:\PUSHXP\I386\$oem$\$1\drivers\net\INTEL\PRO1000\WS03XP2K\E1000MSG.DLL
D:\PUSHXP\I386\$oem$\$1\drivers\net\INTEL\PRO1000\WS03XP2K\E1000NT5.DIN
D:\PUSHXP\I386\$oem$\$1\drivers\net\INTEL\PRO1000\WS03XP2K\E1000NT5.SYS
D:\PUSHXP\I386\$oem$\$1\drivers\net\INTEL\PRO1000\WS03XP2K\E1000325.CAT
D:\PUSHXP\I386\$oem$\$1\drivers\net\INTEL\PRO1000\WS03XP2K\E1000325.DIN
D:\PUSHXP\I386\$oem$\$1\drivers\net\INTEL\PRO1000\WS03XP2K\E1000325.INF
D:\PUSHXP\I386\$oem$\$1\drivers\net\INTEL\PRO1000\WS03XP2K\E1000325.SYS
D:\PUSHXP\I386\$oem$\$1\drivers\net\INTEL\PRO1000\WS03XP2K\ETCO32.DLL
D:\PUSHXP\I386\$oem$\$1\drivers\net\INTEL\PRO1000\WS03XP2K\NICCO32.DLL
D:\PUSHXP\I386\$oem$\$1\drivers\net\INTEL\PRO1000\WS03XP2K\NICIN32.DLL
D:\PUSHXP\I386\$oem$\$1\drivers\net\INTEL\PRO1000\WS03XP2K\PROUNSTL.EXE

(From the \APPS\PROSETDX\2KXPWS03 directory of the Intel CD)
D:\PUSHXP\I386\$oem$\$1\drivers\net\INTEL\APPS\PROSETDX\2KXPWS03\*.MST  ;15 International language files
D:\PUSHXP\I386\$oem$\$1\drivers\net\INTEL\APPS\PROSETDX\2KXPWS03\ANS.CAB
D:\PUSHXP\I386\$oem$\$1\drivers\net\INTEL\APPS\PROSETDX\2KXPWS03\CDM.CAB
D:\PUSHXP\I386\$oem$\$1\drivers\net\INTEL\APPS\PROSETDX\2KXPWS03\CUSTOM.INI
D:\PUSHXP\I386\$oem$\$1\drivers\net\INTEL\APPS\PROSETDX\2KXPWS03\DMIX.CAB
D:\PUSHXP\I386\$oem$\$1\drivers\net\INTEL\APPS\PROSETDX\2KXPWS03\DXSETUP.EXE
D:\PUSHXP\I386\$oem$\$1\drivers\net\INTEL\APPS\PROSETDX\2KXPWS03\DXSETUP.INI
D:\PUSHXP\I386\$oem$\$1\drivers\net\INTEL\APPS\PROSETDX\2KXPWS03\FTMI.CAB
D:\PUSHXP\I386\$oem$\$1\drivers\net\INTEL\APPS\PROSETDX\2KXPWS03\LR_DMIX.CAB
D:\PUSHXP\I386\$oem$\$1\drivers\net\INTEL\APPS\PROSETDX\2KXPWS03\OEMVER.REG
D:\PUSHXP\I386\$oem$\$1\drivers\net\INTEL\APPS\PROSETDX\2KXPWS03\PROSETDX.MSI
D:\PUSHXP\I386\$oem$\$1\drivers\net\INTEL\APPS\PROSETDX\2KXPWS03\SETUP.INI

(From the \APPS\PROSETDX\2KXPWS03\DRIVERS directory of the Intel CD)
D:\PUSHXP\I386\$oem$\$1\drivers\net\INTEL\APPS\PROSETDX\2KXPWS03\DRIVERS\ANSM2KXP.INF
D:\PUSHXP\I386\$oem$\$1\drivers\net\INTEL\APPS\PROSETDX\2KXPWS03\DRIVERS\ANSP2KXP.INF
D:\PUSHXP\I386\$oem$\$1\drivers\net\INTEL\APPS\PROSETDX\2KXPWS03\DRIVERS\IANS2KXP.CAT
D:\PUSHXP\I386\$oem$\$1\drivers\net\INTEL\APPS\PROSETDX\2KXPWS03\DRIVERS\IANSMSG.DLL
D:\PUSHXP\I386\$oem$\$1\drivers\net\INTEL\APPS\PROSETDX\2KXPWS03\DRIVERS\IANSW2K.SYS
D:\PUSHXP\I386\$oem$\$1\drivers\net\INTEL\APPS\PROSETDX\2KXPWS03\DRIVERS\IANSWXP.SYS
D:\PUSHXP\I386\$oem$\$1\drivers\net\INTEL\APPS\PROSETDX\2KXPWS03\DRIVERS\NICCO32.DLL
D:\PUSHXP\I386\$oem$\$1\drivers\net\INTEL\APPS\PROSETDX\2KXPWS03\DRIVERS\NICIN32.DLL
D:\PUSHXP\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:\PUSHXP\I386\$oem$\$1\drivers\net\INTEL\APPS\Setup\SetupBD\W98-WS32\INST98.DLL
D:\PUSHXP\I386\$oem$\$1\drivers\net\INTEL\APPS\Setup\SetupBD\W98-WS32\NETINST.DLL
D:\PUSHXP\I386\$oem$\$1\drivers\net\INTEL\APPS\Setup\SetupBD\W98-WS32\SETBDRES.DLL
D:\PUSHXP\I386\$oem$\$1\drivers\net\INTEL\APPS\Setup\SetupBD\W98-WS32\SETUPBD.DIN
D:\PUSHXP\I386\$oem$\$1\drivers\net\INTEL\APPS\Setup\SetupBD\W98-WS32\SETUPBD.EXE
D:\PUSHXP\I386\$oem$\$1\drivers\net\INTEL\APPS\Setup\SetupBD\W98-WS32\SETUPBD.INI

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

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

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

; 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
