Home > Intel Communities > Open Port IT Community > Intel® vPro™ Expert Center > Microsoft Manageability > Blog > 2008 > June
2

One of the advantages that is brought with SCCM SP1 having integrated support with vPro is the ability to leverage vPro Power On command with Advertisements. What this allows you to do is power up a vPro client that is currently turned off and executive a desired task sequence or software distribution package. So in a scenario where you want to patch your clients at 2:00 am in the morning, you can leveraging vPro and SCCM SP1 to wake your clients up, patch them, and shutdown them back down. This gives you the option of shutting down your vPro clients (to save power) without sacrificing ideal patching / software upgrade times at night (which may be less impactful to your end users) and then gracefully shut them back down again when the patching is complete.

 

 

 

 

In a limited fashion, Wake On LAN (WOL) has given us this option in the past. However unlike WOL, Intel vPro Technology allows you to securely and reliability power up a client without the challenges and potential security issues that comes with the transitional WOL Magic Packet. The following abstract has a pretty good explanation of the differences between WOL and vPro Power On.

 

 

 

 

 

 

To configure SCCM SP1 to use the vPro Power Up commands, you will need to drill down to "Site Database" -> "Site Management" and select properties from the right click menu on your site server. Once the "Site Properties" window appears, click on the Wake On LAN Tab. After ensuring that the "Enable Wake On LAN for this site" is Checked, you will notice three additional configurable options:

 

  • Use power on commands if the computer supports this technology; otherwise, use wake-up packets

  • Use power on commands only

  • Use wake-up packets only

 

 

 

 

 

The reference to "use power on commands" is Microsoft's definition of leveraging vPro Power Management. So to use vPro Power Management for client power on during an advertisements, you will need to ensure that either "Use power on commands if the computer supports this technology; otherwise, use wake-up packets" or "Use power on commands only" is selected. Since you are likely to have a mix of vPro and non-vPro clients in your environment, it is recommended that you use the "Use power on commands if the computer supports this technology; otherwise, use wake-up packets" option.

 

 

 

 

 

 

To allow for easy use of both vPro Power Control and WOL within SCCM SP1, Microsoft decided to bundle both options under "Wake on LAN". So when you are leverage vPro Power Up control on Advertisement, you just need to specify use to Wake on LAN (WOL) and depending on the configuration in the "Site Properties: Wake On LAN Tab" it will use vPro Power or the traditional Legacy WOL packet.

 

 

 

 

 

 

To create an advisement that leverages vPro Power up command...

 

  1. Right Click on the Collection you want the advertisement for and select "Advertise Task Sequence".

  2. When the "New Advertisement Wizard" window appears, enter in the Name of the Advertisement and a comment.

  3. Select the desired "Task Sequence" you have created (To create a Task Sequence, please reference the following article: http://technet.microsoft.com/en-us/library/bb693631.aspx). Click "Next" to Proceed.

  4. On the Schedule Screen, specify your Advertisement Start & Expires (if required) dates.

  5. To allow the "Enable Wake on LAN" option to be selected, you must first specify a "Mandatory Assignments". Click the new icon and define a schedule or immediate action and click "OK".

  6. Once the "Mandatory Assignments" has been defined, check the "Enable Wake on LAN". Select other option and priority as necessary and click "Next".

  7. Select the desired "Distribution Points" options and click "Next".

  8. Select the desired "Interaction" options and click "Next".

  9. Select the desired "Security" options and click "Next".

  10. When the "Summary" Appears, confirm and click "Next".

 

 

 

The advertisement with vPro Power Up control has now been configured. Based on the Mandatory Assignments specified, you should see the vPro Client power on and execute the task sequence. For more details on how to create Advertisements within SCCM SP1, please visit Microsoft Web site.

 

 

 

 

 

--Matt Royer

 

 

2 Comments Permalink
0

On Wednesday, April 30th, Brad Anderson, General Manager of Microsoft Management and Services Division, demonstrated the capabilities of Intel vPro technology with System Center Configuration Manager 2007 in his keynote at MMS 2008. Brad, along with Dave Randall, Microsoft Program Manager for System Center Configuration Manager, showed off the secure power control capabilities of Intel vPro technology by shutting off a collection of 20 PCs with Intel vPro technology during Brad's keynote. Further, Dave went through a remote diagnosis and repair scenario from System Center Configuration Manager 2007 SP1 using Intel vPro technology's Serial Over LAN (SOL) capability. View this Intel vPro technology demonstration from the MMS 2008 keynote below.

 

 



]]>

 

To see more videos from MMS 2008, go to http://www.intel.com/go/mms/.

0 Comments Permalink
2

Some enterprises may find that they want to take advantage of both Microsoft System Center Configuration Manager 2007 (SP1) and System Center Operation Manager 2007 in their environment. Each independently have the ability to provision and manage vPro clients (natively from SCCM and through the Intel SCOM MP for SCOM), but is there a way so that both can manage the same vPro clients? YES, there is!

 

 

 

 

 

The way it works is that SCCM owns the provisioning (setting up certification, ACL, base configuration) and then both SCCM and SCOM w/ Intel SCOM MP can invoke vPro Use Cases. To get SCCM and SCOM w/ Intel AMT Management Pack to work together with vPro, here are the high level steps:

 

 

  1. If you have not already installed Microsoft SCCM SP1, Microsoft SCOM 2007, and the Intel SCOM MP, following the standard install documentation.

  2. Create a domain account that the Intel SCOM MP Service will run under. Once created, ensure you set the Log-in Account for the Intel SCOM MP Service to run under that account.

  3. Within SCCM under the Component Configuration -> AMT Settings -> AMT User Account Setting, add the domain account you created to run the Intel SCOM MP service under. Ensure you give that account sufficient access to perform the desired vPro function.

  4. Within SCOM Intel Management Pack, navigate to the "Intel AMT Management Pack Settings". Under Security Settings, set Kerberos to be used and check the "TLS Enable" check box. Under the CA Certificate, ensure to specify the file location of an export of the Root CA cert (This should be the same CA that SCCM is using to issue AMT client certificates). Once complete, make sure you restart the Intel SCOM MP Service.

  5. Now that base configuration is done, provision your vPro Client normally through SCCM. If you have already provisioned the vPro Client, ensure you "update management controller" so that new ACL is pushed to the vPro Clients. Once provisioned, you should be able to invoke vPro Use Case through SCCM Collection Based power control or the Out of Band Console without issue.

  6. Within SCOM, configure the IP range that includes all vPro Clients to be monitored by the Intel SCOM Management Pack. After the vPro Clients are discovered, you should be able to invoke vPro Usage from within SCOM as well.

 

 

 

 

--Matt Royer

2 Comments Permalink
1

As noted in a previous blog, Microsoft SCCM SP1 natively supports vPro hardware that is running firmware version 3.2.1 or higher. Although SCCM SP1 can support vPro firmware versions less than 3.2.1 by leveraging the Intel WS-MAN Translator, it is advised that you upgrade your OEM vPro Client to the latest supported firmware. Dell, HP, and Lenovo have release the 3.2.1 ME firmware for their vPro platforms and the firmware for those platforms can be downloaded from the following locations:

 

 

 

 

 

As a clarifying note, if you have a vPro Clients that are currently running on vPro firmware 2.x, you are not able to upgrade them to the 3.x version and will be required to use the Intel WS-MAN Translator to provision and manage those systems within SCCM SP1.

 

 

 

 

 

 

--Matt Royer

1 Comments Permalink
2

I've created three videos to cover every step required to install and configure SCCM SP1 to work with Intel AMT platforms. The videos are best viewed at 1024x768 video resolution (click the video to enlarge). Enjoy!

 

SCCM SP1 Pre-Installation video

 

SCCM SP1 Installation video

 

SCCM SP1 Configuration and Provisioning video

 

2 Comments Permalink
0

By default, the Intel WS-MAN Translator has logging turned off. To turn logging on, browse to "C:\Program Files\Intel Corporation\Intel WS-Management Translator\" directory and open "wstrans.exe.config" file with a text editor. Within the wstrans.exe.config file, browse to the the system.diagnostics section. You can change the values of the switches from "off" to "verbose".

 

 

 

 

<system.diagnostics>

 

 

<switches>

<add name="Intel.Wstrans" value="verbose" />
<add name="Intel.Wstrans.Eoi" value="verbose" />
<add name="Intel.Wstrans.WsMan" value="verbose" />

</switches>

</system.diagnostics>

 

 

 

 

After you make the changes, you will be required to restart the Intel WS-MAN translator service for the changes to take effect. After which, the Intel WS-MAN Translator will report actions and errors in the "C:\Program Files\Intel Corporation\Intel WS-Management Translator\wstrans.log".

 

 

 

 

The wstrans.log has been formatted to allow easy readablity via Microsoft SMS Trace utility which is included in the Microsoft System Center Configuration Manager 2007 Toolkit.

 

 

 

 

Matt Royer

 

 

0 Comments Permalink
0

Here is a closer look at the install and configuration of the Intel WS-MAN translator for Microsoft SCCM SP1. The included video should be used as a reference only and not a replacement for the steps defined in the following documentation.

 

High Level Installation steps & reference documentation:

 

 

 

 

 

 

 

 

 

Matt Royer

0 Comments Permalink
0

The Intel WS-MAN translator is a crucial component for providing vPro legacy (less than firmware 3.2.1) support within Microsoft SCCM SP1. The beta of the WS-MAN Translator has been released and can be downloaded from the following location:[http://softwarecommunity.intel.com/articles/eng/3840.htm]

 

 

 

 

The installation and configuration of the WS-MAN Translator is a fairly straight forward process and can be broken up in three key steps: Configuring ISS Certificate, WS-MAN Install & Configuration, and Enabling support for Intel WS-MAN translator within SCCM.

 

 

 

 

 

 

 

High Level Installation steps & reference documentation:

 

 

 

 

 

 

 

 

For additional information on the WS-MAN Translator, please visit the FAQ

 

 

 

 

 

 

Note: The Intel WS-MAN Translator is current in Beta status and not considered a released product at this time.

 

 

 

 

 

 

 

Matt Royer

 

 

0 Comments Permalink