<?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: Sim v5 SP4 and Identification of Win2k3 Servers in Server Management - Systems Insight Manager</title>
    <link>https://community.hpe.com/t5/server-management-systems/sim-v5-sp4-and-identification-of-win2k3-servers/m-p/3779389#M19901</link>
    <description>Looks like we may have sorted it.  In SNMP setting, "Accept SNMP packets from these hosts" was selected, and only the SIM server was added.  Adding the "localhost" fixed the issue.</description>
    <pubDate>Fri, 28 Apr 2006 04:31:00 GMT</pubDate>
    <dc:creator>Malcolm Nicholson</dc:creator>
    <dc:date>2006-04-28T04:31:00Z</dc:date>
    <item>
      <title>Sim v5 SP4 and Identification of Win2k3 Servers</title>
      <link>https://community.hpe.com/t5/server-management-systems/sim-v5-sp4-and-identification-of-win2k3-servers/m-p/3779384#M19896</link>
      <description>We have mixed win2k and win2k3 servers being monitored via SIM.  However we get no information about win2k3 servers, no Product Name, no OS name, only IP data.&lt;BR /&gt;&lt;BR /&gt;Any ideas?</description>
      <pubDate>Fri, 28 Apr 2006 02:36:16 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/sim-v5-sp4-and-identification-of-win2k3-servers/m-p/3779384#M19896</guid>
      <dc:creator>Malcolm Nicholson</dc:creator>
      <dc:date>2006-04-28T02:36:16Z</dc:date>
    </item>
    <item>
      <title>Re: Sim v5 SP4 and Identification of Win2k3 Servers</title>
      <link>https://community.hpe.com/t5/server-management-systems/sim-v5-sp4-and-identification-of-win2k3-servers/m-p/3779385#M19897</link>
      <description>Have you installed SNMP and configured it with the proper community strings? Also trap destination to SIM server?&lt;BR /&gt;When that is done do a hardware and software status polling.&lt;BR /&gt;&lt;BR /&gt;Rgds,&lt;BR /&gt;&lt;BR /&gt;Albert</description>
      <pubDate>Fri, 28 Apr 2006 02:48:49 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/sim-v5-sp4-and-identification-of-win2k3-servers/m-p/3779385#M19897</guid>
      <dc:creator>Albert Austin</dc:creator>
      <dc:date>2006-04-28T02:48:49Z</dc:date>
    </item>
    <item>
      <title>Re: Sim v5 SP4 and Identification of Win2k3 Servers</title>
      <link>https://community.hpe.com/t5/server-management-systems/sim-v5-sp4-and-identification-of-win2k3-servers/m-p/3779386#M19898</link>
      <description>Also forgot to ask if all agents have been installed? Version control agent configured to point to VCRM manager. That should give you OS name. Do a Software polling after configuring agents.</description>
      <pubDate>Fri, 28 Apr 2006 02:51:41 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/sim-v5-sp4-and-identification-of-win2k3-servers/m-p/3779386#M19898</guid>
      <dc:creator>Albert Austin</dc:creator>
      <dc:date>2006-04-28T02:51:41Z</dc:date>
    </item>
    <item>
      <title>Re: Sim v5 SP4 and Identification of Win2k3 Servers</title>
      <link>https://community.hpe.com/t5/server-management-systems/sim-v5-sp4-and-identification-of-win2k3-servers/m-p/3779387#M19899</link>
      <description>An oldy already, but still usefull:&lt;BR /&gt;&lt;A href="http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=969565" target="_blank"&gt;http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=969565&lt;/A&gt;</description>
      <pubDate>Fri, 28 Apr 2006 03:00:59 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/sim-v5-sp4-and-identification-of-win2k3-servers/m-p/3779387#M19899</guid>
      <dc:creator>Ferry Steenvoorde</dc:creator>
      <dc:date>2006-04-28T03:00:59Z</dc:date>
    </item>
    <item>
      <title>Re: Sim v5 SP4 and Identification of Win2k3 Servers</title>
      <link>https://community.hpe.com/t5/server-management-systems/sim-v5-sp4-and-identification-of-win2k3-servers/m-p/3779388#M19900</link>
      <description>I've found a win2k3 system that is being identified correctly.  And it has the same settings as the systems that aren't.&lt;BR /&gt;&lt;BR /&gt;I've also noticed that on the systems, that are not being identified correctly, the Systems Management Homepage cannot be loaded correctly locally on the server.</description>
      <pubDate>Fri, 28 Apr 2006 03:39:10 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/sim-v5-sp4-and-identification-of-win2k3-servers/m-p/3779388#M19900</guid>
      <dc:creator>Malcolm Nicholson</dc:creator>
      <dc:date>2006-04-28T03:39:10Z</dc:date>
    </item>
    <item>
      <title>Re: Sim v5 SP4 and Identification of Win2k3 Servers</title>
      <link>https://community.hpe.com/t5/server-management-systems/sim-v5-sp4-and-identification-of-win2k3-servers/m-p/3779389#M19901</link>
      <description>Looks like we may have sorted it.  In SNMP setting, "Accept SNMP packets from these hosts" was selected, and only the SIM server was added.  Adding the "localhost" fixed the issue.</description>
      <pubDate>Fri, 28 Apr 2006 04:31:00 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/sim-v5-sp4-and-identification-of-win2k3-servers/m-p/3779389#M19901</guid>
      <dc:creator>Malcolm Nicholson</dc:creator>
      <dc:date>2006-04-28T04:31:00Z</dc:date>
    </item>
  </channel>
</rss>

