<?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: Rebuilding SIM Server in Server Management - Systems Insight Manager</title>
    <link>https://community.hpe.com/t5/server-management-systems/rebuilding-sim-server/m-p/3850214#M22233</link>
    <description>Thanks for the info, Rob.  I'll give it a try and post again if it doesn't work.</description>
    <pubDate>Mon, 28 Aug 2006 11:16:55 GMT</pubDate>
    <dc:creator>Skip Tannen</dc:creator>
    <dc:date>2006-08-28T11:16:55Z</dc:date>
    <item>
      <title>Rebuilding SIM Server</title>
      <link>https://community.hpe.com/t5/server-management-systems/rebuilding-sim-server/m-p/3850212#M22231</link>
      <description>Folks,&lt;BR /&gt;&lt;BR /&gt;I recently migrated SIM from an IBM desktop machine (don't ask) to a ProLiant server using HP's migration docs - the database and managed servers migrated fine but for some reason none of the scheduled tasks run and I'm having some VC issues.  Instead of spending a lot of time troubleshooting I'm thinking of rebuilding the SIM server from scratch with a fresh Insight installation.  I'm planning on exporting the SIM host file to get the managed servers into the new SIM installation but I'm wondering how to handle certificates.  I want to name and IP the new SIM server the same as the old one so I don't have to change SNMP on all the managed servers but how do I deal with the Cert?  Can I do an export on the existing server and then import it into the rebuilt server?  How is this done?  Is there anything else I need to consider before taking down the existing server?&lt;BR /&gt;&lt;BR /&gt;Thanks in advance.</description>
      <pubDate>Thu, 24 Aug 2006 14:48:18 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/rebuilding-sim-server/m-p/3850212#M22231</guid>
      <dc:creator>Skip Tannen</dc:creator>
      <dc:date>2006-08-24T14:48:18Z</dc:date>
    </item>
    <item>
      <title>Re: Rebuilding SIM Server</title>
      <link>https://community.hpe.com/t5/server-management-systems/rebuilding-sim-server/m-p/3850213#M22232</link>
      <description>I had a similar task recently and I got around the certificate issue in the following way.&lt;BR /&gt;This does rely on having a common domain account or similar as it uses the Deploy PSP option.&lt;BR /&gt;When the Server has been rebuilt export the certificate from the new server.&lt;BR /&gt;From the VCRM, reconfigure the Management Agent and use the new certifcate - generally just a cut and paste.&lt;BR /&gt;Now the fun bit.&lt;BR /&gt;From the VCRM Create a new Custom Baseline and include only the Management Agent you've updated above.&lt;BR /&gt;From HPSIM, goto Deploy and select the Proliant Support Pack Install, at the appropriate point select the Custom Baseline that just has the SMH Agent.&lt;BR /&gt;Also ensure the Overwrite buton is checked as you want to update those versions that are current.&lt;BR /&gt;Deploy to all of your Servers.&lt;BR /&gt;This shouldn't need a reboot for the SMH.</description>
      <pubDate>Thu, 24 Aug 2006 18:15:44 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/rebuilding-sim-server/m-p/3850213#M22232</guid>
      <dc:creator>Rob Buxton</dc:creator>
      <dc:date>2006-08-24T18:15:44Z</dc:date>
    </item>
    <item>
      <title>Re: Rebuilding SIM Server</title>
      <link>https://community.hpe.com/t5/server-management-systems/rebuilding-sim-server/m-p/3850214#M22233</link>
      <description>Thanks for the info, Rob.  I'll give it a try and post again if it doesn't work.</description>
      <pubDate>Mon, 28 Aug 2006 11:16:55 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/rebuilding-sim-server/m-p/3850214#M22233</guid>
      <dc:creator>Skip Tannen</dc:creator>
      <dc:date>2006-08-28T11:16:55Z</dc:date>
    </item>
  </channel>
</rss>

