ConfigMgr 2007: How to manually kick off a client provisioning task

ConfigMgr 2007: How to manually kick off a client provisioning task

  • Comments 2
  • Likes

imageBy default the SCCM server's site control file sets the agent to provision check automatically every 24 hours. This is not configurable in the UI nor is it an option on the Actions tab of the agent (unlike Hardware Inventory or Machine Policy Requests). In a lab or testing environments this 24 hour default cycle may not be convenient but with the steps below you can execute this check at will or use while troubleshooting issues.

Note: To perform these steps, you must have administrative privileges on the target OS.

Manual Steps to issue WMI command:

1. Open a command prompt and run wbemtest. This is the Windows Management Instrumentation Tester. 

2. After the Windows Management Instrumentation Tester Utility opens, click Connect.  In the Namespace of the Connect Window, type the system name you want to force the check followed by \root\ccm, then click Connect again.

Note: If you’re executing this on the local system then you can leave the default of root\ccm.

3. After you successfully connect to the target system, click the Execute Method button. 

4. In the Get Object Path window, type sms_client in the Object Path field and Click OK. 

5. In the Execute Method Window, enter TriggerSchedule in the Method field.

6. Click the Edit In Parameters button and in the Object editor for _PARAMETERS window, double click the sScheduleID in the Properties field.  In the Property Editor Window, change the Value to Not NULL and add the following:

{00000000-0000-0000-0000-000000000120}

This value is the Object ID to initiate this OOB auto-provisioning check.

7. Click the Save Property button, then in the Object editor for _Parameters window, click the Save Object button. 

8.  In the Execute Method window, click the Execute Button.  After you Execute the method, you should see a message that the Method was executed successfully.

To confirm that your method was executed, look at the target system’s c:\windows\system32\CCM\Logs\oobmgt.log.  You should now see a new entry in the log GetProvisioningSetting indicating that the policy has been re-evaluated.

Alternatively, to perform these steps automatically through a .vbs script all you need to do is run the following command:

cscript sendsched.vbs {00000000-0000-0000-0000-000000000120} ClientName

Sendsched.vbs is piece of code included in the SMS 2003 Toolkit and 00000000-0000-0000-0000-0000 00000120 is the scheduled ID for auto-provisioning policy.

Buz Brodin | Senior Support Escalation Engineer

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

    I'm just wondering if this is valid with the R2 client (4.00.6487.2000) on Windows 7? All I seem to be getting from following the first set of instructions relating to wbemtest is an error as per the following:

    Number: 0x80041002

    Facility: WMI

    Description: Not found

    Cheers,

    Lain

  • Same here. I don't think that particular wbemtest is necessarily valid for Win7.

    But the 'sendsched' and so forth works fine, as far as updating the necessary bells + whistles.

    Still cannot get anything to provision though - some 'missing link' somewhere, regarding at least touching the machines once to set a 'mebx' password, since SCCM will NOT allow 'User admin with password admin.'  This part is very 'vague' in most of the blogs - they seem to lead us to believe that SCCM will 'magically provision' the computers, without ever touching them, but I cannot get this to happen. Add OOB point and all the necessary things (certs, etc.), but no luck.

    Any help appreciated (mine show up as 'Not supported' [which is a false status - they are just not yet 'activated' basically; AND the rest show up as 'Detected' but never get past that part. Never truly provisioned. I have bought the provisioning cert; added that and the Web cert into sccm, but no luck.