Build of Windows Server 2016 | |
OS family | Windows 10 (NT 10.0) |
---|---|
Version number | 10.0 |
Build number | 10586 |
Build revision | 1000 |
Architecture | ARM64 |
Build lab | th2_srv1_nano_dev2 |
Compiled on | 2015-11-12 |
Expiration date | |
Timebomb | 2016-07-15 (+246 days) |
About dialog | |
|
|
Windows Server 2016 build 10586 (th2_srv1_nano_dev2) is a build of Windows Server 2016, the ARM64 compile of which was uploaded on 7 May 2021. This build is notable for not containing any server components as they were not built into the included editions due to the earliness of the ARM64 port. It is also one of the few builds to be available in the Web Server SKU after it was discontinued during the development of Windows Server 2012 and only kept internally as the base edition for other SKUs.[a] Unlike the other supported SKUs, the Web Server SKU uses Windows Server 2012 branding as opposed to a simple Microsoft Confidential banner in winver
. It is the earliest known Server build available in the ARM64 architecture.
The available copy of this build is unstaged and contains private symbols for the kernel, the code integrity component CI.DLL
, and a number of drivers. The kernel uses a debug build of PatchGuard; although obfuscation of PatchGuard code is still in place, there is a debug string mentioning that PatchGuard is in «evaluation mode» and to «contact kejohns» on a PatchGuard false positive. Unlike other Server 2016 builds, this build uses test code signing and as a result can be booted on the current date.
Installation[edit | edit source]
QEMU installation guide:
Prerequisites[edit | edit source]
The following requirements used in order to install this build onto a virtual machine are listed below:
- A 64-bit version of QEMU
- A version of the TianoCore EDK II firmware for ARM64 emulation, to be placed in the QEMU installation directory under
fw/QEMU_EFI.fd
- The Red Hat VirtIO driver package
- Two virtual hard disk images (for storing the installation media and the OS install)
Precautions[edit | edit source]
As a precaution, the second image index in this build’s install.wim
causes Windows Setup to fail due to it consisting of only the base Windows servicing components, as well as lacking any applicable Windows edition whatsoever:
The index must therefore be removed through DISM by invoking the below command, where X is the drive letter of the installation VHD.
DISM /Delete-Image /ImageFile:"X:\sources\install.wim" /Index:2
Instructions[edit | edit source]
Create the needed virtual disk images through the diskpart
utility by running the below script; they will be created under a directory in the C: drive named 10586arm64
. The images and the partitions they contain will be respectively mounted under drive letters M and P.
create vdisk file="C:\10586arm64\install.vhd" maximum=4096 type=expandable select vdisk file="C:\10586arm64\install.vhd" attach vdisk convert gpt create partition primary format quick fs=fat32 assign letter=M create vdisk file="C:\10586arm64\HDD.vhd" maximum=65536 type=expandable select vdisk file="C:\10586arm64\HDD.vhd" attach vdisk convert gpt create partition efi size=100 format quick fs=fat32 create partition primary format quick fs=ntfs assign letter=P exit
Copy the contents of the installation media over to partition M, followed by the contents of the SCSI disk controller driver directory within the VirtIO driver package (located in viostor\w10\ARM64
). Eject all currently attached virtual disks from the machine, and paste and run the contents of the below script onto a batch file within the QEMU installation directory:
qemu-system-aarch64 ^ -M virt,highmem=false -cpu cortex-a72 -smp cores=4,threads=2 -m 2048 ^ -device qemu-xhci -device usb-kbd -device usb-tablet ^ -hda C:\10586arm64\HDD.vhd ^ -hdb C:\10586arm64\install.vhd ^ -bios fw\QEMU_EFI.fd -device ramfb ^ -rtc base=2015-11-12,clock=vm ^ --accel tcg,thread=multi
Load the VirtIO SCSI disk controller driver at the partition selection page and continue installation through normal means.
Editions and keys[edit | edit source]
Edition / SKU | Key |
---|---|
ARM64 Server | DP3NW-RXVQ6-79BFR-VBX83-TCQT8 |
Web Server Core | PCPHN-JH4DV-KW84V-JTWT3-VXHBC |
Gallery[edit | edit source]
Windows Setup[edit | edit source]
-
Autorun
-
SKU selection
-
Interface[edit | edit source]
-
Boot screen
ARM64 Server SKU[edit | edit source]
-
-
System Properties
-
-
Personalization
-
-
PatchGuard debug string, as seen from WinDbg Preview
Web Server Core SKU[edit | edit source]
-
ver
command -
Notes[edit | edit source]
- ↑ The Standard Server edition would eventually become the base SKU for Server Core releases of Windows as of build 15063; the Web Server edition remains, as of writing, the base SKU for all Desktop Experience releases of Windows.
Item Preview
There Is No Preview Available For This Item
This item does not appear to have any files that can be experienced on Archive.org.
Please download files in this item to interact with them on your computer.
Show all files
3,704
Views
8
Favorites
DOWNLOAD OPTIONS
Uploaded by
scamdisk
on
SIMILAR ITEMS (based on metadata)
Windows Server 2016 10.0.14324.1001.rs1_onecore_mqsrv_sc.160414-1853 |
|
Architecture | ARM64 |
---|---|
SKUs | ARM64 Server |
BIOS date | 2016-04-14 (compiled) |
Timebomb | 2016-07-15 (+92 days) |
Windows Server 2016 Build 14324.1001 is a Build of Windows Server 2016. This build was leaked only in the ARM64 architecture.
Installation[]
1. Download and install QEMU for Windows.
2. Download Linaro UEFI.
Then copy the file to the QEMU installation folder.
3. Create VHD.
Run Command Prompt as Administrator, run diskpart and run the following commands:
create vdisk file="C:\test\hdd.vhd" maximum=20000 type=expandable
select vdisk file = "C:\test\hdd.vhd"
attach vdisk
convert gpt
create partition efi size=100
format quick fs=fat32
assign letter=p
create partition primary
format quick
assign letter=w
exit
4. Import the system image.
Mount the ISO image (assuming the drive letter is F). Run Command Prompt as administrator and run the following commands:
dism /apply-image /imagefile:F:\sources\install.wim /index:1 /applydir:W:\
bcdboot W:\Windows /s P: /f UEFI
Remove P or W. Once removed, P remains and disappears after reboot.
5. Launch the emulator.
Go to the QEMU installation folder, create a bat file and run it:
File name: start.bat
qemu-system-aarch64 -m 2048 -cpu cortex-a57 -M virt -bios QEMU_EFI_TEST.fd -device VGA -device ich9-usb-ehci1 -device usb-kbd -device usb-tablet -drive if=none,id=usbstick,file=C:\test\hdd.vhd -device usb-storage,drive=usbstick -rtc base=2016-1-1,clock=vm
6. Install the system.
Press F2 and enter EFI settings, select Boot Manager and then select EFI Internal Shell. Enter a drive letter (for example FS0 in Shell and run the following command:
efi\boot\bootx64.efi
(FS0:
cd EFI
cd Boot
bootx64.efi)
Complete OOBE.
Then you boot into the system.
7. Log in to the desktop.
Each time you reboot, you need to go from the beginning of step 6 to the end of step 6.
Wait patiently for the configuration to complete and do an OOBE to press Ctrl-Alt-Delete to unlock.
Press Ctrl+Alt+2 to switch to QEMU Monitor and input «sendkey ctrl-alt-delete» (without quotation marks) then press enter. Press Ctrl+Alt+1 to switch to the system. Enter your password and login.
Gallery[]
Boot screen
Perhaps the biggest announcement at OCP Summit 2017 was that Microsoft Windows Server 2016 now runs on Qualcomm Centriq 2400. Microsoft is working both with Qualcomm Centriq 2400 and the Cavium ThunderX 2 parts to bring ARM servers into its cloud infrastructure ecosystem. While the majority of the work we have seen on ARM servers thus far has been on the Linux side, Microsoft is using Windows Server with these ARM chips.
On the OCP Summit 2017 floor, Microsoft had a demo running of the Qualcomm Centriq 2400 running Windows Server 2016. Here is the demo in its glory:
For those looking for guideposts on reading that image here is what you are looking at. First and foremost, this is not the production Windows Server 2016 that you may buy. This is an internal version of the OS running .NET services for Microsoft’s cloud services. Here is the official quote from Microsoft’s blog post:
To enable these cloud services, we’ve ported a version of Windows Server, for our internal use only, to run on ARM architecture. We have ported language runtime systems and middleware components, and we have ported and evaluated applications, often running these workloads side-by-side with production workloads.
(Source: Microsoft)
Second, this is a remote desktop session with several console outputs running in the top left. The bottom left window is showing that the particular system is running on a Qualcomm 48 core ARMv8 64-bit processor. The right side of the screen is showing loading across all cores with several pegged at very high CPU utilization.
Third, this is is showing the ARMv8 CPU with a Windows GUI. This is not simply running a core version without GUI which is a feat unto itself.
Fourth, the Qualcomm Centriq 2400 was a single socket design. Cavium ThunderX 2 OCP platforms on display were dual-socket designs.
Final Words
This is certainly a huge milestone towards ARMv8 adoption and a validation both for Qualcomm and Cavium in the marketplace. Microsoft showing off ported Windows code running on the platform along with stating that their evaluation process has lead to ARM selection is a major milestone in the ARM server community.
Microsoft has warmed up to Qualcomm to make a Windows 10 PC based on its ARM chip, and now the companies are bringing Windows Server OS to ARM.
For the first time ever, Microsoft is expected to show the Windows Server OS running on an ARM server. The server runs on Qualcomm’s Centriq 2400, an ARM-based chip designed for cloud servers.
The server is being shown at the Open Project Compute Summit being held in Santa Clara, California, on Wednesday and Thursday.The ARM-based Windows Server hardware is for Microsoft’s internal use. No information was shared on when Windows Server would be available for ARM servers.
The ARM-based Windows Server hardware is for Microsoft’s internal use. The company didn’t share information about when Windows Server would be available for ARM servers.
Putting Windows Server on ARM is a big deal. Way back in 2011, Microsoft said it had no interest in putting the Windows Server OS on ARM servers. Since then, rumors have surfaced that Windows Server 2016 was being ported to ARM, but this is the first time the OS is being shown working on the hardware.
Like with PCs, current editions of Windows Server only run on systems with x86 chips from Intel and AMD. But Microsoft has been warming up to ARM on laptops and now servers. The company’s Windows 10 IoT Core and Windows 10 Mobile already work on ARM chips.
Microsoft and Qualcomm worked for many years to bring Windows Server to Centriq 2400. The collaboration will continue for future generations of server hardware and software, the companies said.
The goal with Windows Server on ARM is to run next-generation Microsoft cloud services on servers with Qualcomm’s Centriq 2400 chips, the companies said in a statement.
Intel, which dominates the server chip market with more than a 90 percent share, will surely take notice of this announcement. Microsoft’s support for Qualcomm is a strong statement that the software company is ready to consider an alternative architecture for Windows Server.
Qualcomm has developed special Windows Server hardware based on its Centriq 2400 processor. The Centriq Open Compute Motherboard server has 48 CPU cores and fits into a 1U server chassis. It has multiple I/O and networking interfaces and supports the latest storage protocols.
The server is based on a new version of Project Olympus, which is an open-source cloud hardware server design developed by Microsoft in collaboration with OCP.
ARM servers haven’t caught on despite being hyped and tested for more than five years. ARM’s server chips are mainly derived from smartphone chip design, and the low-power features could reduce electricity bills for data centers. ARM servers already run on Linux OS, but the application ecosystem is limited.
Qualcomm’s Centriq has an advanced design and high level of integration of I/O and networking protocols and is bringing back interest in ARM servers. The chipmaker is working with many partners to boost adoption of the technology. As Qualcomm progresses up the server ladder, rival ARM chipmakers have been dropping like flies, while server chips from some of them are being mainly used as network and storage processors.