Windows Server 2012 R2 with updates to December 2020.

The assembly is based on the original MSDN images:
en_windows_server_2012_r2_vl_x64_dvd.iso


Composition of editorial staff
en_windows_server_2012_R2_vl_x64:
Windows Server 2012 R2 Standard En with GUI
Windows Server 2012 R2 Datacenter En with GUI


All editions have a Volume distribution channel


List of programs included in the MInstall shell:
Installation of programs is performed using the MInstall shell after installing the OS. (no timer)
There is a choice of software, what to install and what not.
Archivers:
WinRAR v6.0.0, 7-ZIP v19.00
Editors:
Notepad ++ v7.9
Systemic:
Microsoft Visual C ++ (Lib) 2005 ... 2019
Информация:
HashTab v6.0.0.34, CrystalDiskInfo v8.9.0, CPU-Z v1.94
Activation:
AAct v4.2.0
For stable activation, a 30sec timer has been added to the reboot, do not fuss.
It is not worth stopping the installation of programs after starting, after the installation of programs is completed, the computer will be restarted.


Contents of the Support folder automatically copied to the desktop
Activators: KMS Tools Portable 11.2020 (KMS Tools is a pack with activators and utilities)
Driverpack: SDI R2009 with drivers until 12.2020 for LAN / Chipset / MassStorage / USB /
Scripts will be copied to the root of the system disk:
Clean_Win_SxS.ps1 Cleaning the system storage from old components and drivers, followed by a reboot, is a necessary thing.
Repair_WinImage.ps1 to check and, if necessary, restore the system file storage (when the network is connected)


Snappy Driver Installer kit with drivers from 12.2020 for LAN / Chipset / MassStorage / USB added to image
A small set of Snappy Driver Installer R2009 with drivers until 12.2020 for LAN / Chipset / MassStorage / USB has been added to the image -
\ sources \ $ OEM $ \ $ 1 \ Users \ Public \ Desktop \ Soft \ Drivers \ Driverpack \ SDI_2009 ~ 500MB
When starting SDI_x64_R2009. exe shell can install the necessary drivers, and with the presence of the Internet, pull up the selected driver packages
or update your selected drivers.


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


Why is the system recovery window not displayed at the beginning of the installation?
This window is blocked if there is an automatic response file in the root of the image, it is enough to delete this file or rename it.

The following components have been changed:
Standard Component Changes:
.NET Framework 3.5 = Enabled
Server Drivers for Printers = Disabled

Development stage : Release
Version : 6.3.9600.19893
Developer : Microsoft
Bit depth : 64bit


What News?

https://support.microsoft.com/en-us/help/4592495/windows-8-1-update