<?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: Script failed on BL35p in ProLiant Deployment and Provisioning</title>
    <link>https://community.hpe.com/t5/proliant-deployment-and/script-failed-on-bl35p/m-p/5007830#M8306</link>
    <description>See last comment</description>
    <pubDate>Mon, 30 Oct 2006 07:32:27 GMT</pubDate>
    <dc:creator>alonzo</dc:creator>
    <dc:date>2006-10-30T07:32:27Z</dc:date>
    <item>
      <title>Script failed on BL35p</title>
      <link>https://community.hpe.com/t5/proliant-deployment-and/script-failed-on-bl35p/m-p/5007827#M8303</link>
      <description>Hi,&lt;BR /&gt; I installed altiris 6.8 with RDP3.0.&lt;BR /&gt; I'm using WinPE to install win2k3 on blade Bl35p.&lt;BR /&gt;The script failed with following error:&lt;BR /&gt; RDeploy: the disk read or write operation referenced and invalid location&lt;BR /&gt;Status code 30.&lt;BR /&gt;It's failed on the "distribute disk image" step. .\lib\images\NTFS.IMG is existing.</description>
      <pubDate>Tue, 10 Oct 2006 12:16:14 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-deployment-and/script-failed-on-bl35p/m-p/5007827#M8303</guid>
      <dc:creator>alonzo</dc:creator>
      <dc:date>2006-10-10T12:16:14Z</dc:date>
    </item>
    <item>
      <title>Re: Script failed on BL35p</title>
      <link>https://community.hpe.com/t5/proliant-deployment-and/script-failed-on-bl35p/m-p/5007828#M8304</link>
      <description>If you go to this file from within RDP and double click on it can you open the file?  It's empty - the file only exist to do a quick format.  The key is can it open (maybe a bad file).&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Fri, 13 Oct 2006 15:33:46 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-deployment-and/script-failed-on-bl35p/m-p/5007828#M8304</guid>
      <dc:creator>Gordon Leonard</dc:creator>
      <dc:date>2006-10-13T15:33:46Z</dc:date>
    </item>
    <item>
      <title>Re: Script failed on BL35p</title>
      <link>https://community.hpe.com/t5/proliant-deployment-and/script-failed-on-bl35p/m-p/5007829#M8305</link>
      <description>&lt;!--!*#--&gt;Thanks Gordon.&lt;BR /&gt;The problem was solved by changing the Boot order controller order in the bios.&lt;BR /&gt;Move HBA to be the first indtead of IDE controller.&lt;BR /&gt;I didn't metion but the blades are without boot disk and I'm usimg boot from SAN technology.&lt;BR /&gt;Thanks&lt;BR /&gt; Alon&lt;BR /&gt;</description>
      <pubDate>Mon, 30 Oct 2006 06:20:53 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-deployment-and/script-failed-on-bl35p/m-p/5007829#M8305</guid>
      <dc:creator>alonzo</dc:creator>
      <dc:date>2006-10-30T06:20:53Z</dc:date>
    </item>
    <item>
      <title>Re: Script failed on BL35p</title>
      <link>https://community.hpe.com/t5/proliant-deployment-and/script-failed-on-bl35p/m-p/5007830#M8306</link>
      <description>See last comment</description>
      <pubDate>Mon, 30 Oct 2006 07:32:27 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-deployment-and/script-failed-on-bl35p/m-p/5007830#M8306</guid>
      <dc:creator>alonzo</dc:creator>
      <dc:date>2006-10-30T07:32:27Z</dc:date>
    </item>
  </channel>
</rss>

