Windows 10 installation is straightforward most of the time, but not intuitive on Servers. For starters, first check whether the motherboard can support Windows 10. Brute forcing an uncertified Operating System installation can lead to incompatability issues. For Windows, most notably, the infamous BSOD (Blue Screen of Death).
I am installing Windows 10 Pro on an M.2 drive. System/MB supports the OS. For starters, I used the 'Restore Optimized Defaults' in BIOS, and will make changes after finishing the Windows 10 installation.
Windows would not boot without Splash screen/BIOS intervention.
Switching the Windows Boot Manager as Boot Option #1 resolved the boot issue. |
On a separate computer, plug in a blank USB drive, or one that you are willing to part ways with the data for, and visit the link below- AND THEN click 'Download Now' under 'Create Windows 10 installation media'
https://www.microsoft.com/en-us/software-download/windows10
Difference between UEFI and non-UEFI Boot Media installation selection BIOS is whether the USB drive is prefixed with 'UEFI'.
Example:
Stops here.
Unlike the non-UEFI USB option, it will now let you choose your desired Windows 10 OS from a list after selecting the drive. For this article, we are installing Windows 10 Pro.
After it finishes installation, it warns that it is automatically rebooting. Windows Boot Manager and the M.2/NVMe drive shows up at the top of Boot priority.
On default settings, it will not list the M.2/NVMe drive as a bootable disk, but will instead be identified within the Win10 Pro installer. After Windows 10 Pro finishes installing, it will show up as 'Windows Boot Manager' in BIOS with the full part number of the M.2/NVMe drive.
After selecting the Windows Boot Manager right after the Win10 Pro installation rebooted the system, it will run a disk check and repair that will look like below screen.
This takes about 3-4 minutes, and will reboot once more. Without interrupting system boot to visit BIOS Menu, it will boot straight into Windows 10 Pro Basics and Welcome screens.
Language, Keyboard Layout (Skip). It did not list any available Network ports, so I used 'I don't have internet'.
After Account, Password, and declining all services, it will take seconds to finally bring me to a desktop.
On a fresh Windows 10 install from ISO (not triggered from a Win7 upgrade or restored with whatever Boot Media comes with your original system), there are no drivers installed. Since there are no drivers installed, that means the network ports will not work natively, and that you cannot have Windows 10 search online and auto-update to fill in the drivers needed for installed hardware.
With Windows, It cannot fully detect installed hardware from a fresh installation, so I have to yet again plug a USB into another computer- this time to load drivers onto it, and then plug that USB to spoonfeed this Windows 10 Pro
Windows 10 drivers are limited on servers, and heavily varies from manufacturer to manufacturer on their respective resource page from their websites.
Filter and download drivers for chipset and LAN for Windows 10, then download both
Unpack both zip files onto a USB drive
WinRAR is free to download, in case you do not have a package utility in Windows. Personal choice, but I deleted the .zip files, since it is not needed after extracting them. |
Plug USB drive containing the Drivers onto the newly installed Win10 Pro system, install Chipset drivers first
Install Network drivers
Check for Windows Updates, reboot as necessary
I used the latest Windows ISO available on Microsoft's website, so it only took one round of updates to install and update all drivers for installed hardware for my system. Main ones to check are Graphics Card and LAN. If you installed any additional hardware to your system, then you should know what type of component it is to search the dropdown categories. If Windows cannot find your hardware driver via network, then you will need to visit that respective hardware component manufacturer's website to obtain drivers and install them manually.
Coming from default 'Optomized' BIOS settings, Windows will display the Onboard VGA as a display option. I can also use both the onboard VGA and offboard PCI-e display device (Graphics Card) simultaneously. To avoid integrated CPU graphics from being used for display or calculation, you will need to set the system to use Offboard video display in BIOS.
Whole article about it here: System boot times, and Onboard and Offboard video display channels
BIOS Onboard - Single display - Onboard VGABIOS Onboard - Dual display - Onboard VGA and Graphics Card
GPU Burn-in with Onboard/Offboard video display channels
|
For servers that are expected to be on 24/7, disable hibernation. Make sure Windows does not hibernate or power off installed hardware components after a period of time, or that any of the system's front panel (power/reset) buttons hibernate the system. Linux or Windows, hibernation mode messes with the hardware initialization of installed components, and typically results in blank screen while system remains powered on, missing devices (GPU/PCI-e), or remote connectivity issues when attempting to wake the system back up; rebooting would be necessary to have the system properly initialize hardware again.
Check in settings for whether you want the screen to turn off as well. |
Enable remote desktop in settings if you plan on installing this system at a remote location - Remote Desktop Connection (RDC/RDP). Alternatively, make sure your preference of remote dekstop connection app works with this system before racking or installing remotely.
System IT/Admin will have their security protocols or workflows that would need to be applied to the system immediately before handing off to users. If this is a home system, Windows Security is enabled, and is usually all you need. Any off-the-store-shelf computer may come with bloatware that disables Windows Security (e.g. McAfee/Norton).
Benefit of Linux, right after fresh installation, is that the onboard network ports are highly likely of already being detected, and are already work if I enabled them through Linux OS installer, or even in the settings without updating the OS at all. I could also query the installed hardware without drivers.