Using Send Mail in Work Items

Sandy_Wood

I want to expand our staff usage of Send Email in their Work Items to allow more communication with affected users. Right now our Email setting is basic; mail gets sent but users cannot respond back to the default send address we have, ciresonportal@ourdomain.com.

What is the best practice for tweaking this to utilize it the most? I ran across this KB ( https://support.cireson.com/KnowledgeBase/View/4#/ ) that looks pretty interesting to extend email functionality.

Nicholas_Velich

Hi Sandy,

That error can occur in the Exchange Connector from time-to-time, particularly in SCSM 2016. You can try replacing your DLLs, and double check that they are "unblocked." Also, verify you are on the latest version of the Exchange Connector (3.1 I believe).

Removing/modifying the Exchange Connector will not impact the Cireson Service Manager Portal in any way, inbound emails just will not process while uninstalled/non-configured.

Thanks,
Nick

Nicholas_Velich

The Advanced Send Email app allows you to send emails to End Users, and the Portal has a task per Work Item that has similar functionality. These both handle outbound email only (Analyst to End User).

In order for users to respond to the those outbound emails, an Exchange Connector should be setup for the "ciresonportal@ourdomain.com" inbox. The Exchange Connector monitors an inbox for inbound email, and updates the corresponding Work Item in Service Manager with details of the reply.

Justin_Workman

I agree with everything @Nicholas_Velich is saying, but I wanted to add a plug for @Adam_Dzyacky's Exchange Connector.

Sandy_Wood

Thanks for the answer back on my question. I found that we had been using another send address in SCSM that was working for email. In addition, I installed the Notify Analyst app that we needed for alerts that a user has responded to our mail and content is in the Action Log.

Nicholas_Velich

Great to hear! The Notify Analyst app is another great way to send outbound email for those work item assignment use cases.

Sandy_Wood

On a side note, I was mucking around in SCSM and decided to check my Exchange Connector to look at its properties. I'm getting the error below. Checking the web, it seems some have just reinstalled the Exchange EWS service and rebooted. Another person had this error with Cireson installed like myself. Could I do any harm to my Analyst Portal installation if I reinstall the Exchange bits?

Date: 4/16/2018 7:55:48 AM
Application: System Center Service Manager
Application Version: 7.5.3079.607
Severity: Error
Message: A required resource could not be found.

System.IO.FileNotFoundException: Could not load file or assembly 'Microsoft.Exchange.WebServices, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system cannot find the file specified.
File name: 'Microsoft.Exchange.WebServices, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'
   at Microsoft.EnterpriseManagement.UI.SdkDataAccess.ConsoleTaskHandler.DoTask(IList`1 navigationNodes, NavigationModelNodeTask task, List`1 parameterList)
   at Microsoft.EnterpriseManagement.UI.SdkDataAccess.ConsoleTaskHandler.DoTask(IList`1 navigationNodes, NavigationModelNodeTask task)
   at Microsoft.EnterpriseManagement.ConsoleFramework.WindowJobRecord.ExecuteBackgroundJob(Object sender, ConsoleJobEventArgs eventargs)
   at Microsoft.EnterpriseManagement.ServiceManager.UI.Console.ConsoleJobExceptionHandler.ExecuteJob(IComponent component, EventHandler`1 job, Object sender, ConsoleJobEventArgs args)

WRN: Assembly binding logging is turned OFF.
To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
Note: There is some performance penalty associated with assembly bind failure logging.
To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].

Nicholas_Velich

Hi Sandy,

That error can occur in the Exchange Connector from time-to-time, particularly in SCSM 2016. You can try replacing your DLLs, and double check that they are "unblocked." Also, verify you are on the latest version of the Exchange Connector (3.1 I believe).

Removing/modifying the Exchange Connector will not impact the Cireson Service Manager Portal in any way, inbound emails just will not process while uninstalled/non-configured.

Thanks,
Nick

Sandy_Wood

Forget my last post - found that you can't view the connector properties from your desktop SCSM console. Gotta be on the server itself.

Nicholas_Velich

Good point!