Close Menu
    Facebook X (Twitter) Instagram
    Monday, June 23
    X (Twitter) LinkedIn
    All about Endpoint Management
    • Home
    All about Endpoint Management
    Home»SCCM 2007»ConfigMgr(SCCM) 2007 client Schedule ID

    ConfigMgr(SCCM) 2007 client Schedule ID

    Eswar KonetiBy Eswar KonetiJanuary 27, 6:25 pm1 Min Read SCCM 2007 483 Views
    Share
    Facebook Twitter LinkedIn Reddit

    When SCCM client is installed on computers and get assigned to site correctly,you will have schedule ID’s for each agent that runs on the client.  You can use the below codes to kick off different agents 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.

    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}

    Hope it helps.

    Client agent schdule ID's.SCCM client schdule IDs configmgr Configmgr 2007 SCCM 2007 SCCM 2007 client Schedule ID
    Share. Twitter LinkedIn Email Facebook Reddit

    Related Posts

    Migrate Microsoft 365 Updates from SCCM/MECM to Intune for Co-Managed Devices

    February 11, 9:50 pm

    Monitoring Endpoint Security Applications with SCCM ConfigMgr SQL

    October 11, 8:48 pm

    Troubleshooting Windows KMS Activation Issues with SCCM scripts feature

    September 09, 11:07 pm

    Leave a ReplyCancel reply

    This site uses Akismet to reduce spam. Learn how your comment data is processed.

    Sign Up

    Get email notifications for new posts.

    Author

    I’m Eswar Koneti ,a tech enthusiast, security advocate, and your guide to Microsoft Intune and Modern Device Management. My goal? To turn complex tech into actionable insights for a streamlined management experience. Let’s navigate this journey together!

    Support

    Awards

    Archives

    © Copyright 2009-2024 Eswar Koneti, All rights reserved.

    Type above and press Enter to search. Press Esc to cancel.