Precautions when using Windows Server 2016

When installing Windows Server 2016, the use of a firmware version BC17031 or later is recommended.
Please refer to "Software & Operating Systems(Drivers & Downloads)"
for more details.

Event Log may record the following error in a high workload.

Log name: System
Source:IPMIDRV
Event ID:1004
Description: The IPMI device driver attempted to communicate with the IPMI BMC device during normal operation.
However the communication failed due to a timeout. You can increase the timeouts associated with the IPMI device driver.

This can be avoided by increasing the timeouts.

• How to increase the timeouts
  Add entry to following registry subkey.

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\IPMI

Name: CommandWaitTimeoutPeriod
Data Type: REG_DWORD
Data Value(hexadecimal): 3938700

Windows Event Log may be logged after installation of Windows Server 2012 R2 by the Enable kit through it has been authenticated in the System Properties or slmgr command.

Log Name:Application
ource:Security-SPP
Event ID:1058
Description:Installation of the Proof of Purchase from the ACPI table failed.
Error code: 0xC004F057

Such event log recording does not affect the system.

Windows RE(Windows Recovery Environment) may start when the problem occurs at a system boot for Windows.
After Windows RE menu is displayed, click [Continue] restart the system.
If you don't want to start Windows RE you can prevent start of Windows RE by REAgentC.exe /disable command.
Please visit the Microsoft website for detailed information.

Event Log may record the following error at a system boot.

Log name:System
Source:Application Popup
Event ID:56
Description: Driver PCI returned invalid ID for a child device (xxx).

Such event log recording does not affect the system.

Event Log may record the following error at the Performance Monitor start.
Log Name:Application
Source:Microsoft-Windows-Perflib
Event ID:1008
Description:The Open Procedure for service ""BITS"" in DLL ""C:\Windows\System32\bitsperf.dll"" failed. Performance data for this service will not be available. The first four bytes (DWORD) of the Data section contains the error code.

This problem occurs when BITS (Background Intelligent Transfer Service) has been never started.
The error is not recorded if BITS starts by manual operation or Windows Update starts.

Event Log may record the following error during the reboot/power-onoff.
Log name: System
Source:DriverFrameworks-UserMode
Event ID:10114
Description: The UMDF reflector was unable to complete startup because the WUDFPf service was not found. This service may be started later during boot, at which point Windows will attempt to start the device again.

Log name: System
Source:Kernel-PNP
Event ID:219
Description: The driver \Driver\WudfRd failed to load for the device SWD\WPDBUSENUM\_??_USBSTOR#Disk*.

(Note)""*"" is a part of a character string representing an arbitrary device name.

In case that there is no warning on the device manager after recording EventID:219, such event recording does not affect the system.

Please visit the Microsoft website " Event ID 219 is logged when a device is plugged into a Windows-based system " for detailed information.

When executing SIGVERIF.txt for the driver signature verification,
regarding the version of Fujitsu driver and third party driver, ""none"" may be recorded on the outputted SIGVERIF.txt.
Such recording does not affect the operation of both drivers.

The version of Fujitsu driver and third party driver can be confirmed at the property picture of each driver (Driver tab) which appeared on the device manager.

PRIMEQUEST does not support the new feature in Windows Server 2016 "Storage Spaces Direct."

When using the new feature "Shielded Virtual Machine", please apply the cumulative Update KB3213522 provided on 20th December, 2016 or any later cumulative updates.

Due to Ipmidrv.sys issue for Windows Server 2016, the blue screen(0x139) may be displayed. This problem may happen once out of 40 or 50 times.

This can be avoided by applying patch :
"KB4015438" provided on 21st March, 2017 and or any later cumulative updates.
Please visit the Microsoft website for detail information.

The iSCSI boot is not available in Windows Server 2016.