Search This Blog

Monday, June 15, 2015

Skipping task sequence because it is not active yet

After upgrading System Center Configuration manager 2012 R2 to SP1 (or 2012 SP2), you might see this problem.

When deploying a OSD Task Sequence and not selecting when the deployment will be available (meaning now):

image

SCCM will auto select Schedule when this deployment will become available and setting the date and time to now (your current time):

image

But when you for example PXE boot a computer expecting the Task Sequence to be available it might not be so, and in smsts.log you will find the message Skipping Task Sequence because it is not active yet:

image

Changing the schedule to yesterday or just one hour back will make the Task Sequence available:

image

Posted by at
Labels:

6 comments:

  1. Anonymous17 June, 2015 21:37

    Thanks Lars, this helped me today at a customer! Cliff with Microsoft!

    ReplyDelete
  2. Anonymous18 June, 2015 22:52

    Good call. Just ran into the exact same issue and modifying the schedule worked for me!! Never had to do this pre R2 SP1.

    ReplyDelete
  3. Brian Gonzalez17 July, 2015 22:00

    Just ran into this in my SCCM 2012 CU3 R2 lab. Thanks!

    ReplyDelete
  4. Renaud29 July, 2015 15:21

    Hi, thanks we had the same problem and it works !

    ReplyDelete
  5. Anonymous01 April, 2016 22:36

    Thank you, it solved the issue for me.

    ReplyDelete
  6. Unknown27 July, 2016 21:40

    Odd stuff!!! Changing the deployment "Shedule when this deplyment will become available" and "assigment schedule time" to, for example, 12 hours ago, did the trick for me. Is this a bug?

    ReplyDelete

Subscribe to: Post Comments (Atom)