I wanted to quickly share an example of how to set the current power state of a provisioned Intel vPro system using Windows Powershell!

Take a moment, and ask yourself these quick questions:

• Have you ever wanted to be able to automate the powering up, or powering off, of multiple computers?
• Is your company interested in saving money by not needlessly leaving computers powered on at night?
• Do you have a time-critical environment, such as a call center, where you need to reliably power up your computers so they are ready to go in the morning for agents?
• Do you want to be able to create your own helpdesk tools to enable remote reset of hung systems?

If you answered "yes" to any of the previous questions, then hopefully this Powershell code will help you, as an administrator, achieve your goals! Let's take a look at how to perform the actions of:

• Powering up a vPro (AMT) system
• Powering down a vPro (AMT) system (not gracefully, just FYI)
• Power cycling a vPro (AMT) system (also not graceful)
  

For the sake of simplicity, we'll continue to work with the ManageabilityStack.AmtSystem object that I have referenced in my previous article(s). If you aren't sure how to get the $Global:Amtdevice Powershell variable, please look back at my other articles. This will also require the download of the Intel AMT Developer Toolkit. You'll need the Manageability Stack.dll library contained within.

-------------------

In order to control the remote power state of an AMT system, all you really need to know are these 3 hex values:

0x10 = System reset

0x11 = Power on

0x12 = Power off

0x13 = Reset w/ power cycle

These hex values will be used with the $AmtSystem.Remote.SendRemoteControl() method to alter the power state of the remote system. The SendRemoteControl() method included with the DTK includes a number of parameters that go beyond the scope of this article, so we will pass hex value 0x0 to these parameters for the time being. In order to use the above hex values, simply pass the hex value as the first parameter of the SendRemoteControl() method. In order to fulfill the parameter requirements of this method, pass 5 additional parameters with the value 0x0. Here are some examples:

Powering up an AMT System

$Result = $AmtDevice.Remote.SendRemoteControl(0x11, 0x0, 0x0, 0x0, 0x0, 0x0)

Write-Host "Power command resulted with: ${Result}"

Powering off an AMT System

$Result = $AmtDevice.Remote.SendRemoteControl(0x12, 0x0, 0x0, 0x0, 0x0, 0x0)

Write-Host "Power command resulted with: ${Result}"

Power cycling an AMT System

$Result = $AmtDevice.Remote.SendRemoteControl(0x10, 0x0, 0x0, 0x0, 0x0, 0x0)

Write-Host "Power command resulted with: ${Result}"

The above samples show how to use the SendRemoteControl() method of the AmtRemoteControl .NET type in the Intel AMT Developer Toolkit (DTK) to control the power state of a remote AMT device.

If you have any questions about this, please leave a comment or send me a private message.

Sincerely,

Trevor Sullivan

Systems Engineer

OfficeMax Corporation

Introduction

Software Management Solution has the ability to deliver and execute any module or installer made for Windows.  This includes Windows capable Firmware updates.  Both the BIOS updates and Intel ME firmware updates, that are windows capable, available from HP, Dell, Lenovo, and any other computer manufacturer that supports vPro that are windows capable can be sent down and executed through Software Management Solution to upgrade firmware.  This document covers how to setup and configure these updates, and hopefully provide you information on caveats and other potential trouble spots.

Why Update Firmware?

The first thing you need to determine is what type of firmware update do you require?  The two typical updates are the Intel Management Engine (ME) firmware and the standard BIOS firmware.  How these two interact is dependent on the Manufacturer.  Some manufacturers will combine the BIOS and firmware updates into a single executable.  However the configuration, the updates can be delivered via Symantec’s Software Management Solution.

Examples and Reasons

For example HP has a BIOS option to enable or disable Intel AMT, and if it is disabled in the BIOS the Intel ME will not be available.  Another example is the Dell laptop model Lattitude 620 Centrino vPro capable.  The BIOS contains a setting to enable or disable the Serial Over LAN (SOL) and IDE Redirection (IDER) capabilities, and by default these came from the manufacturer disabled.  This and other reasons for firmware updates are detailed in this list:

• Dell Lattitude 620 SOL IDER disabled in the BIOS – The update to automatically enable these features without having to physical update each BIOS manually is a BIOS firmware upgrade that set these as enabled, among other fixes/updates.
• Upgrading AMT 2.1 to 2.2 – Desktop models of AMT version 2.1 can be upgraded to support Remote Configuration (certificate-based zero-touch provisioning) by upgrading the Intel ME firmware to version 2.2.
• Upgrading AMT 2.5 to 2.6 – Notebook models of AMT version 2.5 can be upgraded to support Remote Configuration by upgrading the Intel ME firmware to version 2.6.
• Upgrading AMT 2.0 to 2.1 – Some major fixes were incorporated between versions 2.0 and 2.1 of AMT.
• UUID reset fix for HP Compaq 6910p – This fixed a flaw in the firmware where sometimes Intel ME returned the UUID of all zeroes or a default UUID set in the firmware, causing duplicates.  This update patches the firmware for Intel ME on these laptop models.
• Upgrading Intel AMT 4.0 to 4.1 – On the newer version of AMT for laptops, fixes have been provided via version 4.1 and is available from most manufacturers.
• Miscellaneous fixes to Intel ME – Other fixes have been incorporated in ME firmware updates

Obtaining the Right Firmware Update

For all BIOS updates, the manufacturer’s website should be consulted.  For each vPro model you wish to update BIOS firmware with, use the following basic steps:

1. Go to the Manufacturer’s main site.  For this example, we’ll use Dell.  www.dell.com.
2. Choose the Support icon and click ‘Download and Drivers’.
   
3. An applet will appear where you can choose the system through several options:
4. 1. Model
   2. Service tag
   3. Log in to choose from a list of systems
5. Once you have the right system listed, there will be a list where you can click the plus + next to ‘BIOS’.
6. From the provided list choose the applicable update by clicking the ‘Download Now’ link to the right.  The download will usually be in the form of an EXE.

While Intel manages the basic firmware for the Intel ME, the manufacturer packages it for deployment, including changes that may be required for specific models of vPro capable systems.  It is advised that you only use the manufacturer’s Intel ME firmware updates on your vPro systems.  The following walkthrough will hopefully help you identify what updates are available.  For this example we’re using HP’s website.

1. Go to www.hp.com.
2. Click on the ‘Support and Drivers’ tab.
3. Choose the option Download drivers and software (and firmware) for Step 1 and put in the Model number of the vPro system type you wish the update for, in Step 2.
4. Press Enter to go to the main page for the system.
5. Though it prompts for what Windows you’re running, the updates are OS independent so choose any.
6. For the Intel ME firmware updates, the categories differ.  For HP it’s under simply ‘Firmware’.  Other potential categories include:
7. 1. Firmware
   2. System Firmware
   3. Chipsets
8. Click Download to the right of the applicable ME update.
   
9. Once the EXE is downloaded, move on to the next section.

Rolling out the Firmware Update

Once you’ve obtained the EXE, it’s time to configure a Software Management Solution Software Resource, Package, associated Command lines, and create a task to roll it out with.  It’s important to understand how, depending on how the manufacturer packaged the EXE, the rollout can be accomplished silently without user interaction.  Typically administrators do not want users to interfere with the rollout, or to even be aware of it.  The following walkthrough considers this the desired result; however the configuration can be changed as so noted where applicable below.

Creating a Software Package/Program

1. On the Notification Server place the EXE you downloaded for the firmware update into a self-contained folder.  The folder and everything in it will become a “package” for the Software Resource, thus it is recommended to have only the needed file therein.
   Note: You can use another storage location if you prefer, such as UNC or URL.  Simply adapt these steps to fit your preferred source method
2. In the Symantec Management Console browse under Manage > and choose Software.
3. In the left-hand tree browse under Software Catalog > Deliverable Software > and select Updates and Service Packs.
4. In the resulting right-hand pane, click the Add button and choose Software Update.
5. Above the configuration tabs provide a name for the Update.  In this example we’ll use an HP 6930p laptop firmware update of the Intel ME to version 4.1.1.1028.
6. Click on the Package tab.
7. Click the Add package button.
8. Provide a name for the package and browse to the location referred to in step 1.  The name we’ll use in this example is AMT 4.1 Firmware EXE(Windows) for HP 6930p.  See this screenshot for an example:
   
9. Click OK to save the Package details.
10. Click on the Add command button.
11. Provide a Name for the command-line.  For this example we’ll use: Apply AMT 4.1 Firmware Update silently.
12. Check the option labeled Command line requires a package and ensure that the Package you created previously is selected.
13. Under Installation file type choose the option labeled EXE Software Installation File.
14. Change the Command type to Install.
15. Provide a silent command line under the Command line field (this is the potentially difficult part.  The update I tested with had no documentation on silent installs and I had to tinker to find the –s command-line that ran it silently.   ie: “sp42026.exe” –s).
    NOTE: Due to the nature of firmware updates, it is possible the EXE will want to reboot the system.  It is recommended to test the execution and adjust the command-line to suppress the reboot so no user is interrupted in their work.
    See the below screenshot for an example:
    
16. Click Save changes to complete the Software Resource creation.

Creating a rollout Task

The next step is to create a Quick Delivery Task that pushes out the update.  While a Manage Delivery Job may be used, because of the nature of firmware updates reapplying an update may have unintended consequences so for this example we’ll use a Quick Delivery Task. Follow these steps to create the Task:

1. In the Symantec Management Console browse under Manage > and click Jobs and Tasks.
2. In the left-hand tree browse down through System Jobs and Tasks > Software > and select Quick Delivery.
3. Right-click on the Quick Delivery folder > choose New > and click on Job or Task.
4. Within the resulting window choose Quick Delivery from the left-hand tree.
5. Provide a name for the task.  In this example we’ll use AMT 4.1 Firmware Update for 6930p Rollout.
6. Under the Software resource dropdown choose the name of the Software Resource you created.  In this example it is AMT 4.1 Firmware Update for HP 6930p.
   NOTE: The dropdown is also a type field so you can start typing AMT 4.1 to have the selected software found and displayed in the dropdown.
7. Ensure that the Command line and Package in the two subsequent dropdowns correctly show the Command-line and Package you created.  For our example they are Apply AMT 4.1 Firmware Update silently and AMT 4.1 Firmware EXE(Windows) for HP 6930p respectively.
8. Click the Advanced button.
9. Under the Download Options typically what is configured at the Altiris Agent level should be sufficient for your needs.  Click the Run Options tab.
10. This is your execution environment.  Due to the nature of firmware updates, it is advisable to use the option labeled Altiris Agent credential.
    NOTE: Specific user can be used if you wish to provide an account that has Administrator rights on the target systems directly.
11. Under User run conditions check the option labeled Allow user interaction.  We have found that this option improves success rate due to loading a fuller user stack.
12. Change the Display window to Hidden.  See this screenshot for an example:
    
13. Click OK to save the Advanced options and Click OK on the main Task configuration page to save the details of the Quick Delivery Task.
14. You can use the Quick Run under the Task Status section to test the rollout.  Please see the section following labeled ‘Test the Rollout’.  It is vital to properly test the rollout so any corrections can be made before rolling it out generally.
15. Set a schedule.  You can choose Now or set a specific scheduled time if needed.
16. For the next step under Input you’ll need to manually add devices for this firmware update to be run on or select a target.  Step 17 covers how to create a target for the example we’re using in this sequence.  If you are only adding machines manually step 17 is not required.  Move to step 19.
17. To create a target based off of Inventory Solution data that automatically targets the HP Compaq 6930p laptops, follow these steps:
18. 1. In the Symantec Management Console browse under Manage > and click on Filters.
    2. Browse under Computer Filters and select or create a folder to create the filter in.
    3. Right-click on the folder and choose New > Filter.
    4. Name the Filter.  In our example we’ll use All HP 6930p Laptop Computers.
    5. Under the Filter Definition dropdown choose the option Query Mode: Query Builder.  You’ll receive a notice: You are about to switch to the other query editing mode.  This cannot be undone after save.  Click OK to continue.
    6. Expand the Filter Definition section by clicking on the down-arrow to the far right.
    7. Under the query section, select the tree item ‘Resource’ and click the red X delete icon.
    8. When the page refreshes on the right you’ll see a Base Resource Type.  Choose Computer.  When prompted, choose to continue.
    9. Under the actions section to the right, click the link labeled Use Fields & Data Class Attributes.
    10. In the resulting picker type in or choose from the dropdown the data class and column you wish to reference.  For our example choose [Logical Device].[Model] and click OK.
    11. Click the Filter Expressions tab.
    12. Click the Add Condition button and choose one of the options (for a first filter it doesn’t matter).
    13. Type the same data class and column selected previously.  In our example type [Logical into the If: field and then select [Logical Device].[Model] from the dropdown.
    14. Choose Like in the next dropdown to the right (or if you know the exact value you’re looking for, use Equals).
    15. In the last field type the model number.  In our example type %6930p%.  See this screenshot for an example:
        
    16. Click the Save Changes to complete the Filter.
19. To add the Filter to the schedule, go through the following steps:
20. 1. Under the Task Status click the button New Schedule
    2. Set the schedule as desired.
    3. Under Input click Add and choose Target.
    4. Click the Add rule button in the resulting window.
    5. In the first dropdown choose the option labeled exclude the resources not in.
    6. Leave Filter as the option in the second dropdown.
    7. In the third dropdown type in the first words of the filter you created in the previous step.  In our example type All HP and click the dropdown arrow.  Select the appropriate collection from the list.
    8. Click OK to save the Target.
21. Click Schedule to apply the Task to the selected systems.
22. Done!  This Task type will use Task Server to push out the task.  For systems already online they should receive the task within minutes based off of being active on the network.  For systems not on, the next time they come online and check for Tasks, Task Server will push out the Task at that time.

Test the Rollout

The most important part of this process is to test the rollout.  This will allow you to make corrections to the command line or execution environment should the first attempt fail.  By testing the rollout you can ensure it is ready for the greater environment.  In testing, you should:

1. Target a system that matches your Production Environment as closely as possible
2. Test the command-line to ensure it successfully and silently rolls out the firmware update.  You can accomplish this by copying the files over and running the command line manually from a command prompt or from Start > Run.
3. Check the BIOS or Intel AMT for versioning change.
   Note: the ME version may not be synched with the AMT version.  A good test is to try executing the update again manually to see if you receive a message indicating the version is already up to the latest version.

Conclusion

Using this process, you should be able to remotely update any firmware required for successful use of Intel vPro Systems both with Setup and Configuration using Out of Band Management, and vPro functionality use within any Job and Task in the Symantec Management Platform.

Dell just released a new BIOS update for the Dell Optiplex 755 system, version A13. This update includes an AMT firmware update to version 3.2.3 also that resolves a couple of security issues. I just performed the update on an Optiplex 755 that I had already provisioned, and it didn't break anything

If you're deploying the BIOS update via a ESM software package, such as Microsoft System Center Configuration Manager (SCCM) 2007, you can automate the staging of the BIOS update (without forcing a reboot) using the following command line:

O755-A13.exe -noreboot -nopause

Get it while it's hot!

Trevor Sullivan

Systems Engineer

OfficeMax Corporation

Hi all - A couple of new issues were posted to the Known Issues, Best Practices, and Workarounds. They include:

• Q&A on customized Intel® AMT firmware
  

• Microsoft* SCCM unable to use Intel(R) AMT features when run on Microsoft* Vista* Operating System

Hello!

Have you ever run into the situation where you want to enable the auto-provisioning policy for a ConfigMgr client, but dont' want to wait for the policy to filter down to the client? If you're like me, then you would answer with a hearty "yes." Thankfully, I've got a method for you to force an SCCM client to enable auto-provisioning, without relying on the collection setting!

Keep in mind that, for some odd reason, pasting this code into a Powershell window will probably fail. Instead, paste the first 4 lines, and manually type out the last (red) line.

$OobSettings =  [wmiclass]”root\ccm\policy\machine\actualconfig:CCM_OutOfBandManagementSettings”
$OobSettingsInstance =  $OobSettings.CreateInstance()
$OobSettingsInstance.AutoProvision =  $True
$OobSettingsInstance.SiteSettingsKey =  1
$OobSettingsInstance.Put()

Basically what this does is spawn an instance of the CCM_OutOfBandManagementSettings WMI class, sets two properties on it, and then writes it back to the system. This should enable auto-provisioning immediately so you don't have to wait!

Trevor Sullivan

Systems Engineer

OfficeMax Corporation

Ok, I have one more trick for all you Intel AMT developers trying to build high security software. One good use of Intel AMT is for power state monitoring, one could build an application that polls many computers for their power state and plots the results on a graph. You can see just how “green” your network is. Typically to do this, you call the Intel AMT method to get the power state periodically located in the Remote Control security realm of Intel AMT.

The way Intel AMT security realms are designed: granting a user access to the Remote Control realm gives this user access to reading the power state but also turning on and shutting down (hard shutdown) the computer. As a result, the nice monitoring application you are building can only be run by trusted administrators. It would be nice to be able to create an Intel AMT user with only minimal access to features that could only be used to read the power state and not much else. This is not technically possible…

But wait, there is a trick! Create a user account within Intel AMT with only General Info and Hardware Inventory access. These two realms are the minimum needed to access the Intel AMT web UI. Then, using a normal browser we can load the Web UI and notice that the computer power state is displayed on the web page! With a little code, we can extract this information out of what is normally a human readable web page.

Of course, this is a hack and your software may need to be upgraded as new firmware may change the WebUI. Still, it’s such a good trick; I use it with great success in my own code. Note that the Intel AMT 2.0 page is a little different from Intel AMT 2.5 and above. So far, I have to handle 2.0 differently but the same parsing code seems to work on all Intel AMT computers (up to 5.0). Also, that web UI page is very fast and you get, as bonus information, the computer’s unique identifier and Intel AMT time in a single call.

The only drawback I have noticed is that the WebUI will show the string “Standby” for both S1 and S3 states. So you can’t tell exactly what power state it’s sleeping in. Otherwise, you can detect S0, S4 and S5 states.

Ylian

The release of the Notification Server 7.0 platform will provide a new design and infrastructure.  Out of Band Management will also provide a new release with this platform.  First I’ll provide a brief description of what Out of Band Management is used for.  This article will also cover the differences between the 6.2 version of Out of Band and version 7.0.  The changes include UI improvements, relabeling to be in line with current Intel terms, and the addition of limited Dash support.

INTRODUCTION

Out of Band Management 7.0 allows an administrator or IT Professional to setup and configure several protocol technologies for use in the greater Notification Server infrastructure, or even any other solution that supports the protocols handled by Out of Band Management.  The supported technologies are:

• Intel AMT (Active Management Technology) or vPro
• ASF (Alerts Standard Format) primarily from Broadcom
• DASH technology support (open architecture)

The greater focus is on Intel’s AMT technology.  Using the provided configuration pieces with Out of Band, systems with the above technologies can be configured to respond to functions called from either the RTSM interface or via Task Server.  Once configured, the Notification Server is a trusted entity to the local systems and all available functions are available.

More information can be found by browsing through the articles generated on Out of Band Management 6.x at http://www.symantec.com/community/intel.

Terms/Term changes

It’s important to understand the changes in terminology and labeling so the transition from 6.2 to 7.0 Out of Band Management goes smoothly.  This section will also help explain the naming scheme for Out of Band Management.  The following list provides the term, and the previous label (if different), and a brief description:

1. Configuration, AKA Setup and Configuration – Previous term: Provisioning – Intel has standardized on using Configuration as the term for activating a vPro system.  This more aligns with what is occurring and avoids confusion with basic industry understanding of what provisioning means (putting an OS on the system). 
   NOTE: Since this word is used throughout documentation for 6.x it is important to understand the change!
2. TLS – Transport Layer Security can be considered the next generation of SSL (Secure Sockets Layer).  It’s used in 2 sections of Configuration: Remote Configuration authentication, and TLS within the Configuration Profile.
3. Remote Configuration – This specifically means the process for automatic Configuration via the handshake with a TLS certificate, usually purchased from Verisign, GoDaddy, Comodo.

Out of Band Portal

Out of Band Management now has a Portal page that provides access to most function from a user-friendly UI.  It’s accessed in the Symantec Management Console by going to Home > Remote Management > and click on Out of Band Management.  The following screenshot shows a view of the portal:

The upper left-hand pane shows a list of setting groups that will enable a user to go through those steps necessary to enable or complete Out of Band setup and configurations.  Please note the following items and what they can be used for:

• Configuration Service Settings – This provides all the nodes that are used in the Setup and Configuration process for AMT.
• Basic Configuration (without TLS) – This takes you through the process of setting up Configuration where TLS will not be used in the Configuration Profile (not to be confused with Remote Configuration TLS).  See this screenshot for the way the steps are setup:
  
• Enable Remote Configuration – This walks you through setting up the Notification Server to accept Configuration requests using TLS certificates.  Note that 2.6, 3.0+ AMT systems are automatically configured to send out requests using this method.
• Enable Security (TLS) – This walks you through setting up the Notification Server to use TLS when managing AMT systems.
• Intel AMT Tasks – This is a quick area that reveals the Task Server tasks that directly utilize AMT.
• Configure Site Server – This is a link that opens the Site Server Configuration page as part of the Notification Server Platform.  This is available here because OOB has a Site Service that can be deployed to Site Servers.

As a note, Site Servers allow distribution of Out of Band functions across the environment, and helps alleviate any problems with large rollouts involving a large amount of Configuration.  This brings us closer to having true hierarchy support with Out of Band Management.

UI Changes

Those who are familiar with Out of Band Management 6.2 can use this section to find corresponding functions, configuration pages, and utilities when upgrading to Out of Band 7.0.  If you are unfamiliar with this version skip to the next section.

Out of Band Management looks much the same as it did in 6.2, with some notable exceptions.  The following items cover the differences between the two.  The method used to reach the console area for Out of Band Management is as follows: Browse down through Settings > All Settings > in the left-hand tree browse down through Remote Management > Out of Band Management.  The three subfolders are by the same name as they were in 6.2, lacking the fourth folder: Delayed Provisioning.

1. *Provisioning > Configuration – I called this out previously in this article but with my experience the double-exposure is necessary.  In reference to managing vPro AMT systems, consider the previously used term Provisioning to now be Configuring, or Provision to now be Configuration.  If you’re like me and have the word provisioning ingrained in your mind, it will take some getting used to.
2. Auxiliary Profiles – Three new nodes have been added to this folder.  They are described below:
3. 1. Management Presence Server – (MPS) This is the secure gateway CIRA technology will use to connect securely with the network where the NS resides for remote management from anywhere on the Internet.
   2. Remote Access Policies – In relation to the above MPS, this policy dictates how CIRA connections are handled by the Notification Server.
   3. Trusted Root Certificates – Also in relation to MPS, these are required to establish so that trust can be formed from the calling AMT system, the MPS, and the Notification Server.
4. Configuration Profiles – Formerly known as Provision Profiles.  The following items have been added as tabs within the profile configuration.  Descriptions of the items are supplied as well:
5. 1. Domains – Allows the ability to configure AMT to operate in more than one Domain.
   2. Remote Access – This ties directly to the Remote Access Policies found under the Auxiliary Profiles node.  Edits here will take effect in both places.
6. The remaining nodes under the Configuration Service Settings folder are the same between versions 6.2 and 7.0.
7. Delayed Setup and Configuration – Formerly known as Delayed Provisioning, this has been renamed to fit the proper naming convention.  It also no longer has its own folder, but can be found under the Intel® AMT Systems folder above the Intel AMT Systems node.
8. The following screenshot shows the layout of the console:
   

Intel SCS

The component that Out of Band Management plugs into has not changed between versions.  Intel SCS (Setup and Configuration Services) is still the backbone of Out of Band, and handles all the transactions between the server and the remote Intel AMT clients during the Configuration process.  Please note that management functions of AMT are NOT handled by Intel SCS.  SCS stands for only the Configuration process, including maintenance and reconfiguration tasks (for example for profile updates) as part of maintaining the configured state.

Out of Band Management 6.2 used Intel SCS version 3.0 (or 3.2.1 per the Knowledgebase article found at this location: https://kb.altiris.com/article.asp?article=40076&p=1).  Intel SCS version 5.0 ships with Out of Band Management.  While the UI does not reveal all the additional capabilities, SCS 5.0 comes with a tool called Activator.  This utility can handle a number of scenarios that were sticky points in the previous versions of Out of Band and Intel SCS.  The abilities include the following:

1. FQDN Name Change – The Activator, when run on the local AMT system, can tell AMT to send updated information to Intel SCS on its FQDN.  This is especially important if the FQDN has changed in Windows, thus changing the identity of the machine.
2. • The problems associated with this are the failure of AMT systems to authenticate using TLS due to FQDN sensitivity if enabled, and also the inability of Intel SCS to contact back a system whose FQDN has changed.
3. Resending of Hello Packets – While the 3.0 version of Out of Band had the ability to send Hello packets using the Delayed Provisioning (AKA Delayed Configuration) task, it did not have the ability to send PSK (pre shared keys) packets if the 24 hour cycle of the hello packets sequence expires.  This functionality was also added to verison 3.2.1 of Intel SCS.
4. • The problems associated with this are when systems are not configured within that 24-hour cycle they need to be acted upon to get the needed information to the server for configuration.

The above two functions can be utilized by sending Activator down using a Delivery Software job in the Software Management Solution.

Conclusion

Hopefully this introduction will help those familiar with Intel vPro, and especially familiar with Out of Band Management in the Notification Server 6.0 infrastructure, to understand the changes and functions in version 7.0 of Out of Band Management.  In depth articles will be generated in the future to cover some of the new features such as the MPS and CIRA functionality.