Windows 10: PXE Boot Issue After Upgrading SCCM to Version 2304

After upgrading to SCCM 2304, I encountered a PXE boot issue where downloading the smsboot\x64\wdsmgfw.efi file now takes over 10 minutes, whereas it previously completed in less than 5 seconds. Additionally, when deploying 20 machines simultaneously, the RAM usage on the distribution point reaches 100%, primarily due to the svchost.exe process WDS service. As a result, the deployment of new hire machines is currently blocked. This is an urgent issue, and I would appreciate your assistance in resolving it.

:)

 

sccm pxe boot destroys oobe

Hi Mike,

I am Dave, I will help you with this.

I apologize, Community is just a consumer forum, due to the scope of your question (SCCM and PXE) can you please post this question to our sister forum on Microsoft Q&A (The IT Pro Forum)

Over there you will have access to a host of SCCM and PXE experts and will get a knowledgeable and quick answer to this question.

https://docs.microsoft.com/en-us/answers/index....

 

sccm pxe boot destroys oobe

Configuration Manager 2107

Windows 10 21H2

Problem:

When I use dism to deploy a captured wim image, I could get oobe and the user has to create their username and password etc to use the new computer.

However, when I deploy the same wim image using sccm and pxe, I cannot start with oobe no matter what. I always end up with starting with a pre-built user account or no user account.

How can I deploy the wim image using sccm and pxe so that the target computer starts with oobe instead of either a fixed user account (have to know the password) or no user account (cannot log in)?

 

PXE BOOT and Defrag

Fog is an awesome utility we used it to image over 200 machine over at place I used to be employed at. You might be able to setup a PXE of hirens boot