Microsoft Manageability : Tags : wryork

Microsoft SCCM 2007 SP1 Intel vPro Training Videos

We’re pleased to announce the availability of Microsoft SCCM 2007 SP1 Intel vPro Training videos. During a recent training event in Redmond, Washington, we had the cameras rolling for this detailed and robust training experience and it is now available for you to experience and utilize.

Below is an overview and link for each training section.

		Introduction Technical overview of Microsoft System Center Configuration Manager 2007 SP1 support of Intel vPro technology with specific focus on supported use cases, provisioning process and infrastructure prerequisites for Intel vPro Out of Band Management.

		Lab Module One Configuration steps of Active Directory and PKI infrastructure to support Intel vPro Out of Band Management within Microsoft System Center Configuration Manager 2007 SP1.

		Lab Module Two Steps for Microsoft System Center Configuration Manager 2007 SP1 OOB Service Point installation, OOB Component Configuration and Network Discovery for Management Controllers.

		Lab Module Three Steps for creating a collection for housing Intel vPro clients and configuring that collection for automatic provisioning of the Out of Band Management Controllers.

		Lab Module Four Installation overview for the Microsoft System Center Configuration Manager 2007 SP1 client agent and initiation of Intel vPro client provisioning.

		Lab Module Five Technical overview of the Out of Band Management Console, Intel vPro Management Engine Interface and Intel AMT power control via Advertisements.

		Lab Module Six Configuration steps of the Intel WS-MAN Translator to support legacy Intel vPro clients (Intel AMT firmware versions less than 3.2.1).

		Lab Module Seven Provisioning legacy Intel vPro clients (Intel AMT firmware versions less than 3.2.1) through the Intel WS-MAN Translator using PSK provisioning.

		Lab Module Eight Overview of the Intel vPro migration process from the Intel SCS / Microsoft SMS 2003 Add-on to Microsoft System Center Configuration Manager 2007 SP1.

Please let us know if you have questions or comments regarding this material.

This resource along with other resources on the Intel vPro Expert Center can assist you in answering questions when deploying Intel vPro clients in conjunction with Microsoft System Center Configuration Manager 2007 SP1.

6 Comments Permalink Tags: wryork, 2007, amt, center, configmgr, configuration, configuration_manager, manageability, microsoft, sccm, migration, sms, sccm_sp1, jeremy_nicholes, matt_royer, manager, ws-man_translator

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