CM12 SP1: Why runs custom task sequence twice if using boot from PXE?

My goal is boot into WinPE4 then run a few commands line steps that backup my target PC (with a propietary tool) and at last reboot back to the installed operating system. Nothing else. I use CM12 SP1.

To achieve this I use a custom task sequence. To start it I use 'clear required PXE deployments' and boot/reboot the target PC.

1. Now that target PC smoothly boots from PXE, loads WinPE4 and runs athe command line steps successfully. (I even set all steps to 'continue on error' to ignore potential errors from the propietary tool.) 

2. After that it restarts and again boots from PXE and again runs the same few command line steps.

3. Then it restarts again and boots the installed operating system finally. I was like.... Huh, why does it run twice?

Does it mean that the task sequence didn't give feedback to the server that it finished the first time? If so how can I force the task sequence to finalize at the end of the first run? Custom vbs or powershell script?

Deployment settings are: install required, make available only media and PXE and rerun behavior is never rerun.

Thanks for your ideas!

June 28th, 2013 8:00pm

What task sequence steps are in the task sequence? What's in smsts.log?
Free Windows Admin Tool Kit Click here and download it now
June 28th, 2013 10:46pm

smsts.log says to all command line steps exit code 0, all actions completed successfully.

I found an easy way how anyone should be able to reproduce my problem in CM12 SP1:

1. Create custom task sequence which is empty at first

2. Add just one 'run command line' step and do a 5s sleep, e.g. cmd /c ping -n 6 127.0.0.1

3. Use a boot image: standard WinPE4 x64 boot image from ADK

4. Deploy to a collection that has got one PC and boot that PC from PXE 

5. Now you'll see everything going smoothly - just one curse: next boot up it will run again from PXE.

July 1st, 2013 11:50am

Hi,

Could you make a screenshot of your task sequence please ?

Regards,

Rgis

Free Windows Admin Tool Kit Click here and download it now
July 1st, 2013 12:30pm

Here's a screenshot from the simplified test task sequence that I described in the posting before to reproduce my problem.

Just use a standard WinPE4 boot image. No conditions set in the options tab. You can reproduce my problem with this:

 

July 3rd, 2013 2:19am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics