I have been gradually trying to implement the vPro technology into our environment without a test environment. We just upgraded to SCCM 2007 SP2 with R2. I have some test machines provisioned already, and yesterday I was pretty sure that I was able to see the system status and details in the oob management console. I was unable to connect to the serial connection and got a failed message and ever since then I cannot seem to connect to any provisioned machines. When I start up the OOB management console the status shows connecting for a while, then shows "System: Disconnected". The OOBConsole.log shows the following entries:[6][12/16/2009 3:30:33 PM] :System.Management.ManagementException\r\nInvalid parameter \r\n at System.Management.ManagementException.ThrowWithExtendedInfo(ManagementStatus errorCode) at System.Management.ManagementPath.SetWbemPath(IWbemPath wbemPath, String path) at System.Management.ManagementPath.CreateWbemPath(String path) at System.Management.ManagementPath..ctor(String path) at Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlConnectionManager.GetInstance(String objectPath)\r\nManagementException details:[6][12/16/2009 3:30:37 PM] :GetAMTPowerState fail with result:0x80070005<repeat last line over and over>I am able to successfully use the power off and on controls from the right click menu: Power Control, but cannot log in from the web console after modifying the registry settings for IE 6 and am using IE7 running on XP SP3 on my workstation. (https://pcname@domain.com:16993). When I click on the Logon button, I get a message stating "webpage cannot be displayed".If I try to connect from the site server using the OOB management console I get the same problem and same log entries. I have tried to update provisioning data in management controller which appeared to successfully update from the server logs.I am a domain adminbelieve that all the out of band components are set up correctly. I tried researching the forums and common troubleshooting docs but can't seem to find anything that applies. Please help direct me to find the cause of this problem when you get a chance! Thanks!

Forgot to mention site server is running on Windows Server 2003 SP2 with R2; AMT Full version is 5.03Also have a test laptop I just provisioned that is showing up as unknown under AMT Status in console pane, but properties page shows AMT status = 3. That has AMT Full version 4.1.1 (I know this is probably a completely different issue!)Thanks again.

So you're running the OOB console from your XP workstation? Have you upgraded the XP workstation to the SP2 console?Trevor SullivanConsultant | 1E Inc.http://trevorsullivan.wordpress.com