Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people, just like you, are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions

SCCM - PXE Boot/Mandatory Advertisement/Task Sequence.

Posted on 2010-11-17
Last Modified: 2013-11-21
So here's the scenario:

I'm doing a bulk install of Windows 7 on 2000+ PC's.  I've configured a task sequence and assigned a mandatory advertisement to a 'build' collection.

All the desktops are HP, so I've enabled PXE as the first boot option.  I pre-stage the computers into the 'build' collection and switch the machines on.

Everything works as expected and on start-up, the machines start imaging.

The problem is this:
After the task sequence completes and the machines reboot, it starts the image build process again.  There are no errors in the advertisement status.

Can anyone help me stop this from happening?

Help would be greatly appreciated!!
Question by:jamie77777
  • 2
  • 2
LVL 10

Expert Comment

ID: 34158815
what are your advertisment schedule properties?  
LVL 10

Expert Comment

ID: 34158963
I would ensure that your advertisement properties are set to "Never re-run".

This can be occuring if your Task Sequence advertisement is set to "re-run if failed previous attempt", and the task sequence is failing on one of the last steps (so the OS build looks complete).


You have more than one Advertisement for the Windows deployment, when a computer builds, the only package/program it knows it has completed is the Windows deployment one it just ran.  So if there was a second advert for OS deployment advertsied, it would start that one straight after (I've got myself in that loop a couple of times!)

Author Comment

ID: 34159212
Thanks for the suggestions Jon.  I can definately confirm that there is only one advertisement for the task sequence on the site.

Jon/Kezzi:  See screenshot of advertisement properties.

Any other idea's?  I'm to the point where I'm considering scripting the BIOS to change boot order at the end of the TS.  I'm sure this shouldn't be happening though! Advertisement Schedule Properties
LVL 10

Accepted Solution

JonLambert earned 500 total points
ID: 34160119
After the client is PXE booted, it should 'mark' the SCCM resource record for the client as having executed a PXE boot, and will not execute another PXE boot until the existing PXE advet is cleared off the SCCM resource.

You mention that it restarts and starts re-imaging, which to me says it's nothing to do with PXE, but is re-executing the one advert.

I would check the status messages (either by report or status message queries) for a workstation to see if you can work out from them what/why it is re-imaging.

Author Comment

ID: 34160761
Hi Jon,

First of all, thanks.  You sparked a review of my thinking and it's sorted.

I tried to keep it simple for my EE question, but the truth was I missed out some important parts.  Should also note this is a clients site, and all information/testing was relayed...

To give them the ability to image 'new' machines, I've configured a pre-execution hook in another boot image and assigned it to 'unknown computers'.  The pre-execution hooks populates the SCCM 'build' collection on the fly enabling unknown machines to build a selection of task sequences assigned to the 'build' collection.  After doing that, it was decided to use one dynamic task sequence and make it mandatory for roll out, setting PXE as first boot.  When a machine is 'pre-staged' (i.e. Computer Association set up), it's not a problem... See below my explanation.

So, I got the wrong end of the stick when I posted the question and there was no way you could've answered it, but you kind of did :)  Nice work.

The following is the process (behaviour) of a computer that is 're-imaging'.

Computer is unknown to SCCM (or known through Active Directory, but has no client information).
PXE boot is automatic
PXE boot starts as 'unknown computer' loading 'unknown computer boot image'.
GUI asks for 'Computer Name' using pre-execution hook
Pre-execution hook creates SCCM record containing client information (MAC Address etc.) and adds to 'build' collection
Boot image reads the 'standard build' advertisement as mandatory and copies 'known computer boot image' to client
Sets PXE boot flag to complete (for the current 'unknown computer')
Computer reboots and loads 'Known computer boot image' <-- not using PXE
Computer builds standard image
Computer now exists in SCCM and is member of 'build collection'
(PXE Boot image is not set as complete, as the 'correct' record of the computer hasn't technically booted using PXE)
Computer reboots and starts PXE boot, loading 'known computer boot image' as is now member of 'build collection'
Computer 're-images', setting PXE flag as complete
... and doesn't re-image again.

So in conclusion:
While the 'standard build' advertisement is mandatory, computers that are set to PXE boot automatically will re-image unless the computer is 'pre-staged'.
The computer doesn't have to pre-staged if the 'standard build' advertisement isn't mandatory (and selected during GUI process) and will image only once - which will be the case after rollout.


Featured Post

Ransomware: The New Cyber Threat & How to Stop It

This infographic explains ransomware, type of malware that blocks access to your files or your systems and holds them hostage until a ransom is paid. It also examines the different types of ransomware and explains what you can do to thwart this sinister online threat.  

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

New Windows 7 Installations take days for Windows-Updates to show up and install. This can easily be fixed. I have finally decided to write an article because this seems to get asked several times a day lately. This Article and the Links apply to…
When you try to share a printer , you may receive one of the following error messages. Error message when you use the Add Printer Wizard to share a printer: Windows could not share your printer. Operation could not be completed (Error 0x000006…
This Micro Tutorial will give you a basic overview of Windows DVD Burner through its features and interface. This will be demonstrated using Windows 7 operating system.
The viewer will learn how to successfully create a multiboot device using the SARDU utility on Windows 7. Start the SARDU utility: Change the image directory to wherever you store your ISOs, this will prevent you from having 2 copies of an ISO wit…

808 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question