Home > Intel Communities > Open Port IT Community > Intel® vPro™ Expert Center > Microsoft Manageability > Blog > 2008 > September
Up to Blog Posts in Microsoft Manageability
Previous Next

Microsoft Manageability

September 2008
William York
1

While working on-site with a customer and a Microsoft SCCM Technical Consultant, I was shown a great capability in the OS to force the SCCM client agent to check its AMT auto-provisioning policy at will.

 

The Windows OS ships with a utility called Windows Management Instrumentation Tester that can be used to force the SCCM agent to check its AMT Auto-Provisioning Policy (standard WMI calls). The following steps show this manual method that you can perform with this utility, either locally or remotely, to force this check. By default the SCCM server's site control file sets the agent check to automatically run every 24 hours. However, in a lab or testing environments this 24 hour default cycle is not convenient. With these steps below, you can execute this check at will or even use while troubleshooting issues. To perform these steps, you must have administrative privileges on the target OS.

 

After the manual steps listed below, Matt Royer has provided a reference to a .vbs file that performs these steps to help automate the process. Feel free to use these steps and scripts for your environment. And if you find new and/or improved methods with these WMI calls, please post for others to learn from.

Manual Steps to issue WMI command:

  • Open a command prompt and type wbemtest

    This is the Windows Management Instrumentation Tester

  • 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

    Example: **

  • Click Connect

  • You can also simply run the command on the local system by simply leaving out the host name

  • Example: \root\ccm

 

  • After you successfully connect to the target system, click the Execute Method Button

  • In the Get Object Path window, type sms_client in the Object Path field

    Click OK

  • In the Execute Method Window, enter TriggerSchedule in the Method Field

    Click the Edit In Parameters Button

  • 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.

  • Click the Save Property button

 

  • In the Object editor for _Parameters window, click the Save Object button

  • 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 systems 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.

 

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} <target vpro machine name with sccm client>

 

sendsched.vbs is piece of code included in the SMS 2003 Toolkit: http://technet.microsoft.com/en-us/sms/bb676787.aspx

 

00000000-0000-0000-0000-0000 00000120 is the scheduled ID for auto-provisioning policy.

1 Comments Permalink Tags: sccm_sp1, wryork, provisioning, vpro
Josh Hilliker
2

If you are using SCCM SP1 with AMT 3.2.1 machines (ex: HP7800P) and you see the following error.. this post is for you.

 

 

Here is what MEinfo read back during this state of detection

 

 

If you do, no need to be frustrated, just need to run a couple of steps to get back on the road. You can utilize Matt Royer's blog at Intel AMT 3.2.1 Self-signed certificate issue and working around it for Microsoft System Configuration Manager SP1

 

For me I had to give it a go myself, so Nick & I did the following:

  • secured our SCCM environment

  • borrowed 2 new HP boxes in the box

  • downloaded the vbscript file, wsman translator.

 

After 3 trial runs at it, we captured the video today and here it is. Here are the top things I wish I knew prior to installing:

#1. OOB settings is under component configuration (Under site settings) in SCCM

#2. Having your cert (*.pfx) file downloaded and handy is important (and it's in the dictionary)

#3. Make sure you run the following: winrm set winrm/config/client/auth @{Basic="true"} on the console your running the box on

#4. Be patient - this was the single hardest thing during this process for me..

 

Here's the video.

 

 

My recommendation, if your stuck in this state on your machines, follow Matt's blog, check out my video and then ask if any questions..

2 Comments Permalink Tags: ws-man_translator, sccm_sp1, josh_hilliker, microsoft, matt_royer, provisioning, vpro

Popular Blog Posts

Incoming Links