Update: April 26, 2013 - Exchange Connector 3.0 RTM has been released now and is officially supported:
At long last the Exchange Connector 3.0 RC is released! I've made quite a few improvements in this release.
The Exchange Connector 3.0 release is compatible only with System Center 2012 - Service Manager
Feature Summary: . It contains bug fixes and still has the original set of features including:
New features include:
Please keep in mind that the Exchange connector is still not officially supported by Microsoft.
This RC release has been tested by TAP customers and is currently used in production by our internal operations team MPSD. You may still encounter some bugs. If you have any questions or issues with it please post them on the forums. I'll monitor the threads and see what I can do to help.
We do plan to include the Exchange connector out of the box in the next version of System Center so that it will be fully supported by Microsoft.
You can get the new Exchange Connector 3.0 RC version here:
Update May 9th 2012: Looks like the location to download the Exchange web service client library assembly from might have moved. You can get it from here:
Great job. Thanks a lot.
thats excellent, thanks
out of curiosity when you say "next version of Systems Center", do you mean next major release (so SC 2014 or 15?), or next SP release for 2012? or is that unknown at this stage?
@Simon - It will be a shorter timeframe release. We havent announced the name of it yet.
The previous connector for 2010 had the "Send Mail" feature. I don't think it is in this one. Are we likely to see that feature again?
A new version of SendEmail 2.0 is included with Exchange Connector 3.0. SendEmail 2.0 will only work with SCSM 2012.
The documentation shows two powershell commands to run for Exchange 2007 to incorporate the impersonation feature. Both commands are identical. Is this an error in the documentation? We ran the command and are receiving insufficient permissions errors.
One of the new features is that users are added to the related items, but we need the header of the e-mail sent to/copy to also be added to the action log.
We have customized this, so that we do not use the send e-mail, but Outlook to send e-mails. See here ke.karlsen.nu/.../using-outlook-for-e-mail-communication-with-service-manager .
Since we use the Exchange Connector to communicate with the end user and external contacts, we also need to have more than one recipient and it would have been nice to who the e-mail is sent to and where it comes from header.
Our internal customer - MPSD - has a similar solution. I worked together with them on this design and they have modified their console task to get the related users and their email addresses from the CMDB. Maybe you can do the same?
Hi Travis, maybe it's a solution, can you give me any more details on how it is working?
I have just found a critical problem for us regarding the new Exchange connector 3, it seems that there's an issue when a user is not in the Service Manager database. For example our external contacts.
If there's an e-mail in the inbox to or from a contact that's not in the database, the Exchange Connector never finish the syncronization and we get lot's of these errors in the Operation Manager event log:
A Windows Workflow Foundation workflow failed during execution.
Workflow Type: Microsoft.SystemCenter.ExchangeConnector.ProcessEmailsWorkflow
Workflow Identifier: b2c8cd80-5959-bcec-6026-9d7d1eb9ddc4
Exception Type: System.Security.SecurityException
Exception Message: The source was not found, but some or all event logs could not be searched. Inaccessible logs: Security.
Exception Stack: at System.Diagnostics.EventLog.FindSourceRegistration(String source, String machineName, Boolean readOnly)
at System.Diagnostics.EventLog.SourceExists(String source, String machineName)
at System.Diagnostics.EventLog.VerifyAndCreateSource(String sourceName, String currentMachineName)
at System.Diagnostics.EventLog.WriteEntry(String message, EventLogEntryType type, Int32 eventID, Int16 category, Byte rawData)
at System.Diagnostics.EventLog.WriteEntry(String message)
at Microsoft.SystemCenter.ExchangeConnector.TraceListener.Trace(String traceType, String traceMessage)
at Microsoft.SystemCenter.ExchangeConnector.ExchangeInbox.logMessage(String message, Int32 level)
at Microsoft.SystemCenter.ExchangeConnector.ProcessEmailsWorkflow.Execute(ActivityExecutionContext executionContext)
at System.Workflow.ComponentModel.ActivityExecutor`1.Execute(T activity, ActivityExecutionContext executionContext)
at System.Workflow.ComponentModel.CompositeActivityExecutor`1.Execute(T activity, ActivityExecutionContext executionContext)
at System.Workflow.ComponentModel.ActivityExecutor`1.Execute(Activity activity, ActivityExecutionContext executionContext)
at System.Workflow.ComponentModel.ActivityExecutorOperation.Run(IWorkflowCoreRuntime workflowCoreRuntime)
Maybe it's becuause it's trying to add all contacts under related items, do anyone know how to turn this off? Btw. this worked fine with the Exchange Connector 2.0.
The download link for the Exchange Web Services Managed API client dll link in the documentation doesn't seem to work anymore.
There is an updated dll available here - www.microsoft.com/.../details.aspx (EwsManagedApi.msi) which seems to work fine.
Sorry, but I should have posted the last question in the forums and not here.
You may fibnd my post on the forums here:
Great, glad to see that 3.0 is released.
Unfortunately, until Microsoft officially supports the Exchange connector, I'm not allowed to install it or use any of it's features.
Come on, whoever at MS decides whether it is a supported product, please approve it for support.
Looks like the Exchange web service assembly download location might have moved. You can get it from here now:
Send mail is a great customisation, thanks for that.
Is it possible to clear the fields "message" and "message type" at a given moment after the workflow ran?
At the moment is isn't possible to use the send mail options two times for one incident, except if we manually clear those fields.
If you follow the instructions exactly you should be able to use Send Email more than once for the same incident except for the case where the message is *Exactly* the same before the update and after the update.