none
Software Updates Scan Cyle

    Question

  • Is there a way of initiating a Software Updates Scan Cyle from a cmd line on a group of SCCM clients?
    Thursday, June 10, 2010 5:59 PM

Answers

All replies

  • Take a look at the right click tools, they already have that feature. Or the SDK if you want to develop your own.

    Right click tools - http://myitforum.com/cs2/blogs/rhouchins/archive/2008/04/09/sccm-right-click-tools.aspx

    SDK - http://www.microsoft.com/downloads/details.aspx?familyid=064a995f-ef13-4200-81ad-e3af6218edcc&displaylang=en


    Kent Agerlund | http://scug.dk/members/Agerlund/default.aspx | The Danish community for System Center products
    Thursday, June 10, 2010 6:04 PM
    Moderator
  • Hi Mate

     

    I use this this WMIC cmd on certain collections

    Trigger sofware update scan

    WMIC /namespace:\\root\ccm path sms_client CALL TriggerSchedule "{00000000-0000-0000-0000-000000000113}" /NOINTERACTIVE

    Trigger software update deployment

    WMIC /namespace:\\root\ccm path sms_client CALL TriggerSchedule "{00000000-0000-0000-0000-000000000108}" /NOINTERACTIVE

    Fire off the WMIC CMD Trigger sofware update scan and monitor WUAHandler.log

    Hope this helps


    G-Man8
    • Marked as answer by Robotop Thursday, June 30, 2011 5:29 PM
    Friday, June 11, 2010 8:49 AM
  • I'm not able to run this command.  I am trying to do this as part of a task sequence so I can get all of the updates installed.  But I can't even get it to work from the command line.  The command I am using is:

    WMIC /namespace:\\root\ccm path sms_client CALL TriggerSchedule "{00000000-0000-0000-0000-000000000113}" /NOINTERACTIVE

    When I run it I get:

    Executing (sms_client)->TriggerSchedule()

    ERROR:

    Description = Not found

    If I run the same thing but change it to "000000000108" it runs and says:

    Executing (sms_client)->TriggerSchedule()

    Method execution successful.

    Why won't it work?  I'm using a CM2012 R2 client (5.00.7958.1000).  I looked in CIM Studio and I can see most of the other actions but I don't see 113 (ScanAgent).  Did this get changed in R2 version?


    Shane Curtis

    Thursday, November 21, 2013 7:26 PM
  • Did you ever manage to work this out?

    I'm running 2012 R2 and also unable to use the 113 scan agent.  Google comes back with nothing!

    Thursday, January 16, 2014 11:04 AM
  • Never did.  I had to settle for just running it once.  It seems to apply all of the necessary patches though because I'm running it during a reference build task sequence and then again in my gold deployment task sequence.  When I run it the second time it doesn't apply any patches (or maybe 1 or 2, can't remember offhand now, it's been a while since I've looked at that step).  My hope is that maybe Microsoft fixed it so you don't have to run the apply software updates step multiple times.

    Shane Curtis

    Thursday, January 16, 2014 11:33 PM
  • I'm not able to run this command.  I am trying to do this as part of a task sequence so I can get all of the updates installed.  But I can't even get it to work from the command line.  The command I am using is:

    WMIC /namespace:\\root\ccm path sms_client CALL TriggerSchedule "{00000000-0000-0000-0000-000000000113}" /NOINTERACTIVE

    When I run it I get:

    Executing (sms_client)->TriggerSchedule()

    ERROR:

    Description = Not found

    If I run the same thing but change it to "000000000108" it runs and says:

    Executing (sms_client)->TriggerSchedule()

    Method execution successful.

    Why won't it work?  I'm using a CM2012 R2 client (5.00.7958.1000).  I looked in CIM Studio and I can see most of the other actions but I don't see 113 (ScanAgent).  Did this get changed in R2 version?


    Shane Curtis

    Is there a reboot between the first scan and subsequent scans? We had a similar issue and it turned out that the CM client finished installing in-between scans, which moved that client out from "All Unknown Systems". It was not yet part of any other collections with Software Update enabled in the client settings, so we would also get that error.
    • Proposed as answer by Impulse12 Monday, March 03, 2014 2:02 PM
    Monday, March 03, 2014 2:01 PM