Hi, I'm currently configuring my WDS with MDT so I can deploy Windows 10. I'm using VMs to test out different configurations, but suddenly everytime I try to deploy Windows 10 it ends up bluescreening and giving the INACCESSIBLE_BOOT_DEVICE error code. This only happens when I deploy on a VM. It works fine on a physical machine. Any suggestions?
> That would mean that somehow MDT doesn't inject the needed driver or am I completely wrong?
It means that there is a mismatch between the injected driver and the actual config of the VM.
Maybe you have injected the LSI-SAS driver but configured the VM to use the normal LSI controller.
WDS with MDT
Sorry, but what does this mean?
but suddenly everytime I try to deploy Windows 10 it ends up bluescreening and giving the INACCESSIBLE_BOOT_DEVICE error code.
This often means the driver for the storage controller isn't properly installed.
WDS with MDT
Sorry, but what does this mean?
Windows Deployment Server with the Microsoft Deployment Toolkit.
but suddenly everytime I try to deploy Windows 10 it ends up bluescreening and giving the INACCESSIBLE_BOOT_DEVICE error code.
This often means the driver for the storage controller isn't properly installed.
That would mean that somehow MDT doesn't inject the needed driver or am I completely wrong?
That would be my assessment. What is the resulting configuration of the VM it's building? What storage controller type does it have?
> That would mean that somehow MDT doesn't inject the needed driver or am I completely wrong?
It means that there is a mismatch between the injected driver and the actual config of the VM.
Maybe you have injected the LSI-SAS driver but configured the VM to use the normal LSI controller.
It uses LSI SAS. I've tried the others as well to no avail.
Your deployment tool isn't configuring the correct drivers in that case. It's far simpler to just deploy from an existing vSphere template, then you won't have to worry about this.
It means that there is a mismatch between the injected driver and the actual config of the VM.
Turned out I managed to import some disk controller drivers from lenovo's pages which was causing the problem. Fixed now, thanks for the help!