pushw2k.txt Driver File Contents (Wireless11Mbit.exe)

Windows* 2000 Push Install Instructions
Release Notes
May 29, 2002
=============================================

Copyright (C) 2002, 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.

Contents:
I.	Introduction
II.   	Setting up an install directory on the file server
III.  	Deployment Methods
IV.     Microsoft documentation for unattended installations of Windows
        2000.
V.      A sample unattend.txt file for Windows 2000 Professional.
VI.     Directory structure for unattended installation files.
    

I. Introduction

	A "Push", or unattended installation of Windows 2000 provides a
    means for network adminstrators to easily install Windows 2000 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 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.  

    The elements necessary for the Windows 2000 unattend installation are:

    -  A Windows 2000 Server with a shared image of the \I386 directory
       from the Windows 2000 installation CD.

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


II. 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 in this readme use the network share 
    D:\PUSH2K.  To create this share, create a directory on the server, 
    (EX: D:\PUSH2K) and create an I386 directory beneath it.  
	Next, use the "My Computer" applet in Windows 2000 to locate the D:\PUSH2K 
    folder. Right-click on the folder and select "Sharing".  Select "Share 
    this folder", Give it a share name (EX: PUSH2K).  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".   Adjust permissions as necessary and click OK.  

    To prepare the distribution folder:

       	1. Copy the \I386 folder from the Windows 2000 CD to D:\PUSH2K.
	       Use Windows Explorer or XCOPY in order to maintain the same 
           directory structure as on the CD.  When the copy is complete, the
           Windows 2000 installation files should be in the D:\PUSH2K\I386
           directory.
 	
        2. Copy Unattend.txt from the Intel media (found in \APPS\SETUP\PUSH\WIN2K)
           into the shared directory D:\PUSH2K\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 will copy 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 the Intel(R) PROSet II configuration and
                 diagnostic utility.
               
                 Example:  From a Windows 2000 command prompt:
                           e:
                           (where e: is the drive letter of your CDROM drive)
                           cd \APPS\SETUP\PUSH
                           (you must be in the \APPS\SETUP\PUSH directory to run 
                           PUSHCOPY)
                           pushcopy D:\PUSH2K\I386 w2k"
    
                 The above command will create the $OEM$ directory structure and 
                 copy all the necessary files to install the driver and 
                 PROSetII.  However, PROSetII will not be installed unless the 
                 line:

           ;    Command1="c:\drivers\net\Intel\Proset.msi /qn"
                 is uncommented from unattend.txt.



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


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

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

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


IV.  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 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/support/kb/articles/Q246/1/84.ASP?LN=EN-US&SD=gn&FR=0

     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/support/kb/articles/q254/0/78.asp?LN=EN-US&SD=gn&FR=0



V.  A sample Unattend.txt file for Windows* 2000 Professional:

[Unattended]
    UnattendMode=FullUnattended
    OemSkipEula=Yes
    OemPreinstall=Yes
    OemPnPDriversPath=\drivers\net\INTEL
    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

[GuiRunOnce]
    ; *** command to install PROSetII - uncomment to install PROSetII after push install
;   Command2="c:\drivers\net\Intel\proset.msi /qn"

[Identification]
    JoinWorkGroup = Workgroup
;  *Use the following for a domain installation
;    JoinDomain=MYDOMAIN
;    CreateComputerAccountInDomain=Yes
;    DomainAdmin=Installer
;    DomainAdminPassword=install

[Networking]
    InstallDefaultComponents=Yes

(end of unattend.txt sample)


VI.  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 PROSet II.  The 
directory D:\PUSH2K refers to the location of the files from the \I386 
directory on the Windows 2000 installation CD.

D:\PUSH2K\$OEM$\$$\System32

   <no files are copied into this directory>

D:\PUSH2K\$OEM$\$1\DRIVERS\NET\Intel

    (From the \PRO100\WIN2K directory of the Intel drivers CD)

    E100BNT5.INF
    E100BNT5.DIN
    E100BNT5.SYS
    E100BNT5.CAT
    E100BMSG.DLL
    INTELNIC.DLL
    PROUNSTL.EXE

    (From the \PRO1000\WIN2K directory of the Intel drivers CD)

    E1000NT5.INF
    E1000NT5.DIN
    E1000NT5.SYS
    E1000NT5.CAT
    E1000MSG.DLL


    (From the \APPS\SETUP\PUSH\WIN2K directory of the Intel drivers CD)

	UNATTEND.TXT
	PUSHW2K.TXT

    (From the \APPS\PROSET\Win2K directory of the Intel drivers CD)

    ANSPW2K.INF
    ANSMW2K.INF
    IANSMSG.DLL
    IANSW2K.SYS
    IANSW2K.CAT
    PROSET.MSI
    S8023DEV.REG
    *.MST     ;  International language files

;  To activate the PRoset II installation once the above directories have
;  been created and populated, uncomment the line:

;   Command2="c:\drivers\net\INTEL\Proset.msi /qn"
;  in the [GuiRunOnce] section of Unattend.txt
Download Driver Pack

How To Update Drivers Manually

After your driver has been downloaded, follow these simple steps to install it.

  • Expand the archive file (if the download file is in zip or rar format).

  • If the expanded file has an .exe extension, double click it and follow the installation instructions.

  • Otherwise, open Device Manager by right-clicking the Start menu and selecting Device Manager.

  • Find the device and model you want to update in the device list.

  • Double-click on it to open the Properties dialog box.

  • From the Properties dialog box, select the Driver tab.

  • Click the Update Driver button, then follow the instructions.

Very important: You must reboot your system to ensure that any driver updates have taken effect.

For more help, visit our Driver Support section for step-by-step videos on how to install drivers for every file type.

server: web3, load: 0.39