locked
Deployment jobs cannot be run immediately on SCCM 2012 RRS feed

  • Question

  • Hello Guys,

    I have a packages to be deployed to our clients. When I schedule the package to be deployed to the devices collection and set the schedule to ASAP, it may take 30 minutes then start the deployments. How can we reduce the waiting for the SCCM 2012 packges deployments?

    thanks,

    SCCM 2012 USers

    Friday, November 30, 2012 7:46 AM

Answers

  • When you deploy a pacakage to a device collection, and the deployment is configured to run ASAP, the client will install the package when it gets the policy.

    The default value for the client policy cycle is 60 minutes, and is controlled by client settings.

    If you want the deployment to start faster, you need to change this schedule.


    Ronni Pedersen | Microsoft MVP - ConfigMgr | Blogs: http://www.ronnipedersen.com/ and SCUG.dk/ | Twitter @ronnipedersen

    Friday, November 30, 2012 8:15 AM
  • the wait time depends on many factors:

    - client policy polling

    - client location (should it download the package first)

    if you want to have it really ASAP, you can install one of the rightclick tools and force a machine policy and retrieval cycle

    Friday, November 30, 2012 8:15 AM
  • You've got a few options:

    - you can change your policy refresh interval to a shorter period, but think about consequences for your infrastructure.

    - You can create your own console extension that'll trigger policy update on your clients

    - you can use existing "Right Click Tools" - http://myitforum.com/myitforumwp/2012/10/23/configmgr-2012-powershell-right-click-tools-update/


    Mikhail

    • Marked as answer by VLV2012 Saturday, December 8, 2012 4:13 PM
    Friday, November 30, 2012 9:36 AM

All replies

  • When you deploy a pacakage to a device collection, and the deployment is configured to run ASAP, the client will install the package when it gets the policy.

    The default value for the client policy cycle is 60 minutes, and is controlled by client settings.

    If you want the deployment to start faster, you need to change this schedule.


    Ronni Pedersen | Microsoft MVP - ConfigMgr | Blogs: http://www.ronnipedersen.com/ and SCUG.dk/ | Twitter @ronnipedersen

    Friday, November 30, 2012 8:15 AM
  • the wait time depends on many factors:

    - client policy polling

    - client location (should it download the package first)

    if you want to have it really ASAP, you can install one of the rightclick tools and force a machine policy and retrieval cycle

    Friday, November 30, 2012 8:15 AM
  • You've got a few options:

    - you can change your policy refresh interval to a shorter period, but think about consequences for your infrastructure.

    - You can create your own console extension that'll trigger policy update on your clients

    - you can use existing "Right Click Tools" - http://myitforum.com/myitforumwp/2012/10/23/configmgr-2012-powershell-right-click-tools-update/


    Mikhail

    • Marked as answer by VLV2012 Saturday, December 8, 2012 4:13 PM
    Friday, November 30, 2012 9:36 AM