Can someone provide me an understanding of what specific data SCOM provides to Remedy through the connector and what the corresponding data fields are within SCOM and Remedy that allow this to work? We're thinking of implementing this solution but I haven't found much detail on what is actually communicated and what data fields in SCOM map to data fields in Remedy. Appreciate any help or insights you can provide.

Hi, as far as I understand, you can configure the mapping when you setup the connector: http://technet.microsoft.com/en-us/library/ee210404.aspx Also, if I'm not mistaken, MS pretty much dropped the connector stuff for SCOM 2012. I think the new strategy is to use Orchestrator runbooks to create incidents/tickets in other systems... cheers, StefanStefan Koell | http://www.code4ward.net

Exactly, the new "official" connector is Orchestrator. Basically, you are able to do the following actions in Remedy Create RequestUpdate RequestGet RequestMonitor Request Of course, you have access to all your forms and fields. http://www.vnext.be/2012/03/27/bmc-products-integration-packs-for-orchestrator-2012/ He did an implementation for a customer, and I matched the followings fields between the bot application. From SCOM to Remedy ServerName -> Customer Alert Description -> Incident Description From Remedy to SCOM Owner <- Assigned Group Alert ID <- Incident Number ChristopherChristopher Keyaert - MVP - My SCUG.be blog : http://scug.be/blogs/christopher

that's not true. connectors can still be used, only ms will not create connectors anymore. They will use orchestrator, but nothing prevents you to create your own connector or use a vendor made connector...Rob Korving http://jama00.wordpress.com/