<?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: Automation of firmware updates in Servers - General</title>
    <link>https://community.hpe.com/t5/servers-general/automation-of-firmware-updates/m-p/7027203#M9498</link>
    <description>&lt;P&gt;For ILO (4 and later) you may also consider ILO federation and ILO Amplifier.&lt;/P&gt;</description>
    <pubDate>Fri, 30 Nov 2018 13:54:18 GMT</pubDate>
    <dc:creator>Torsten.</dc:creator>
    <dc:date>2018-11-30T13:54:18Z</dc:date>
    <item>
      <title>Automation of firmware updates</title>
      <link>https://community.hpe.com/t5/servers-general/automation-of-firmware-updates/m-p/7027190#M9495</link>
      <description>&lt;P&gt;Hello all,&lt;/P&gt;&lt;P&gt;Sorry if I missed a conversation regarding this topic, but I was wondering if number of servers (DL160, 360, 380, 580, Gen7, Gen8, Gen9, c7000 chassis etc.) could be automatically updated when it comes to firmware (SPP)?&lt;/P&gt;&lt;P&gt;I have found some cdmlet's for POSH, like HPEiLOCmdlets or&amp;nbsp;HPOneView.400 (OneView appliances) but I cant seem to find any solution for SPP updates. Our organisation has hudreds of these servers, and this would significantly saved our time..&lt;/P&gt;&lt;P&gt;Any proposals?&amp;nbsp;&lt;/P&gt;&lt;P&gt;BR,&lt;BR /&gt;Nikola.&lt;/P&gt;</description>
      <pubDate>Fri, 30 Nov 2018 11:48:03 GMT</pubDate>
      <guid>https://community.hpe.com/t5/servers-general/automation-of-firmware-updates/m-p/7027190#M9495</guid>
      <dc:creator>Nikolape</dc:creator>
      <dc:date>2018-11-30T11:48:03Z</dc:date>
    </item>
    <item>
      <title>Re: Automation of firmware updates</title>
      <link>https://community.hpe.com/t5/servers-general/automation-of-firmware-updates/m-p/7027199#M9496</link>
      <description>&lt;P&gt;It depends on your needs ...&lt;/P&gt;&lt;P&gt;You can mount a SPP image to ILO and let a server boot from in order to update the firmware ...&lt;/P&gt;&lt;P&gt;You can run a SUM with a SPP baseline as a remote session against a server to update firmware and drivers ...&lt;/P&gt;&lt;P&gt;You can automate all this by using OneView starting with Gen8 servers and using a standard or custom SPP as a baseline ...&lt;/P&gt;</description>
      <pubDate>Fri, 30 Nov 2018 13:39:35 GMT</pubDate>
      <guid>https://community.hpe.com/t5/servers-general/automation-of-firmware-updates/m-p/7027199#M9496</guid>
      <dc:creator>Torsten.</dc:creator>
      <dc:date>2018-11-30T13:39:35Z</dc:date>
    </item>
    <item>
      <title>Re: Automation of firmware updates</title>
      <link>https://community.hpe.com/t5/servers-general/automation-of-firmware-updates/m-p/7027201#M9497</link>
      <description>&lt;P&gt;Hello Torsten,&lt;/P&gt;&lt;P&gt;Thanks for reply.&amp;nbsp;&lt;/P&gt;&lt;P&gt;I know these options. But I was interested in another solution, if there is one. For example, we wrote some scripts using POSH and&amp;nbsp;HPEiLOCmdlets for updating iLO's. For a defined list of IP's (defined in some .csv file) update iLO, and command runs serially (when one iLO is updated, it connects to other and so on).&amp;nbsp;&lt;/P&gt;&lt;P&gt;The task of server updates (SPP) would be much easier, if we could script these jobs too.&amp;nbsp;&lt;/P&gt;&lt;P&gt;BR,&lt;BR /&gt;Nikola.&lt;/P&gt;</description>
      <pubDate>Fri, 30 Nov 2018 13:52:02 GMT</pubDate>
      <guid>https://community.hpe.com/t5/servers-general/automation-of-firmware-updates/m-p/7027201#M9497</guid>
      <dc:creator>Nikolape</dc:creator>
      <dc:date>2018-11-30T13:52:02Z</dc:date>
    </item>
    <item>
      <title>Re: Automation of firmware updates</title>
      <link>https://community.hpe.com/t5/servers-general/automation-of-firmware-updates/m-p/7027203#M9498</link>
      <description>&lt;P&gt;For ILO (4 and later) you may also consider ILO federation and ILO Amplifier.&lt;/P&gt;</description>
      <pubDate>Fri, 30 Nov 2018 13:54:18 GMT</pubDate>
      <guid>https://community.hpe.com/t5/servers-general/automation-of-firmware-updates/m-p/7027203#M9498</guid>
      <dc:creator>Torsten.</dc:creator>
      <dc:date>2018-11-30T13:54:18Z</dc:date>
    </item>
    <item>
      <title>Re: Automation of firmware updates</title>
      <link>https://community.hpe.com/t5/servers-general/automation-of-firmware-updates/m-p/7027205#M9499</link>
      <description>&lt;P&gt;What are those? POSH cmdlets?&lt;/P&gt;</description>
      <pubDate>Fri, 30 Nov 2018 13:56:01 GMT</pubDate>
      <guid>https://community.hpe.com/t5/servers-general/automation-of-firmware-updates/m-p/7027205#M9499</guid>
      <dc:creator>Nikolape</dc:creator>
      <dc:date>2018-11-30T13:56:01Z</dc:date>
    </item>
    <item>
      <title>Re: Automation of firmware updates</title>
      <link>https://community.hpe.com/t5/servers-general/automation-of-firmware-updates/m-p/7027207#M9500</link>
      <description>&lt;P&gt;ILO federation is a built-in functionality, ILO Amplifier is an appliance.&lt;/P&gt;</description>
      <pubDate>Fri, 30 Nov 2018 13:57:44 GMT</pubDate>
      <guid>https://community.hpe.com/t5/servers-general/automation-of-firmware-updates/m-p/7027207#M9500</guid>
      <dc:creator>Torsten.</dc:creator>
      <dc:date>2018-11-30T13:57:44Z</dc:date>
    </item>
    <item>
      <title>Re: Automation of firmware updates</title>
      <link>https://community.hpe.com/t5/servers-general/automation-of-firmware-updates/m-p/7027208#M9501</link>
      <description>&lt;P&gt;Tnx Torsten,&lt;/P&gt;&lt;P&gt;iLO Amplifier seems preety fine for me. I will get into this a bit further.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 30 Nov 2018 14:09:16 GMT</pubDate>
      <guid>https://community.hpe.com/t5/servers-general/automation-of-firmware-updates/m-p/7027208#M9501</guid>
      <dc:creator>Nikolape</dc:creator>
      <dc:date>2018-11-30T14:09:16Z</dc:date>
    </item>
    <item>
      <title>Re: Automation of firmware updates</title>
      <link>https://community.hpe.com/t5/servers-general/automation-of-firmware-updates/m-p/7033512#M9851</link>
      <description>&lt;P&gt;iLO Amplifier is a great tool for firmware/drivers update BUT for the moment there is only a GUI interface, there is no command line so it's impossible to script it for automation.&lt;/P&gt;</description>
      <pubDate>Mon, 04 Feb 2019 15:20:34 GMT</pubDate>
      <guid>https://community.hpe.com/t5/servers-general/automation-of-firmware-updates/m-p/7033512#M9851</guid>
      <dc:creator>Marcbis</dc:creator>
      <dc:date>2019-02-04T15:20:34Z</dc:date>
    </item>
    <item>
      <title>Re: Automation of firmware updates</title>
      <link>https://community.hpe.com/t5/servers-general/automation-of-firmware-updates/m-p/7034783#M9922</link>
      <description>&lt;P&gt;From the responses, it is obvious there are many ways to install SPP content on numerous targets.&amp;nbsp; &amp;nbsp;In my organization, we must update hundreds of Windows servers in one night, so we focus on using Powershell scripting and the command line capability of Smart Update Manager.&amp;nbsp; &amp;nbsp;We use Microsoft SCCM to distribute content (the SPP including sub-folders, but pruned of all non-Windows packages), but content distribution can be handled many ways.&amp;nbsp; Then we initiate a Powershell script on each remote target server that kicks off a CLI session of Smart Update Manager.&amp;nbsp; Here are a few fragments of the code:&lt;/P&gt;&lt;P&gt;$InstallExe = "$($InstDir)\x64\sum_bin_x64.exe"&lt;BR /&gt;$InstArgs = "/silent /allow_non_bundle_components /ignore_tpm /debuglogdir c:\logfiles&lt;/P&gt;&lt;P&gt;$Install = Start-Process -FilePath $InstallExe -ArgumentList $InstArgs -PassThru&lt;/P&gt;&lt;P&gt;Now the entire script is lengthy,&amp;nbsp; and it has logic for watching the SUM process to see when it exits, etc, but this is the high-level sequence.&lt;/P&gt;</description>
      <pubDate>Thu, 14 Feb 2019 17:38:09 GMT</pubDate>
      <guid>https://community.hpe.com/t5/servers-general/automation-of-firmware-updates/m-p/7034783#M9922</guid>
      <dc:creator>Steve_Tippett</dc:creator>
      <dc:date>2019-02-14T17:38:09Z</dc:date>
    </item>
    <item>
      <title>Re: Automation of firmware updates</title>
      <link>https://community.hpe.com/t5/servers-general/automation-of-firmware-updates/m-p/7034787#M9923</link>
      <description>Hello Steve,&lt;BR /&gt;Tnx for the reply. Can you please PM me an example of script? Do I need to install PS module for it?&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;Nikola.</description>
      <pubDate>Thu, 14 Feb 2019 18:44:23 GMT</pubDate>
      <guid>https://community.hpe.com/t5/servers-general/automation-of-firmware-updates/m-p/7034787#M9923</guid>
      <dc:creator>Nikolape</dc:creator>
      <dc:date>2019-02-14T18:44:23Z</dc:date>
    </item>
    <item>
      <title>Re: Automation of firmware updates</title>
      <link>https://community.hpe.com/t5/servers-general/automation-of-firmware-updates/m-p/7034799#M9925</link>
      <description>&lt;P&gt;Sorry, the entire script is intellectual property and cannot be shared.&amp;nbsp; I have provided the basic concept to follow in developing your own script to suit your specific needs.&amp;nbsp; No, you do not need to load any additional Powershell cmdlet modules.&amp;nbsp; You do need to stage the SPP content on all of the target servers, and I recommend pruning out the components you don't need, which greatly speeds the SPP update process.&lt;/P&gt;&lt;P&gt;While developing your script, you can test by executing the command line yourself while logged on to the server console.&lt;/P&gt;</description>
      <pubDate>Thu, 14 Feb 2019 21:33:19 GMT</pubDate>
      <guid>https://community.hpe.com/t5/servers-general/automation-of-firmware-updates/m-p/7034799#M9925</guid>
      <dc:creator>Steve_Tippett</dc:creator>
      <dc:date>2019-02-14T21:33:19Z</dc:date>
    </item>
  </channel>
</rss>

