Run Task Sequence may take up to 24 hours to start deployment in Configuration Manager 2012


After installing and configuring Microsoft System Center 2012 Configuration Manager and configure Operating System Deployment feature to deploy Windows 7, you deploy task sequence to specific Collection but unfortunately Task Sequence take very long time to start “24 Hours approximately”.

When we check Download Center on the client machine, we notice that: “Downloading (0% Complete)”, and when we check server Monitoring -> Deployment -> Deployment Name -> Compilation Statistics: status was In Progress with Waiting for content message.


Connection speed (fast or slow) is not defined in Boundaries group.


  1. Open System Center 2012 Configuration Manager Console and go to Administration.
  2. Navigate Overview -> Hierarchy Configuration -> Boundaries Group

  3. Right click on boundaries group name and go to properties

  4. Go to ‘References’ tab

  5. In Content location add boundary that client use it to locate content

  6. Make sure that fast connection is selected

Abduljalil Abolzahab

  1. #1 by Mirko on January 2, 2013 - 3:00 PM

    We found that a dirct deployment from a Tasksequence are cecking for all steps in it, goes more longer than a PXE or Bootable-Media deployed Tasksequence.
    There are a open case by Microsoft for this 😉

Leave a Reply

Please log in using one of these methods to post your comment: Logo

You are commenting using your account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: