<?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-image using 4.0.1 tiny image in HPE SimpliVity</title>
    <link>https://community.hpe.com/t5/hpe-simplivity/re-image-using-4-0-1-tiny-image/m-p/7127999#M2414</link>
    <description>&lt;P&gt;Hi&lt;/P&gt;&lt;P&gt;Just a couple of quick questions on this procedure.&lt;/P&gt;&lt;P&gt;1) once the SimpliVity node has been boot using the 4.0.1 img file (via iLO virtual media) does the .img file need to remain mounted during the Deployment Manager process or can it be ejected once the node is in the 'waiting to be discovered' state?&lt;/P&gt;&lt;P&gt;2) There's mention to "&lt;SPAN&gt;Unzip the deployment package to your c:\Users\&amp;lt;username&amp;gt;\Download directory for deployment managers to pick up the required files and upload them". Is it mandatory to use the Downloads folder or is it that they just need to be in the same folder from where Deployment Manager is run?&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;many thanks&lt;/SPAN&gt;&lt;/P&gt;</description>
    <pubDate>Wed, 31 Mar 2021 17:53:49 GMT</pubDate>
    <dc:creator>jlangmead</dc:creator>
    <dc:date>2021-03-31T17:53:49Z</dc:date>
    <item>
      <title>Re-image using 4.0.1 tiny image</title>
      <link>https://community.hpe.com/t5/hpe-simplivity/re-image-using-4-0-1-tiny-image/m-p/7127999#M2414</link>
      <description>&lt;P&gt;Hi&lt;/P&gt;&lt;P&gt;Just a couple of quick questions on this procedure.&lt;/P&gt;&lt;P&gt;1) once the SimpliVity node has been boot using the 4.0.1 img file (via iLO virtual media) does the .img file need to remain mounted during the Deployment Manager process or can it be ejected once the node is in the 'waiting to be discovered' state?&lt;/P&gt;&lt;P&gt;2) There's mention to "&lt;SPAN&gt;Unzip the deployment package to your c:\Users\&amp;lt;username&amp;gt;\Download directory for deployment managers to pick up the required files and upload them". Is it mandatory to use the Downloads folder or is it that they just need to be in the same folder from where Deployment Manager is run?&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;many thanks&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 31 Mar 2021 17:53:49 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-simplivity/re-image-using-4-0-1-tiny-image/m-p/7127999#M2414</guid>
      <dc:creator>jlangmead</dc:creator>
      <dc:date>2021-03-31T17:53:49Z</dc:date>
    </item>
    <item>
      <title>Re: Re-image using 4.0.1 tiny image</title>
      <link>https://community.hpe.com/t5/hpe-simplivity/re-image-using-4-0-1-tiny-image/m-p/7128008#M2415</link>
      <description>&lt;P&gt;Hi there...&lt;/P&gt;&lt;P&gt;1. At the point the Deployment "shim" is loaded, you can likely disconnect the image file, but there is no need to.&amp;nbsp; It should disconnect automatically after the deployment manager kicks off.&lt;/P&gt;&lt;P&gt;2. The package can be unzipped anywhere you want.&amp;nbsp; The only condition is that you need to copy/move your offline bundles and firmware images into the same folder as the executable (if you use the Upgrade Manager) for the app to "see" them.&amp;nbsp; The deployment manager should already have ESXi bundles and there is no option to upgrade the firmware at that time as far as I am aware.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;That said, is this a new install? or just want to rebuild an existing environment?&amp;nbsp; If new, the equipment should have been sold with Pointnext services to deploy the hardware.&lt;/P&gt;</description>
      <pubDate>Wed, 31 Mar 2021 21:21:18 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-simplivity/re-image-using-4-0-1-tiny-image/m-p/7128008#M2415</guid>
      <dc:creator>Steven Clementi</dc:creator>
      <dc:date>2021-03-31T21:21:18Z</dc:date>
    </item>
  </channel>
</rss>

