- Notes, cautions, and warnings
- Important information about Microsoft Windows Server 2016
- iDRAC, BIOS, system firmware, RAID controller driver versions
- Systems Management support for Microsoft Windows Server 2016
- Multilingual operating system media for Windows Server 2016
- Pre-Installed Virtual Machine
- Retrieving Integrated Dell Remote Access Controller (iDRAC) IP address
- Operating system support matrix for Dell PowerEdge servers
- Known Issues
- Administrative template errors occur when starting local group policy editor
- I/O errors or unresponsive virtual machines
- Cluster VD errors logged during I/O operation
- Bus type of NVDIMMs displayed as Unknown
- Windows Blue Screen error while booting from iSCSI target and Intel i350 initiator
- Drivers without inbox support
- Operating system name is displayed incorrectly
- Unable to convert Windows Server Core to OS with Desktop Experience
- Unable to boot into Windows Server 2016 if Host Guardian Hyper-V Support or Device Guard is enabled on PERC H330
- When NVMe device is attached to a running VM, the device is not enumerated
- Unable to modify or create TPM password, system displays error message
- Getting help
Microsoft Windows Server 2016 for Dell PowerEdge Systems Important Information Guide
I/O errors or unresponsive virtual machines
- Description
- The issue occurs on Dell EMC hardware that is configured for failover cluster and have attached shared storage hosting multiple virtual machines with Multipath I/O (MPIO) enabled. If you perform multiple removals and installations of the PowerEdge MX5016s storage expander module, or if you remove and install the PowerEdge MX5000s SAS I/O module, I/O errors occur and the virtual machines goes to unresponsive or failed state. This issue may cause the Cluster Shared volume to go to failed state.
- Workaround
- For servers running Shared Storage Cluster on Windows Server 2016, install Microsoft KB4457127 or a latest update package from Windows Update service on all the nodes that are part of the cluster.
- Create a registry key, Reg_DWORD with a value 0x1 in the following registry path on all the cluster nodes:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\StorPort\QoSFlags.
- Restart the nodes to enable the registry key.
- Affected Systems
- PowerEdge MX7000 chassis with PowerEdge MX740c or PowerEdge MX840c compute nodes and PowerEdge MX5016s storage sleds
- Any Rx4x or Tx4x PowerEdge servers with external storage array attached
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please select whether the article was helpful or not.
Comments cannot contain these special characters: <>()\