<?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: Yet another Version Control question in Server Management - Systems Insight Manager</title>
    <link>https://community.hpe.com/t5/server-management-systems/yet-another-version-control-question/m-p/3373017#M5737</link>
    <description>Ok thanks, since I've so far only deployed using pre-config'ed HP bundles where I've entered the system name (and/or fqdn), is there any good ideas on how to roll out a certificate based login during setup of new servers and also to existing servers ? (I really don't feel like logging in to 1100 servers manually... ;-))&lt;BR /&gt;&lt;BR /&gt;Also it's kind of strange that it works sometimes and sometimes not, does anyone know what is best practice to use ? Name or certificate, my HP contact says HP themselves uses trust by name.</description>
    <pubDate>Tue, 07 Sep 2004 05:55:29 GMT</pubDate>
    <dc:creator>Mikael Rönnbäck</dc:creator>
    <dc:date>2004-09-07T05:55:29Z</dc:date>
    <item>
      <title>Yet another Version Control question</title>
      <link>https://community.hpe.com/t5/server-management-systems/yet-another-version-control-question/m-p/3373014#M5734</link>
      <description>Since upgrading from CIM7 to HPSIM I'm getting a "no trust relation established" for most of my systems. If all systems had had this failure I would have thought of it as just an upgrade issue that needed re-config. but now some of the systems actually work properly and still have the same settings as the ones that do not work. (I'm using Trust By Name)&lt;BR /&gt;Any ideas what to look for, the manual does not tell me very much on this issue ?</description>
      <pubDate>Mon, 06 Sep 2004 09:15:40 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/yet-another-version-control-question/m-p/3373014#M5734</guid>
      <dc:creator>Mikael Rönnbäck</dc:creator>
      <dc:date>2004-09-06T09:15:40Z</dc:date>
    </item>
    <item>
      <title>Re: Yet another Version Control question</title>
      <link>https://community.hpe.com/t5/server-management-systems/yet-another-version-control-question/m-p/3373015#M5735</link>
      <description>Mikael,&lt;BR /&gt;I didn't migrate, so I can only guess. Possibly HPSIM makes more use of FQDNs and it's showing up as a difference.&lt;BR /&gt;&lt;BR /&gt;I use Trust by certificate which seems to work well.</description>
      <pubDate>Mon, 06 Sep 2004 19:25:24 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/yet-another-version-control-question/m-p/3373015#M5735</guid>
      <dc:creator>Rob Buxton</dc:creator>
      <dc:date>2004-09-06T19:25:24Z</dc:date>
    </item>
    <item>
      <title>Re: Yet another Version Control question</title>
      <link>https://community.hpe.com/t5/server-management-systems/yet-another-version-control-question/m-p/3373016#M5736</link>
      <description>I agree with Rob - I tried using "trust by name" and "trust all" (not a good idea, but I was getting desperate!). Using "trust by certificate" and importing the certificate of the CMS on each server seems to work the best. &lt;BR /&gt;&lt;BR /&gt;One tip, if you use the same machine all the time to access SIM, it's worth installing the certificates of each individual machine as you go along - that way it stops nagging you all the time!</description>
      <pubDate>Tue, 07 Sep 2004 04:34:40 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/yet-another-version-control-question/m-p/3373016#M5736</guid>
      <dc:creator>Colin Moors</dc:creator>
      <dc:date>2004-09-07T04:34:40Z</dc:date>
    </item>
    <item>
      <title>Re: Yet another Version Control question</title>
      <link>https://community.hpe.com/t5/server-management-systems/yet-another-version-control-question/m-p/3373017#M5737</link>
      <description>Ok thanks, since I've so far only deployed using pre-config'ed HP bundles where I've entered the system name (and/or fqdn), is there any good ideas on how to roll out a certificate based login during setup of new servers and also to existing servers ? (I really don't feel like logging in to 1100 servers manually... ;-))&lt;BR /&gt;&lt;BR /&gt;Also it's kind of strange that it works sometimes and sometimes not, does anyone know what is best practice to use ? Name or certificate, my HP contact says HP themselves uses trust by name.</description>
      <pubDate>Tue, 07 Sep 2004 05:55:29 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/yet-another-version-control-question/m-p/3373017#M5737</guid>
      <dc:creator>Mikael Rönnbäck</dc:creator>
      <dc:date>2004-09-07T05:55:29Z</dc:date>
    </item>
    <item>
      <title>Re: Yet another Version Control question</title>
      <link>https://community.hpe.com/t5/server-management-systems/yet-another-version-control-question/m-p/3373018#M5738</link>
      <description>Mikael,&lt;BR /&gt;You can configure the Agents with the HPSIM Server Certifacte, you just export it to a file and then cut 'n' paste that into the Agent Configuration.&lt;BR /&gt;So, when you deploy the Agents you've got all of your settings already there.&lt;BR /&gt;&lt;BR /&gt;Alas, becasue this is a Trust issue, you may not be able to use the Replicate Agent Settings</description>
      <pubDate>Tue, 07 Sep 2004 15:39:34 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/yet-another-version-control-question/m-p/3373018#M5738</guid>
      <dc:creator>Rob Buxton</dc:creator>
      <dc:date>2004-09-07T15:39:34Z</dc:date>
    </item>
    <item>
      <title>Re: Yet another Version Control question</title>
      <link>https://community.hpe.com/t5/server-management-systems/yet-another-version-control-question/m-p/3373019#M5739</link>
      <description>Thanks for the advice, I will try that at out nexr driver upgrade, in the meantime I will have to live with trust by name.</description>
      <pubDate>Thu, 09 Sep 2004 06:15:24 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/yet-another-version-control-question/m-p/3373019#M5739</guid>
      <dc:creator>Mikael Rönnbäck</dc:creator>
      <dc:date>2004-09-09T06:15:24Z</dc:date>
    </item>
  </channel>
</rss>

