NS204i-u not recognized as disk 0 by diskpart, making MDT deployment impossible

[RadioFr]

Hi,

Until now, we were deploying Windows Server 2019 on all our servers (mainly ProLiant Gen10 units) without any problems using Microsoft MDT.
We have recently acquired a ProLiant DL360 Gen11 equipped with NS204i-u boot device and a MR416i-o storage controller.
Problem: Microsoft MDT (actually the WinPE running the MDT task sequence) always tries to deploy the OS on one of the disks controlled bt the MR416i and not on the NS204i-u boot device, which prevents the server from booting at the first boot following OS image copy.
It is apparently due to the fact that MDT always tries to deploy the operating system image on the disk presented by diskpart as disk 0 which is never the case with the virtual volume presented by the NS204i-u boot device.

How can we force the boot device virtual disk do be seen as disk 0 so that MDT could select the right disk to deploy Windows?

Thanks for your help.

[BPSingh]

Greetings

Please try these steps and check if it works.

-> From the System Utilities screen (F9), select System Configuration > BIOS/Platform Configuration (RBSU) > PCIe Device Configuration Options, select the MR416i and disable it. 
-> Reboot once for the changes to take place. 
-> Install the OS and test if it boots as expected. 
-> Later you can re-enable the MR416i using the same steps as mentioned above. 

[support_s]

Hello,

Let us know if you were able to resolve the issue.

If you have no further query, and you are satisfied with the answer then kindly mark the topic as Solved so that it is helpful for all community members.

Please click on "Thumbs Up/Kudo" icon to give a "Kudo".

Thank you for being a HPE valuable community member.

[Davidaz1]

@BPSingh We are having the same issue with MDT  and the drives, controllers, etc. We have thrown everything at the server and it will not image.  We are also getting this from the Microsoft deployment toolkit, aka s screenshot.

[RadioFr]

Hello,

The issue is partially resolved.

We are able to deploy the Operating System, but whenever we re-enable the MR416i controller in the BIOS, it is not recognized by the server because the driver and tools cannot be installed if the device is PCIe disabled.

We therefore have to install the MegaRaid driver and tools after the MDT deployment, because of the fact that MegaRaid cp cannot be predeployed when the controller is disabled in BIOS.

Regards.

[BPSingh]

Thank you for the update.

I understand that you needed to use the workaround mentioned above to partially resolve the issue. If the controller firmware and BIOS are running on the latest revision, please log a support case to have this investigated further.