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:
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:
Hey Herb, just did. I have also used the command as in the guide just now:
New-ManagementRoleAssignment -Name:AdminImpersonateAll -Role:ApplicationImpersonation -User SCSMWorkflow
Same error. I'm currently running with the SCSMWorkflow account as the Run As Account and trying to impersonate SCSMAdmin (for testing).
Not sure what could be wrong. I'd assume it is on the exchange side, but now all permissions are assigned.
RE: this error message:
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.
It looks like maybe the template that you chose to apply to an incident on update has an ID coded in it. You could check that by exporting out the MP that contains the template and looking at the configuration in XML.
Devil is the details. I could swear I had the Workflow account in the Administrators role, but...was not there. Works now!
Thank you very much! That must have been it. I simply changed the template and viola!!
I am having the same problem as @Herb was having when trying to process reply updates. ( Error Message=The key value of an object cannot be changed.) I switched the templates around with no change. I even created a new (incident) template, and I stored it in a brand new MP as well. Rebooted the server, and still no luck. Any ideas?
Thanks for any help.
After Turning up logging to 7, I receive "Exchange Connector: Adding action log entry." when the connector try's parsing a Reply, however the Action Log of that IR is still empty, and the e-mail was never deleted from the inbox.
try exporting out the MP and look at the XML. You'll find an ObjectTemplate element that represents the template. Look and see what the ID property is set to inside of there.
I am seeing a strange issue with the connector.
When I try to create the connector it fails with my WorkFlow Account.
I have increased the logging to Level 7 and I see that it is failing to pass the full username of the WorkFlow account. For Example: My account is SVC_Workflow.Company.int. The event log shows that AutoDiscover failed for SVC_Workflow@Company.
I would expect that it would use SVC_Workflow@Company.int
Even the Autodiscover URL it is attempting to get to strips off the .int and I get:
Trying to get Autodiscover redirection URL from autodiscover.compnay/.../autodiscover.xml.
Is there a bug in the Connector that some how strips out any .int value?
Or is there something else I might be doing wrong with the setup of the mailbox?
(if I log on to a PC with the workflow account and open Outlook it autodiscovers without an issue)
Even if I manually enter the EWS URL I get a similar error.
Exchange Connector: Attempting to connect to Exchange with the settings: login email address="SVC_SCSM_Workflow@COMPANY", impersonation email address="none", server URL="cassrv01.company.int/.../Exchange.asmx"
Travis can you guide me to where the changelog is located (if it's there). I've looked in the DepGuide, but can't seem to find what bugs has been corrected.
@Travis, we too have experienced the errors with "key value of an object cannot be changed", and after extensive testing with exporting xml's, looking for ID fields, creating new templates and so on, we still could not get it to work. As we are working with different customers on this, and some did not have any problems, I noticed that there was a difference between where we had implemented the SendEmail solution and not. And when we removed the SendEmail 2.0 (SendEmail.mpb) Management Pack, updates to incidents with EC 3.0 RTM started working again. We also tried to re-import the SendEmail.mpb from the TechNet Gallery (which by the way is exactly the same version as earlier?), the problem was reintroduced. After removing again, updates are working.
Would be great to have any input on this from Microsoft. Thanks.
I concur with Jan. The instant that I removed the SendMail MP all email replies to requests began to work.
Is there another email solution other than SendMail or an update?
I also hit the same issue of "The key value of an object cannot be changed" which I have exported the template and check that no ID is there and I don't have sendmail solution installed as well. Please help.
@PedroMah - Do you have custom properties that you have extended the incident class with?
Same issue here with the connector failing to process email for incident updates. I have the SendEmail MP installed. I will try without it and report back.
Does the EC 3.0 need Exchange at any Service pack level? If so, whats the minimum?