<?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: Duplicate mxguid's in SIM in Server Management - Systems Insight Manager</title>
    <link>https://community.hpe.com/t5/server-management-systems/duplicate-mxguid-s-in-sim/m-p/4892081#M45208</link>
    <description>I had that problem once long time ago and basically it took me tracing most of the relationships between tables inside SIM DB to clean that up. Unfortunately I didn't write down all the steps at that point.... but it is more then one table that you have to clean up in order to solve this. Sorry...</description>
    <pubDate>Thu, 24 Mar 2005 17:18:13 GMT</pubDate>
    <dc:creator>Peter Narkotsky_1</dc:creator>
    <dc:date>2005-03-24T17:18:13Z</dc:date>
    <item>
      <title>Duplicate mxguid's in SIM</title>
      <link>https://community.hpe.com/t5/server-management-systems/duplicate-mxguid-s-in-sim/m-p/4892080#M45207</link>
      <description>I have 2 servers which whenever I discover them they get the same mxguid in the SIM database. This means that they overwrite each other and only one ever exists in SIM. Strangely though, whichever one exists in SIM has the IP addresses of BOTH servers.&lt;BR /&gt;I've tried clearing out the entries from the devices table in the database but they always get discovered with the same mxguid.&lt;BR /&gt;Does anyone know of a SIM database checker or a resolutino to this problem?&lt;BR /&gt;&lt;BR /&gt;Thanks&lt;BR /&gt;&lt;BR /&gt;Tony Cresswell</description>
      <pubDate>Mon, 21 Mar 2005 08:32:22 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/duplicate-mxguid-s-in-sim/m-p/4892080#M45207</guid>
      <dc:creator>Tony Cresswell</dc:creator>
      <dc:date>2005-03-21T08:32:22Z</dc:date>
    </item>
    <item>
      <title>Re: Duplicate mxguid's in SIM</title>
      <link>https://community.hpe.com/t5/server-management-systems/duplicate-mxguid-s-in-sim/m-p/4892081#M45208</link>
      <description>I had that problem once long time ago and basically it took me tracing most of the relationships between tables inside SIM DB to clean that up. Unfortunately I didn't write down all the steps at that point.... but it is more then one table that you have to clean up in order to solve this. Sorry...</description>
      <pubDate>Thu, 24 Mar 2005 17:18:13 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/duplicate-mxguid-s-in-sim/m-p/4892081#M45208</guid>
      <dc:creator>Peter Narkotsky_1</dc:creator>
      <dc:date>2005-03-24T17:18:13Z</dc:date>
    </item>
    <item>
      <title>Re: Duplicate mxguid's in SIM</title>
      <link>https://community.hpe.com/t5/server-management-systems/duplicate-mxguid-s-in-sim/m-p/4892082#M45209</link>
      <description>If the server that you are adding have same GUID (Globally unique identifier) as in a existing device, then the ipaddress will be appended.&lt;BR /&gt;&lt;BR /&gt;The most common cause is from using drive imaging software, such as Altiris. When imaging systems, a globally unique identifier is used by the Web Agents and HP Systems Insight Manager for identification purposes. On Windows systems, this problem can be avoided by deleting the registry key entry, HKEY_LOCAL_MACHINE\Software\Compaq\CIMAgent\GUID, from the registry before creating the image. For systems that have already been imaged, stop the foundation agents, remove the key, and restart the agents. A new discovery corrects the problem.</description>
      <pubDate>Fri, 25 Mar 2005 12:14:07 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/duplicate-mxguid-s-in-sim/m-p/4892082#M45209</guid>
      <dc:creator>Haridas</dc:creator>
      <dc:date>2005-03-25T12:14:07Z</dc:date>
    </item>
    <item>
      <title>Re: Duplicate mxguid's in SIM</title>
      <link>https://community.hpe.com/t5/server-management-systems/duplicate-mxguid-s-in-sim/m-p/4892083#M45210</link>
      <description>I've actually found the problem, silly really but might catch someone (like me) out!&lt;BR /&gt;&lt;BR /&gt;The 3 servers that were all overwriting each other in SIM were all DL380's and all (for some unknown reason) had their Serial Numbers set in the System Partition utility set to the same value!&lt;BR /&gt;&lt;BR /&gt;SIM obviously saw them as the same server even though they had different names, ip addresses and DNS entries!</description>
      <pubDate>Tue, 29 Mar 2005 02:59:27 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/duplicate-mxguid-s-in-sim/m-p/4892083#M45210</guid>
      <dc:creator>Tony Cresswell</dc:creator>
      <dc:date>2005-03-29T02:59:27Z</dc:date>
    </item>
    <item>
      <title>Re: Duplicate mxguid's in SIM</title>
      <link>https://community.hpe.com/t5/server-management-systems/duplicate-mxguid-s-in-sim/m-p/4892084#M45211</link>
      <description>See above fix</description>
      <pubDate>Tue, 29 Mar 2005 03:00:26 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/duplicate-mxguid-s-in-sim/m-p/4892084#M45211</guid>
      <dc:creator>Tony Cresswell</dc:creator>
      <dc:date>2005-03-29T03:00:26Z</dc:date>
    </item>
  </channel>
</rss>

