<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:clearspace="http://www.jivesoftware.com/xmlns/clearspace/rss" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:opensearch="http://a9.com/-/spec/opensearch/1.1/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>Microsoft-vPro</title>
    <link>http://communities.intel.com/openport/blogs/microsoft-vpro</link>
    <description>Comment Feed for Microsoft-vPro</description>
    <pubDate>Wed, 08 Oct 2008 20:41:53 GMT</pubDate>
    <generator>Clearspace 1.7.0 (http://jivesoftware.com/products/clearspace/)</generator>
    <dc:date>2008-10-08T20:41:53Z</dc:date>
    <item>
      <title>RE:&amp;nbsp;Intel WS-MAN Translator 1.0 released</title>
      <link>http://communities.intel.com/openport/blogs/microsoft-vpro/2008/08/19/intel-wsman-translator-10-released#comments-2860</link>
      <description>Step 6 (in Configuring the WS-MAN Translator) says to "...select the WS-Man Translator certificate created in previous step" - I did this and got this message:&lt;br /&gt;
&lt;br /&gt;
"An attempt was made to load a program with an incorrect format. (Exception from HRESULT: 0x8007000B)" after clicking finish on Select TLS/forwarding options&lt;br /&gt;
&lt;br /&gt;
I can click OK and it will prompt me to restart the translator service. Can I assume everything is ok or is there a test to see if the service is correctly configured?</description>
      <pubDate>Wed, 08 Oct 2008 20:41:53 GMT</pubDate>
      <author>swood</author>
      <guid>http://communities.intel.com/openport/blogs/microsoft-vpro/2008/08/19/intel-wsman-translator-10-released#comments-2860</guid>
      <dc:date>2008-10-08T20:41:53Z</dc:date>
    </item>
    <item>
      <title>RE:&amp;nbsp;Using WMI to force the SCCM Agent to check for its AMT Auto Provisioning Policy</title>
      <link>http://communities.intel.com/openport/blogs/microsoft-vpro/2008/10/01/using-wmi-to-force-the-sccm-agent-to-check-for-its-amt-auto-provisioning-policy#comments-2795</link>
      <description>This is defiantly a good find Bill.  The SendSched.vbs can be used in a variety of different ways.&lt;br /&gt;
&lt;br /&gt;
For example, you could enumerate a sccm collection and execute SendSched against each client in that collection.&lt;br /&gt;
&lt;br /&gt;
&lt;strike&gt;Code vbscript Begin&lt;/strike&gt;&lt;br /&gt;
Const SMSSITECODE = "VPD"				'SMS Site Code&lt;br /&gt;
Const SMSSERVER = "SCCMSP1.vprodemo.com" 	'SMS Site Server &lt;br /&gt;
Const SMSCollection = "SMS00001"			'SMS Collection ID to enumerate clients from &lt;br /&gt;
&lt;br /&gt;
Set objLocation = CreateObject("WbemScripting.SWbemLocator")&lt;br /&gt;
Set WbemServices = objLocation.ConnectServer(SMSSERVER, "root\SMS\site_" &amp; SMSSITECODE)&lt;br /&gt;
Set colMembers = wbemServices.ExecQuery("Select * From SMS_FullCollectionMembership WHERE COllectionID='" &amp; SMSCollection &amp; "'")&lt;br /&gt;
Set wshShell = WScript.CreateObject("WSCript.shell")&lt;br /&gt;
&lt;br /&gt;
For Each colMember in colMembers&lt;br /&gt;
	runScript = "cscript sendsched.vbs {00000000-0000-0000-0000-0000 00000120} " &amp; colMember.name&lt;br /&gt;
	set oExec = wshShell.Exec(runScript)&lt;br /&gt;
	Do While oExec.Status = 0&lt;br /&gt;
		WScript.Sleep 1000&lt;br /&gt;
	Loop&lt;br /&gt;
Next&lt;br /&gt;
&lt;br /&gt;
Set wshShell = Nothing&lt;br /&gt;
Set WbemServices = Nothing&lt;br /&gt;
Set objLocation = Nothing&lt;br /&gt;
&lt;strike&gt;Code End&lt;/strike&gt;&lt;br /&gt;
&lt;br /&gt;
Another option may be to create an sccm advertisement to execute the SendSched locally on the client.  Just set up a Command Line Task Sequence using cscript sendsched.vbs {00000000-0000-0000-0000-0000 00000120} and advertise that task sequence to a particular collection.&lt;br /&gt;
&lt;br /&gt;
--Matt Royer</description>
      <pubDate>Wed, 01 Oct 2008 14:52:07 GMT</pubDate>
      <author>miroyer</author>
      <guid>http://communities.intel.com/openport/blogs/microsoft-vpro/2008/10/01/using-wmi-to-force-the-sccm-agent-to-check-for-its-amt-auto-provisioning-policy#comments-2795</guid>
      <dc:date>2008-10-01T14:52:07Z</dc:date>
    </item>
    <item>
      <title>RE:&amp;nbsp;Intel WS-MAN Translator 1.0 released</title>
      <link>http://communities.intel.com/openport/blogs/microsoft-vpro/2008/08/19/intel-wsman-translator-10-released#comments-2793</link>
      <description>I mean, the key is now correctly imported without error message, but selfsignedfix.vbs still does not connect.</description>
      <pubDate>Wed, 01 Oct 2008 07:48:11 GMT</pubDate>
      <author>william.gregoire</author>
      <guid>http://communities.intel.com/openport/blogs/microsoft-vpro/2008/08/19/intel-wsman-translator-10-released#comments-2793</guid>
      <dc:date>2008-10-01T07:48:11Z</dc:date>
    </item>
    <item>
      <title>RE:&amp;nbsp;Intel WS-MAN Translator 1.0 released</title>
      <link>http://communities.intel.com/openport/blogs/microsoft-vpro/2008/08/19/intel-wsman-translator-10-released#comments-2792</link>
      <description>Thanks, that worked!</description>
      <pubDate>Wed, 01 Oct 2008 07:46:29 GMT</pubDate>
      <author>william.gregoire</author>
      <guid>http://communities.intel.com/openport/blogs/microsoft-vpro/2008/08/19/intel-wsman-translator-10-released#comments-2792</guid>
      <dc:date>2008-10-01T07:46:29Z</dc:date>
    </item>
    <item>
      <title>RE:&amp;nbsp;Intel AMT 3.2.1 Self-signed certificate issue and working around it for Microsoft System Configuration Manager SP1</title>
      <link>http://communities.intel.com/openport/blogs/microsoft-vpro/2008/08/19/intel-amt-321-selfsigned-certificate-issue-and-working-around-it-for-microsoft-system-configuration-manager-sp1#comments-2790</link>
      <description>Billc,&lt;br /&gt;
&lt;br /&gt;
Yes, this guide is appropriate if you are running AMT in enterprise mode.  Please note that SCCM SP1 only supports enterprise mode provisioning in a TLS configuration.  Configuring in SMB mode and unprovisioning is just the alternate way of regenerating a new self signed certificate beside running this remote provision / unprovision script.&lt;br /&gt;
&lt;br /&gt;
--Matt Royer</description>
      <pubDate>Wed, 01 Oct 2008 01:29:21 GMT</pubDate>
      <author>miroyer</author>
      <guid>http://communities.intel.com/openport/blogs/microsoft-vpro/2008/08/19/intel-amt-321-selfsigned-certificate-issue-and-working-around-it-for-microsoft-system-configuration-manager-sp1#comments-2790</guid>
      <dc:date>2008-10-01T01:29:21Z</dc:date>
    </item>
    <item>
      <title>RE:&amp;nbsp;Intel WS-MAN Translator 1.0 released</title>
      <link>http://communities.intel.com/openport/blogs/microsoft-vpro/2008/08/19/intel-wsman-translator-10-released#comments-2789</link>
      <description>The "the given key was not present in the dictionary" error when configuring the Intel WS-MAN Translator is usually related to the private key not being in the exported certificate.  When you export the certificate, you need to ensure that you export the private key and also include the certificate chain.&lt;br /&gt;
&lt;br /&gt;
--Matt Royer</description>
      <pubDate>Wed, 01 Oct 2008 01:24:36 GMT</pubDate>
      <author>miroyer</author>
      <guid>http://communities.intel.com/openport/blogs/microsoft-vpro/2008/08/19/intel-wsman-translator-10-released#comments-2789</guid>
      <dc:date>2008-10-01T01:24:36Z</dc:date>
    </item>
    <item>
      <title>RE:&amp;nbsp;vPro Machines stuck in "Detected" State?</title>
      <link>http://communities.intel.com/openport/blogs/microsoft-vpro/2008/09/17/vpro-machines-stuck-in-detected-state#comments-2747</link>
      <description>Bill,&lt;br /&gt;
&lt;br /&gt;
Absolutely.  I would download Matt's guide, then go through the 3 main steps, you will see the boxes move from detected to provisioned. if any questions either blog me back here or on Matt's post. &lt;br /&gt;
&lt;br /&gt;
Josh H</description>
      <pubDate>Mon, 22 Sep 2008 13:35:30 GMT</pubDate>
      <author>josh.hilliker</author>
      <guid>http://communities.intel.com/openport/blogs/microsoft-vpro/2008/09/17/vpro-machines-stuck-in-detected-state#comments-2747</guid>
      <dc:date>2008-09-22T13:35:30Z</dc:date>
    </item>
    <item>
      <title>RE:&amp;nbsp;vPro Machines stuck in "Detected" State?</title>
      <link>http://communities.intel.com/openport/blogs/microsoft-vpro/2008/09/17/vpro-machines-stuck-in-detected-state#comments-2745</link>
      <description>I have similar issue on provisioning. SCCM SP1 indicate the AMT status is detected or unprovisioned, but my AMT is enterprise PKI model. May I use your guide to provision it? Is it AMT bugs or SCCM bugs?&lt;br /&gt;
&lt;br /&gt;
Thanks!&lt;br /&gt;
Bill</description>
      <pubDate>Mon, 22 Sep 2008 12:02:16 GMT</pubDate>
      <author>billc</author>
      <guid>http://communities.intel.com/openport/blogs/microsoft-vpro/2008/09/17/vpro-machines-stuck-in-detected-state#comments-2745</guid>
      <dc:date>2008-09-22T12:02:16Z</dc:date>
    </item>
    <item>
      <title>RE:&amp;nbsp;Intel AMT 3.2.1 Self-signed certificate issue and working around it for Microsoft System Configuration Manager SP1</title>
      <link>http://communities.intel.com/openport/blogs/microsoft-vpro/2008/08/19/intel-amt-321-selfsigned-certificate-issue-and-working-around-it-for-microsoft-system-configuration-manager-sp1#comments-2744</link>
      <description>I have similar issue on provision and SCCM shows it's detected status, but the AMT model is enterprise. Is the guide useful for my case if I run AMT is enterprise model?&lt;br /&gt;
&lt;br /&gt;
bill</description>
      <pubDate>Mon, 22 Sep 2008 09:57:22 GMT</pubDate>
      <author>billc</author>
      <guid>http://communities.intel.com/openport/blogs/microsoft-vpro/2008/08/19/intel-amt-321-selfsigned-certificate-issue-and-working-around-it-for-microsoft-system-configuration-manager-sp1#comments-2744</guid>
      <dc:date>2008-09-22T09:57:22Z</dc:date>
    </item>
    <item>
      <title>RE:&amp;nbsp;Intel WS-MAN Translator 1.0 released</title>
      <link>http://communities.intel.com/openport/blogs/microsoft-vpro/2008/08/19/intel-wsman-translator-10-released#comments-2743</link>
      <description>No, this is still an open issue for me.&lt;br /&gt;
&lt;br /&gt;
Regading the problem "the given key was not present in the dictionary" I was told o to use the option to export the certificate with the root keys, at the time to make the PFX file. I have had the chance to try it yet (since I´m away from the project). Would you try that and tell?</description>
      <pubDate>Sun, 21 Sep 2008 20:14:33 GMT</pubDate>
      <author>william.gregoire</author>
      <guid>http://communities.intel.com/openport/blogs/microsoft-vpro/2008/08/19/intel-wsman-translator-10-released#comments-2743</guid>
      <dc:date>2008-09-21T20:14:33Z</dc:date>
    </item>
  </channel>
</rss>

