PENDING SCCM Deployment of Windows 10: Error Code 0xc000000f

[TOTO JDD]

Hello,

I just configured a SCCM 1710 server to deploy Windows 10 with MDT integration.

1. Here are the configurations made on the SCCM server

• Import the OS image (.WIM file) into the SCCM console and its distribution on the distribution point.

• Distribution of default boot images (x64 and x86) on DP

• Enable PXE support for clients (unknown computer support) in the DP property box

• Create TS in SCCM with "Create MDT Task sequence", publish the TS at the distribution point, deploy the TS on the collection of unknown computers

2. Enable DHCP Options (066 SCCM Server FQDN Boot Server Hostname and 067 Boot file name \ SMSboot \ x64 \ wdsmgfw.efi)

3. I booted a new computer in PXE and got the following message:

Windows Deployment Services encountered an error:

Error Code: 0xc000000f



4. This is the SMSPXE.log file



How to fix this error?

 

[TOTO JDD]

Hello,
Does somebody have an orientation to solve this problem? SCCM OSD Windows 10 with MDT integration return an error as you can see above.

Cordialy, ...

 

[Prajwal Desai]

Have you tried the steps mentioned in this post - https://prajwaldesai.com/sccm-error-code-0xc000000f-boot-configuration-data-missing/

 

[TOTO JDD]

Have you tried the steps mentioned in this post - https://prajwaldesai.com/sccm-error-code-0xc000000f-boot-configuration-data-missing/

Hello Prajwal Desai,

Exactly, I followed these steps but without success. In another forum offers not to set the options 66 and 67 DHCP and make an IP helper from the client network to the PXE server and an IP helper from the client network to the DHCP server.

Do you have an idea for that?

Cordialy.

 

[Prajwal Desai]

In another forum offers not to set the options 66 and 67 DHCP and make an IP helper from the client network to the PXE server and an IP helper from the client network to the DHCP server.

If you have got a single VLAN with just one DHCP server, you need not configure option 66,67 and no OP helper address is required. If you have multiple VLAN's you can either use DHCP options or use IP helper address instead that points to your WDS server.

 

[TOTO JDD]

Hello,

Finally I managed to start the PXE and execute my task sequence successfully.

The problem was because the distribution point and the management point were configured to use https but it was the self signed certificate that was configured on the distribution point. As expected, the HKLM\Software\Microsoft\SMS\DP | ManagementPoints value is empty. This registry key would need to have a value like https://ServerName.DomainName

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\DP]
AlgID = 26115
BindExcept =
…
ManagementPoints =

To resolve this problem, I correctly configure the distribution point with the PKI certificate

Before testing the deployment, I was reassured that the client computer does not exist in the sccm console as the deployment of the task sequence was done on the collection All unknown computers.

Please find the procedures I used for the KPI certificate through these links:

• https://prajwaldesai.com/deploying-the-client-certificate-for-distribution-points/
• https://prajwaldesai.com/deploying-the-client-certificate-for-windows-computers/

Thank you all for your guidance.