<?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 AEH -- 1 step forward, 2 steps back in Server Management - Systems Insight Manager</title>
    <link>https://community.hpe.com/t5/server-management-systems/aeh-1-step-forward-2-steps-back/m-p/3221658#M1837</link>
    <description>While combining the CIM7 event query and notification task functions into SIM Automatic Event Handling tasks is a welcome change, the loss of granularity in creating those tasks is a huge disappointment.&lt;BR /&gt;&lt;BR /&gt;In CIM7, I can create a query and select the specific servers and events I want notification on simply by clicking a few checkboxes, or by selecting an entire category and deselecting the few events I don't want included.  This ability does not exist in SIM.  Instead, one must add several "OR" entries.  It's bad enough to have to do this for the specific servers in a query, to do this for specific events within a few categories would be a nightmare.  I hope HP realizes what a huge mistake they've made with this, as this is enough to keep us from making the switch from CIM7</description>
    <pubDate>Wed, 17 Mar 2004 10:55:32 GMT</pubDate>
    <dc:creator>Jeff Cottrill_1</dc:creator>
    <dc:date>2004-03-17T10:55:32Z</dc:date>
    <item>
      <title>AEH -- 1 step forward, 2 steps back</title>
      <link>https://community.hpe.com/t5/server-management-systems/aeh-1-step-forward-2-steps-back/m-p/3221658#M1837</link>
      <description>While combining the CIM7 event query and notification task functions into SIM Automatic Event Handling tasks is a welcome change, the loss of granularity in creating those tasks is a huge disappointment.&lt;BR /&gt;&lt;BR /&gt;In CIM7, I can create a query and select the specific servers and events I want notification on simply by clicking a few checkboxes, or by selecting an entire category and deselecting the few events I don't want included.  This ability does not exist in SIM.  Instead, one must add several "OR" entries.  It's bad enough to have to do this for the specific servers in a query, to do this for specific events within a few categories would be a nightmare.  I hope HP realizes what a huge mistake they've made with this, as this is enough to keep us from making the switch from CIM7</description>
      <pubDate>Wed, 17 Mar 2004 10:55:32 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/aeh-1-step-forward-2-steps-back/m-p/3221658#M1837</guid>
      <dc:creator>Jeff Cottrill_1</dc:creator>
      <dc:date>2004-03-17T10:55:32Z</dc:date>
    </item>
    <item>
      <title>Re: AEH -- 1 step forward, 2 steps back</title>
      <link>https://community.hpe.com/t5/server-management-systems/aeh-1-step-forward-2-steps-back/m-p/3221659#M1838</link>
      <description>Jeff,&lt;BR /&gt;A suggestion I've made is to be able to use System Lists for AEH. This would allow you to create a view of certain Servers for user viewing and to use the same view for event reporting. It would save work because if you added / changedd servers there would jut be the single list to update rather than various queries etc.&lt;BR /&gt;&lt;BR /&gt;I've stuck with my old way of doing things, I have a general query which uses the application launch and a perl script. It then makes some of the determinations as to when to e-mail etc, including reading a Server exclusion list I can update quickly.</description>
      <pubDate>Wed, 17 Mar 2004 14:27:22 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/aeh-1-step-forward-2-steps-back/m-p/3221659#M1838</guid>
      <dc:creator>Rob Buxton</dc:creator>
      <dc:date>2004-03-17T14:27:22Z</dc:date>
    </item>
  </channel>
</rss>

