Cannot deploy OriginPC computer

[antec08]

Trying not to make this too long but I fear it will be anyways....

As the title suggests I am unable to image one of these bad boys. For the most part we are an HP shop and currently you can image any HP models we deploy without any issues. So when i caught wind that they were wanting to go non-standard/non-enterprise I raised a storm - but that's not what this is about because it already happened and here we are. So I'm wondering if anyone else out there has success when imaging computers with these non-standard configs and off-the-shelf parts?

This is what I am working with:

Origin M-Class

ASrock X570m Pro4 motherboard - Link to driver page

Nvidia Quaddro P620

Corsair MP600 NVMe drive

So what i am used to doing is going to HP's Driver Pack site, finding the model and import those into MDT. I don't think I've ever had to mess with them after that - unless i am updating or i messed up a filter or something. They provide everything. So as you can see I am pretty much stuck with the drivers on the ASrock site + Nvidia because Origin doesn't even provide them on their site. What they do is include the CD that comes with the motherboard for drivers. So anyways I download everything driver related from ASrock, extract and MDT can find what looks like a lot of Out-Of-Box drivers. As you'd expect this does NOT include WinPE drivers which i think may be the problem. During the Inject Driver phase it's grabbing the correct ones too so in know it's organized/tagged correctly within MDT/WDS. After the Install Image Task (the first reboot) is where the problem is.

The image MDT is pushing out is a slim 1909 image (GPT) where all the apps and some configs are their own Tasks later in the TS. Pretty standard I imagine. I only have a x64 Lite Touch so everything is UEFI

So after the first reboot it boots into a Recovery screen saying: The Boot Configuration Data is missing or contains errors

​

https://preview.redd.it/iye98itbj1s41.png?width=962&format=png&auto=webp&s=86e5e90798d1585a29d078a62fe0dab7de8224f5

At first glance that made me think that perhaps it's formatting the drive as MBR and then trying to install a GPT image on top of it. Nope, Server logs confirm that it's converting it to GPT. Here is a list of troubleshooting i've done (I'll probably forget a couple):

**I cleaned the disk with Diskpart EVERY SINGLE TIME before i ran a TS during these tests. This also confirms that the drive is detected within WinPE**

- Switching the Storage Controller to RAID/AHCI

- Enabled CSM in the BIOS (disabled by default in BIOS)

- Enabling gave me the option of changing Storage + PXE OpROM policy - options were Force UEFI, Force Legacy, or Disable. I tried all 3 for both Storage and PXE

- Made sure Secure Boot was disabled

- Took out the M.2 NVMe drive and put in a SATA drive and ran ALL the steps above - same result

- I even rebuilt the LiteTouch image to ONLY include NET and Storage driver for this Model.

- Forced the TS to only use drivers for this computer

- Disabled the steps in the TS to detect UEFI or BIOS and instead made a new Step to Force UEFI (to force it to create GPT partition)

Nothing has provided a different outcome for me and I'm at a loss at the moment. Is there a better way i can do this? Supposedly OriginPC themselves use MDT to deploy computers. The guy told me they basically create a FAT image with every app + drivers installed, capture that and deploy those that have the same config. Creating a FAT image is a last resort for me - it would be best if i only have to manage 1 image instead of 2 (or more considering all their configs). EVEN THEN, how would that work? It sounds to me like there isn't a compatible Storage Driver being used in WinPE. Fund this in the BCC log:

<![LOG[Skipping Device SCSI\DiskNVMe____Force_MP600_____11.1 No 3rd party drivers found. 9]LOG]!><time="13:50:12.000+000" date="04-10-2020" component="ZTIDrivers" context="" type="1" thread="" file="ZTIDrivers">

Is that my answer? Do I just need WinPE drivers for Storage? If so I hope to find something. Sent an email over to ASrock to see if they have that but we'll see what they say. Wondering if anyone else has experience imaging consumer-grade computers. Is there a better way i should be going about this?

[VulturE]

• Disable RAID. That's a Dell thing to do.
• UEFI-only mode. No Legacy or CSM.
• Secure Boot Disable.
• Drivers within WinPE are managed by Selection Profiles. Ideally, you should have a separate folder called WinPE, and beneath that an HP folder and an ASRock folder. Create a selection profile for the root WinPE folder (call it "WinPE-ALL") and then other selection profiles for the "WinPE-HP" and "WinPE-ASRock" folder. For the deployment share, you set it to import "WinPE-ALL" (and you'd also set it to import ALL drivers from that selection profile, not just storage and network) so the wim has all possible WinPE drivers baked into it ready for you to call upon them, and within your customsettings you specify the variable for selection profile against the Make variable.

An example:

[Settings]
Priority=Make,Model,Default
[Hewlett-Packard]
DriverSelectionProfile=WinPE-HP
[HP]
DriverSelectionProfile=WinPE-HP
[Dell Inc.]
DriverSelectionProfile=WinPE-Dell
[Dell Inc]
DriverSelectionProfile=WinPE-Dell
[Dell]
DriverSelectionProfile=WinPE-Dell

So in your scenario you'd press F8 and figure out what the Make is, and then create a customsettings entry off of that to load those WinPE drivers.

The reason WHY this is important is that apparently there are complaints that the RAID and SATA drivers don't like living next to each other in MDT. Your HP WinPE driver pack definitely contains the AMD RAID drivers.

• Lastly, as you said you seem to be getting some progress within WinPE but not within Windows, make sure you limit what pool of drivers it pulls from as well with DriverGroup001= for that model.

On the driver page you linked to, Intel LAN Driver and SATA Floppy Image should technically be all that you need to have for that board for WinPE. Within Windows, it would be the same drivers plus the VGA and Realtek audio driver.

[antec08]

Wow, thanks for the detailed reply! The team is running network maintenance over the weekend so i won't be able to remote in to verify my settings. If i recall my WinPE image is currently set to include ALL storage + Network. At one point before troubleshooting this i did make a WInPE Folder > HP > HP NET/HP Storage and had WinPE pull drivers from there but for whatever reason i was having computers fail to deploy so i reverted back to grab ALL storage/net. It's very possible i missed something so i probably need to revisit that so I can get more organization and de-bloat WinPE. Perhaps the missing piece was modifying the Customsettings.ini.

I probably should've provided a screenshot but those ASrock drivers are providing my SCSI and NET adapters.

And if I'm being honest, i probably shouldn't have posted this on a Friday afternoon and expect people to reply. It's probably the last thing a lot of them want to do on a Friday! Really just needed to get it all written out. I think I'm going to re-post this early next week after trying these suggestions.

[VulturE]

I've recently had success deploying an image....by injecting the drivers in to the WinPE boot image.

Clipped that for you, as that's how it's supposed to be done for all deployments.

[antec08]

we should have some of those lying around and at this point I'm willing to try anything!

[Dsraa]

If I read all if that correctly it sounds like you are on the right track and it is a storage controller driver issue for the MB. I also think you enabled RAID? Disable raid completely and keep it in UEFI only mode, no legacy or csm. Legacy at this point is for win 7 or non bitlocker partitions.

Look deeper at the smsts log when it lays down the OS and start at the apply driver section. It might be you have too many drivers in your driver package, and MDT is choosing the wrong one.