Windows Server 2012 R2 x64 VL with Update 08.2018

The distribution includes the standard .Net Framework 3.5 component

Integrated updates for August 2018
The script disconnects the service at the end of the installation – Diagnostics Tracking Service
With these exceptions, the editorial board of os is unchanged.

Distinctive feature from the previous hands:
the backups are not cleaned up, so the size matters.
To burn images you need a flash drive from 16GB,
all files in the images are compatible with the FAT32 file system.
(The install image is not compressed into esd, because its size will exceed the FAT32 volume limit)

Stage of development: Release
Version: 6.3.9600.19101
Developer: Microsoft
Bit depth: 64bit
Language: English
Tabletka: Present
Assembly Author: AG

System requirements:
from 2 GHz 64-bit Processor
from 4 GB RAM
from 64 GB HDD

Composition of the Support folder automatically copied to the desktop
Activators: KMS Tools Portable (KMS Tools is a pack with activators and utilities)
Driver: SDI R1806 with drivers for 08.2018 for LAN / Chipset / MassStorage / USB /
SkipMetroSuite – crutch to disable the pop-up sidebar (only in the ru image)
At the root of the system disk, there will be a Repair_WinImage.ps1 script for checking and, if necessary, restoring
storage of system files (when the network is connected)

The Snappy Driver Installer with drivers from 08.2018 for LAN / Chipset / MassStorage / USB is added to the image
A small set of Snappy Driver Installer R1806 with drivers for 08.2018 for LAN / Chipset / MassStorage / USB is added to the image –
\ sources \ $ OEM $ \ $ 1 \ Users \ Public \ Desktop \ Soft \ Drivers \ Driver \ SDI_1806 ~ 500mb
When you start SDI_x64_R1806.exe, the shell can install the necessary drivers, and with the presence of Ineta, you can tighten the selected driver packages
or update the drivers you selected.

The standard WinPE feature is used to add drivers to the image before installation
This function is designed to easily add drivers critical for the installation or the ability to start working with the OS, such as raid controllers.
At the root of the image there is a folder $ WinPEDriver $. It is in it should be located drivers for the hardware to which the installation is planned.
Note that for example in new HP servers in the UEFI environment there is (HP iLO Management Engine) with the ability to automatically preset the necessary drivers.
It can be updated over the network or using HP Service Pack for ProLiant (DVD).

About System Activation
After installation on the desktop in the folder Support will be a folder with activators.
By selecting the required KMSAuto Net or AAct activator in KMS Tools Portable, you need to start it.
In the activated shell of the activator, you need to find the "Activate Windows" button, you can use it for the intended purpose.
KMSAuto Net issues a confirmation window after activation to add an automatic re-activation cycle to the task scheduler.
In the future, you should pay attention to the time of the task of automatic re-activation, in KMSAuto Net the default cycle
set after 10 days at 10.00. Perhaps some evening users it makes sense to translate the hours of the re-activation cycle into the evening time.
Activator with exotic name AAct automatically does not add to the task scheduler the task of re-activation, for this it is necessary
Before activation, click on the gear in the left lower part of the running AAct shell, and install the corresponding bird.

http://microsoft.com/