SCCM Deployment issue

[neonetman]

I currently have a task lists deployed to our student PCs' using "available" so when we rebuild the machines, we have a choice of images to deploy.

 

This morning, I captured a new wim file from a machine, added it to a new OS image and distributed that to the DP

I have copied an existing task sequence, and then amended the OS being used.

 

Currently if I PXE boot a PC, I get an option for the F12 network service boot, however once I deploy this new task sequence, the PC will then sit for a couple of minutes waiting for server, before timing out.

 

I've check the OS image has successfully distributed to the DP, and have check the site status query messages (nothing untoward in there)

 

I'm at a loss how to troubleshoot this

Edited September 12, 2019 by neonetman

[neonetman]

EDIT:: I've got another task sequence causing the same problem. The boot image and WIM files are distributed correctly, and I can't find anything in the logs to indicate the issue

[jslate1980]

Turn on development tools on you boot.wim file. When at the pxe environment. Press F8 which will bring up command line. Type cmtrace.exe and locate the smsts logs. This will have a breakdown of what error it is having at pre deployment.

 

Edit: sorry didn't read your last post fully. Not trying to teach your grandmother to suck eggs.

Edited September 12, 2019 by jslate1980

[neonetman]

I'm not getting as far as the PXE environment... it doesn't get as far as giving me the option for pressing F12 for service boot.... If I remove the deployment, the option re-appears and I can then PXE as normal

[snagrat]

When you copy a TS it does not seem to copy the settings on what Boot file it should use.

Check on the properties of the TS that it is set to use the correct boot file