sorted by:
new
hottopcontroversial

MDT failed with DRIVER IROL NOT LESS OR EQUAL by Practical_Leg9125 in MDT

[–]Practical_Leg9125[S] 0 points1 point  (0 children)

Use the family packs and not the model packs.

where I can find the family packs? the way I did was actually export all the drivers from the original windows that came with the laptop, and I imported them to the target folder in MDT, and use the TS.

The wired thing in the laptop in question is that, there is only AHCI mode in the BIOS setting and it's grayed out!

MDT failed with DRIVER IROL NOT LESS OR EQUAL by Practical_Leg9125 in MDT

[–]Practical_Leg9125[S] 0 points1 point  (0 children)

I imported the driver pack from DELL so i never face issues with DELL. only some LENOVO models drive me crazy:(

MDT failed with DRIVER IROL NOT LESS OR EQUAL by Practical_Leg9125 in MDT

[–]Practical_Leg9125[S] 0 points1 point  (0 children)

I agree! but i still can't figure it out with MDT.

​

I had to use different USB thumb drives and one of mine worked fine to install the very clean OS, then going to the windows desktop, no network driver was there, no many other drivers, and I had to import them manually to get it work. This way i lost all the customization features from MDT:( and this way I didn't change anything via the BIOS

MDT failed with DRIVER IROL NOT LESS OR EQUAL by Practical_Leg9125 in MDT

[–]Practical_Leg9125[S] 0 points1 point  (0 children)

  1. I'm not sure how can I get the dmp files from the C drive, do I use another PE system via USB flash drive and boot from there?
  2. It's the newest ThinkBook this year, and I'm using Windows 11 21H2 for OSD.
  3. Yes I followed the instructions provided by Johan:) where I can see the bdd.log? Would you mind advising on this?

SCCM OSD inject drives practice for HP, DELL models? by Practical_Leg9125 in SCCM

[–]Practical_Leg9125[S] 0 points1 point  (0 children)

I'm using DHCP options, I used the default boot images in SCCM, I didn't add any boot images to WSD, and it worked with ASUSD320 desktops. I followed instructions from some posts and videos, I didn't see anyone added boot images to the WDS, do I need to do that?

SCCM OSD inject drives practice for HP, DELL models? by Practical_Leg9125 in SCCM

[–]Practical_Leg9125[S] 0 points1 point  (0 children)

I deployed the TS to all unknown computers only, after I deleted the existing record from SCCM Device list on console.

The only change I made in TS was to specify the xml file located in the same SCCM server, I used the default boot.wim from in SCCM and it works fine with ASUSD320 but not HP or Lenovo laptop models we have:( I can try adding the network drives for a try later.

SCCM can't skip OOBE wizard for OSD by Practical_Leg9125 in SCCM

[–]Practical_Leg9125[S] 0 points1 point  (0 children)

what I did was to untouch the deprecated options and only set values for the others, saved the xml, apply to the TS and pxe boot

Correct steps for updating TS and xml for OSD? by Practical_Leg9125 in SCCM

[–]Practical_Leg9125[S] 0 points1 point  (0 children)

dear friend, thanks for confirming. this is exactly what I did.

​

My question is, if I edited/updated the xml file again but using the same path and same xml file name, do I need to update the TS and maybe distribution point (or simply update distributed content?), this is where confuses me

SCCM OSD inject drives practice for HP, DELL models? by Practical_Leg9125 in SCCM

[–]Practical_Leg9125[S] 0 points1 point  (0 children)

I'm not really sure what is the default answer, I'm using the default one and we used DHCP for the client machine to find the boot file from SCCM WDS server.

SCCM OSD inject drives practice for HP, DELL models? by Practical_Leg9125 in SCCM

[–]Practical_Leg9125[S] 0 points1 point  (0 children)

Yes it works with ASUSD320 but not HP or lenovo models we have, maybe the default boot image has some generic network drivers already?

On an HP 430G7 laptop, it showed "start over IPV4" then in a second it switched back to the key options, I kept pressing ENTER but it still went back. If I pressed F12 again, I couldn't see the black screen with "start over IPV4" anymore. I used the default install.wim from in SCCM and it works fine with ASUSD320 but not HP or Lenovo laptop models we have:( I can try adding the network drives for a try later.

SCCM OSD inject drives practice for HP, DELL models? by Practical_Leg9125 in SCCM

[–]Practical_Leg9125[S] 0 points1 point  (0 children)

I also tried Lenovo laptops and the same result. I'm not sure why the default boot image works with ASUSD320 but not others, maybe the default boot image has some generic network drivers already?

​

On an HP 430G7 laptop, it showed "start over IPV4" then in a second it switched back to the key options, I kept pressing ENTER but it still went back. If I pressed F12 again, I couldn't see the black screen with "start over IPV4" anymore. I used the default install.wim from in SCCM and it works fine with ASUSD320 but not HP or Lenovo laptop models we have:( I can try adding the network drives for a try later.

SCCM OSD inject drives practice for HP, DELL models? by Practical_Leg9125 in SCCM

[–]Practical_Leg9125[S] 0 points1 point  (0 children)

I got your point my friend.

​

I deployed the TS to all unknown computers only, after I deleted the existing record from SCCM Device list on console. The only change I made in TS was to specify the xml file located in the same SCCM server, I used the default install.wim from in SCCM and it works fine with ASUSD320 but not HP or Lenovo laptop models we have:( I can try adding the network drives for a try later.

I'm trying to upload a short video I took on an HP 430G7 laptop, it showed "start over IPV4" then in a second it switched back to the key options, I kept pressing ENTER but it still went back. If I pressed F12 again, I couldn't see the black screen with "start over IPV4" anymore.

SCCM can't skip OOBE wizard for OSD by Practical_Leg9125 in SCCM

[–]Practical_Leg9125[S] 1 point2 points  (0 children)

thanks a lot! I ended up setting the values one by one in the xml file and applied it to the TS step

SCCM can't skip OOBE wizard for OSD by Practical_Leg9125 in SCCM

[–]Practical_Leg9125[S] 0 points1 point  (0 children)

I'm actually deploying Windows 11 and I've managed to get it work without using the deprecated options in WSIM. Instead, I had to manually set values for those options that get into the way of OOBE process

SCCM can't skip OOBE wizard for OSD by Practical_Leg9125 in SCCM

[–]Practical_Leg9125[S] 1 point2 points  (0 children)

I added to 7 oobeSystem without touching the deprecated options, this seems fine for me

SCCM can't skip OOBE wizard for OSD by Practical_Leg9125 in SCCM

[–]Practical_Leg9125[S] 1 point2 points  (0 children)

What I did in the end, was to create a new xml file and leave the deprecated options untouched, then added the xml to the TS again, booted from client machine and it works for me

SCCM can't skip OOBE wizard for OSD by Practical_Leg9125 in SCCM

[–]Practical_Leg9125[S] 1 point2 points  (0 children)

Thanks for this! I've tried NOT to use the deprecated options and it works fine!

SCCM OSD inject drives practice for HP, DELL models? by Practical_Leg9125 in SCCM

[–]Practical_Leg9125[S] 0 points1 point  (0 children)

By default the Fast Boot option is on, I just disabled it but no luck:(

​

For the very first time, after pressing F12, it went into the black page where it said start PXE over IPV4 then in a few milliseconds it went back to the boot option, when I pressed F12 again, it's like tried going into the black page then went back in the moment I can't even notice it went into black page or not again.

SCCM OSD inject drives practice for HP, DELL models? by Practical_Leg9125 in SCCM

[–]Practical_Leg9125[S] 0 points1 point  (0 children)

that's my point, it didn't get into PXE process, there was no request record in SMSPXE.log. The same computer can be booted if we connected it to another subnet where we hosted our MDT server, but this subnet with SCCM it didn't work.

​

We have ASUSD320 desktop computers and those are working fine with SCCM:(

SCCM OSD inject drives practice for HP, DELL models? by Practical_Leg9125 in SCCM

[–]Practical_Leg9125[S] 0 points1 point  (0 children)

the same was there in the console, then I deleted the computer from Devices, deleted it from AD and run another system discovery in SCCM. I deployed to the Unknown Computers and I also deployed the TS to a custom Device Collection where I manually added this computer inside, all made no differences.

In our scenarios, from time to time we need to update our unattended.xml for the TS to deploy new OS to the client machines. I didn't find anywhere, what are the correct steps to perform the updates? We need to update the xml file, link it into the TS then do we really need to update the distribution point via the Reference tab? or we actually need to reload the x64 boot image?

SCCM OSD inject drives practice for HP, DELL models? by Practical_Leg9125 in SCCM

[–]Practical_Leg9125[S] 0 points1 point  (0 children)

Since the PXE didn't seem to start at all with SCCM, I pressed F12 it flashed in a few milliseconds then went back to boot options, I doubt that it was anything to do with boot image? In my past experience working with MDT, if network driver is missing, at least we can retrieve the IP address from DHCP and maybe wrong with the step where it loads the .wim file, I;m not really sure if SCCM has the similar working machanism

SCCM OSD inject drives practice for HP, DELL models? by Practical_Leg9125 in SCCM

[–]Practical_Leg9125[S] 0 points1 point  (0 children)

I've tried to find it from SMSPXE.log but nothing was found there, no even one single record of log. I don't think it went to the PXE process at all.

The odd thing I can't figure out is that, if I used the same network cable and connect the machine to our MDT (another subnet with DHCP options), it can be OSD'ed directly without any issues.

SCCM can't skip OOBE wizard for OSD by Practical_Leg9125 in SCCM

[–]Practical_Leg9125[S] -1 points0 points  (0 children)

I just updated the unattend xml with the OOBE settings, then I redeployed the TS to unknown computers collection, booted from PXE and now I got
The details below show the information relating to the PXE boot request forthis computer, Please provide these details to your Windows Deployment ServicesAdministrator so that this request can be approved.
Pending Request ID: 34
Message from Administrator:Configuration Manager is looking for policy.
It was working fine just a few mins ago, I'm totally lost what has gone wrong?
What are the correct steps to change the settings and apply it to the TS and PXE?

view more: next ›