home-Keyboard-How to prepare your Windows installation image. Sysprep is a standard utility for adapting Windows to new hardware Creating a reference image of Windows 10

How to prepare your Windows installation image. Sysprep is a standard utility for adapting Windows to new hardware Creating a reference image of Windows 10

If you are a system administrator, then you will definitely be faced with the issue of mass deployment operating system to users' computers. And no matter how you deploy it - from USB, through a WDS server with MDT, using SCCM - in any case, you will use a WIM file with an operating system image.

Overview of OS fork methods

  1. Installation from boot USB storage . The answer file should be located on it in the root of the disk autounattend.xml. This is the file you create in advance using Windows System Image Manager (SIM) which is included in the kit Windows package ADK. Please note that all Windows 10 builds have their own ADK version. You can download it from the Microsoft website. The OS image file itself with the WIM or ESD extension is located in the sources folder of your USB. You can take the original MSDN image, copy it from somewhere, or prepare your own. You need to integrate the drivers in advance into the WIM file or put them in the $OEM$ subfolder, and the path to it is indicated in the autounattend.xml file.
    This method is suitable for single installations without the possibility of deep customization for different tasks, different users or different hardware.
  2. Deployment using MDT from a USB drive. In this case, myself boot disk you prepare using MDT (Microsoft Deployment Toolkit). You can download the MDT package for free from the Microsoft website (again, different versions MDT supports different versions of deployed OS). MDT also requires the correct version of ADK to work. Latest on this moment MDT 8450 currently only supports Windows 10 1709 and older. In the MDT environment, you prepare a Task Sequence, add packages, drivers, and an operating system WIM file. Next, you create a bootable media that will include all of the above and copy it to USB. The subtlety is that here you customize the image either by modifying the WIM file in advance, or by editing the unattend.xml file related to the Task Sequence you created in MDT, which will be automatically included in the media, or by writing scripts that you add to packages and include it in the installation process as a Task Sequence step.
    When creating media MDT, boot.wim will be created for you boot file, which will be executed when loading from a flash drive. It will download for you Windows environment PE from which the installation will begin.
    A very flexible method that allows you to enable any drivers and install any software during OS installation.
  3. Deployment using MDT and WDS server. The only difference between this method is that the boot.wim created in MDT will not be located on USB, but on the network on a WDS server, from where you can boot via PXE.
  4. Deployment using SCCM and WDS server. The client is loaded as in option 3, but the difference is that all WIM files, drivers and packages, as well as the Task Sequence itself with the unattend.xml file will be created and launched from the SCCM server, and not from MDT. A bootable boot.wim image will also be created using SCCM.
    This option is suitable for the most complex deployments with a large number of distributed installations.

Please also note that the unattend.xml response file can be included in the WIM image itself by placing it in the %WINDIR%\Panther\Unattend folder, but for MDT and SCCM a separate external file will still be required to execute the Task Sequence.

As I already indicated, the unattend.xml or autounattend.xml files can be edited manually in the editor, but it is more correct and safer to do this through SIM. The WIM operating system image file itself is created and edited using a console utility DISM, having many keys. Moreover, the same utility also deploys (apply) the WIM file to disk.

The DISM utility is included in the ADK package; it is important to use the version of the utility that supports the OS you are deploying.

Image Capture and WIM Creation

In order to create a WIM file, you must perform the Sysprep and Capture operations. To do this, install the system on your computer, configure it as you wish, install or remove applications, and install updates. Also, for successful sysprep in Windows 10, you need to clean the system and remove some installed Modern App applications from HP and Canon, otherwise sysprep will fail. This can be done with Powershell commands:

Sysprep.exe /generalize /shutdown /oobe

In this case, the system will go to OOBE mode (Out-Of-Box Experience, as if it were just being installed from scratch), and then the computer will turn off. You can read more about this procedure in the Microsoft documentation.

Now the disk image can be captured. Disk capture is performed by the already mentioned DISM utility.

If you capture manually, you need to boot into Windows PE from USB or over the network, or connect the disk to another computer. Windows PE should already include the dism utility. Capturing the image is done with the command (assuming you are capturing the C: drive):

1 Dism /Capture-Image /ImageFile:D:\my-windows-partition.wim /CaptureDir:C:\ /Name:"My Windows partition"

Dism /Capture-Image /ImageFile:D:\my-windows-partition.wim /CaptureDir:C:\ /Name:"My Windows partition"

One WIM file can contain multiple OS images, you can add a new captured disk to an existing image. This is convenient when you need to deploy different systems (for example, with a different set of programs) from one WIM file. You can edit the properties of the wim file, the name of the images in it.

Each image in the file has an index starting with 1. Accordingly, when you apply the image to a blank disk, you will need to specify the system index:

bcdboot C:\Windows

will create a BCD boot loader on the disk with the operating system. In addition, you will need to make a Recovery partition. To make it quick, I’ll give an example of a typical bat script that performs all these operations from the Microsoft documentation.

In fact, this is not the purpose of our article, but rather an overview that allows you to understand which utilities should be used and in what case. After all, the syntax of all commands is well described in the documentation. In addition, the procedure for both sysprep / capture and deploying an image to a pre-formatted disk is easier to perform through MDT by creating the appropriate Task Sequence in it, however, MDT requires skills; for one-time tasks it is easier to do everything manually.

Utilities for working with WIM images

All utilities in this list will be graphical replacements for console DISM.

This great utility, written in the AutoIt scripting language, saves you a lot of time by doing:

  • capturing a disk into an image (capture)
  • applying the image to disk (apply)
  • shows information from the finished wim image
  • allows you to mount an image into a folder, edit its contents and unmount it back (mount and unmount)
  • uploading a single image from a wim file with multiple images
  • editing the name and description of images in a wim file

The current version 2.2.0 is compatible up to Windows 10 build 1803. All operations are performed in one click. No installation required. Use case: capturing another partition on your disk or on a connected disk, as well as editing an existing wim file. Working in Windows PE is not implied.

This utility is written in Powershell, but is intended for slightly different operations, namely for maintaining and editing the existing WIM. All bookmarks are arranged in the order of their use: first you mount the image into a folder, and then edit it or save changes.

The utility allows you to:

  • integrate drivers into the image (drivers)
  • add cab packages and enable/disable features
  • Attribute license information and key
  • use ready-made Unattend.xml
  • get a list of applications and patches in the image
  • capture and apply image

The third utility is designed to prepare the system for capture. It allows you to cut or add whatever you want from it in a very granular manner:

  • clearing caches, logs, Appx (Modern applications), temporary files
  • management of installed Appx applications - allows you to remove Modern Apps, which previously could only be done through Powershell.
  • optimization and customization of menus and icons
  • adding and removing drivers
  • adding and removing Windows components
  • adding and deleting Windows features(Features on Demand)
  • adding and removing updates
  • setting up file associations
  • Editing the Unattend.xml response file

Today there are a large number of users who are wondering how they can create a wim image of the Windows 10 operating system and then use it to install the OS.

Creating a Windows 10 installation wim image with software using WDS

This procedure can be carried out if you use two computer devices with pre-installed Windows Server 2012 R2 and Windows 10 Enterprise x64, for example. These two machines may have different sets of utilities installed.

In order to achieve readiness system partition computer device To create a wim image of the Windows 10 operating system, you need to find a program called Sysprep. Usually this utility located us system disk WITH.

After opening this program, you need to set the parameters in it that are in the picture below.

After this, the program begins to carry out its activities.

When it finishes its work, the computer device running the Windows 10 operating system will turn off.

On a computer device with installed Windows Server 2012 R2 needs to open the console, which is required to control WDS. Next we need to select the server that we need. It is listed as WIN-L1P3UL7JP8H. After this you need to go to Images and Downloads.


Then you need to click on the Windows 10 Enterprise (x64) Setup boot image and open it context menu. There you should click on the Create recording image command.


In the new window, you should specify the name and all the basic parameters of the image that we want to create.

After the procedure has been completed, you need to go to Review in order to decide on the place where we will save it.


Review

In this particular case, the image will be stored in the Capture folder.

After this, image creation will begin.

Thus, the image of our record will be formed. In the new window, after completing the procedure, you must check the box where you want to mark the addition of the image to the operating system deployment server.


The process of adding the created image to the server will begin.

After adding, you must click on Finish.

When the work is completed, you need to start the computer device over the network with pre-installed Windows 10 Enterprise x64. On the page that appears, select Windows partition 10 Enterprise (x64) Capture.

On this computer device, you need to select the system partition where the Windows 10 image will be created for installation purposes.


Name

After this, the system partition of the computer device is saved to a file for wim installation purposes.

The procedure is complete.

It will appear in the previously selected location for storing the OS image.

This documentation has been archived and is no longer maintained.

Build and deploy a Windows 10 Classic edition image (Home, Pro, Enterprise, and educational institutions)

In this article

You can use the Windows Image and Configuration Designer (ICD) to create new image Windows 10 Classic Editions and customize it with drivers, apps, language packs, settings, and more. You can also create deployment media in a folder or USB key.

Note This imaging method requires a Windows Image file (Install.wim) that contains a base Windows image.

Build a custom Windows 10 image for classic editions

    On the Windows ICD start page, select the command.

    You can also choose Create a project... on the menu File.

    In the window Enter project details please indicate Name And Location of your project. If you wish, you can also enter a short Description to describe your project.

    If you have chosen a team Create a new custom Windows image on the home page, skip this step.

    In the window Select a project workflow select Working with images from the list of available project workflows and click Further.

    In the window Selecting the source format to create the image select item The Windows image is based on a WIM file and press the button Further.

    In the window Choosing an image click Review to launch File Explorer. Search for and locate the Install.wim file.

    After selecting the Install.wim file, all Windows images in the WIM file are listed in the panel Available images. By default, the first Windows image in the list is selected, and information about that image is displayed in the panel Image details.

    Select the Windows image you want to use and click Further.

    Optional. If you have a provisioning package that contains settings already made in another project and you want to reuse them from this package, click Review on the screen Import a provisioning package and find the provisioning package exported from another project.

    Note You can only import one provisioning package.

    Click the button Ready.

    All settings that can be configured depending on the edition of Windows selected will be downloaded. Once all available settings have loaded, the Settings page will be displayed.

    On this page, select the resources and settings you want to configure in the panel Available settings. There may be:

    • Applications
    • Driver set
    • Drivers
    • Components on demand
    • Language packs
    • Reference device data
    • Options
    • Windows Updates

    For more information about configuring resources and settings, see .

    Note

    • The resources and options available for configuration depend on the edition of Windows you selected in the previous step, so not all of these resources may be available.

      Addition language packs may include a set of dependencies. For more information, see the article.

      If you want to add languages ​​to the environment Windows recovery, this will need to be done separately. For more information, see .

    Not necessary. If you've finished configuring your custom image, you can export the provisioning package if you want to reuse all or most of the settings configured in that project.

    To do this, click the drop-down list Export in the main menu, select Training package, add the required package information, set parameters, and create the package.

    If you've finished configuring your custom image or finished exporting the provisioning package (optional), create the media that will host the image.

    To do this, click Create from the main menu, and then select one of the media types.

    • Working media- a medium to be used by equipment manufacturers. This carrier can be run in full autopilot mode. This media provides the ability to boot in audit mode and use an optional test script.

      Production media provides several optimization options to save deployment time.

      Carrier for clean install - This media may only be used by the end user for a clean installation. This media starts when the computer is first turned on, waits for end user input, and continues to boot into desktop mode. The installation itself is completed before starting when you turn on the computer for the first time.

      When you build media for a clean installation, all resources are placed in a provisioning package along with an install.wim file. The .ppkg file is not embedded in the installation, but rather embedded in the operating system during deployment.

      System recovery media- this media can be used by the end user only to recover data from a partially functioning (showing signs of life) device. It can only be in WIM image format.

    • On the screen Select image format To create an image, you can select WIM or FFU format.

      • WIM- an image is created in the format Windows file Image (WIM).

        This option allows you to build the media into local folder on a computer or network folder, and also create bootable media on a USB drive.

        FFU- the image is built in Full Flash Update (FFU) file format.

      • You can also choose image options, such as enabling compact OS and defining first boot behavior. This includes booting in audit mode and selecting a script to run during the first boot.

      On the screen Deployment media select the media type you want to create.

      • If you select this option, enter or select a path for the destination location.

        Create a bootable USB drive- bootable media is created on a USB drive.

        When this option is selected, Windows ICD detects all available USB drives connected to the host computer and lists them in a drop-down list Output drives. If Windows ICD does not detect USB drives, connect the USB drive to your computer and click Update.

    Click the button Further and then click Run build to start building the image. Project details are displayed on the build progress page, and a progress bar indicates the status of the build.

    To cancel the construction, click the button Cancel. The current build process will be canceled, the wizard will close, and you will be returned to the settings page.

    If the build fails, an error message will be displayed with a link to the project folder. You can review the logs to determine what caused the error. After the problem is resolved, try building the image again.

    If the build is successful, the image name, output directory, and project directory will be displayed.

    • If necessary, you can build the image again by selecting a different image format, selecting deployment media (or both), and starting another build. To do this, click Back to select the item you want to change and click Further to start another build.

    • If you are finished, click the button Ready to close the wizard and return to the settings page.

    Important Files generated when creating media with using Windows ICD should only be used for installation while booting from media. Affiliates must not modify or use these files for purposes other than downloading from the media.

Deploying an image on a computer

    Insert the USB drive that contains the bootable media into your computer and boot your computer from the USB drive.

    Enter your product key.

    Accept the terms license agreement and wait for the installation to complete.

Create your own customized Windows 10 distribution. Or the perfect way to transfer Windows to an SSD.

We can say with confidence that such a distribution is an ideal backup copy, which is deployed on a computer (and not only on your own) through a simple and familiar installation of the operating system. I personally see this method as ideal for transferring Windows from regular HDD to an SSD.

Managing disks on a laptop with Windows 10 installed.

The laptop hard drive is divided into two partitions (C:) and (D:). We will need to create a Windows 10 image file (drive (C:) and place it on drive (D:)
On the drive (C:), after installing all the programs I need, 13 GB of disk space is occupied.

Creating a bootable USB flash drive Live CD AOMEI PE Builder

First of all, let's create bootable USB flash drive Live CD AOMEI PE Builder. This Live CD is based on Windows 8.1 Enterprise.

Download Live CD AOMEI PE Builder and create a bootable USB flash drive from it (gcontent)download Live CD AOMEI PE Builder (/gcontent)

Download and run the WinSetupFromUSB-1-6 utility, it will create a bootable USB flash drive for us.

In the main WinSetupFromUSB window, select the name of our flash drive.

Check the Auto format it with FBinst checkbox and check the FAT32 checkbox.

Check the box Vista/7/8/Server 2008/2012 based ISO and click on the button that opens the Explorer window.

Explorer opens, find it on the computer ISO image Live CD AOMEI PE Builder and select it with the left mouse, click "Open".

Click “GO”.

The creation of a bootable USB flash drive Live CD AOMEI PE Builder begins.

The bootable USB flash drive is ready.

We boot the laptop from a bootable flash drive Live CD AOMEI PE Builder. Our flash drive is universal; from it you can boot a laptop with a UEFI interface, as well as a regular BIOS.

Press “Enter” on the keyboard.

The Live CD AOMEI PE Builder desktop loads, which is a regular Live CD on Windows based 8.1.

Click on Windows button Disk Management.

We see two sections hard drive(C:) and (D:). Windows 10 is located on the drive (C:), let's create a full image of it and save it on the partition (D:).

To create a backup image of Windows 10, we will use the system for maintaining and deploying operating system images - DISM. This tool command line was developed by Microsoft specifically for creating and subsequently deploying images of Windows operating systems.

Launch the command line.

and enter the command:

Dism /Capture-Image /ImageFile:D:\install.wim /CaptureDir:C:\ /Name:Windows

install.wim: is the name of the WIM disk image (C:) with Windows 10.

C:\ - partition with Windows 10 installed.

D:\ is the location where the WIM image is saved.

Operation progress 100%. The system image has been created.

The Windows 10 image is located in the install.wim file on disk (D:) and has a capacity of 4.80 GB.

Reboot

Restart your computer and enter Windows 10.

Download the Windows 10 distribution kit from the official Microsoft website and save it on the partition (D:).

Create a folder on the partition (D:) and name it 10.

Copy all Windows 10 distribution files to this folder

After the files have been copied, go to the D:\10\sources folder and delete the install.esd file in it.

Instead, copy the install.wim file located on the partition (D:)

The install.wim file has been copied and is located in the D:\10\sources folder

Note: An attentive user may ask why we delete the install.esd file and copy the install.wim file instead, because the files are different, will there be any conflict?

Friends, the fact is that starting with Windows 8.1 (DISM 6.3) for the Windows Installer and DISM, the esd and wim extensions are the same thing, esd=wim and wim=esd .

WinToolkit 1.5

Download and run the WinToolkit 1.5 program.

If you don't have it installed on your computer NET Framework 3.5, then the program will ask you to install it.

In the main program window, click on the Basic button, and then on ISO Maker.

In the next window, the program asks us to open the folder into which we copied the Windows 10 distribution files, in our case D:\10

Click on Browse.

In the explorer that opens, find the drive (D:) and folder 10 on it, select it with the left mouse and click Select folder.

In the next window we need to select the location to save the future Windows 10 ISO image.

Click on Browse.

An explorer window opens. I will save the Windows 10 ISO image to drive (D:). I’ll call the image Windows 10.

Click on the Create ISO button

and the process of creating your own customized Windows 10 distribution begins.

The ISO image is ready.

The ISO image of Windows 10 turned out to be 5 GB in size.

Windows 10 installation process

Process Windows installations 10 from the distribution package we prepared can be called an express installation.

We boot our computer from the flash drive, the boot menu appears, in which you can select Live CD AOMEI PE Builder or Windows 10, select Windows 10.

Installation.

If you don't have license key, then click on the “I don’t have a product key” button.

We accept the license terms.

Custom: Windows installation only.

If you want, create partitions on the hard drive, and I will install the operating system on the unallocated space on the SSD.

The installation process is in progress.

Windows 10 is loading.

The system is fully functional, all programs work.

Conclusion:

If you install Win 10 on your computer from such a distribution, then there should be no problems with the installation and further work in the operating system. You can also install such an assembly on another computer, with hardware different from your computer, in this case you will have to install device drivers into the system, that is, do everything that is usually done after installing the system, the only thing is that you will not need to install programs, since they are already in your assembly.

Note: If you are creating this build on a computer built on Intel platform(Intel processor) and then deploy the system to a computer with an AMD processor (or vice versa AMD-->Intel), then in some cases problems may arise during installation (a conflict between foreign hardware and installed drivers chipset motherboard), which is why many system administrators use the “sysprep” utility when creating their own distribution, which performs “unlinking” installed system from the computer hardware, removes unique system parameters and drivers, in this case you create your own customized Windows 10 distribution, which can be deployed to any other computer with hardware different from yours. But again, a minus, when installing the system on your computer, you will have to install drivers for the devices.

There can be many reasons to create your own distribution of the Windows 10 operating system, and they are not the topic of this article. The important thing is that there is a need for your own version of the distribution kit, and we will tell you how to create it using only the Windows ADK (Toolkit for Windows deployments) And command line, in other words, we can do without third party software using only tools built into the OS.

So, a customized distribution may be needed, for example, if you plan to increase the number of computers. You have decided to get another machine, in addition to the laptop, you have decided to order the assembly of a more productive computer, but the set of software on it will be approximately the same as on the laptop.

You can, of course, install the OS on new car, and then install and configure the remaining software. You can do it differently: turn that Windows 10 configuration, complete with all installed programs, that runs on one of the computers, into a distribution kit. All that remains is to install the system on a new machine, and all the necessary software will be installed automatically. All that remains is to install drivers for the hardware that will be in the new computer.

To work you will need two computers, in extreme cases, for experiments you can get by with one, but install virtual machine. Let's assume that Windows 10 and all the necessary software are installed on one of them.

Preparation

You will need an OS distribution, which can be downloaded from the Microsoft website.

We create a bootable USB flash drive using this distribution and run the “sysprep” utility built into the system. The task of this utility is to prepare a system image, which includes all settings and installed programs, to transfer to another computer.

You need to start the command line and enter the command:

C:\Windows\System32\Sysprep\Sysprep.exe

In the window that opens, all parameters are set as shown in the screenshot:

Let us explain a little what some points mean:

  • Switching the system to OOBE mode - the next time you start the system, the system will switch to OS transfer mode.
  • Preparation for use - unnecessary information not intended for copying will be deleted, for example, activation data, etc., while all installed programs and utilities must be included in the copying.

The "sysprep" utility will run for several minutes, the duration depending on the amount of data that will be transferred to the new computer.

Once completed, the computer will turn off.

Creating an image in ESD format

Now you need to connect an external drive, insert the bootable USB flash drive you prepared earlier, and boot from it. When the Windows 10 installation window appears, press the key combination “Shift+10”.

  1. "Diskpart" (a utility that allows you to work with sections of hard disk),
  2. “lisvol” (viewing disk partitions, so Windows 10 is installed in partition C:, and the connected USB drive has the letter I:),
  3. “exit” (exit the utility. We have found out the data about the partitions).

Now you need to start the process of saving drive C:, where the installed Windows 10 OS is located, to an image file in ESD format to the connected USB drive. The command looks like this:

Dism /Capture-Image /ImageFile:I:\install.esd /CaptureDir:C:\ /Name:Windows

Let's explain the command:

  • Install.esd – name created file with the system image,
  • I: - the disk on which this file will be created. In our case, this is a portable disk I:),
  • C:\ is the drive where the original Windows 10 OS is installed.

You can also specify the compression level of the resulting file. This parameter is not specified in this line and the default value - fast - will be used. If a different operating mode is needed, then a different value can be used. It should be remembered that the stronger the compression, the more time it takes to work.

Upon completion of work on removable disk will appear ready file with the image.

Now you can turn off the computer on which Windows 10 was installed and which was used to create the image. The rest of the work will be done on the second computer.

Additional compression of the image file

This section is not required. The “Install.esd” file obtained at the previous stage can be compressed even more by reducing its size. We check the presence of the file on the removable disk.

Enter the command:

DISM /Export-Image /SourceImageFile:I:\install.esd /SourceIndex:1 /DestinationImageFile:I:\install2.esd /Compress:recovery

With this command we create a second file named “Install2.esd”, which should differ from the original only in size. At the same time, we use a new type of compression - Compress:recovery.

After the operation is completed, there will be 2 files on the disk that differ in size. Now you can delete the original image file (“Install.esd”), and rename the new one from “Install2.esd” to “Install.esd”.

As a result, again only one file remains with the same name “Install.esd”, but of a reduced size.

Editing a Windows 10 ISO Image

Now it’s time to start creating the version of the OS image we need. To do this, take the distribution kit downloaded earlier from the Microsoft website and copy its contents into the folder that we create on portable disk, where our file is already located. Let's name the folder "10".



After copying is complete, in the “sources” subfolder you can see a file with the same name as the source computer file we created when creating the OS image. Our task is to replace this file with our own. To do this, copy our “Install.esd” file.

Then we paste it into the “sources” folder of the Windows 10 distribution.

It is necessary to replace the original file with ours.

Creating an ISO Image

There is little left to do. From the folder into which you copied the contents of the original Windows 10 distribution, and where you replaced one file with your own, create an ISO image again. To do this, we will use the Windows ADK (Windows Deployment Kit). It is usually installed along with the OS. If it is not there, you can download it from the Microsoft website and install it.

We launch the environment for deployment tools and working with images.

In the window that opens, enter the command:

Oscdimg /u2 /m /bootdata:2#p0,e,bI:\10\boot\Etfsboot.com#pef,e,bI:\10\efi\microsoft\boot\Efisys.bin I:\10 I:\ Windows.iso

Let's explain the command:

    • u2 — file system UDF
    • m – the image has no size restrictions,
    • b — boot sector write down etfsboot.com, the path to the file etfsboot.com when specifying b(boot) is written without a space: bI:\10\boot\etfsboot.com,
    • I:\10 – indicate the folder in which the files for creating the image are located,
    • I:\Windows.iso – we indicate that the final image file should be named Windows.iso and located on the I: drive.

After the operation is completed, a Windows.iso distribution image file will appear on the disk.

Create bootable media

The distribution kit has been created, now you need to write it onto the media from which the system will be installed on another computer. You can use a flash drive. How to create a bootable USB flash drive can be found on the Internet. It is not difficult. If you managed to create your own distribution kit without resorting to outside help, without bothering friends, acquaintances or the system administrator at your work, and did not contact laptop repair near the Otradnoye metro station, where, for example, you live or work, then you will cope with this task.

As a result, we get a medium from which you can install a system with an integrated set of necessary software, and you can install it on any computer as with UEFI bios, and with the usual one.

Installing Windows 10 OS

If you have already installed this version of the OS, you are familiar with the procedure. There are no differences when using a self-created distribution. In extreme cases, the installation process will take a little longer.

After completion, you will have a computer on which all the necessary software is already installed. The only thing left to do is install the device drivers for this computer.

This assembly is convenient if you need to transfer the system to another computer. If you need to install the OS on several computers, then this distribution can be used as a basic configuration with an integrated set of necessary software.

Similar publications: