Skipping task sequence because it is not active yet

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

+ posts

Table of Contents

Share this post
Search blog posts
Search
Authors
Modern Workplace consultant and a Microsoft MVP in Enterprise Mobility.

Modern Workplace consultant and a Microsoft MVP in Windows and Devices.

Infrastructure architect with focus on Modern Workplace and Microsoft 365 security.

Cloud & security specialist with focus on Microsoft backend products and cloud technologies.

Cloud & security specialist with focus on Microsoft 365.

Cloud & Security Specialist, with a passion for all things Cybersecurity

Cloud and infrastructure security specialist with background in networking.

Infrastructure architect with focus on design, implementation, migration and consolidation.

Infrastructure consultant with focus on cloud solutions in Office365 and Azure.

Modern workplace and infrastructure architect with a focus on Microsoft 365 and security.

follow us in feedly
Categories

Follow on SoMe