locked
task sequences not showing up RRS feed

  • Question

  • I have created a new task sequence and renamed another.    I have advertised both to All Systems collection.   I've waited over 20 min and I never see the new TS or the renamed TS on my target machines inside Software Center.  I've stopped/restarted the SMS Host Agent and still nothing.  I've pressed F5 many times and nothing.

    Why does it take so long for a new or renamed task sequence to show up in the Software Center?



    mqh7

    Thursday, September 10, 2015 4:22 PM

Answers

  • The computer will only see them after renewing the policy. By default the computer look for the policy every 1 hour. If you want to make this quicker go on the computer. Open control panel click on the configmgr icon. You should see the action tab and select retrieve computer policy and start it. After 1 min or so if you open the software center you should see the task sequence.

    Also when you deploy a task sequence make sure it's available to configmgr client and not just pxe boot

    • Edited by Frederick Dicaire Thursday, September 10, 2015 4:25 PM
    • Marked as answer by mqh7 Thursday, September 10, 2015 4:32 PM
    Thursday, September 10, 2015 4:23 PM

All replies

  • The computer will only see them after renewing the policy. By default the computer look for the policy every 1 hour. If you want to make this quicker go on the computer. Open control panel click on the configmgr icon. You should see the action tab and select retrieve computer policy and start it. After 1 min or so if you open the software center you should see the task sequence.

    Also when you deploy a task sequence make sure it's available to configmgr client and not just pxe boot

    • Edited by Frederick Dicaire Thursday, September 10, 2015 4:25 PM
    • Marked as answer by mqh7 Thursday, September 10, 2015 4:32 PM
    Thursday, September 10, 2015 4:23 PM
  • ok, that worked but..... stopping and starting the service does not do the same thing?   how come?  

    mqh7

    Thursday, September 10, 2015 4:32 PM
  • Also keep in mind that there is a known issue with SP2/R2SP1. The 'available time' of the deployment does not honor DST so the deployment will "arrive" one hour late at the client. So what you might have seen might be coincidence. Set the available time to a date in the past and you should not experience this issue. (The client has to retrieve machine policies in order to see the new TS).
    Deploying to "All Systems" might also be not the best solution.

    Torsten Meringer | http://www.mssccmfaq.de

    Thursday, September 10, 2015 7:41 PM