Even though the Out Of Band Console is packaged and part of SCCM SP1, it really is treated as a separate executable from the core SMS Exec service.
With that in mind, the Out of Band Console is not routing traffic for vPro client less than 3.2.1 through the WS-MAN translator and attempts to do a native connection. Due to the lack of WS-MAN support in firmware 2.x and the SCCM dependencies required in 3.x firmware version less than 3.2.1, SCCM OOB Console is unable to manage the vPro Client. So any use going through the SCCM Out of Band Console is impacted for legacy clients until the hotfix is released.
Provisioning and collection based power control for legacy systems (less than 3.2.1) are not impacted because those use cases do not use the Out of Band Console.
Matt Royer
Hotfix is in final testing. Should be availible in the near future.
--Matt Royer
So what's the impact for the OOB management? Do all of the OOB functions does not work for the legancy AMT machines?