Installation, Drivers and Software
Azure Stack HCI Trusted Enterprise Virtualisation Solution Brief
Virtualization-based security (VBS) is a key component of the security investments in Microsoft Azure Stack HCI to protect hosts and virtual machines from security threats.
The attached solution brief illustrates how you can leverage VBS with Microsoft Azure Stack HCI and the Stone Computers Elysium SF (Hybrid Acceleration Series)
Booting from and Using UEFI / GPT Partitions
If your RAID or disk volume is larger than 2TB, you will need to use one of the following methods to use all of the capacity and to be able to boot from the volume:
For more information, please see attached the Intel GPT white paper, available here, or attached.
Selected models of servers come with or can be upgraded to include a remote management module, such as the Intel RMM4. Use the instructions below to setup your remote management module.
You will need the following:
To connect to the management console, use a web browser and connect to the IP address or hostname you specified.
You will need to have Java installed to use the remote KVM (keyboard/video/mouse) and media redirection.
Getting More Help
For more information, see the Intel RMM4 user guide or contact Stone support.
Intel RAID Manual
Intel have produced a manual which covers the setting up and basic maintenance of their RAID systems, primarily those based around the LSI RAID stack. This includes controllers such as the RMS25CB080 and RS2BL080.
The manual can be downloaded here, or attached.
Stone Equinox / Storage Spaces Direct (S2D) Hyper-V Cluster UPS Shutdown Script
Storage Spaces Direct (S2D) nodes provide disk resiliency to each other as part of the storage network.
When an extended power outage occurs that exceeds the available battery runtime, it is important that a managed shutdown process is used:
A software package is now available to provide this shutdown facility. It is compatible with all UPS software that supports shutdown via a script.
A. Install your UPS Software as normal
Its a good idea to install your UPS Software first, as depending on the type of software installed, the software will be configured for you by the installation script.
B. Manual creation of a domain service account. Optional: If you do not follow this step to create a S2D Management domain account called svcUPs, the installation script will do it for you.
Check for a scheduled Task called UPShutdown in the \MANAGEMENT folder, in Task Scheduler
You should install your UPS software before running the UPS Shutdown script installer, as the script installer may be able to configure your software for you.
After installation, we recommend that manually check your UPS Software shutdown settings
Software Supported for Automatic Configuration
Manual Configuration / Verifying your UPS Software Shutdown settings
You should arrange full systems downtime to test the shutdown sequence. You can then test the software either from the UPS software, or by running StartShutdown.CMD from an Administrative command prompt
All of the settings in ShutdownControl.txt / ShutdownControl.PS1 are shown below.
# Stage 1 - Shutting down Local VMs on this host Only
# if $SaveLocalVMs=$true
# Stage 2 - Start shutting down the Global cluster
SEL Troubleshooting Guide
Intel produce the SEL guide to help you understand the contents of the SEL and SYSINFO Logs.
For example, translate CPU numbering used in the logs to the numbering used in the motherboard manual or TPS
Technical Product Specification Documents
Intel produce these TPS documents for each family of server or workstation motherboard. Use these documents to:
Note 1: Intel server boards often have slightly different names for the number of LAN ports that they have. For example, the S2400GP2 has two LAN ports, and the S2400GP4 has four LAN ports, and they both belong to the S2400GP Family, for which you can use the S2400GP Technical Product Specification document.
Note 2: Always check the Intel web site for updated documents.
Intel Server Systems
Intel Server Systems include Intel server or workstation motherboards. The second part of the Intel Server System model code indicates which motherboard is fitted. For example, the R2000GZ series of Intel Server system indicates that it includes an S2600GZ motherboard. The R2000GZ series includes different 2U models with different drive bay configurations.
Spares / Accessories List and Configuration Guide for Server Systems
These guides are available for Intel Server systems to allow research into the spare parts and accessories that are available for that model family.
S2600GZ / GL - R1000GZ/GL Server System and R2000GZ/GL Server System - Spares / Accessories List and Configuration Guide
S2600WT - R1000WT Server System and R2000WT Server System - Spares / Accessories List and Configuration Guide
Newer versions of the Realtek LAN Driver, from around mid-2014 onwards, may fail to import into Windows Deployment Services, either WDS 2008R2 or WDS 2012.
WDS reports that the package addition failed. However, no actual error code or meaningful reason for the failure is displayed.
The root cause appears to be a problem with the WDS Jet Database and either the size of the Realtek LAN driver, or some particular information inside the driver INF. If you use the WDS Powershell utilities to try and import the driver an error code is return which indicates that a database error is being generated, with a record being "too big".
There is one full resolution for this issue and three alternatives should your situation require it. However with the release of the April 2016 Realtek driver, only the full resolution should be required.
As of April 2017, some x64 versions of the Realtek driver, even the WinPE version, do not import into WDS for Server 2008R2. There is no resolution for this apart from upgrading your Server infrastructure or the work-arounds below.
Overview of Adding a Driver to a WIM file
Imagex /mountrw "d:\wimwork\boot.wim" 1 d:\output
Dism /Image:d:\output /Add-Driver /Driver:d:\drivers /Recurse /ForceUnsigned
Imagex /unmount /commit d:\output
Note: Always ensure that the finished, built machine has the latest Realtek network driver on it, before handing it over to the user. The temporary 2013 Realtek network driver should not be left running on deployed machines.