How To Install Windows Aik

Tabular array of Contents

Network-booting Windows PE

Windows PE (WinPE) is the Windows Preinstallation Environment, used for installation and repair of Windows computers.

Using iPXE and wimboot, yous can kick into Windows PE via HTTP. You can then connect to a standard Windows file server to install a total version of Windows to the local hard disk drive (or to an iSCSI target).

Booting Windows PE via HTTP is much faster than using traditional TFTP-based methods such every bit Windows Deployment Services (WDS). On a Gigabit Ethernet network, it should take less than two seconds to download a typical 200MB Windows PE image.

Setting upwardly Windows PE

Windows PE is available as part of the Windows Assessment and Deployment Toolkit (ADK) for current versions of Windows, or every bit part of the Windows Automated Installation Kit (AIK) for earlier versions of Windows.

Windows Assessment and Deployment Toolkit (ADK)

The Windows Assessment and Deployment Toolkit (ADK) is compatible with Windows Server 2012, Windows viii, Windows seven, Windows Server 2008, and Vista.

Download and install the ADK onto a working Windows organization (the "technician computer").

From the Start menu, choose All Programs → Windows Kits → Windows ADK → Deployment and Imaging Tools Surround. This should open a command prompt window. Create 32-bit and 64-fleck versions of Windows PE:

            mkdir C:\temp\winpe   copype x86 C:\temp\winpe\x86   copype amd64 C:\temp\winpe\amd64

Copy the contents of C:\temp\winpe to a directory on your spider web server (east.g. /var/world wide web/winpe for Apache, or C:\inetpub\wwwroot\winpe for IIS).

Download the latest version of wimboot and relieve it to the same directory on your web server.

Create a text file boot.ipxe in the same directory on your web server, containing:

            #!ipxe      cpuid --ext 29 && set up arch amd64 || set arch x86   kernel wimboot   initrd ${arch}/media/Boot/BCD                     BCD   initrd ${curvation}/media/Boot/boot.sdi                boot.sdi   initrd ${arch}/media/sources/boot.wim             kicking.wim   boot

Windows Automatic Installation Kit (AIK)

The Windows Automated Installation Kit (AIK) is compatible with Windows 7, Windows Server 2008, Vista, and Windows Server 2003.

Download and install the AIK onto a working Windows system (the "technician computer").

From the Showtime card, choose All Programs → Microsoft Windows AIK → Deployment Tools Command Prompt. This should open a command prompt window. Create 32-chip and 64-chip versions of Windows PE:

            mkdir C:\temp\winpe   copype x86 C:\temp\winpe\x86   copype amd64 C:\temp\winpe\amd64

Copy the contents of C:\temp\winpe to a directory on your spider web server (east.g. /var/world wide web/winpe for Apache, or C:\inetpub\wwwroot\winpe for IIS).

Download the latest version of wimboot and salve information technology to the aforementioned directory on your web server.

Create a text file boot.ipxe in the same directory on your web server, containing:

            #!ipxe      cpuid --ext 29 && ready curvation amd64 || ready arch x86   kernel wimboot   initrd ${curvation}/ISO/boot/bcd          BCD   initrd ${arch}/ISO/boot/boot.sdi     boot.sdi   initrd -n boot.wim ${curvation}/winpe.wim boot.wim   boot

Booting Windows PE

Boot using iPXE from the URI of your boot.ipxe script, e.grand. http://my.web.server/winpe/kick.ipxe. You lot should come across iPXE download and boot Windows PE via HTTP:

Installing Windows

You tin now connect to a Windows (or Samba) file server to run the Windows installer. For example, if you have copied the contents of your Windows installation DVD-ROM to \\myserver\installers\win8, and so you can start the installer using:

            net use \\myserver\installers   \\myserver\installers\win8\setup.exe

Advanced topics

Adding a startup batch file

You tin customise your Windows PE image so that information technology automatically connects to a file server and runs the Windows installer.

Create a text file install.bat containing the commands needed to connect to your file server and kickoff the installer:

            wpeinit   net employ \\myserver\installers   \\myserver\installers\win8\setup.exe

Create a text file winpeshl.ini instructing Windows PE to run your install.bat file:

            [LaunchApps]   "install.bat"

Copy install.bat and winpeshl.ini to your web server and edit your boot.ipxe script to load these files:

            #!ipxe      cpuid --ext 29 && set curvation amd64 || fix arch x86   kernel wimboot   initrd install.bat                                install.bat   initrd winpeshl.ini                               winpeshl.ini   initrd ${arch}/media/Boot/BCD                     BCD   initrd ${arch}/media/Kick/boot.sdi                kick.sdi   initrd ${arch}/media/sources/boot.wim             boot.wim   boot

When you kicking into Windows PE, information technology should now automatically connect to your file server and run the Windows installer.

Calculation a network menu driver

You tin customise your Windows PE paradigm to include drivers for your network bill of fare, if your card is not already supported by Windows PE. Yous will need the ImageX and DISM tools, which are office of the Windows ADK (or AIK). A Linux version of imagex is also bachelor as part of the wimlib package.

Download the drivers for your network card, and excerpt the driver to C:\temp\winpe\drivers. If you lot are using the ADK then you will demand to download a driver uniform with Windows 8; if you are using the AIK then you will need a driver uniform with Windows 7.

Use ImageX and DISM to add together this driver to your Windows PE epitome:

            imagex /mountrw C:\temp\winpe\amd64\media\sources\boot.wim 1 C:\temp\winpe\amd64\mount   dism /prototype:C:\temp\winpe\amd64\mount /add-driver /driver:c:\temp\winpe\drivers /recurse   imagex /unmount /commit C:\temp\winpe\amd64\mount

Installing to an iSCSI target

You can use your Windows PE image to install Windows to an iSCSI target. Create a text file install.ipxe containing:

            #!ipxe      prompt -k 0x197e -t 2000 Press F12 to install Windows... || exit   concatenation kick.ipxe

and copy it to the directory on your web server containing your kicking.ipxe script.

Configure your DHCP server to provide the URI of your install.ipxe script as the kick filename, and the SAN URI of your iSCSI target as the root-path. If your iSCSI target uses access control lists (ACLs), then you may also need to provide the correct initiator-iqn.

You should see the diskless figurer connect to the iSCSI target and then prompt you to "Printing F12 to install Windows":

Press F12 to begin the installation process. If yous have already added a startup batch file as described above, then the Windows installer will commencement automatically. If not, so connect to your file server and run the Windows installer manually.

Continue to install Windows every bit usual. When you achieve the "Where do you desire to install Windows?" screen, you should encounter the iSCSI disk announced every bit a possible install location:

Source: https://ipxe.org/howto/winpe

Posted by: buitronthasma.blogspot.com

Share this post