PENDING Cannot provision bare-metal device with Windows 11 using Microsoft Configuration Manager.

[utcl_ken]

This is the first time I have attempted to install or use MCM.

The goal of the project is to be able to install a fresh image on bare hardware. This is a task we do between 5 and 50 times a week.

I have installed Microsoft Endpoint Config Mgr 2203 on SQL 2019 on Server 2022.
Also installed MDK (6.3.8456.1000), ADK (10.1.22621.1) and the Windows PE extensions for ADK (10.1.22621.1).
IIS is installed.
WSUS is also installed, as I read it was required. I have done no configuration in WSUS other than install and allow it to do the automatic configuration.

All software resides on 1 server. Server and target are on the same IP v4 subnet.

I have Wireshark and SSMS available.

I downloaded the Windows 11 installation ISO from Microsoft.

I was able to create:

1. A boot image
2. An Operating System image
3. A driver pack (removed from Task Sequence for simplified testing.
4. A bootable USB (from Create Task Sequence Media)
5. A task sequence to bind them together.

I can boot the target machine using the media created.
It loads Configuration Manager, then a few seconds later shows "Welcome to the Task Sequence Wizard"

I click next
I am presented with a Task Sequence Wizard that allows me to change network settings. None should be required, so I click Next. I then see the Wizard showing me my Task Sequence. I select it and click Next.


A few seconds later the Task Sequence Wizard shows the error:
"Failed to Run Task Sequence"

The task sequence cannot be run because the program files for 10000008 cannot be located on a distribution point. For more information..."

I can see with Wireshark that the target:
1. Gets an appropriate IP address, and
2. Communicates with the correct Distribution Point

When I check the Management server, I see that 10000008 is the Windows 11 boot image. I check the status and determine that it is, in fact, on the DP and is up-to-date.

I followed the procedure here and then updated my boot image.
I then regenerated the boot media. After confirming that all updates to the DP were complete, I rebooted the target using the new boot media.

I see the following errors:
"Content location request for 10000008:5 failed. (Code 0x80040102"
"Failed to resolve PackageID=10000008"
"Failed to resolve selected task sequence dependancies. (Code 0x80040102)"
"ThreadToResolveAndExecuteTaskSequence failed. (Code 0x80040102)"


If I allow the machine to PXE boot, rather than boot from media, I see the following in SMSPXE.log on the DP:
<![LOG[TFTP: 172.16.54.178: request for smsboot\10000008\x64\wdsmgfw.efi.]LOG]!><time="10:03:32.158+360" date="03-27-2024" component="SCCMPXE" context="" type="1" thread="7160" file="tftpserver.cpp:52">

I assume that "smsboot\10000008\x64\" is a logical path, and wdsmgfw.efi is the file it is failing to find. I can confirm that wdsmgfw.efi does not exist anywhere on the server.
I suspect that is my real problem.

Clearly I have done one or more things incorrectly. I would appreciate any assistance resolving these issues.

 

[utcl_ken]

I started over, using this as a guide.
Everything worked up until step 8.
After the machine starts Configuration Manager, I saw the same errors.

First it was missing 1000002. I determined that this was the Configuration Manager Client Package. Even though the Distribution Status shows the package is available on the DP. I disabled the "Setup Windows and Configuration Manager" step to troubleshoot.

Now it shows it is missing 1000004. This is the Boot Image. It too shows that it available on the DP.

 

[utcl_ken]

I started over, using this as a guide.
Everything worked up until step 8.
After the machine starts Configuration Manager, I saw the same errors.

First it was missing 1000002. I determined that this was the Configuration Manager Client Package. Even though the Distribution Status shows the package is available on the DP. I disabled the "Setup Windows and Configuration Manager" step to troubleshoot.

Now it shows it is missing 1000004. This is the Boot Image. It too shows that it available on the DP.

I attempted to monitor the process using this, but there are no entries after the creation of the deployment.
Last message:
User "DOMAIN\user" created a deployment named "DeployWin11Pro_10000013_AllUnknownComputers" (1002000F) deploying program "*".


I have attempted this Task Sequence 3 times since it was deployed. No entries in the log.

 

[utcl_ken]

I am not sure what is up with this site and why this submission is still "Pending".

Anyway, after being told repeatedly on the internet that this was THE site to get help with SCCM, and trying multiple times to resolve the issues with my site, I blew it all away and started fresh using blog posts from this site.
It was a dismal failure. Same errors. Same warnings. Same frustration.

I then blew it all away AGAIN, and rebuilt from the ground up without using any information from this site.
Worked 100% the first time.

Going through the blog posts I used from THIS site, I can see that a few steps were missed.

 

[utcl_ken]

Oh, well.
See all y'all on some other forum.