Client Schedule ID’s

Client Schedule ID’s

  • Comments 6
  • Likes

I get asked this quite often so I have been compiling a list of the Schedule ID’s for a Config Manager client.  This is not a complete list by no means but I think that it is most of them.  I add to it as I find new ones.

Hardware Inventory Collection Task

{00000000-0000-0000-0000-000000000001}

Software Inventory Collection Task

{00000000-0000-0000-0000-000000000002}

Heartbeat Discovery Cycle

{00000000-0000-0000-0000-000000000003}

Software Inventory File Collection Task

{00000000-0000-0000-0000-000000000010}

Request Machine Policy Assignments

{00000000-0000-0000-0000-000000000021}

Evaluate Machine Policy Assignments

{00000000-0000-0000-0000-000000000022}

Refresh Default MP Task

{00000000-0000-0000-0000-000000000023}

Refresh Location Services Task

{00000000-0000-0000-0000-000000000024}

Location Services Cleanup Task

{00000000-0000-0000-0000-000000000025}

Software Metering Report Cycle

{00000000-0000-0000-0000-000000000031}

Source Update Manage Update Cycle

{00000000-0000-0000-0000-000000000032}

Policy Agent Cleanup Cycle

{00000000-0000-0000-0000-000000000040}

Request Machine Policy Assignments

{00000000-0000-0000-0000-000000000042}

Certificate Maintenance Cycle

{00000000-0000-0000-0000-000000000051}

Peer Distribution Point Status Task

{00000000-0000-0000-0000-000000000061}

Peer Distribution Point Provisioning Status Task

{00000000-0000-0000-0000-000000000062}

Compliance Interval Enforcement

{00000000-0000-0000-0000-000000000071}

Software Updates Agent Assignment Evaluation Cycle

{00000000-0000-0000-0000-000000000108}

Send Unsent State Messages

{00000000-0000-0000-0000-000000000111}

State Message Manager Task

{00000000-0000-0000-0000-000000000112}

Force Update Scan

{00000000-0000-0000-0000-000000000113}

AMT Provision Cycle

{00000000-0000-0000-0000-000000000120}

 

You can use the above codes to kick off different events on the client.  There are several scripts out there that will allow you to to do this.  One of the most used is the SendSched.vbs file from the SMS 2003 Toolkit2.  The toolkit can be downloaded from this link.

Comments
  • Linking to mwiles' post: http://blogs.technet.com/mwiles/archive/2009/02/06/client-schedule-id-s.aspx

  • Well this is an ancient post, but you can also leverage wmic to trigger these schedules. Here's an example to trigger hinv:

    wmic /node:"[COMPUTERNAME]" /namespace:\\root\ccm path sms_client call TriggerSchedule sScheduleID="{00000000-0000-0000-0000-000000000001}"

  • Here is a wmi for kicking off the application eval cycle in SCCM 2012.

    wmic /node:"[COMPUTERNAME]" /namespace:\\root\ccm path sms_client call TriggerSchedule sScheduleID="{00000000-0000-0000-0000-000000000121}"

Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment