<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic vPro in a Multi-Domain Environment in Intel vPro® Platform</title>
    <link>https://community.intel.com/t5/Intel-vPro-Platform/vPro-in-a-Multi-Domain-Environment/m-p/223152#M756</link>
    <description>&lt;P&gt;Hi All,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I just wanted to share the scenario and fix for similar types of hierarchy as we do. Currently, we have 2 domains that we deal with. &lt;A href="http://Domain1.int"&gt;Domain1.int&lt;/A&gt; and &lt;A href="http://Domain2.int"&gt;Domain2.int&lt;/A&gt; (for examples). In &lt;A href="http://Domain1.int"&gt;Domain1.int&lt;/A&gt;, we have our Enterprise CA which handles all the the domains certificate needs. In &lt;A href="http://Domain2.int"&gt;Domain2.int&lt;/A&gt;, we have&lt;/P&gt;&lt;P&gt;out SCCM SP1 Primary Site Server named &lt;A href="http://pri-sccm01.domain2.int"&gt;pri-sccm01.domain2.int&lt;/A&gt;. We were able to exclude the 3rd party certificate as the source of the issue because&lt;/P&gt;&lt;P&gt;we could get the OOB SP to recognize, connect, id the machine as a vPro box, and start the provision. It looked like there was a problem with the Web Server certificate not being able to see the trusted root. Becuase of this, the process broke down as it was not able to issue a certification for the machine&lt;/P&gt;&lt;P&gt;to be provisioned.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In Amtopmgr.log, we saw the following "Missed device certificate. To provision device with TLS server or Mutual Auth mode, device certificate is required." So we referenced &lt;A href="http://technet.microsoft.com/en-us/library/cc161803.aspx"&gt;http://technet.microsoft.com/en-us/library/cc161803.aspx&lt;/A&gt; &lt;A href="http://technet.microsoft.com/en-us/library/cc161803.aspx"&gt;http://technet.microsoft.com/en-us/library/cc161803.aspx&lt;/A&gt; and saw the corresponding entry. At first we a certificate chain issue and something wrong with our PKI. While that was a problem, it wasn't the root cause. The issue is that our SCCM OOB Point needed access to act as a CA itself to have permissions to and revoke certificates. The problem is that we didn't anticipate the issue from our lab testing. We set up our lab as a single domain with the CA and the SCCM box on the same level.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Ultimately, the fix was the next entry below the "Missing device certificate..." entry. Upon inspection of the amtproxymgr.log, we saw ERROR: ICertRequest2-&amp;gt;Submit failed: 0x80070005. The issue was that we needed to get our &lt;A href="http://pri-sccm001.domain2.int"&gt;pri-sccm001.domain2.int&lt;/A&gt; into the security group CERTSRV_DOM_ACCESS in &lt;A href="http://domain1.int"&gt;domain1.int&lt;/A&gt;. We bounced the server and we were then able to provision machines pretty happily. I hope this helps someone down the road. Happy trails!&lt;/P&gt;</description>
    <pubDate>Fri, 08 May 2009 18:13:55 GMT</pubDate>
    <dc:creator>idata</dc:creator>
    <dc:date>2009-05-08T18:13:55Z</dc:date>
    <item>
      <title>vPro in a Multi-Domain Environment</title>
      <link>https://community.intel.com/t5/Intel-vPro-Platform/vPro-in-a-Multi-Domain-Environment/m-p/223152#M756</link>
      <description>&lt;P&gt;Hi All,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I just wanted to share the scenario and fix for similar types of hierarchy as we do. Currently, we have 2 domains that we deal with. &lt;A href="http://Domain1.int"&gt;Domain1.int&lt;/A&gt; and &lt;A href="http://Domain2.int"&gt;Domain2.int&lt;/A&gt; (for examples). In &lt;A href="http://Domain1.int"&gt;Domain1.int&lt;/A&gt;, we have our Enterprise CA which handles all the the domains certificate needs. In &lt;A href="http://Domain2.int"&gt;Domain2.int&lt;/A&gt;, we have&lt;/P&gt;&lt;P&gt;out SCCM SP1 Primary Site Server named &lt;A href="http://pri-sccm01.domain2.int"&gt;pri-sccm01.domain2.int&lt;/A&gt;. We were able to exclude the 3rd party certificate as the source of the issue because&lt;/P&gt;&lt;P&gt;we could get the OOB SP to recognize, connect, id the machine as a vPro box, and start the provision. It looked like there was a problem with the Web Server certificate not being able to see the trusted root. Becuase of this, the process broke down as it was not able to issue a certification for the machine&lt;/P&gt;&lt;P&gt;to be provisioned.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In Amtopmgr.log, we saw the following "Missed device certificate. To provision device with TLS server or Mutual Auth mode, device certificate is required." So we referenced &lt;A href="http://technet.microsoft.com/en-us/library/cc161803.aspx"&gt;http://technet.microsoft.com/en-us/library/cc161803.aspx&lt;/A&gt; &lt;A href="http://technet.microsoft.com/en-us/library/cc161803.aspx"&gt;http://technet.microsoft.com/en-us/library/cc161803.aspx&lt;/A&gt; and saw the corresponding entry. At first we a certificate chain issue and something wrong with our PKI. While that was a problem, it wasn't the root cause. The issue is that our SCCM OOB Point needed access to act as a CA itself to have permissions to and revoke certificates. The problem is that we didn't anticipate the issue from our lab testing. We set up our lab as a single domain with the CA and the SCCM box on the same level.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Ultimately, the fix was the next entry below the "Missing device certificate..." entry. Upon inspection of the amtproxymgr.log, we saw ERROR: ICertRequest2-&amp;gt;Submit failed: 0x80070005. The issue was that we needed to get our &lt;A href="http://pri-sccm001.domain2.int"&gt;pri-sccm001.domain2.int&lt;/A&gt; into the security group CERTSRV_DOM_ACCESS in &lt;A href="http://domain1.int"&gt;domain1.int&lt;/A&gt;. We bounced the server and we were then able to provision machines pretty happily. I hope this helps someone down the road. Happy trails!&lt;/P&gt;</description>
      <pubDate>Fri, 08 May 2009 18:13:55 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-vPro-Platform/vPro-in-a-Multi-Domain-Environment/m-p/223152#M756</guid>
      <dc:creator>idata</dc:creator>
      <dc:date>2009-05-08T18:13:55Z</dc:date>
    </item>
  </channel>
</rss>

