Installing windows 7 from the network. Self-installation of Windows over the network. We configure servers

Greetings to everyone on the pages of my blog !!!

You never know at what moment we need to install our beloved one, and it happens that there is neither a floppy drive, nor a USB drive, nor even a flash drive with sufficient memory that is just lying around, then there is only one way to install it .. ....... through the network. It's not just that the BIOS has a function to boot from a network card.

Installing Windows 7 over a local area network

To carry out this operation, we will need the following set:

with the version you want.
Windows® Automated Installation Kit (AIK) for Windows® 7;
Emulator of TFTP and DHCP servers. However, we will still take tftpd32;
Any computer on which will be installed:
a.Windows 7 in any edition you like. Windows Server 2008 and Windows Vista will do the same;
b. Any program for emulating a disk image. For example Daemon Tools Lite or another one you have in stock
Mindfulness, composure and straight arms. (Growing from the right place will also come down)
are you ready? If yes, then ........ let's go Gentlemen !!!

First, we'll install our Windows Automated Installation Kit (AIK) for Windows® 7. You need to mount the Daemon Tools Lite image or in similar programs (Alcohol 120%, ImgBurn, Nero, UltraISO). You can also unzip the image to any folder and run StartCD.exe

In the "Start" menu, look for and find the Microsoft Windows AIK, see "Command Prompt for Deployment Tools" and run. The console will open immediately. This is where the fun begins.
We enter these commands into the console. (X is any drive)

Copype.cmd x86 x: winpe imagex / mountrw winpe.wim 1 mount.

Made. Now in x: winpemount we have a ready mounted wipe.wim image.
So that we do not need to map the network drive ourselves and not manually launch the Setup program, we need to correct the startnet.cmd file, which is located in x: winpemountwindowssystem32. The file should look like this:

Wpeinit net use y: \ 192.168.1.1seven / user: install install if exist y: sourcessetup.exe (y: cd sources setup.exe)

This means that the IP address has a value of 192.168.1.1. Have a different IP address? Please enter its exact value.
Note that the connection from the second computer to which we are installing is made with the rights of the install user with the same password - install. You need to create an install user in advance. This can be done using this command:

Net user install install / add / passwordchg: no

Now the work with the image is finished, and we can unmount it using the command:

Imagex.exe / unmount / commit mount

With the image sorted out, and now we need to create directories for the files that will be needed for the installation.
So, create a folder from which files will be loaded over the network. For example, X: Windows7. In the created folder, create another directory called boot. It will store the download files. And now from the Windows 7 disk we need to copy the contents of the source folder to our Windows7 folder. You can also push the autounattend.xml file into the source. It stores the unattended setup setup. It is worth saying that everything will go smoothly without him.
Now we need to fill in our boot. Enter the commands:

Imagex / mount x: winpewinpe.wim 1 x: winpemount. xcopy / ey x: winpemountwindowsootpxe x: Windows7 xcopy / iy x: winpemountwindowsootfonts x: Windows7ootfonts copy / y x: winpeISOootoot.sdi x: Windows7oot

We have moved the necessary files to download to x: Windows7.

Unmount the image again using the same command:

Imagex.exe / unmount d: winpemount

By the way, we will also transfer the image to X: Windows7oot using the command:

Copy / y d: winpewinpe.wim x: Windows7oot

We open access for all users to the folder x: Windows7oot.
Now let's create a BCD - a store of boot parameters. We can do this using a special createbcd.cmd script, which we create in the x: Windows7oot folder.

For the distribution kit in Russian:

bcdedit -createstore% 1BCD bcdedit -store% 1BCD -create (ramdiskoptions) / d "Ramdisk options" bcdedit -store% 1BCD -set (ramdiskoptions) ramdisksdidevice boot bcdedit -store% 1BCD -set (ramdiskoptionsdoto) ramdisis "tokens = 2" %% i in ("bcdedit -store% 1BCD -create / d" MyWinPE Boot Image "/ application osloader") do set guid = %% i bcdedit -store% 1BCD -set% guid% systemroot Windows bcdedit -store% 1BCD -set% guid% detecthal Yes bcdedit -store% 1BCD -set% guid% winpe Yes bcdedit -store% 1BCD -set% guid% osdevice ramdisk = Bootwinpe.wim, (ramdiskoptions) bcdedit -store% 1BCD -set % guid% device ramdisk = Bootwinpe.wim, (ramdiskoptions) bcdedit -store% 1BCD -create (bootmgr) / d "Windows VISTA BootManager" bcdedit -store% 1BCD -set (bootmgr) timeout 30 bcdedit -store% 1BCD -set ( bootmgr) displayorder% guid%

For the distribution in English:

bcdedit -createstore% 1BCD bcdedit -store% 1BCD -create (ramdiskoptions) / d "Ramdisk options" bcdedit -store% 1BCD -set (ramdiskoptions) ramdisksdidevice boot bcdedit -store% 1BCD -set (ramdiskoptionsdoto) ramdisis "tokens = 3" %% i in ("bcdedit -store% 1BCD -create / d" MyWinPE Boot Image "/ application osloader") do set guid = %% i bcdedit -store% 1BCD -set% guid% systemroot Windows bcdedit -store% 1BCD -set% guid% detecthal Yes bcdedit -store% 1BCD -set% guid% winpe Yes bcdedit -store% 1BCD -set% guid% osdevice ramdisk = Bootwinpe.wim, (ramdiskoptions) bcdedit -store% 1BCD -set % guid% device ramdisk = Bootwinpe.wim, (ramdiskoptions) bcdedit -store% 1BCD -create (bootmgr) / d "Windows VISTA BootManager" bcdedit -store% 1BCD -set (bootmgr) timeout 30 bcdedit -store% 1BCD -set ( bootmgr) displayorder% guid%

Now enter in the console:

Createbcd.cmd x: uploadoot Now we need to configure the tftpd32 program.

In the main window, in the "Current Directory" we enter our directory x: Windows7 Server interface: 192.168.1.1. In the "DHCP server" tab, in "IP pool starting address" - 192.168.1.2 "Size of pool" - 10 "Boot file" - pxeboot.n12 In "WINSDNS Server" and "Default router" set 0.0.0.0. Leave “Mask” - 255.255.255.0 Domain Name blank, “Additional Option” - 0.

Poke Settings.

Check the boxes for "TFTP Server", "DHCP Server", "Ping address before assignation", "Persistant leases", "Option negotiation", "Show Progress bar", "Translate Unix file names", "Bind TFTP to this address" , "Bind TFTP to this address" and "Allow" "As virtual root".

In "TFTP Security" we select Standart.

In "TFTP configuration":

Set "Timeout" to 3;

"Max Retransmit" is set to 6;

"Tftp port" is set to 69;

Leave the "Local ports pool" empty.

That's all. Now we connect the network cable, put the boot from the network card in the BIOS and, while enjoying, we watch the process. Everything will happen in exactly the same way if you installed the system from a regular Windows 7 disk.
Enjoy!

Perhaps that's all for now and see you again.

One of the most important capabilities of computers is transmission of information from one car to another. Thanks to this, almost endless possibilities open up for users, which everyone has known for a long time - entertainment, work, communication, and so on.

Many are well aware of the existence of global and local networks. If we use the first one mainly for transmitting information over great distances, then the second one is used for transmitting data among a small number of users. In this article, we will take a closer look at the local network, as well as describe its creation and configuration in Windows 7.

General concepts

A local network is called a network into which united 2 or more computers, usually located within an apartment or, say, a building. Machines can be connected to each other by network cables or wireless communication channel (usually Wi-Fi).

In order for each individual computer to be able to "see" any other, also connected to the local network, two rules must be observed. At first, all cars must be n connected to one common communication device - router(you can do without it - more on that later), which receives information from one computer and transfers it to another. Secondly, each of the machines must have unique network address... Compliance with these conditions is enough to unite many PCs into a simple local network.

It is also worth knowing that there are two ways (or types) of combining computers - star and ring.

The first one involves using a router (router, switch, hub - whatever is more convenient for you) as a communication device (the principle of operation was described above).

Network type " ring"Does not require the use of such devices, but for its functioning, each computer must have at least two network cards... Roughly speaking, one of them will play the role of a receiver of information, the other - a sender.

This data will be enough for you to move on to the next part of the article.

Preparatory work

Before setting up a home or office local area network, you must first prepare all computers and the communication line for work. If you are using wired router as a communication device, you will need connect network cables from each computer to it... If you are creating a home network using wireless router Wi-Fi, then just connect every machine to it.

Building a home local network like " Ring"Will require cable routing according to the following scheme (for example, 4 computers):

Connect two cables to computer No. 1 into different sockets of network cards;
Pull one of the cables to PC No. 2, the second - to PC No. 3;
Connect the second cable in PC No. 2 to another free socket of the network card and drop it to computer No. 4;
Do the same for PC # 3 by connecting it to an empty board slot from PC # 4.

You can see that when connecting like " Ring»Each of the computers is connected by wires only with two adjacent ones. In our case, PC # 1 does not have a cable connection with PC # 4.

By the way, setting up a network like " Ring" may be done without wires, that is, via Wi-Fi. However, this will require that each computer can not only "be able" to connect to Wi-Fi, but also have the ability to create a virtual access point so that other machines can connect to it. But we will not consider this option.

Configuring Windows

After connecting computers to a network using wires or Wi-Fi, it is necessary to perform certain settings otherwise such a home network will simply not function properly. The whole point of customization is just to give each PC its own unique network address(connection settings will be considered on the example of Windows 7).

Start with any one computer:

Now, almost the same must be done for each computer connected to your home network. There is one difference - in the IP address field the value of the last number must be unique... Set, for example, on PC No. 2 the address is 192.168.0.2, on PC No. 3, specify 3 as the last digit, etc. to the very last computer on your home network.

By the way, if you want all computers on the network to be able to access the Internet, then additionally you need to fill in the fields “ Main gate" and " DNS server». The gateway and DNS at the same time can be, for example, the address of your Wi-Fi router in case the latter is configured to work in the global network. You can also specify in these fields the address of the computer connected to the Internet. In this case, the network settings of the latter should indicate that it allows other machines on the local network to use the Internet connection. But that is another topic.

Something else. When your computer connects to a local network, Windows 7 automatically asks where you would like it to be located. 3 options are offered - " home network», « Enterprise network" or " Public network". Some network settings of Windows depend on this choice - restrictions or permissions of actions of other machines on the network in relation to yours. We will not describe everything - just choose the first option " home network».

How to check the connection

You can check whether computers "see" each other on the network using standard Windows tools, namely, using the command line. To open it:

Do the same on all computers.

Related Videos

We remind you that attempts to repeat the actions of the author may lead to the loss of the warranty for the equipment and even to its failure. The material is provided for informational purposes only. If you are going to reproduce the steps described below, we strongly advise you to carefully read the article to the end at least once. 3DNews editors are not responsible for any possible consequences.

Earlier, we have already got acquainted with the process of massive deployment over the network of a ready-made hard disk image with pre-installed Windows 7 to many machines at once. For this we used a bunch of DRBL and Clonezilla. The key disadvantage of this approach is the lack of flexibility associated with the forced restriction on the use of the same type of configuration of client PCs. Building on the topic of network boot, we looked at creating a generic PXE resuscitator. In this case, at startup, the PC loads a live image of a particular OS from the server into RAM and works with it.

In a similar way, we can download the Windows preinstallation environment () over the network, mount the shared folder with the installation files and run the installer from there. Proprietary Microsoft RIS or WDS services work in a similar way, but they require Windows Server. In the case of a small number of client machines, you can get by with free solutions. We will consider an example of a "classical" implementation of such a scheme. One of the computers with Windows Vista / 7 will have a DHCP / TFTP / SMB server up.

The hardware requirements have already been discussed in previous materials. Nevertheless, we will briefly go over them once again. First, network boot must be enabled in the BIOS of all computers. Secondly, all machines must be temporarily connected to an isolated local area network, preferably a gigabit one. Naturally, their configuration must meet the requirements of 32-bit Windows 7, since we will consider installing this particular OS. But in general terms, the described method is also suitable for Windows Vista. It’s probably too early to talk about the G8.

Again we need the Windows Automated Installation Kit (WAIK). Download the ISO image, unpack or mount it and install this set of utilities. In the main menu, select Microsoft Windows AIK → Deployment Tools Command Prompt. A console will open in front of us, in which you need to enter the following command:

Copype.cmd x86 C: \ WinPE

This command copies to the directory C: \ WinPE files required to create an image with a preinstallation environment for 32-bit Windows 7. For a 64-bit version, you must specify the parameter amd64 instead of x86... Immediately create another folder C: \ TFTP \, which will be the root for the TFTP server, and in it make the directory Boot... The latter will store the boot files. To get these, you need to mount the base Windows PE wim image and copy them from there.

Imagex / mountrw winpe.wim 1 mount copy mount \ Windows \ Boot \ PXE \ *. * C: \ TFTP \ Boot

Command imagex just unpacks the files from the wim image into the mount subfolder. You can edit them or, for example, add your own, and then pack them back into a single archive. We will do this a little later, but for now, close and reopen the Deployment Tools Command Prompt, copy another important file and unmount the image.

Copy x86 \ boot \ boot.sdi C: \ TFTP \ Boot cd / d C: \ WinPE imagex / unmount mount

Copy the file winpe.wim to catalog C: \ TFTP \ Boot under the name boot.wim and let's start creating a Windows boot menu (BCD).

Copy winpe.wim C: \ TFTP \ Boot \ boot.wim cd / d C: \ TFTP \ Boot bcdedit -createstore BCD

In the simplest case, we just need to specify the parameters for the RAM disk.

Bcdedit -store BCD -create (ramdiskoptions) / d "Ramdisk options" bcdedit -store BCD -set (ramdiskoptions) ramdisksdidevice boot bcdedit -store BCD -set (ramdiskoptions) ramdisksdipath \ boot \ boot.sdi bcdedit -store "PE Boot Image" / application osloader

Notice the output of the last command you ran. It contains a GUID that needs to be copied and substituted for { guid) in the commands below.

Bcdedit -store BCD -set (guid) systemroot \ Windows bcdedit -store BCD -set (guid) detecthal Yes bcdedit -store BCD -set (guid) winpe Yes bcdedit -store BCD -set (guid) osdevice ramdisk = \ Boot \ boot .wim, (ramdiskoptions) bcdedit -store BCD -set (guid) device ramdisk = \ Boot \ boot.wim, (ramdiskoptions)

The first step is to try booting from a "clean" Windows PE image. However, some changes will need to be made to it. First, you may need drivers for a network card or hard disk controller. Secondly, it would be nice to make an automatic connection to a network folder and launch the installer. Open the WAIK console again and mount the boot image.

Cd / d C: \ WinPE imagex / mountrw winpe.wim 1 mount

To add drivers (in the form of * .inf and related files, of course), use the following command:

Dism / image: mount / add-driver / driver: Path to folder or inf file

You also need to edit a simple text file [ C: \WinPE \] mount \ windows \ system32 \startnet.cmd... This script will be executed at the start of the PE environment and will mount the network folder as a logical drive from which the Windows 7 installer will start.

Wpeinit net use z: \\ 192.168.0.51 \ Win7Install password / user: username z: \ setup.exe

192.168.0.51 is the IP address of the server from which the installation is performed. On it, you need to copy all the files from the Windows 7 installation image to a folder (in our example, this is Win7Install) and open access to it over the network. Instead of password and username the password and local username must be specified accordingly. You can even create a separate account for this case. Finally, don't forget to close the wim file with the changes applied and copy it to the TFTP server directory. The console can be closed.

Imagex / unmounts / commit mount copy winpe.wim C: \ TFTP \ Boot \ boot.wim

Earlier, we have already touched on the topic of the answer file to automate the installation process and the initial configuration of Windows 7. In this case, we also have every right to use its capabilities. It is better to use the Windows System Image Manager utility from the WAIK to prepare the file. After launching in the menu, select File → New answer file, then we will be prompted to select the installation image of the system. It is located in the sources directory, from where the OS will be installed (in our example Win7Install /sources) - select the file with the extension clg and your OS revision as a name (for example, install_Windows 7 PROFESSIONAL.clg).

The Windows Image panel contains a tree of components that you can customize. To do this, right-click on any of them and select Add Setting to Pass * from the pop-up menu - it will immediately appear in the Answer File panel, where you can edit various parameters. For example, add accounts, partition disks, install updates, and so on. We will not dwell on filling the answer file in detail - all the necessary information can be found on the Web or from the built-in help. The finished file must be saved in the same installation directory. sources under the name autounattend.xml.

There is very little left. DHCP and TFTP must be configured. Basically, you can use almost any software implementation of these servers. As an example, we will use the universal utility Serva32 / 64. After starting the program, click on the Settings button, go to the DHCP tab and check the DHCP server box. Just below, click on Bind DHCP to this address and in the drop-down list select the IP address of the network interface on which the server will run. Naturally, the address must be static and predefined.

In the IP Pool 1 st addr field, we indicate the starting IP address of the range of issued addresses, and in the Pool size - the number of DHCP clients. Do not forget to also register the Subnet mask. Finally, in the Boot File, specify the relative path to the PXE bootloader file. In our case, it can be pxeboot.com or pxeboot.n12... In the first case, to start the network boot, you will be prompted to press the F12 key, otherwise the startup from local media will continue. If F12 is missing, then you need to specify the second bootloader (you may have to rename it to pxeboot.com).

On the TFTP tab, the TFTP Server and Bind TFTP to this address checkboxes are turned on in the same way, the server root folder is indicated (we have this C: \TFTP) and the Option negotiation option is required, and PXE Compatibility is disabled. That's it, now click OK, thereby saving the settings, and restart the utility. Check that the firewall is not blocking the ports in use (UDP 67-69). You can try to boot over the network on one of the client machines. Use the logs generated by Serva to identify problems. If everything is in order, the Windows 7 installer will automatically start, further work with which is no different from the one that goes when booting from the installation USB / DVD / HDD.

That, in fact, is all. We've covered a fairly simple example of a Windows 7 network installation. How can you improve it? Well, firstly, you can add additional options to the Windows bootloader so that it boots from local media by default and not over the network. Secondly, the syslinux bootloader, which was mentioned last time, can be safely used with the Serva32 / 64 utility. Configuration file format ( pxelinux.cfg / default) the same. Third, it doesn't hurt to delve deeper into the capabilities of the answer file and the unattended installation of Windows. In general, there is a lot to dig. But we will leave this for independent study and in parting traditionally wish good luck in network experiments.

In this article, we want to highlight the process of initializing the installation of the Windows 7 operating system over a local network.

It is likely that you have repeatedly encountered a situation when you need to install an operating system on your computer, but the computer does not have a DVD drive, and there is no USB drive at hand. It is then that the thought comes to mind: it is not for nothing that in the "BIOS" there is the possibility of booting from a network card.

So, all we need for the installation procedure:

1. Computer with Windows 7 / Windows Vista / Server 2003 or 2008 already installed
2. Network cable (patch cord) - usually this little thing is simply forgotten
3. Windows® Automated Installation Kit (AIK) for Windows® 7
4. Emulator program for DHCP and TFTP servers, for example tftpd32
5. Distribution with Windows 7, any edition
6. A program that allows you to work with iso-disk images, for example Daemon Tools

Now let's get down to the process of preparing for the installation:

Step 1. You need to download the Windows® Automated Installation Kit (AIK) for Windows® 7 (OS authentication is not required), then mount its iso image to the virtual drive and start the installation process (StartCD.exe).

Step 2. In the main menu "Start" we find the Microsoft Windows AIK and run the "Command line of the deployment tools" - the console will open

Step 3. In the console of the deployment tools, enter the following commands (drive X is any drive on your computer):

1) copype.cmd x86 x: \ winpe 2) imagex / mountrw winpe.wim 1 mount

Now in the directory x: \ winpe \ mount the mounted winpe.wim image is located.

Step 4. Further, to get rid of the need to manually map a network drive and initialize the launch of the executable application, you need to correct the startnet.cmd batch file located in the directory x: \ winpe \ mount \ windows \ system32... The file structure should be like this:

Wpeinit net use y: \\ 192.168.1.1 \ seven / user: install install if exist y: \ sources \ setup.exe (y: cd \ sources setup.exe)

In this case, it is assumed that the IP address of the computer from which the files will be downloaded over the network has the value 192.168.1.1, if it differs from the example, then enter your specific address. Connection to the computer from the side of the second PC, on which the installation is performed, will be done as the install user with the install password, so you need to create such a user in advance, for example, using the command:

Net user install install / add / passwordchg: no

Step 5. Now you need to unmount the created image. Run the following command in the console:

Imagex.exe / unmount / commit mount

Step 6. Create a folder on the computer from which the distribution files will be downloaded over the network in the future, for example x: \ upload, in it we create another directory - boot (x: \ upload \ boot), it will contain the boot files.

Step 7. Copy to folder x: \ upload catalog sources from the existing Windows 7 distribution.

Step 8. In the console, we execute several commands, with the help of which we fill the boot directory and make it possible to download files over the network:

1) imagex.exe / mount x: \ winpe \ winpe.wim 1 x: \ winpe \ mount. 2) xcopy / ey x: \ winpe \ mount \ windows \ boot \ pxe x: \ upload 3) xcopy / iy x: \ winpe \ mount \ windows \ boot \ fonts x: \ upload \ boot \ fonts 4) copy / yx: \ winpe \ ISO \ boot \ boot.sdi x: \ upload \ boot 5) imagex.exe / unmount d: \ winpe \ mount

Step 8. Copy the newly created winpe.wim image to the folder x: \ upload \ boot, for example using the command:

Copy / y d: \ winpe \ winpe.wim d: \ seven \ boot

Step 9. Sharing a folder x: \ upload for ALL users

Step 10. Create a Boot Configuration Data store, for which we use a special createbcd.cmd script, which must be created in the directory x: \ winpe \... The content of this script differs depending on the language of the operating system being installed, in general it should be as follows:

FOR RUSSIAN DISTRIBUTION

Bcdedit -createstore% 1 \ BCD bcdedit -store% 1 \ BCD -create (ramdiskoptions) / d "Ramdisk options" bcdedit -store% 1 \ BCD -set (ramdiskoptions) ramdisksdidevice boot bcdedit -store% 1 \ BCD -set (ramdiskoptions ) ramdisksdipath \ boot \ boot.sdi for / F "tokens = 2" %% i in ("bcdedit -store% 1 \ BCD -create / d" MyWinPE Boot Image "/ application osloader") do set guid = %% i bcdedit -store% 1 \ BCD -set% guid% systemroot \ Windows bcdedit -store% 1 \ BCD -set% guid% detecthal Yes bcdedit -store% 1 \ BCD -set% guid% winpe Yes bcdedit -store% 1 \ BCD -set% guid% osdevice ramdisk = \ Boot \ winpe.wim, (ramdiskoptions) bcdedit -store% 1 \ BCD -set% guid% device ramdisk = \ Boot \ winpe.wim, (ramdiskoptions) bcdedit -store% 1 \ BCD -create (bootmgr) / d "Windows VISTA BootManager" bcdedit -store% 1 \ BCD -set (bootmgr) timeout 30 bcdedit -store% 1 \ BCD -set (bootmgr) displayorder% guid%

FOR ENGLISH DISTRIBUTION:

Bcdedit -createstore% 1 \ BCD bcdedit -store% 1 \ BCD -create (ramdiskoptions) / d "Ramdisk options" bcdedit -store% 1 \ BCD -set (ramdiskoptions) ramdisksdidevice boot bcdedit -store% 1 \ BCD -set (ramdiskoptions ) ramdisksdipath \ boot \ boot.sdi for / F "tokens = 3" %% i in ("bcdedit -store% 1 \ BCD -create / d" MyWinPE Boot Image "/ application osloader") do set guid = %% i bcdedit -store% 1 \ BCD -set% guid% systemroot \ Windows bcdedit -store% 1 \ BCD -set% guid% detecthal Yes bcdedit -store% 1 \ BCD -set% guid% winpe Yes bcdedit -store% 1 \ BCD -set% guid% osdevice ramdisk = \ Boot \ winpe.wim, (ramdiskoptions) bcdedit -store% 1 \ BCD -set% guid% device ramdisk = \ Boot \ winpe.wim, (ramdiskoptions) bcdedit -store% 1 \ BCD -create (bootmgr) / d "Windows VISTA BootManager" bcdedit -store% 1 \ BCD -set (bootmgr) timeout 30 bcdedit -store% 1 \ BCD -set (bootmgr) displayorder% guid%

Step 11. You need to run the following command:

Createbcd.cmd x: \ upload \ boot

Step 12. We configure the tftpd32 utility exactly as shown in the figures:

The other day I needed to install Windows 7 on a netbook. Neither a usb drive nor a decent volume flash drive was at hand - so I decided to do the installation over the network. Googling in search of a ready-made solution and never finding it, I decided to try to do it in the same way as Windows Vista, all the same, the systems are very similar.
So what we need:

1. Distribution with Windows 7 of the edition you need
2. Windows® Automated Installation Kit (AIK) for Windows® 7
3. DHCP and TFTP servers. Using tftpd32

4. Computer with installed:

Windows Server 2003 with Service Pack 2
Windows Vista Service Pack 1 (SP1)
Windows Server 2008 family
Windows 7 family
Windows Server 2008 R2 family
With a program like Daemon Tools Lite

5. Straight arms and 20 minutes of time. Go!!!

First, install " Windows® Automated Installation Kit (AIK) for Windows® 7", for this you will have to mount the installation image into a virtual drive (DaemonTools, Alcohol, UltraIso, Nero ...) or unpack it into a separate folder and run StartCD.exe from there
In the disc autorun menu, select Installing Windows AIK- Next ... - Next-Done.

Now in the start menu we are looking for Microsoft Windows AIK and run from there Deployment Tools Command Line... Now the fun begins :)

Create a Windows PE image

In the open console, enter the commands
copype.cmd x86 d: \ winpe
imagex / mountrw winpe.wim 1 mount.
Now in the d: \ winpe \ mount directory we have a mounted winpe.wim image.

As the current Windows PE image is booted, a command prompt appears on the screen. In order not to map a network drive and run the setup program manually, you must in the directory d: \ winpe \ mount \ windows \ system32 edit the startnet.cmd file to look like this.

wpeinit net use y: \\ 192.168.1.1 \ seven / user: install install if exist y: \ sources \ setup.exe (y: cd \ sources setup.exe)

Please note that the disk is connected using the install user rights with the password of the same name. Therefore, it is important to create an install user on the machine that will act as the server. For example, you can do this using the command:
net user install install / add / passwordchg: no

If you have an exotic network card, read the SUPPLEMENT at the end of the article.

After all the work with the image is finished, you need to unmount it. This can be done using the command:
imagex.exe / unmount / commit mount
The image is now ready.

Create directories for network booting

Create a root directory for download, for example D: \ Seven \... In it we create a directory boot- in which the boot files will be stored. Now copy the directory sources from the Windows 7 DVD to the folder Seven. Also in the directory sources you can throw the file autounattend.xmlwith settings for automatic installation, but without it, it will work.

Now let's fill in the directory boot.
Mount the winpe.wim image again in order to copy the files necessary for booting over the network. This can be done using the command
imagex / mount d: \ winpe \ winpe.wim 1 d: \ winpe \ mount.
Using commands
xcopy / ey d: \ winpe \ mount \ windows \ boot \ pxe d: \ seven
xcopy / iy d: \ winpe \ mount \ windows \ boot \ fonts d: \ seven \ boot \ fonts
copy / y d: \ winpe \ ISO \ boot \ boot.sdi d: \ seven \ boot
copy the necessary files to the d: \ seven directory to boot over the network.
After all the work is finished, you need to unmount the used image with the command:
imagex.exe / unmount d: \ winpe \ mount
The used WinPE image must also be copied to the directory d: \ seven \ boot with the command:
copy / y d: \ winpe \ winpe.wim d: \ seven \ boot
You also need to make general access (share) to the D: \ Seven folder for all users or specifically for the install user.

Now let's create a file BCD- boot configuration data (storage of boot parameters)
For this we need a script d: \ winpe \ createbcd.cmdwith the following content:

FOR RUSSIAN DISTRIBUTION

bcdedit -createstore% 1 \ BCD
bcdedit -store% 1 \ BCD -create (ramdiskoptions) / d "Ramdisk options"
bcdedit -store% 1 \ BCD -set (ramdiskoptions) ramdisksdidevice boot
bcdedit -store% 1 \ BCD -set (ramdiskoptions) ramdisksdipath \ boot \ boot.sdi
for / F "tokens = 2" %% i in ("bcdedit -store% 1 \ BCD -create / d" MyWinPE Boot Image "/ application osloader") do set guid = %% i
bcdedit -store% 1 \ BCD -set% guid% systemroot \ Windows
bcdedit -store% 1 \ BCD -set% guid% detecthal Yes
bcdedit -store% 1 \ BCD -set% guid% winpe Yes
bcdedit -store% 1 \ BCD -set% guid% osdevice ramdisk = \ Boot \ winpe.wim, (ramdiskoptions)
bcdedit -store% 1 \ BCD -set% guid% device ramdisk = \ Boot \ winpe.wim, (ramdiskoptions)
bcdedit -store% 1 \ BCD -create (bootmgr) / d "Windows VISTA BootManager"
bcdedit -store% 1 \ BCD -set (bootmgr) timeout 30
bcdedit -store% 1 \ BCD -set (bootmgr) displayorder% guid%

FOR ENGLISH DISTRIBUTION

bcdedit -createstore% 1 \ BCD bcdedit -store% 1 \ BCD -create (ramdiskoptions) / d "Ramdisk options" bcdedit -store% 1 \ BCD -set (ramdiskoptions) ramdisksdidevice boot bcdedit -store% 1 \ BCD -set (ramdiskoptions ) ramdisksdipath \ boot \ boot.sdi for / F "tokens = 3" %% i in ("bcdedit -store% 1 \ BCD -create / d" MyWinPE Boot Image "/ application osloader") do set guid = %% i bcdedit -store% 1 \ BCD -set% guid% systemroot \ Windows bcdedit -store% 1 \ BCD -set% guid% detecthal Yes bcdedit -store% 1 \ BCD -set% guid% winpe Yes bcdedit -store% 1 \ BCD -set% guid% osdevice ramdisk = \ Boot \ winpe.wim, (ramdiskoptions) bcdedit -store% 1 \ BCD -set% guid% device ramdisk = \ Boot \ winpe.wim, (ramdiskoptions) bcdedit -store% 1 \ BCD -create (bootmgr) / d "Windows VISTA BootManager" bcdedit -store% 1 \ BCD -set (bootmgr) timeout 30 bcdedit -store% 1 \ BCD -set (bootmgr) displayorder% guid%

Now in our console we execute the command:
createbcd.cmd d: \ seven \ boot

Configuring the TFTPD32 program

Launch tftpd32.exe, go to the DHCP tab and set everything as in the screenshot

Now click Settings, set it as in the screenshot, restart the server.

ALL IS READY!

Now you need to connect the patient to this server over the network and enable boot from the network card in the BIOS. After that, an IP address will be obtained via DHCP and pxeboot.n12 will be executed - which will launch WinPE from the winpe.wim file. Immediately after loading WinPE, the Seven directory will be automatically mounted and the installation will start from it. Further, the installation proceeds in the same way as from the DVD.

ADDITION
If you have an exotic network card whose drivers are not included in the Windows Seven distribution, you can add them yourself at the stage of creating a WinPE image. To do this, take the * .cat, * .inf, * .sys files from the driver and copy them to the d: \ landrv directory.
Now you can start installing these drivers into the mounted image in the mount directory. This can be done using the command:
peimg.exe / inf = d: \ landrv \ (DRIVERNAME) mount \ windows
Where instead of (DRIVERNAME) the name of your * .inf file

Most of the information I got from the site http://unattendedxp.com. Checked and tested personally.