Push Install Instructions for x64 Microsoft Windows* Operating Systems
================================================================================

- Introduction 
- Setting up an Install Directory on the File Server
- Instructions for Creating Teams and VLANs (Optional)
- Microsoft Windows* 7, Vista*, and Server* 2008 Instructions
  - Deployment methods 
  - Microsoft documentation for unattended installations 
- Microsoft Windows XP and Server 2003 Instructions
  - Deployment methods 
  - Microsoft documentation for unattended installations 
  - Sample unattend.txt file for Windows XP 
 
================================================================================

Introduction
================================================================================

A "Push", or unattended installation provides a means for network administrators
to easily install a 32-bit Microsoft Windows* operating system on similarly 
equipped systems. The network administrator can create a bootable media 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 that 
includes the installation of drivers for Intel(R) Networking Devices. 

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

Supported operating systems are:
- Microsoft Windows* XP x64
- Microsoft Windows Vista* x64
- Microsoft Windows* 7 x64
- Microsoft Windows Server* 2003 x64
- Microsoft Windows Server* 2008 x64
- Microsoft Windows Server* 2008 R2

================================================================================

Setting up an Install Directory on the File Server
================================================================================

The server must be setup with a distribution folder that holds the required 
Windows 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:\WINPUSH. To create this share:

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

================================================================================

Instructions for Creating Teams and VLANs (Optional)
================================================================================

If you wish to create teams/VLANS as part of the unattended installation, you need
to create a configuration file with the team/VLAN information in it.  To create
this file you need a sample system that has the same type 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 
team/VLAN configuration you want.

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 Server, create a directory in the $OEM$\$1 directory called 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 that preceeds the second START command.
   The file should look like the follow when finished:
   
   Start /wait %systemdrive%\drivers\net\INTEL\APPS\ProsetDX\Win32\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
7) If you are installing Microsoft Windows Vista, run ImageX.exe to create 
   the Intel.wim containing the team or VLAN.

================================================================================
Microsoft Windows 7, Vista, and Server 2008 Instructions
================================================================================

To prepare the distribution folder:

1) Copy the entire contents from the Windows Install DVD to D:\WINPUSH. Use Windows 
   Explorer or XCOPY to maintain the same directory structure as on the 
   Windows Install DVD. When the copy is complete, the Windows installation 
   files should be in the D:\WINPUSH directory. 
2) Use the Windows System Image Manager to edit/generate the 
   Unattend.xml file and save it to the D:\WINPUSH directory.
3) Create the driver install directory structure and copy the driver files 
   to it. 

Example: From a Windows 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:\WINPUSH [VISTA32]

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 FirstLogonCommands is added as seen in the example below.

[Microsoft-Windows-Shell-Setup\FirstLogonCommands\SynchronousCommand]
CommandLine= %systemdrive%\WMIScr\Install.bat
Description= Begins silent unattended install of Intel PROSet for Windows Device Manager
Order= 1

4) Using ImageX.EXE from the WAIK (Windows Automated Installation Kit ), create a 
   WIM image file of the $OEM$ folder

Example: From the Windows command prompt:
Imagex /capture d:\WINPUSH\$oem$\$1 d:\WINPUSH\intel.wim "Intel(R) PROSet for Device Manager Drivers and Software"

--------------------------------------------------------------------------------
Deployment methods
--------------------------------------------------------------------------------

Boot using your WinPE 2.0 media and connect to the server containing your Windows
Vista 32 installation share. 

Run the command from the \\Server\WINPUSH prompt: 
	setup /unattend:<full path to answer file> 

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

For a complete description of the parameters supported in Unattend.XML visit 
support.microsoft.com to view the Windows Automated Installation Kit (WAIK) 
documentation.

================================================================================

Microsoft Windows XP and Server 2003 Instructions
================================================================================

To prepare the distribution folder:

1) Copy the \I386 folder from the Windows XP CD to D:\WINPUSH. 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:\WINPUSH\I386 directory. 
2) Copy Unattend.txt from the Intel CD (found in \APPS\SETUP\PUSH\Win32) into 
   the shared directory D:\WINPUSH\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 edited to specify the License type 
   and the number of users if the license type is PerServer. 
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 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:\WINPUSH\I386 [XP|WS03]

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.

--------------------------------------------------------------------------------
Deployment methods
--------------------------------------------------------------------------------

Make sure that you have a copy of a network bootable MS-DOS* floppy that connects 
to the Z:\WINPUSH 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\WINPUSH\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
--------------------------------------------------------------------------------

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

[Unattended]
UnattendMode=FullUnattended
OemSkipEula=Yes
OemPreinstall=Yes
OemPnPDriversPath = "\drivers\net\INTEL\PRO100\Win32;\drivers\net\INTEL\PRO1000\Win32;\drivers\net\INTEL\PLATFORM\INTELAMT\DRIVERS\Win32;\drivers\net\INTEL\PLATFORM\IOATDMA\Win32"
TargetPath= *
DriverSigningPolicy=Ignore
Filesystem=LeaveAlone
OverwriteOemFilesOnUpgrade=No

; This switch prevents the user setup dialog from running when Windows
; 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 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

; 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


================================================================================

Copyright (C) 1998-2009, Intel Corporation.  All rights reserved.

Intel Corporation assumes no responsibility for errors or omissions in 
this document. Nor does Intel make any commitment to update the information 
contained herein.

* Other product and corporate names may be trademarks of other companies 
and are used only for explanation and to the owners' benefit, without intent 
to infringe.
