Answered SCSM 2012 - Exchange connector

  • יום רביעי 09 נובמבר 2011 12:31
     
     

    Hi

    I was wondering if the is any documentation on how to create a Exchange connector, or if anyone know when the Exchange 3.0 connector will be released.

כל התגובות

  • יום רביעי 09 נובמבר 2011 12:55
     
     

    Hi

    Do you mean documentation how to create your own Connector while you are waiting for 3.0 to be released or do you mean documentation how to install Exchange Connector 2.0?

    Here is the download for Exchange Connector 2.0 and it comes with documentation how to install it:
    http://www.microsoft.com/download/en/details.aspx?id=26927

    I saw a comment from Travis that Exchange Connector 3.0 will be released in early November on the MS downloads site.
    Check out this site so you don´t miss it:
    http://blogs.technet.com/b/servicemanager/

     


    Stefan Allansson, Lumagate, Sweden, www.lumagate.com Blog: www.scsm.se
  • יום רביעי 09 נובמבר 2011 13:04
     
     

    Hi Stefan

    Yes i was looking for documentation on how to create my own while i wait for the 3.0 to be released, i am keeping an eye on Travis. My main concern is that we are going in production on SCSM 2012 Beta the 1. December so i need to have a working mail mangement in SCSM.

    The upside to making my own would also be that incase we wants some changes they would be easy to implement.

  • יום שני 28 נובמבר 2011 15:49
     
     

    Hi Guys,

    Did you manage to create a custom exchange connector? We are also waiting to go live with SCSM 2012 Beta but until we get the exchange connector 3.0 it will be impossible.

    I have also been shadowing Travis' blog and have posted asking if there was any update seeings that we are now almost through November, but have not received any update.

    Thanks

     

  • יום שלישי 29 נובמבר 2011 06:53
     
     

    Hi tpanicos

    No i havent managed to make a exchange connector for scsm 2012 since i could not find any information about how to do that. But i have managed to make a custom version of a exchange integration pack originally made by Ryan Andorfer so i can handle the mails with system center orchestrator 2012 beta.

    I decided on discarding the exchange connector all togeather because it wont be supported by Microsoft and when using SCO we get the posibility to create all sorts of logic and error handling.

    You can have the Integration Pack and i help you make the runbooks needed if you want. But its still very much a alpha version since i have been given 2 more days by management to be ready for SCSM 2012 production :-) So my main focus is functionality rather than neat looking  C# :-) But i will ofcource clean up the code after we have gone to production.   

  • יום שלישי 29 נובמבר 2011 13:38
     
     תשובה

    This is a picture of our update incident from email Runbook

  • יום שלישי 29 נובמבר 2011 13:53
     
     

    What is does is:

    1. Read mails from a Exchange mailbox and look for mails containing a [ in the subject.

    2. Split the subject into a string so i only get the data inside the [ xxxxx ].

    3. I then get the incident from SCSM, and there i evaluate.

         3. 1 if the incident has status closed, i send a email to the user explaining that he/she is trying to update information on a closed case that cant be reopened and the information is discarded.

        3.2 if i cant find a matching incident in SCSM i create a new incident in SCSM with information about the subject etc. and move the mail to a error folder inside the exchange mailbox. then a analyst can look at the mail at see if a user typed a subject with [ ] example.. [Please call me]

        3.3 if none of the above is true i continue.

    4. I export the email from the mailbox as a .eml to keep the formatting and attachements in its original format (including embedded images)

    5. I then read information about the exported mail needed for importing the file as a attachment on the incident

    6. I do some dataformatting (due to regional settings)

    7. I create the file attachment object.

    8. I upload the file to the attachment object.

    9. I delete the file

    10. I add the body of the mail as a user comment on the incident

    11. I update the status to Active and the last modified source to E-mail

    12. I move the processed email to deleted items in the Exchange Mailbox

     

    Thats it, this is the first revision. I will be adding more functionality and error handling eventually and the posibillity to handle Service Requests and other sorts of mails going into SCSM or Orchestrator in general. But for now this works perfectly.

  • יום שלישי 29 נובמבר 2011 14:00
     
     

    I might aswell show the "new" incident from email Runbook

    1. Read mails from Exchange and look for mails with a subject not containing a [

    2. Create a incident in SCSM with subject as title, body as description and from as alternate contact method.

    3. Run a Powershell script seaching the Active Directory for a user with the email address matching the from address.

       3.1 If a matching user is found, get the same user from the CMDB  and update the Affected user on the incident with the known user.

       3.2 If no matching user is found proceed

    4. Move the processed email to deleted items in the exchange mailbox.

     

    I hope this can work for you. I know you need to install a Orchestrator server aswell, but if you plan on using SCSM that is a GOOOOOOOOD idea anyway.

  • יום שני 19 דצמבר 2011 11:08
     
     

    Hi Kristensen - Jaesper

     

    I was just wondering if there would be any possibilty of either sending me a link or posting a download of the to runbooks and exchange IP pack you created as I am sure i'm not the only one gettting frustrated that the exchange connector hasn't been released for SCSM 2012 yet. I have looked at your solution and I have to say it looks very good and exactly what I am looking for.

    Thanks

    David

  • יום שלישי 20 דצמבר 2011 06:52
     
     

    Hi David.

    Sure i can send you the MP and the runbooks but i must also urge to tell you that i keep perfecting them :-) So its not a finished product that you get of the shelf.

    Strangely i dont have a blog but i might make one, since i have gathered quite an extensive knowledge on how to get the best from Service Manager and Orchestrator.

    This is how my runbooks have evolved so far, including additional features and more error handling.

    The New mail runbook

     

    Just send me a email at jesper.kristensen (at) eg (dot) dk and ill mail you the Management pack and the runbooks. Between christmas and new year ill be adding a runbook to do  mail handling for Service Requests.

     

    The update email runbook

  • יום שלישי 20 דצמבר 2011 07:12
     
     

    I also have runbooks for notifying users should an analyst update/request additional information on a incident or service request. (Very useful)

     

     

  • יום שלישי 20 דצמבר 2011 08:11
     
     

    Hi Jesper


    I have sent you an email, hopefully you will have recieved it, thank you for your quick reply it is much appreciated.

    I can now get our SCSM guy to look at these and try and make them work for us.


    David

  • יום רביעי 25 אפריל 2012 18:47
    בעלים
     
     תשובה

    Exchange Connector 3.0 RC has been released now:

    http://blogs.technet.com/b/servicemanager/archive/2012/04/15/exchange-connector-3-0-rc-released.aspx


    Travis Wright Senior Program Manager Microsoft

  • יום שלישי 22 מאי 2012 09:11
     
     
    I discovered a very critical bug on Exchange Connector 3.0 RC. Any place that I can submit it?

    • נערך על-ידי pantonis יום שלישי 22 מאי 2012 09:11
    •  
  • יום שלישי 22 מאי 2012 09:16
     
     

    Hi Pantonis

    I think Travis is following this thread still if not i will help you report it to him. You can email me at j e s p e r . k r i s t e n s e n @ e g (dot) d k and i can forward that message to Travis if he dont reply to you here.

  • יום רביעי 23 מאי 2012 10:52
     
     

    Hi,

    When a user that is not in the CMDB sends an email to the Exchange connector mailbox, an Incident is created. The affected user is set to Unknown (Unknown).

    Meanwhile, in the eventlogs I see that a user IS created in the CMDB for this external user.