<?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: RDeploy hangs during image creation in ProLiant Deployment and Provisioning</title>
    <link>https://community.hpe.com/t5/proliant-deployment-and/rdeploy-hangs-during-image-creation/m-p/3444137#M1348</link>
    <description>Note what IP the blade gets as soon as the PXE boot prcoess starts - it says "CLIENT IP=x.x.x.x". Shut the blade down and ping that address. Most likely you have something configured to use that address and it was not reserved in DHCP. Set a reservation in DHCP for that address and reserve it to aabbccddeeff and no one will ever get it. Do this even if nothing replies to your ping (this happens if the device doesn't respond to ICMP).</description>
    <pubDate>Wed, 15 Dec 2004 11:03:07 GMT</pubDate>
    <dc:creator>Jeff Allen_5</dc:creator>
    <dc:date>2004-12-15T11:03:07Z</dc:date>
    <item>
      <title>RDeploy hangs during image creation</title>
      <link>https://community.hpe.com/t5/proliant-deployment-and/rdeploy-hangs-during-image-creation/m-p/3444136#M1347</link>
      <description>We have been using RDP to create and deploy images on our HP BL20P blades for several months now, without incident. Recently these processes become hit and miss and now they seem to stop working altogether. &lt;BR /&gt;   We setup an image creation job and send it to the desired blade. The blade powers down, goes into PXE mode, obtains an DHCP IP Address but then hangs at "Initializing TCPIP over DHCP" and will not continue. &lt;BR /&gt;   We have tried resetting our DHCP Server, Reseating the blade, and re-installed the altiris client. RDP was installed over a prior install of Altiris deployment server and our RDP console version is 6.1, SP1.&lt;BR /&gt;   Any thoughts would be greating appreciated.</description>
      <pubDate>Wed, 15 Dec 2004 07:26:29 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-deployment-and/rdeploy-hangs-during-image-creation/m-p/3444136#M1347</guid>
      <dc:creator>Joe Buerkle</dc:creator>
      <dc:date>2004-12-15T07:26:29Z</dc:date>
    </item>
    <item>
      <title>Re: RDeploy hangs during image creation</title>
      <link>https://community.hpe.com/t5/proliant-deployment-and/rdeploy-hangs-during-image-creation/m-p/3444137#M1348</link>
      <description>Note what IP the blade gets as soon as the PXE boot prcoess starts - it says "CLIENT IP=x.x.x.x". Shut the blade down and ping that address. Most likely you have something configured to use that address and it was not reserved in DHCP. Set a reservation in DHCP for that address and reserve it to aabbccddeeff and no one will ever get it. Do this even if nothing replies to your ping (this happens if the device doesn't respond to ICMP).</description>
      <pubDate>Wed, 15 Dec 2004 11:03:07 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-deployment-and/rdeploy-hangs-during-image-creation/m-p/3444137#M1348</guid>
      <dc:creator>Jeff Allen_5</dc:creator>
      <dc:date>2004-12-15T11:03:07Z</dc:date>
    </item>
  </channel>
</rss>

