<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:opensearch="http://a9.com/-/spec/opensearch/1.1/" xmlns:clearspace="http://www.jivesoftware.com/xmlns/clearspace/rss" xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0">
  <channel>
    <title>Intel vPro Expert Center Blog</title>
    <link>http://communities.intel.com/community/openportit/vproexpert/blog</link>
    <description>Intel vPro Expert Center Blog</description>
    <pubDate>Mon, 22 Jun 2009 20:50:08 GMT</pubDate>
    <generator>Clearspace 2.5.9 (http://jivesoftware.com/products/clearspace/)</generator>
    <dc:date>2009-06-22T20:50:08Z</dc:date>
    <item>
      <title>OOB Console Error</title>
      <link>http://communities.intel.com/community/openportit/vproexpert/blog/2009/06/22/oob-console-error</link>
      <description>&lt;!-- [DocumentBodyStart:9ebc64c0-d3d3-49e7-97c6-74367407f005] --&gt;&lt;div class='jive-rendered-content'&gt;&lt;p&gt;Hello vPro Experts!&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;Are you having trouble getting the Microsoft Out-of-Band (OOB) Console to connect to your Intel vPro clients? If so, one of the first things you should do, is enable verbose logging in your &lt;span style="color: #0000ff;"&gt;OOBConsole.exe.config&lt;/span&gt; file. This file is located in the following folder: &lt;span style="color: #0000ff;"&gt;%PROGRAMFILES%\Microsoft Configuration Manager Console\AdminUI\bin&lt;/span&gt;. If you open this file in Notepad, you should see a line that looks like &lt;span style="color: #0000ff;"&gt;&amp;lt;source name="OOBConsole" switchValue="Error"&amp;gt;&lt;/span&gt;. If you change the text &lt;span style="color: #000000;"&gt;&lt;span style="color: #0000ff;"&gt;Error&lt;/span&gt; &lt;/span&gt;to&lt;span style="color: #000000;"&gt; &lt;span style="color: #0000ff;"&gt;Verbose&lt;/span&gt;&lt;/span&gt;, you will enable verbose logging for the OOB Console. The next time you try to connect to an AMT device, you should start seeing more detailed logging in the OOBconsole.log file, located in:&lt;span style="color: #000000;"&gt; &lt;span style="color: #0000ff;"&gt;%PROGRAMFILES%\Microsoft Configuration Manager Console\AdminUI\AdminUILog&lt;/span&gt;.&lt;/span&gt;&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;If you're seeing this message specifically: &lt;span style="color: #0000ff;"&gt;GetAMTPowerState fail with result:0x800401F3&lt;/span&gt;, then you might have forgotten to install &lt;a class="jive-link-external-small" href="http://www.microsoft.com/Downloads/details.aspx?FamilyID=845289ca-16cc-4c73-8934-dd46b5ed1d33&amp;amp;displaylang=en"&gt;WinRM 1.1&lt;/a&gt; on your Windows XP client running the OOB console. Also make sure that you're running Windows XP Service Pack 3! Once you install WinRM 1.1, this error should magically disappear, and have you well on your way to managing vPro devices!&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;Cheers,&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;&lt;strong&gt;Trevor Sullivan&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;&lt;em&gt;Systems Engineer&lt;/em&gt;&lt;/p&gt;&lt;p&gt;OfficeMax Corporation&lt;/p&gt;&lt;/div&gt;&lt;!-- [DocumentBodyEnd:9ebc64c0-d3d3-49e7-97c6-74367407f005] --&gt;</description>
      <category domain="http://communities.intel.com/community/openportit/vproexpert/blog/tags">oobconsole</category>
      <category domain="http://communities.intel.com/community/openportit/vproexpert/blog/tags">vpro</category>
      <category domain="http://communities.intel.com/community/openportit/vproexpert/blog/tags">issue</category>
      <category domain="http://communities.intel.com/community/openportit/vproexpert/blog/tags">problem</category>
      <category domain="http://communities.intel.com/community/openportit/vproexpert/blog/tags">error</category>
      <category domain="http://communities.intel.com/community/openportit/vproexpert/blog/tags">message</category>
      <category domain="http://communities.intel.com/community/openportit/vproexpert/blog/tags">microsoft</category>
      <category domain="http://communities.intel.com/community/openportit/vproexpert/blog/tags">configmgr</category>
      <category domain="http://communities.intel.com/community/openportit/vproexpert/blog/tags">configuration</category>
      <category domain="http://communities.intel.com/community/openportit/vproexpert/blog/tags">manager</category>
      <category domain="http://communities.intel.com/community/openportit/vproexpert/blog/tags">amt</category>
      <category domain="http://communities.intel.com/community/openportit/vproexpert/blog/tags">isv</category>
      <category domain="http://communities.intel.com/community/openportit/vproexpert/blog/tags">software</category>
      <category domain="http://communities.intel.com/community/openportit/vproexpert/blog/tags">console</category>
      <category domain="http://communities.intel.com/community/openportit/vproexpert/blog/tags">sccm</category>
      <pubDate>Mon, 22 Jun 2009 20:50:08 GMT</pubDate>
      <author>pcgeek86@gmail.com</author>
      <guid>http://communities.intel.com/community/openportit/vproexpert/blog/2009/06/22/oob-console-error</guid>
      <dc:date>2009-06-22T20:50:08Z</dc:date>
      <clearspace:dateToText>5 months, 1 week ago</clearspace:dateToText>
      <wfw:comment>http://communities.intel.com/community/openportit/vproexpert/blog/comment/oob-console-error</wfw:comment>
      <wfw:commentRss>http://communities.intel.com/community/openportit/vproexpert/blog/feeds/comments?blogPost=12286</wfw:commentRss>
    </item>
  </channel>
</rss>

