Hello all, Have a somewhat generic question around SCOM R2 / Alert Differentiator / CA Connector to an existing ticketing system: I have looked at the alerts that are coming through and can not figure out a way to assign an alert to an application team (without just assigning the servername to the application team). Of course the servername comes through, however, we want to avoid assigning a server name to a application support group. We would like this to be more granular like: CRM 4.0 management pack alerts on CRM front-end server (application error only, hardware is fine) > ALERT generated > forward to CA Connector to ticketing system > Ticketing system send to application team (based on application error, not server name). With the above scenario (and understanding that the ticketing system will map accordingly), what can we use by default/custom for a differentiator so the servername is not used to assign to an application group, but rather by the application's management pack? Cheers, Greg

I think this might involve a few steps. One of the things I have used before is to send alerts based on machine role groups (Exchange servers or Exchange computers) and for instance splitting anything coming from the Sun Solrais mp to another alert channel. In the channel (for instance a script channel or even email) you can define a field/word to differentiate on. Another possibility is to find a way to assign a resolution state to an alert (for instance you create Exchange and Sun resolution states), run scripts to auto assign a lot of these to the right resol state by looking at words (we do this for ISA servers by filtering on words like ISA and Array and so on). You can pass the resolution state to an alert channel or use it to split it into a specific channel. I think both methods will not cleanly split all alerts, because some are based on Computer or the agent and some might have words that are not cleanly distributed to groups or resolution states. It helps a lot, but is not 100% coverage I think.Bob Cornelissen - BICTT (My BICTT Blog)