SCSM - Exchange Connector 3.0 RTM Released & Supported

  • Comments 70
  • Likes

At long last!  We have released a version of the Exchange Connector which has been thoroughly tested, passed on strict security audit process, and most importantly is officially supported!  It’s been a long time coming, but finally the day is here!

This version of the Exchange Connector is just an evolution of the Exchange Connector 3.0 RC where we have fixed a few bugs and added some security-related features.

In order to use the Exchange Connector 3.0 RTM you need to:

  • Have System Center 2012 SP1 – Service Manager Cumulative Update 2.  It is a prerequisite due to a workflow change required to support the new ability in the Exchange Connector to specify a Run As Account similar to the other connectors.
  • Uninstall Exchange Connector 3.0 RC first.  Do this by deleting all of the Exchange Connectors you have in the Connectors view (you might want to take screenshots of the properties dialogs or something to remind you of how to set everything back up again).  Then delete the Exchange Connector management pack from the Management Packs view.  Then delete the .dll in the Service Manager Program Files directory.

Please see the documentation included in the download package for all the other information you need to know.

The Send Email solution is no longer included in the Exchange Connector package.  We have moved it to the TechNet Gallery.  It is still not a supported solution.  We will work on productizing this at some point in the future.  Also, keep in mind that Patrik Sundqvist (MVP) has created a version of SendEmail for service requests that is also on the TechNet Gallery.

The Exchange Connector 3.0 RC download has been taken down now.  Exchange Connector 2.0 RTM is still available for customers that are using SCSM 2010, but that is still not a technically supported solution.  The Exchange Connector 3.0 RTM will not work on SCSM 2010.

Thank you to everyone for your testing and patience as this critical solution has evolved.

Here is the download location:

SCSM - Exchange Connector 3.0 RTM Released & Supported

Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment
  • Woohoo! Great news! :)

  • Great.

  • Great!

  • Where can I see the changelog ?

  • Great news!!! Thanks :-)

  • Awesome!! Thanks for the hard work!

  • I just tested the new connector and it works fine. The old bug regarding Service Request status not properly updating is now fixed. Testet with a Service Request template with and without activities.

  • Hi,

    anyone successfully implemented the RTM connector on Windows Server 2012 with SCSM SP1 RU2? I'm stuck a the connector configuration where to set the run-as account. I'm using the workflow account which has a mailbox and is local administrator on the SCSM server. I'm stuck at a error message I get, that the security eventlog is not accessible:


    The connection to the server was unsuccessful. Please check the server name and/or credentials entered.

    Additional Information: The source was not found, but some or all event logs could not be searched.  Inaccessible logs: Security.



  • Tested and works great, thx!  I noticed that Analyst Comments that are processed by the Exchange Connector still have "IsPrivate" as Null.  This breaks our notification subscriptions for Trouble Ticket Analyst Comment, any plans to fix this? (Subscription has IsPrivate equals False as condition, GUI doesn't have option to add "Or if Null").

  • I am using an Office 365 account but am getting bad username or password in the event log but test successful while configuring the connector.

    My normal username is

    So I am using\servicedesk

    Is this the correct format?

  • I guess the server just needed a reboot.  I am now experiencing other issues:

    When replying to a Request with the ID# formatted like this [ID194] i am getting:

    Exchange Connector: Unable to process mail item. Subject="RE: An incident has been opened for you.  ID: [IR194]", Error Message=The key value of an object cannot be changed.

    Also, something with the Health service and the 365 email box credentials:

    The Health Service could not log on the RunAs account\servicedesk for management group MG_SCSMPD.  The error is Logon failure: unknown user name or bad password.(1326L).  This will prevent the health service from monitoring or performing actions using this RunAs account

    Google provides no help.

  • Great !!! thx !

  • Hi, I'm also facing some sort of permissions issue. I have tried impersonating by giving impersonation rights to the workflow account and setting the Workflow account as the run as account(and I can actually test the connection successfully) . Then I get a lot of errors in the Event log:

    Windows Workflow Foundation workflow failed during execution.

    Workflow Type: Microsoft.SystemCenter.ExchangeConnector.ProcessEmailsWorkflow

    Workflow Identifier: 04a1a194-ffd2-d841-0418-6cdb3f604a56

    Exception Type: Microsoft.EnterpriseManagement.Common.UnauthorizedAccessEnterpriseManagementException

    Exception Message: The user DOMAIN\SCSMWorkflow does not have sufficient permission to perform the operation.

    I reviewed the powershell commands, run them again just in case, no luck:

    New-ManagementScope -Name ’SCSM Impersonation Scope’ -RecipientRestrictionFilter {DisplayName -eq ‘SCSM Admin’}

    New-ManagementRoleAssignment –Name ’SCSMWorkflow impersonates Servicemanager’ -Role ApplicationImpersonation -User SCSMWorkflow -CustomRecipientWriteScope ’SCSM Impersonation Scope’

    I have also tried to impersonate by using the same account in the run as account (SCSM Admin), but then I can't even test the connection.

    Any ideas?

  • Is anyone else having trouble replying to the email notification from SCSM and having it update the request?  Everything appears to be going fine then this error is thrown (which is oddly recorded and Infomational in the event log):

    Exchange Connector: Unable to process mail item. Subject="RE: An incident has been opened for you.  ID: [IR194]", Error Message=The key value of an object cannot be changed.

  • @Jose Try rebooting, that seemed to clear up many of my workflow issues relating to that error.