Update: April 26, 2013 - Exchange Connector 3.0 RTM has been released now and is officially supported:
http://blogs.technet.com/b/servicemanager/archive/2013/04/26/scsm-exchange-connector-3-0-rtm-released-amp-supported.aspx
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:
http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=29423
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:
http://www.microsoft.com/en-us/download/details.aspx?id=28952
When using Send Email feature of EC 3.0 is there any way to send screen shots or attachments to end user, currently in our environment when every helpdesk has to send email to end user with screen shot or attachment they go to Outlook.
Had anyone found workaround or solution for this concern.
Thanks & Regards,
Vamshi Gupta
@Vamshi Gupta
Sorry, no, it is not possible to send outbound email file attachments since the underlying notification infrastructure in SCSM doesn't support it.
HI Travis, Thanks for answering my query.. I have one more doubt if We can use "Send Email" feature to send email to other user other than the "Affected User".. Scenario would be that helpdesk would have to send email to other user other than affected to ask for approval or requesting additional info or request troubleshooting steps from L2
@Vamshi Gupta -
Yes, you can send a notification to someone other than the affected user. You just need to add the recipient(s) you want in the notification subscription.
Hi Travis,
If the email notification channel is disabled, will SCSM keep the emails to be triggered in queue and once we enable the notification channel will it send out all the queued emails?
Please help in this as we are not getting this information from any where.
Thanks
@kulaks -
I haven't tested it myself but I doubt the mail notifications would be queued.
We did testing on this functionality. Like we have configured SMTP server to keep mails in the folder and then we enabled email notification channel. Then we had a look into that folder for mails and there is no emails. But, we are seeing the mails for any new workflows.
Also, before this testing we kill the MontoringHost.exe process on the workflow management server. Does this removes all the queued emails?
We have tested in our environment for email notification when the notification channel is disabled.
Yes, If notification channel is disabled
•All workflow will trigered
•But email will not sent
And if notification channel is re-enabled, only new notification will be sent.
Hi guys,
I know that the connector sadly did not support digitally signed emails :( :( .... a lot of you user are communicating with those signed email. Is it planned that the connector can handle this in the next version?
Cheers
R
We have had the connector working fine for some time now but it stopped working the other day. The only clue is "The specified forest does not exist or cannot be contacted" being reported in the event logs. I checked and its still pointing at the forest not a domain. I also deleted and re-created the connector from scratch. Still no dice.
I guess my question is:
How does the connector try to verify that emails exist in the forest? If I knew this I could probably track down what's not working.
Thanks for your time.
-S
Can we use this feature to create problem requests instead of incident requests? We have monitoring alerts on network equipment that currently transition to IR's, but we'd want them to be classified as problems instead.
@Adam
Yes, you can create any type of work item with EC 3.0 RC+.
We are a Domino shop. Is there anyway to make this Exchange Connector work with Domino or other email solutions?
@Corey - sorry, no integration with Domino. There is an out of box solution in SCSM that allows you to pick up mail items from a file share (SMTP server) and convert them into incidents though. Maybe that could work in your situation?
Are there any limitations in the subject line? How many chars a supported?