Preparation of the image of Windows 7 followed by activation. Installing applications and system setup. We make a Windows installation template in audit mode

Friends, as you think, can I make from a flash drive to 4 GB multi-loading, placing the installation image of Windows and some live disks on it? The answer is yes. But, naturally, such "yes" is due to: if only this will be the installation image of Windows 7, and the weight of the Live disks in total will not exceed 1.2-1.3 GB. The actual size of the flash drive on 4 GB is usually about 3.7 GB. The ISO image of a pure Windows 7 distribution is placed on such a carrier, which weighs somewhere 3 GB. And there will still be 600-700 MB for a small Live disk of any program such as disc manager, backer or antivirus. However, if the installation image of the "seven" is maximized to a little less than 2.5 GB, save space on the carrier. And under the Live disk we will have a little more space, approximately 1.2-1.3 GB. And this volume can already be chosen in the network of some Live disk with an extent alarm softe. And, by the way, it would be nice, if all its releases were present in the installation image of the system - Home, Professional, Ultimate. How to create a maximum compressed installation image with all Windows 7 releases?

WIM-image of Windows 7 is an Install.wim file included in the installation ISO image, in fact, the distribution base is stored in it to install files. The weight of this file can be reduced by 30-40%. To do this, it will be necessary to compress it using the DISM system image tools present on board Windows 8.1 and 10.

• Important: The DISM version is part of Windows 7, unfortunately, does not know how to perform the operations that we will be carried out below. It is necessary to work in the versions of the system 8.1 and 10.

A compressed WIM image can then be packaged in an ISO image to write on a flash drive. But before you download the original distribution "Seven".

Downloading the source distribution of Windows 7

You can download the clean installation ISO image of the "seven" by at least two ways:

Through. windows programs ISO downloader;

On Tech Bench website.

I choose the last one. We go to the TECH BENCH website at:

https://tb.rg-adguard.net/public.php.

We choose the distribution, in our case it is a 64-bit Windows 7 Ultimate (maximum). Click "Download".

WIM image compression

The downloaded ISO weighs 3 GB.

Let's squeeze it. Mount the image into the system.

Open the command line on behalf of the administrator. We enter the command:

DISM / Get-Wiminfo / WiMFile: M: \\ Sources \\ Install.wim

where M. - the letter of the disk, under which you will have a padded ISO with a "seven",

this command we learn that inside the archiveinstall.wim with windows 7 are Four indexes four version of the OS.

We still enter the team:

DISM / EXPORT-image / SourceImageFile :M :\\Sources\\Install.Wim / SourceIndex: 1 /destinationImageFile ::D:\\InStall.Wim / Compress: Recovery

In the team change:

m - on the letter of the disk, under which you will have a mounted ISO with a "seven",

d - on the letter of the disk (or path), where you can temporarily place a compressed WIM image, while we work with it,

we create an Install.wim archive file with this command at the root (D :) and copy to it Windows 7 home basic, I also change the FAST compression on Recovery (in fact, our Install.wim archive becomes an install.es archive, details).

Upon completion of compression at the output, we get a WIM-image weighing of 1.67 GB.

Adding all issues of Windows 7

Now the WIM image needs to add other releases "seven". To do this, in the command line, I also enter the type commands:

DISM / EXPORT-Image /SourceSeMStall.wim / SourceIndex: 2 /destinationImagefile: 2:s: Recovery: Wim / Compress: Recovery

DISM / EXPORT-image / SourceSempFile.wim / SourceIndex: 3 /DestinationImageFile: 3 / pieceMAGEFILE: 3 /Install.Wim / Compress: Recovery

DISM / EXPORT-image / SourceSempFile.wim / SourceIndex: 4 /destinationImageFile: 4 /dstinationImagefile:D:\\Install.wim / Compress: Recovery

As in the previous paragraph of the article, in the team change:

m. - on the letter of the disk, under which you will have a mounted ISO with a "seven",

d. - on the letter of the disk (or path) that you specified to create a compressed WIM-embodiment.

The install.wim file has increased, and now it weighs 1.75 GB.

Now, friends, WIM-image with all the releases of Windows 7 must be packaged in an ISO image.

Packaging in ISO.

To pack the WIM image of Windows 7, we need:

Installation ISO-image 10;

Ultraiso program.

Distribution "Dozens" does not have to be relevant, from there we need only an external shell of the installation process. So if you had an ISO somewhere with the "dozen" not the first freshness, it is quite suitable for further goals. If there is nothing on the computer disk, Windows 10 download either the same ways that are described above (in the first paragraph of the article), or with.

Run Ultraiso. Click the "File - Open" menu, open the ISO file with Windows 10.

At the top of the left reveal the "Sources" folder. Switch to the right panel at the top and build files by size. Thus, the install.esd file you need will be displayed on top of the list, because this is the most weighty file. Click it, press the right mouse button, select the "Delete" item.

• Note: Friends, do not be afraid to delete Install.esd if you work with the desired distribution kit of Windows 10. You can not make it copies. All this is still just a new ISO project with outlined for operations. As a result, the original distribution of "dozens" will remain whole and unharmed.

Now in the window ultraiso programs Switch to the bottom panels. In the one that on the left, choose the path of storage of a compressed WIM image, in our case this is the root of the disk D. And in the one that the WIM image itself is chosen, i.e. File install.wim and drag it up, on the left panel, in the "Sources" folder.

So we replaced the source file Install.esd with contents Windows 10 on a compressed install.wim with the contents of Windows 7.

Now let's turn the ISO image. Click menu "File-Save As", select the save path, call a new file. We save.

16.06.2010 20:41

Files installed windows 7 may be damaged or deleted by mistake or as a result of computer infection with viruses, trojans and other dangerous programs. Instead of reinstalling Windows 7 due to one or two damaged files, you can extract the desired files from the installation DVD Windows. 7.

Everything windows files 7 Compressed and packaged to file image install.wimlocated in the folder sources. installation disk Windows 7. There are two ways to open the WIM file and remove the necessary data from it:

Connecting an image to means DISM

1. Insert the Windows 7 installation disk into the DVD drive, open it and copy the file. install.wim From the folder sources. to Disk D.

2. Create a folder on Disk D and name it, for example, wseven.. Install.wim image will be connected to this folder. Please note that as a folder to connect an INSTALL.WIM image. Disc roin cannot be used..

3. Open Start\u003e All Programs\u003e Standard .

4. Run:

dISM / MOUNT-WIM /WIMFile:D:\\ Windows 7 Ultimate / Name: "Windows 7 Ultimate" / Mountdir: D: \\ Wseven

Explanations:

• dISM - Built-in command line utility built in Windows 7, allowing you to connect WIM images and manage them.
• The / Mount-WIM parameter connects the WIM file.
• The / WiMFile parameter allows you to specify the location and name of the WIM file to be connected.
• The / Name parameter allows you to specify the name of the release of Windows 7, which will be mounted.
• Parameter / Mountdir: Indicates the folder to which the WIM image will be mounted.

6. Wait until the image connects. It may take a few minutes.

7. Open the D: \\ WSEven folder, find the desired file in it and copy it to any place on the hard disk (for example, replace the damaged file of Windows 7).

Disable the image in DISM

After copying the necessary files The image can be turned off.

1. Close all folders and files.

2. Open Start\u003e All Programs\u003e StandardClick right-click Mice on the command line icon and select Run on the name of the administrator.

3. Run the command:

dISM / UNMOUNT-WIM / MOUNTDIR: D: \\ WSEVEN / DISCARD

Explanations:

• The / unmount-WIM parameter disables the image.
• Parameter / Mountdir: Specifies the folder to which the image that needs to be turned off is mounted.
• The / Discard parameter cancels all changes made to the image.

4. Wait for the image to disable.

5. Delete the folder wseven. and file. install.wim from Disk D.

Opening the WIM file using the 7-ZIP archiver

1. Download and install a free 7-zip archiver.

2. Insert the Windows 7 installation disk into the DVD drive, open the folder Sources. and find the file in it. install.wim.

3. Right-click on the file install.wim And in the appearance context menu Choose To open with.

4. In the window that opens, select 7-zip. File Manager. and press OK..

5. In the archiver window, it can be displayed from one to five folders, depending on the release of Windows 7. In the installation images of 32-bit Windows 7 there are all releases, except Enterprise, so folders will be five:

• the "1" folder contains all folders and Windows 7 Starter files (initial);
• in the "2" folder - all folders and Windows 7 files Home Basic (home basic);
• in the folder "3" - Windows 7 Home Premium (home extended);
• in the folder "4" - Windows 7 Professional (Professional);
• in the folder "5" - Windows 7 Ultimate (maximum).

In the installation images of 64-bit windows 7, the "initial" release is missing, so the folders will only be four:

• the "1" folder contains all folders and Windows 7 HOME BASIC files (home base);
• in the folder "2" - Home Premium (home extended);
• in the folder "3" - Professional (professional);
• in the folder "4" - Ultimate (maximum).

In the installation images of Windows 7 Enterprise (corporate) there is only one folder - with the "corporate" itself, other issues in the distribution are not included.

Creating a fully configured image operating system from installed applications It is often necessary in a corporate environment, and home users will not refuse the installation disk in which the favorite set of programs and tweaks is introduced. In the modern Windows OS, create such an image is much easier than in Windows XP, while you can do the package tools. automatic installation.

This article describes how to prepare a fully configured system image and deploy it, as well as address the backup of the operating system to the WIM image.

On this page

You need

• Deployment Tools From Windows Assessment and Deployment Kit (ADK)

Of course, you will need a computer to install and set the OS, as well as a place to save the system image. A virtual machine (for example, Hyper-V from Windows or VirtualBox) can be installed as a computer for installation (for example, Hyper-V from Windows or VirtualBox). You can save the configured image on the unwatching section of this computer.

For example, during the installation of the system, you can create two partitions - to one install the OS, and on the second subsequently save the image. Also, in the virtual machine you can always connect another virtual disk. Finally, the configured image can be saved on a network resource or USB disk. As you can see, there are many options - there is from what to choose.

Advantages and disadvantages of using a configured image

In my opinion, the advantages of a fully configured image look preferably shortcomings.

Benefits

• Fast installation of a system with a set of applications, because it does not spend time on their installation. However, compared with the standard disparation of the configured image takes a little longer.
• It is possible to further configure the operating system using the response file used in combination with the configured manner.
• The ability to deploy an image using the utility Imagex. Standard image can only be used in conjunction with the installation program, since not all parameters are configured (for example, linguistic).

disadvantages

• The size of the image is increasing. The final size depends on the number and scope of the applications installed. If further installation from a DVD disk is planned, it is necessary to take into account the limit of 32-bit versions to the size of the WIM file in 4 GB (2 ^ 32 bytes).
• Can enduring versions of applications included in the image. To maintain topical versions of applications, you will have to collect the image again. Regularly updated applications, most likely, does not make sense to include in the image. They can be installed separately by automating this process.

Stages of creating a configured image

Creating your own WIM image can be divided into the following steps:

1. Installing applications and system setup
2. Preparation of the system with the help of the utility sysprep.
3. Loading in Windows PE and save the image using the utility Imagex

Then the resulting image can be enabled in the installation disk, install from a network resource or deployed with Imagex.

Note on setting up custom parameters

In addition to installing applications, you can configure custom parameters in the audit mode. To apply settings to the image there are two ways.

You can:

• Configure only system parameters, and custom imported using reg files to a configured WIM image (or to the original image before the installation described here).
• Configure both user and system parameters, and then secure the response file to copy the built-in account profile Administrator in profile standard user.

Import registry parameters

The principle itself is considered in detail the use of the registry tweaks. I believe that you have read it and accounted for a complete picture of the import of custom and system parameters.

Copy profile using the response file

To copy a profile of a configured account to a standard user profile, you can use the answer file containing the parameter

Microsoft-Windows-Shell-Setup | CopyProfile.

If this parameter is set to value true.Profile copying is performed.

Use this feature you need when installing a configured imageBy turning on the answer file this parameter. In this case, profile copying will occur on the passage 4 Specialize.

Example of a universal response file for 32-bit and 64-bit OS

true. true.

Why is it recommended to copy a profile when installing instead of pointing to the response file SYSPREP using the image to summarize the image?

Copying the profile in any case occurs during installation at the Specialize stage. If you use the / Unattend parameter SYSPREP, the answer file is cached and then activated during installation. At the time of writing the first version of the article, it did not work, despite the documentation.

If you use MDT or SCCM, described in the article Method is required for reasons set out in KB973289:

Now everything is in order.

Start the installation of the operating system from the installation disk and input to the audit mode

The first step of preparing the configured image is the launch of the OS from the installation disk. Installation can be done manually, or automate this process using the responses file.

Manual installation

Manual installation does not charge any tricks. If you are planning to save the configured image on a non-system disc section, use the Windows installation program to create partitions.

Council. When installing the system on a virtual machine, you can connect the second virtual disk and subsequently use it to save the image. This will simplify copying the image to your working environmentSince VHD (X) can always be connected on a physical machine.

Continue the installation up to the Oobe step. It is easy to find out on the suggestion to select the account name and drawing for it.

At this stage, not Choosing an account name, click Ctrl + SHIFT + F3. This key combination will transfer the system to an audit mode with the integrated account rights. Administrator.

Automatic installation

Using the responses file, you can automate all Windows installation steps including partition management. hard disk, Log in to Audit mode and even installing applications in it, as described in the article. You can follow the instructions in it down to the section "Transfer of the system to Oobe mode" (the article discusses the full installation automation).

Installing updates, applications and system settings

By logging into an audit mode, you can start installing, updates, applications and setting the parameters of the operating system. Do not close the utility window sysprep. - It will be needed at the end of the setting step.

If you need to restart the system to install or update, you can do it. After rebooting, the system will return to the audit mode. As mentioned above, the process of installing applications can be automated using the response file. You can configure any system and user parameters in graphic windows interface. You can also import the registry settings from pre-prepared REG files.

In Windows 8 and newer, do not update the applications from windows StoreSince this will lead to problems when generalizing the image. Delete modern applications are also needed by science. See Warning in the TechNet and KB2769827 library.

After completing the installation of applications and setting up the system, you must prepare it for further use.

Preparation of the system using the SYSPREP utility

At the end of the installation of applications and system settings, preparation is prepared using the utility. sysprep.. Depending on what kind of installation method you have chosen, the actions will differ slightly.

Manual installation

For manual installation Utility systems sysprep. It starts when entering the audit mode. To prepare the system to further use (in this case, to create a configured image), you must specify the parameters utility, as shown in the figure below.

The specified parameters are made (in parentheses equivalent parameters of the SYSPREP command line):

1. System Preparation (/ Generalize) - Deleting unique system parameters, cleaning event logs, resetting security identifier (SID), etc. This parameter is absolutely necessary to create a configured image.
2. Translation of the system to Oobe mode (/ Oobe) - This mode will be activated by the next system start.
3. Turning off the system (/ shutdown).

Example of a universal response file to save 32-64-bit drivers

true. true.

Automatic installation

If you automate the entry into the audit mode and installing applications using the responses file, as described in the article Setting applications in audit mode, you need to add the following synchronous command with the highest sequence number. This command can also be used when manually installed, pre-closing the Utility window sysperp..

% Systemroot% \\ System32 \\ sysprep \\ sysprep.exe / Generalize / Oobe / Shutdown / Quiet

The first three command line parameters are indicated in the same order as the parameters described above the utility graphical interface parameters. Parameter / Quiet. - Provides work in a quiet mode and is necessary for automation.

After sysprep. Complete work, the system will be turned off. Now it is fully configured, and you can create its image using the utility. Imagex.

Loading in Windows PE and save the image using the ImageX utility

Note. Image size install.wimincluded in the installation disk of the 32-bit operating system should not exceed 4 GB (2 ^ 32 bytes). Otherwise, the installation will be completed with an error. This restriction does not apply to the deployment of the image using the utility Imagex.

If a setup files Windows is posted on a network resource, you can copy the configured image and the answer file there, and then downloading it in Windows PE and connecting to the network resource, start the installation from the command line.

NET USE: \\\\ Network_Share \\ Distrib Y: \\ setup.exe /unattend:unattend.xml

Deploy a configured image using the IMAGEX utility

Using Windows PE and utility Imagex, You can deploy a configured image on your computer.

The sequence of actions is this:

Tom formatting using utility Diskpart.

Apply a configured image to the utility Imagex

Note. Deploy an image with Imagex It is possible only on that having the same letter of the disk, which was saved in the image. In addition, with Imagex You can not deploy the standard (source) image Install.wim.

Let's consider an example of deploying a configured image. It is assumed that hDD Computer is not formatted. Uploaded to Windows PE, you need using the utility Diskpart. Create a partition on your hard disk and format it. I will demonstrate the creation of one partition on the disk.

Diskpart Select Disk 0 Create Partition Primary Select Partition 1 Active Format FS \u003d NTFS Label \u003d "System" Quick Assign Letter \u003d C EXIT

Additional information about the commands of the utility Diskpart. You can get by running it with the key /? or from the article Description of the DiskPart program with the command line interface. If desired, the process of creating a section can be automated.

It remains only to apply the image.

ImageX / Apply E: \\ Custom.wim 1 C:

In this team:

• / Apply - Application of the image
• E: \\ Custom.wim - The path to the image. When placed on the network disk, you must first connect it to the command net Use. E: \\\\ Network_Share \\ Images.
• 1 - The image index saved in the WIM file.
• c: - The letter of the volume to which the image is applied.

Applying an image, you can make sure (team dir.) that on the section C. There are files unpacked from the image. Now this section contains an operating system in the state in which it was at the time of creating an image. If the image has been saved after executing the settings in the audit mode, the system will enter the OBE mode, giving the user the ability to perform the user initial setting parameters.

If you preparing an image of a configured account profile, all new accounts Will have exactly the same parameters.

Deploy a configured image with WDS

As in the case of a standard manner, Windows Deployment Services (WDS) can be used to deploy a configured image. Detailed story About this method goes beyond the articles, so I will limit the reference to the WDS Guide, placed on Microsoft TechNet.

Backup operating system in WIM-image

The article focuses on installing applications and setting up the system in audit mode and preserve the image at this installation stage. The advantage of this approach is that the saved image is neutral - it does not contain any accounts (except for embedded), personal files and confidential data.

You may be interested in the question whether it is possible to save the image of the system at the end full installation, i.e. after the Oobe stage, the first login and subsequent setting. Such a question is relevant if you want to install the system, to work in it for a while - install applications, configure various parameters, etc., and then create an image.

The reference to the fact that ImageX does not know how to use hard links (I checked - knows how).

So, after applying the image:

• Extended file attributes are lost. These are NTFS attributes that are needed only for reverse compatibility with applications ... OS / 2.
• Sparse files are captured, but after use is no longer any.
• Symbolic references and consensions are automatically updated. In some scenarios (for example, SIS), this leads to the fact that the links do not do there.

In my opinion, in typical scenarios of using the client OS at home, these restrictions can be neglected. But the restoration of such an image on another PC (even with the same hardware configuration) can lead to serious equipment conflicts.

At the same time there are several moments that I would like to draw your attention.

• The installed programs and personal files can occupy a lot of disk space, which will affect the size of the backup WIM image. To store the image you may need a two-layer DVD or a large-capacity USB disk.
• You can reduce the size of the WIM image, eliminating files and folders from its composition when capturing the volume utility Imagex. To do this, use the file Wimscript.ini.which briefly discusses the article on the creation boot disk Windows PE. His detailed description there is a reference file "Guide windows User. PE "included in the ADK.

Restoration

Recovery from the backup WIM image is executed as described in the section Articles section. However, the utility command sequence Diskpart. need to adjust.

For example, if several partitions are installed on the disk, and the system is set to the first, the sequence of commands to prepare this section to restore will be like this:

Diskpart Select Disk 0 SELECT Partition 1 Active Format FS \u003d NTFS Label \u003d "System" Quick Assign Letter \u003d C EXIT

You can enable a configured WIM image into the boot disk with Windows PE, thereby creating a universal system for restoring the system to restore the system and standby image.

Conclusion

Creating and deploying a fully configured Windows system image with the means included in ADK is a fairly simple task. Such an image can be made neutral (i.e. not containing personal files and personal data) by installing applications and setting parameters in audit mode.

This approach allows you to further configure the image during installation using the response file, and also saves the ability to set personal parameters for the end user at the Oobe stage when you first start the system. In addition, you can use WIM-image technology to create backup operating system.

Hello everybody! Today I decided to affect the restoration of the installed OS. We will discuss, of course, about Windows.

I think many users faced the problem when Windows suddenly stops running.

The reasons for such trouble can be the most different - penetration into the system, spoiled blocks of hard disk, iron problems, shoals of someone from users ...

In many cases, the image of an existing operating system can help out. About how to create an image of the system I will tell.

Regular tools of Windows

When using the method provided by the Operations itself, you will not need any additional program. The only thing you need is administrator rights, more external hard drives are desirable.

Consider all the details on the example of "seven", while still the most popular system from the Windows family.

So. First you need to prepare a computer to the upcoming operation. In order to reduce the size of the image that you will use to restore, take all unnecessary programs and files from the system partition (usually the C drive C).

But be careful, remove only what you know for sure that it is superfluous, do not touch the windows of the Windows itself!

And, by the way, be sure to think what programs should be installed so that they are already in the image and cut in the future (after restorative procedures) additional action. Then the computer is better to restart.

On the left in the window, click "Creating a System Image". For some time you have to wait - the system will evaluate system section and scan local disks. The following window will prompt you to select the device to save the archive.

Choosing a suitable media

Other options are possible, but I do not advise you to save on a disk, which is a systemic, moreover, Windows in some cases may not provide such an opportunity at all.

The volume of the DVD disk for such needs is small, but to divide full image On a dozen pieces, each of which is recorded on a separate DVD, is clearly not the best solution.

In general, you choose what is more suitable for your case, connect all the necessary devices and click "Next".

In the next window, check whether everything is correctly assigned - disks for archiving and the location of the backup (the window is called: "confirmation of archiving parameters") - and click the "Archive" button.

Prior to the completion of the process, you must leave the computer alone - do not turn off, do not run any programs, do not interrupt the archiving process.

In addition to the saved image, you can make a boot disk by selecting the Create System Recovery CD. It may be needed if you do not have an installation disk containing the Windows distribution and all the necessary utilities. To contact the same - to the "control panel", then in "Archiving and Restoring".

How it works

Now consider how to apply an archive file image. In the case of serious failures, the boot disk is used - the one with which Windows was installed, or created as I described above.

It you just need to insert into the DVD drive and run a computer from it. The menu will appear on the screen - select "Restore from the previously created image."

Then you will need to specify the placement of the image file - the external hard drive with the file must already be connected. Specify the file and the recovery operation will begin. The result will be working, goodwill in the form, in which it was at the time of creating the image.

With respect! Abdullin Ruslan

Not so long ago faced a situation, which in principle does not cause special problems with system administrators. There was a need to update the OS on numerous computers of the organization, which in turn still caused a number of some problems whose decisions had to be collected in parts, as well as to finish most of all the process itself about what I actually want to tell you.

These problems were restrictions in the presence of one DVD-ROM drive, one day of free time, as well as about twenty computers to which it was necessary to install Windows 7 with the whole set. necessary drivers, programs etc.
When searching for information in Google on this issue there was no nothing that would work without jambs or worked at all. But let's start in order.

Preparation of an operating system

For simplicity of preparation of the combat OS, Oracle VirtualBox was taken latest version, as well as Windows 7 x64 professional. The first thing to do is to install and configure Windows 7 on a virtual machine. To do this, in the process of adding VM, we create two virtual hard disk. One for installation and configuration on it Windows 7, the second for later saving the image of a configured system. It is also necessary to install the additions of the guest OS VirtualBox - Virtual Machine Additions and create a shared folder to further copy the created image to the physical machine.
After installing on the VM of all the filling, go to the system preparation step using the utility sysprep.The root of our VM system:% windir% \\ System32 \\ sysprep \\ sysprep.exe
To prepare the system to create a configured image, you must specify the Utility settings:

1. Switching to the System Greeting Window (Oobe) - this mode will be activated when the system starts next. Runs a computer in a welcome screen mode.
2. Install the "Preparation for use" checkbox - prepares installing Windows Before creating an image. The security identifier (SID) is reset, the system recovery points are reset, event logs are deleted.
3. The completion parameters "Shutdown" - at the end of the utility utility, the system will complete its work.

Do not run the OS until the system is saved, since a specialized setting step starts to work during the next start of the computer. A new security identifier (SID) is created and the Windows Activation Clock is reset.

The utility removes including installed drivers. To save them, you need to perform sysprep. From the command line with the: / Unattend: Path to the response file in the answer file, you must specify the PersistalDeviceInstalls parameter (starting with Windows 8 there is also a DonotCleanUnonPresentDevices parameter):
true. After cleaning, the system will automatically turn off. Getting Started for the next stage.

Installing and configuring Windows AIK + PE

Download and install the Windows Automatic Setup (AIK) package for Windows 7. After starting the setup.exe, select the "Install Windows AIK" item. There should be no special problems when installing.

Creating and configuring a Windows PE image

Windows PE. - Presets used to prepare for OC installation. FROM using windows PE we will capture system Tom in WIM-image with utility imagex And save them to another hard disk section.
In this case, the creation of a disk with 64-bit windows version PE. If you create a 32-bit version of Windows PE, you will need to replace the architecture in all commands (AMD64 on x86).

In the Start menu, run all programs\u003e Microsoft Windows. AIK\u003e Deployment Command Line (Deployment Tools Command Prompt) - All subsequent commands will be entered into this command line window. Run is required on behalf of the administrator.
Copy Windows PE Image Files
Copype.cmd AMD64 D: \\ WinPE_Image
To change the copied image of Windows PE it must be connected by the command
DISM / MOUNT-WIM /WIMFILE :D:'WIM / INDEX: 1 / Mountdir: D: \\ WinPE_IMAGE \\ MOUNT
Now connecting the image, we can install packages and add your own files.
Add to our image utility imagex.
xcopy "% ProgramFiles% \\ Windows Aik \\ Tools \\ amd64 \\ imagex.exe" D: \\ WINPE_IMAGE \\ ISO \\
Also, if desired, you can immediately prepare a list of exceptions - files and folders that will not be included in the stored image. Create in anyone text editor The WimScript.ini file and specify files and folders in it that you want to exclude from the image. The wimscript.ini file is located in the same folder with IMEGEX.
Default imagex uses the following exceptions:
\\ $ ntfs.log \\ hiberfil.sys \\ pagefile.sys "\\ System Volume Information" \\ Recycler \\ Windows \\ CSC * .mp3 * .zip * .cab \\ Windows \\ inf \\ *. PNF
Now you need to save the image of the command:
DISM / UNMOUNT-WIM / MOUNTDIR: D: \\ WINPE_IMAGE \\ MOUNT / COMMIT
All preparatory work was carried out with the WinPE.wim file, and for the boot windows disk PE uses the boot.wim file located in the WINPE_X86 \\ ISO \\ Sources folder. Therefore, it is necessary to replace the boot.wim file WinPE.WIM, while performing renaming.
xcopy / y d: \\ winpe_image \\ winpe.wim d: \\ WinPE_Image \\ ISO \\ Sources \\ Boot.wim
To create an image, execute the command:
OSCDIMG -N -BD: \\ WinPE_IMAGE \\ ETFSBOOT.com D: \\ WinPE_Image \\ ISO D: \\ WinPE_Image \\ WinPE_Image.iso

Creating an image of Windows 7

It is necessary to maintain the image of our OS with the utility imagex. We load in VM with the image of WinPE_Image.iso which we created earlier. After good download Before us opens the command line window, we will work in it.
Capture and save the image is made by one command
F: \\ imagex.exe / Capture E: D: \\ install.wim "Windows 7 x64" / Compress Maximum
/ Capture E: - capture section E:
D: \\ install.wim - location and name of the saved WIM file.
"Windows 7 x64" - The name of the image. The name must be enclosed in quotes.
/ Compress Maximum - The type of file compression in the image (optional). For parameter / COMPRESS. Valid values maximum (maximum compression), fast. (quick compression) and none (without compression). If the parameter is not specified, quick compression is used. Maximum compression allows you to reduce the size of the image, but the capture takes more time than with a quick compression. The impact speed of the image is practically independent of the type of compression. It remains to wait 20-30 minutes and the image will be ready.

After saving the image on the second disk virtual machineFor further work it needs to be transferred to the physical OS. Run the virtual machine again and terminate the installation of Windows interrupted at the Oobe. If you have already installed Virtual Machine Additions, now you need to copy the file from the virtual machine to physical using shared folder (Shared Folder), which can be specified in the Virtual Machine Settings.

Setting up Windows 7 boot image

At this stage, we again run the "Deployment Command Line" and copy the Windows PE image files:
Copype.cmd AMD64 D: \\ WinPE
Mount Imagine
ImageX / Mountrw Winpe.wim 1 Mount Windows PE is mounted and in the D: \\ WINPE folder you can find the WinPE.wim file.

Setting up the Windows installation autorun.

In order not to create a manually virtual disk and not start the installation manually, you can edit the file Startnet.cmd and startnet2.cmd. They are D: \\ Winpe \\ Mount \\ Windows \\ System32.

Startnet.cmd.
Wpeinit% Windir% \\ System32 \\ Startnet2.cmd
Startnet2.cmd.
CHCP 1251 NETSH INTERFACE IP SET ADDRESS NAME \u003d "Connection by local network"Source \u003d DHCP CHCP 866 PAUSE NET USE Z: \\\\ 192.168.0.1 \\ Win7 / User: Install Install CD / D Z: \\ Sources Setup.exe
The NET USE command connects to a computer with an IP address 192.168.0.1 (our computer server) to a shared directory with the name Win7 for the rights of the Install user with the same password.
Create a user you need this command in CMD
Net User Install Install / Add / Passwordchg: No
We perform the following instructions:

• On a computer server, create a root directory to download (I have it d: \\ win7 \\), and in it the boot folder.
• We share the win7 folder, that is, we give general access To all users.
• Copy the entire SOURCES folder from the Windows 7 installation disk in D: \\ Win7.
• We replace the install.wim file in the d: \\ win7 \\ sources directory to the file that was previously copied from the virtual machine (ready image of Windows 7)

Now you need to copy additional files To install Windows 7.
We lay WinPE image:
ImageX / Mountrw WinPE.Wim 1 Mount
Copy:
XCopy D: \\ Winpe \\ Mount \\ Windows \\ Boot \\ pxe \\ pxeboot.n12 D: \\ Win7 XCopy D: \\ Winpe \\ Mount \\ Windows \\ Boot \\ pxe \\ bootmgr.exe d: \\ win7 xcopy d: \\ winpe \\ winpe. WIM D: \\ Win7 \\ Boot Xcopy D: \\ Winpe \\ ISO \\ Boot \\ Boot.sdi D: \\ Win7 \\ Boot
Unmount the image of the team:
imagex.exe / unmount D: \\ WinPE \\ Mount

Next, you need to create a BCD file in the D: \\ Win7 \\ Boot directory. To simplify this process, use the CreateBCD.cmd file. Create a D: \\ Winpe \\ CreateBCD.cmd file and fit into it:
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 \u003d 2 DELIMS \u003d ()" %% i in ("BCDEDIT -Store% 1 \\ BCD -CREATE / D" MyWinpe Boot Image "/ Application OSLoader") do set guid \u003d (%% i) BCDedit -Store% 1 \\ BCD -SET% Guid% Systemroot \\ Windows BCDEDIT -Store% 1 \\ BCD -SET% GUID% Detecthaal Yes BCDEDIT -Store% 1 \\ BCD -Set% Guid% Winpe Yes Bcdedit -Store% 1 \\ BCD -Set% Guid% OSDEVICE RAMDISK \u003d \\ BOOT \\ WINPE.WIM, (RAMDISKOPTIONS) BCDEDITT -STORE% 1 \\ BCD -SET% GUID% Device Ramdisk \u003d \\ Bot \\ Winpe.wim, (Ramdiskoptions) BCDEDIT -Store% 1 \\ BCD -CREATE (BOOTMGR) / D "Windows BootManager" BCDEDIT -Store% 1 \\ BCD -SET (BootMGR) Timeout 30 BCDEDIT -Store% 1 \\ BCD -SET (bootmgr) DisplayOrder% GUID%
Run the command with administrator rights:
CreateBCD.cmd D: \\ Win7 \\ Boot
If you have problems with drivers, you can also add them to " Command line Deployment tools »:
Mounting an image to add drivers
DISM / MOUNT-WIM /WIMFILE :WINPE.WIM / INDEX: 1 / MOUNTDIR: MOUNT
To integrate drivers in the already mounted image, a command is used
DISM / Image: Mount / Add-Driver / DRIVER:<каталог с драйверами либо файл с расширением inf>
After all the work with the way finished it needs to unmount
DISM / UNMOUNT-WIM / MOUNTDIR: MOUNT / COMMIT

Configuring the TFTP and DHCP Server

To create these servers, you need to download the TFTPD32 program.
The task of the DHCP server is to provide information remote computer About the free IP address, network masks, as well as the name of the downloaded file and the address of the TFTP server, where this file is located. The TFTP server task is to transfer the remote computer you need to download files.

Run the program and select first folder D: \\ Win7, and a little below - IP network card. In my case, the computer has an IP 192.168.0.1.
We go into the settings (the settings button in the middle at the bottom) and gradually fill in the tabs:

• Tab Global - Table ticks Only opposite TFTP Server, DHCP Server and Enable IPv6.
• TFTP Tab - Select the D: \\ WIN7 folder.
• TFTP Security - Standart.
• TFTP Configuration - Leave as it is.
• Advanced TFTP Options - should stand the ticks opposite: Option Negotiation, Show Process Bar and Translate Unix File Names.
• DHCP Tab
• IP Pool Starting Address Indicates which IP address to start issuing addresses. In my example, the issuance of IP addresses will begin with 192.168.0.2.
• Size of Pool indicates the number of IP addresses that will be dynamically stand out. I set a value of 30.
• Boot File informs the remote computer file name to use as a loader. Install the value in pxeboot.n12.
• Mask, indicates the network mask. In our case, it is 255.255.255.0. The remaining parameter values \u200b\u200bare left by default.
• Ping Address Before Assignation - Remove a tick (if you have a connection computer without switches and routers).

Now you need to turn on BIOS Download With a network card and boot from it. After that, the IP address will be received via DHCP and execute PxEboot.n12 - which will run Windows PE with WinPE.wim file. Right after windows downloads PE will automatically mounted the Win7 directory and install the installation from it. Next, the installation passes exactly as from the disk.

Tags:

• windows system administration
• windows AIK.
• windows PE.
• imagex
• dISM.
• windows7.

Add Tags