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:
Not sure if this is a bug or not. However, when for instance an analyst has commented on an incident using the send mail field, and he then assign the incident to another user or then resolves the issue, due to the property still filled in on the extensions form, 2 workflows are triggered? One for the incident being assigned\resolved (In this scenario) and one because the message type\message are still populated from the comment the analyst made previously? Have i set the workflow incorrectly or is this a bug?
Will the Exchange Connector stay as a RC release only or will it be come an official/RTM release at some point in the future?
It would appear that Version 1.0 installation documentation was included with the SendEmail 2.0 feature... Is this still accurate or am I missing something? Editing the .xml at the end does not seem to match up with the file I have...
@John Smith -
The RC will be the RTM. We are just going to rename it. There haven't been any significant bugs reported with it yet.
@G. Koon -
I believe that is just a typo. The XML editing part of the SendEmail solution hasn't changed from 1.0 to 2.0.
@Travis Wright MSFT
Thank you for your quick response, I have been trying to get an answer to that question for some time. However, I am still having trouble with editing the .xml area of deployment, it does not seem to match-up with the sendemail.xml file I exported... I am new to working with .xml so perhaps I am missing something. Step 4.d of the Configuration section of the deployment guide is specifically when things do not seem to align... I appreciate any clarification or assistance you can provide.
Exchange Connector does not seem to grab signed emails in an inpersonation mail box. It will get non-signed emails and create incident with no problem. Is this a design limitation of the connector itself? Or perhaps the fact that we are using EWS with impersonation causes signed emails to be inaccessible to the EC? Thoughts??
EC 3.0 doesnt' support processing digitally signed emails yet.
That splains it! Thank Travis.
Thanks for the speedy response. Will the RTM version be released as part of SP1 for System Center? or will it be released before then? As I am not permitted to install the RC version so I am waiting for the RTM version.
Since there have been no significant bugs reporting regarinding the RC, the RC *is* the RTM release. We are just going to rename it on the download site.
Thanks again for the quick response, do you know when it will be renamed? as until is renamed I am not allowed to use it.
I've started the process today. The release process can sometimes take a while though depending on the backlog of releases. I'll try to get it changed to RTM ASAP.
Thanks very much for this, it is greatly appreciated
Following up on Dries post and your subsequent reply, I too am having issues with follow up emails using the Send Email function.
As a test I sent 3 emails from one Incident ticket using "Request Additional Info From Affected User" as Message Type with the following Message Bodies "a test message", "this is a second test" and "Tuesday morning" so they are definitely not the same, but only the first one works. If I manually clear Message Type and Message from the ticket it works.
Sorry for such a long post here but there have been no answer from the forums and the ability to have email conversation with a user is essential.