<?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 Re: Multi-Client IDER boot to iso in Intel vPro® Platform</title>
    <link>https://community.intel.com/t5/Intel-vPro-Platform/Multi-Client-IDER-boot-to-iso/m-p/232923#M1508</link>
    <description>&lt;P&gt;yes. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Have done with Altiris - created a task\job for IDER boot (both forcing PXE and defined DOS ISO) - and successfully booted 4 of the 5 systems in my lab.  The 5th system that didn't boot appears to have a firmware issue.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If planning multiple IDER sessions - have to reboot between each.  Haven't done a network\services trace - yet it appears the connection between the server and the vPro\AMT system remains from the IDE-Redirect session until next system boot.  This makes sense since by definition the IDE-R boot overrides the client's BIOS boot order.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Also - noticed that if I tried to force session, after session, after session... eventually the server starts to be the hold up.  Working with a virtualized server environment and have resource constraints.  During one IDER test - the client systems didn't appear to respond.  However - when I reset the virtual server environment, the queued up jobs commenced once the server completed loading\logon.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;haven't stress tested how many concurrent IDER sessions can be run&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- TC&lt;/P&gt;</description>
    <pubDate>Thu, 29 May 2008 21:26:36 GMT</pubDate>
    <dc:creator>Terry_C_Intel</dc:creator>
    <dc:date>2008-05-29T21:26:36Z</dc:date>
    <item>
      <title>Multi-Client IDER boot to iso</title>
      <link>https://community.intel.com/t5/Intel-vPro-Platform/Multi-Client-IDER-boot-to-iso/m-p/232922#M1507</link>
      <description>&lt;P&gt;Anyone successfully launched multiple IDER sessions using an SMS collection or Altiris job?&lt;/P&gt;</description>
      <pubDate>Thu, 29 May 2008 18:20:59 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-vPro-Platform/Multi-Client-IDER-boot-to-iso/m-p/232922#M1507</guid>
      <dc:creator>idata</dc:creator>
      <dc:date>2008-05-29T18:20:59Z</dc:date>
    </item>
    <item>
      <title>Re: Multi-Client IDER boot to iso</title>
      <link>https://community.intel.com/t5/Intel-vPro-Platform/Multi-Client-IDER-boot-to-iso/m-p/232923#M1508</link>
      <description>&lt;P&gt;yes. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Have done with Altiris - created a task\job for IDER boot (both forcing PXE and defined DOS ISO) - and successfully booted 4 of the 5 systems in my lab.  The 5th system that didn't boot appears to have a firmware issue.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If planning multiple IDER sessions - have to reboot between each.  Haven't done a network\services trace - yet it appears the connection between the server and the vPro\AMT system remains from the IDE-Redirect session until next system boot.  This makes sense since by definition the IDE-R boot overrides the client's BIOS boot order.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Also - noticed that if I tried to force session, after session, after session... eventually the server starts to be the hold up.  Working with a virtualized server environment and have resource constraints.  During one IDER test - the client systems didn't appear to respond.  However - when I reset the virtual server environment, the queued up jobs commenced once the server completed loading\logon.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;haven't stress tested how many concurrent IDER sessions can be run&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- TC&lt;/P&gt;</description>
      <pubDate>Thu, 29 May 2008 21:26:36 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-vPro-Platform/Multi-Client-IDER-boot-to-iso/m-p/232923#M1508</guid>
      <dc:creator>Terry_C_Intel</dc:creator>
      <dc:date>2008-05-29T21:26:36Z</dc:date>
    </item>
    <item>
      <title>Re: Multi-Client IDER boot to iso</title>
      <link>https://community.intel.com/t5/Intel-vPro-Platform/Multi-Client-IDER-boot-to-iso/m-p/232924#M1509</link>
      <description>&lt;P&gt;&lt;/P&gt;&lt;P&gt;After remotely Power-Cycling the clients from the SMS collection container, i could get 10/10 clients to launch IDER sessions.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;thanks!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 30 May 2008 18:25:17 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-vPro-Platform/Multi-Client-IDER-boot-to-iso/m-p/232924#M1509</guid>
      <dc:creator>idata</dc:creator>
      <dc:date>2008-05-30T18:25:17Z</dc:date>
    </item>
  </channel>
</rss>

