Hi, We are running ConfigMgr 2007 R3 on both server and clients. We have 1 primary site that acts as an SLP, DP, RP, MP, PXE service Point, SUP. We also have an additional server that acts as a DP only and another server for the DB We are having an issue at the moment whereby our task sequences run twice. We deploy windows 7 via either pxe boot or prestaging the boot process, and then when the os is installed and ready, the task sequence will then run again! It seems the first pass doesnt make the previous object obsolete and so it runs again. On the second pass, the object is marked as obsolete and a new object created.. Here is our setup: Container called Reimage Desktop computer. No queries on this, its manually add the resources only Task sequence has a mandatory advertisement set to the reimage desktop computer container. It set to "as soon as possible" and program rerun behaviour is set to always rerun. So we manually add the computer, it reimages and installs windows as normal. At this stage, it seems to use the existing computer object rather than marking it as obsolete. Hence the task sequence then runs again and once its done, it makes the original object obsolete as it should and therefore does not rerun the task sequence Any ideas on this? Thanks!

The always rerun setting does exactly what it says, it will always rerun. So change the rerun behaviour to never or only if previous failed and you should be fine.My Blog: http://www.petervanderwoude.nl/ Follow me on twitter: pvanderwoude

Hello! Might I recommend this excellent blogg post that Jrgen has written that can help you with your problem :) Remove from OSD Task Sequence collection //Andreas

Sorry in the delay with replying. I am happy to change it off the always re-run setting, but I am concerned because I guess i dont understand the process very well. From my understanding, if you "reimage" a machine using a task sequence, and install the client during part of the install process, it should mark the previous sccm object as obsolete, correct? If so, the always re-run setting shouldnt matter, as that previous object should be obsolete What I am finding however, is that if the machine runs the task sequence via PXE boot, it will then finish the sequence, boot to windows and then windows will prestage winpe and run the whole process again. Its at this point the object is marked as obsolete and therefore the imaging stops... but I would think that it shouldnt matter how winpe runs in the first place, the object should still be marked as obsolete I would love some help with understanding exactly whats going on here - any ideas? Thanks

Also, thanks for the script that removes it from the group when imaging is finished. The funny thing is, the script works great, but the machine still reimages again anyway! I find the problem is most prevailent when starting the task sequence via PXE boot rather than prestaging from windows.. Is there a way to turn off the windows prestaging? I would rather either just have PXE boot imaging only