Hi and welcome to our new Out of Band Management support team blog! If you've been following our Configuration Manager support team blog then you've probably already seen a couple posts on AMT and OOB but due to the increasing popularity of this subject we've decided to branch off and start a new blog dedicated solely to using OOB/AMT in SCCM 2007 SP1 and later. Look for a lot of new stuff on AMT and OOB right here very soon.
Now first off, if you're not familiar with AMT and OOB then you're probably wondering what all the fuss is about so let me give a brief overview of what this is. I can't take all of the credit for what follows since I stole most of it from our TechNet site but why try to improve upon the great job they've already done?
Out of band management in Configuration Manager 2007 provides powerful management control for computers that have the Intel vPro chip set and a version of the Intel Active Management Technology (Intel AMT) that is supported by Configuration Manager. For more information about supported AMT versions, see Configuration Manager 2007 SP1 Supported Configurations and Configuration Manager 2007 SP2 Supported Configurations.
Note: The information here applies only to Configuration Manager 2007 SP1 and later.
Out of band management allows an administrator to connect to a computer's management controller when the computer is turned off, in sleep or hibernate modes, or otherwise unresponsive through the operating system. By way of contrast, in-band management is the classic approach used by Configuration Manager and its predecessors whereby an agent runs in the full operating system on the managed computer and the management controller accomplishes tasks by communicating with the management agent.
Out of band management supplements in-band management. While in-band management supports a wider range of operations because its environment is the full operating system, in-band management might not be functional if the operating system is not present or is not operational. In these situations, the supplementary capabilities of out of band management allow administrators to manage these computers without requiring local access to the computer.
Out of band management tasks include the following:
If you are using Configuration Manager 2007 SP1, these out of band management tasks are natively supported on an unauthenticated, wired connection. However, with Configuration Manager 2007 SP2 and later, they are also supported on an authenticated 802.1X wired connection and wireless connection. Configuration Manager 2007 SP2 also has the following additional features:
For example scenarios of how out of band management can be used, see Example Scenarios for Using Out of Band Management.
Some of the preceding tasks are performed from the Configuration Manager console, while others require running the out of band management console that is supplied with Configuration Manager 2007 SP1 and later. Out of band management uses Windows remote management technology (WS-MAN) to connect to the management controller on a computer.
Note: Out of band management is not supported for clients that are managed over the Internet with Internet-based client management. Additionally, Configuration Manager clients that are blocked by a Configuration Manager 2007 SP1 site continue to accept out of band management communication. Configuration Manager clients that are blocked by a Configuration Manager 2007 SP2 site cannot be managed out of band.
For more in-depth information about using Out of Band management in Configuration Manager 2007 SP1 and later, see the following TechNet documentation:
Again, welcome to our new site. I hope you find the things we discuss helpful and if you have any requests just let us know.
J.C. Hornbeck | System Center Knowledge Engineer