<?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 HPE 385 G10 system provision failure in ProLiant Servers (ML,DL,SL)</title>
    <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/hpe-385-g10-system-provision-failure/m-p/7027238#M164820</link>
    <description>&lt;P&gt;Each time tring to install Win Svr 2016 from iso through intelligent provisioning, after copying data and restart only HPE enterprise logo shows up and nothing happens&lt;/P&gt;
&lt;P&gt;Have got 3 x raid 1 arrays created&lt;/P&gt;
&lt;P&gt;&lt;STRIKE&gt;confidential information has been erased&lt;/STRIKE&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Mon, 03 Dec 2018 04:51:39 GMT</pubDate>
    <dc:creator>whitecrow</dc:creator>
    <dc:date>2018-12-03T04:51:39Z</dc:date>
    <item>
      <title>HPE 385 G10 system provision failure</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/hpe-385-g10-system-provision-failure/m-p/7027238#M164820</link>
      <description>&lt;P&gt;Each time tring to install Win Svr 2016 from iso through intelligent provisioning, after copying data and restart only HPE enterprise logo shows up and nothing happens&lt;/P&gt;
&lt;P&gt;Have got 3 x raid 1 arrays created&lt;/P&gt;
&lt;P&gt;&lt;STRIKE&gt;confidential information has been erased&lt;/STRIKE&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 03 Dec 2018 04:51:39 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/hpe-385-g10-system-provision-failure/m-p/7027238#M164820</guid>
      <dc:creator>whitecrow</dc:creator>
      <dc:date>2018-12-03T04:51:39Z</dc:date>
    </item>
    <item>
      <title>Re: HPE 385 G10 system provision failure</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/hpe-385-g10-system-provision-failure/m-p/7027368#M164830</link>
      <description>&lt;P&gt;Hi Whitecrow,&lt;/P&gt;&lt;P&gt;Please check the following :&lt;/P&gt;&lt;P&gt;Ilo firmware and drivers&lt;/P&gt;&lt;P&gt;Controller firmwares&lt;/P&gt;&lt;P&gt;Please update the above firmware and drivers to resolve this issue.&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Srinath&lt;/P&gt;</description>
      <pubDate>Mon, 03 Dec 2018 10:33:57 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/hpe-385-g10-system-provision-failure/m-p/7027368#M164830</guid>
      <dc:creator>Srinath_Raju</dc:creator>
      <dc:date>2018-12-03T10:33:57Z</dc:date>
    </item>
    <item>
      <title>Re: HPE 385 G10 system provision failure</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/hpe-385-g10-system-provision-failure/m-p/7027387#M164834</link>
      <description>Found a solution to my problem&lt;BR /&gt;&lt;BR /&gt;Had to disable AMD virtualisation feature iommu in BIOS to install windows 2016... after doing that it worked ok, then had to update windows server and could reenable it...&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;I think this info should be widely accessible, as its first time i've seen such an issue... but hey took me just 3 days to get it going</description>
      <pubDate>Mon, 03 Dec 2018 12:23:31 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/hpe-385-g10-system-provision-failure/m-p/7027387#M164834</guid>
      <dc:creator>whitecrow</dc:creator>
      <dc:date>2018-12-03T12:23:31Z</dc:date>
    </item>
  </channel>
</rss>

