MECM 2309 OSD via client failing at Applying device drivers

[jlyons1983]

Hi,

I am relatively new to MECM and am having an issue with OSD via config client on all models of computers in our organization. all computers are physical computers.

They are failing at applying device drivers with the following error

interestingly enough the usb distribution is completing successfully:

attached full log

I want to add what i have tried so far, to no avail:

1. according to this link:

 https://learn.microsoft.com/en-us/answers/questions/784791/configmanager-unable-to-perform-osd-that-...

i added a command to change the registry:

reg.exe add HKLM\SOFTWARE\Policies\Microsoft\TPM /v OSManagedAuthLevel /t REG_DWORD /d 2 /f

before and after the apply operating system stage.

2. Rebuilt the task sequence with only basic commands 

why is this failing?

Is there any more information that may help?

one interesting difference that i noticed is that the config client osd is trying to set a client certificate however the usb osd is creating successfully a media certificate.

on further investigation and working according to this blog:

https://www.prajwaldesai.com/enable-sccm-enhanced-http-configuration/

I found that enhanced http is configured on the server

, however even thought the certificate is found in the certlm.msc

, the manager is not importing the certificate to the IIS:

Referring to the difference between USB OSD and CLient Config OSD the certificates only show on the client after the USB OSD and not when using the client.

The server is 2016 

I have tried to restart the server, remove and re-install the configuration, also to no avail. 

[#2 · Accepted solution]

@jlyons1983 

I finally found the solution, i noticed that the boot image wasnt up to date, so i created a new one and heh presto it worked.

Then i saw you can also update current boot images without creating new ones by updating the distribution point, that may also do the job:

[#3]

In Microsoft Intune and Configuration Manager (MECM) 2309, an OSD (Operating System Deployment) failure during the "Applying device drivers" phase may occur due to issues with driver compatibility, incorrect driver packages, or configuration errors. Troubleshooting steps include verifying driver compatibility with the OS, checking the driver package configuration, and ensuring that drivers are correctly integrated into the task sequence. For more details join now

[#4]

@marybucy79 

you are absolutely correct, but in this particular situation it is clear from the logs that the problem was with the certificate which I understand was caused due to the fact the client was not up to date in the boot image.

this also explains why there was only a problem when using the client to do OSD where as with the USB it worked