SMLets Exchange Connector v3.2

SMLets Exchange Connector v3.2

General
The Management Pack (3.2.0.18) introduces a new checkbox on the Processing Logic pane to optionally leave messages in the mailbox after processing. This is done to continue to meet parity with the stock connector, while opening the door to new possibilities with Custom Events given the Invoke-AfterProcessing style events.

PLEASE NOTE TO ALL THOSE UPGRADING: The connector since its inception has marked the message as read and moved messages to Deleted Items/Trash after processing. If you wish to continue this behavior, after you import the Management Pack you must go into the Settings UI, then Processing Logic, and check off "Move to Deleted Items After Processing". If timing is of the utmost importance to you, import the MPB, change the value, then deploy the new PowerShell.

• Diff from v3.1

New Features

• Emails can now optionally be left in the inbox after processing. They will be still be marked as read to prevent subsequent processing

Enhancements

• More logging has been introduced to handle events generated by Multi-Mailbox functionality

Bugs

• When an email is attached to a Work Item and then opened in the Service Manager Console, it is possible the Console throws an error about a file extension and then closes
• Depending on how the connector's ps1 is opened, it could render with non-PowerShell characters due to differences in file encoding
• Issue with MultiMailbox datatype prevents successful run

Documentation

• Multi Mailbox configuration Wiki now shows how to configure mailbox redirection entirely through the Exchange Web UI
• Configuration document now cites that custom templates should be used on primary and secondary mailboxes
• In the Settings UI, the tooltip on hover for enabling use of Active Directory groups on Review Activities has a typo on the word "Activities"
• A contributor's name was misspelled

SMLets Exchange Connector v3.1

SMLets Exchange Connector v3.1

General
The Management Pack (3.1.0.9) introduces 2 new UI elements to ignore digitally signed emails with invalid certificates and define the new [pwsh] keyword.

• Diff from v3.0

New Features

• Emails with an invalid certificate can now be ignored for processing. You can also optionally trigger the Invoke-InvalidDigitalSignatureAction function through Custom Events.
• New [pwsh] keyword and Custom Action (Invoke-ValidDigitalSignatureAction) introduces the ability invoke PowerShell directly from email. This use of this feature requires the use of digital signatures in order to securely verify the Sender's authenticity. For a list of ideas and how to get started, head over to the wiki.

Enhancements

• More logging has been introduced to handle events generated by Mimekit
• Emails that are both digitally signed and encrypted can now be parsed correctly

Bugs

• When using the management pack outside of the United States, the Minimum File Size in KB decimal field can't pass validation due to use of different decimal delimiters used
• When using the management pack outside of the United States, decimal fields that don't have validation (Announcement Hour Expirations, Azure Cognitive Services, and Azure Machine Learning) compound their values on every save of the MP. This eventually leads to an inability to open the Settings UI due to conversion overflow errors as the decimal values become so large that .NET can no longer parse them
  • If you experience this error, you unfortunately must delete the MP, re-import the MP, and then reconfigure your settings
  • If you do not currently experience this error, you should upgrade to prevent the error from occurring in your environment

Miscellaneous

• MimeKit has been upgraded from v1.18.1 to v2.9.2
• MimeKit requires the use of BouncyCastle cryptography. This new dll should be placed in the same location/alongside where MimeKit.dll is stored
• If you're currently using Custom Events and wish to take advantage of the two new functions introduced in this release. Just copy the two new functions into your current Custom Events and save

SMLets Exchange Connector v3.0

SMLets Exchange Connector v3.0

General
The Management Pack (3.0.0.28) introduces the ability to run the connector via the SCSM workflow engine and provides detailed logging regardless of deployment strategy.

• Diff from v2.4

New Features

• Ability to use the SCSM Workflow Engine to run the connector. If chosen, you'll gain the ability to:

  • Impersonate your Service Manager mailbox with a chosen Run as Account on the "General" page
  • Select a Run as Account on the "General" and "Cireson" pages
  • Define the path on the "DLL" page to choose the location of the smletsexchangeconnector.ps1 file
  • New "Workflow" page to define whether or not the workflow is enabled as well as how often it runs in seconds

• Logging that works with Task Scheduler, SMA, Azure Automation, or SCSM Workflow based deployments:

  • The new "Logging" page enables you to define logging levels so you can modify how much data each run of the connector generates. SMA/Azure Automation will perform a mix of Write-Output and Write-Warning, while running through Task Scheduler/SCSM workflows will generate its own Windows Event Log. A full breakdown of what logging captures as well as how to introduce you own logging can be found here on the wiki.

Instruction on how move to SCSM workflows can be found on the wiki here

SMLets Exchange Connector v3.0 RC1

SMLets Exchange Connector v3.0-RC1

Summary
Release Candidate 1 for v3.0 of the connector that introduces the ability to run the connector via the SCSM Workflow engine. Upon enabling the workflow, your Service Manager Linking Framework Configuration MP (unsealed) will be altered with the introduction of a single new Rule by the ID of SMLets.Exchange.Connector.15d8b765a2f8b63ead14472f9b3c12f0. This Rule's status (enabled/disabled) and frequency (in seconds) is then controlled through the Settings UI. If you ever want to delete the Rule you'll have to export the SCSM LFX mp, delete the rule, then re-import the MP. This behavior is identical to the stock connector.

General
Barring significant issues as they pertain to workflows, run as accounts, or logging this version is the most representative in terms of functionality to the final v3 release. The MP/DLL also have moved up in versions to represent the number of commits to the branch/version. In this case, 21 commits to v3 comes out to v3.0.0.21. This versioning schema will continue forward into the v3 series of releases.

New Features

• The management pack introduces the following changes to the Administrative Settings UI:
  • Ability to impersonate your Service Manager mailbox with a chosen Run as Account on the "General" page
  • Run as Account drop down on the "General" and "Cireson" pages
  • New field on the "DLL" page to define the location of the smletsexchangeconnector.ps1 file
  • New "Workflow" page to define whether or not the workflow is enabled as well as how often it runs in seconds
  • Logging level so you can modify how much data each run of the connector generates. SMA/Azure Automation will perform a mix of Write-Output and Write-Warning, while running through SCSM workflows will generate its own Windows Event Log.
  • Diff from v2.4

Documentation on how move to SCSM workflows can be found on the wiki here

FIXED ISSUES FROM BETA1 & BETA2

• While the Cireson SCSM Portal Run as Account can be set, it isn't used by the PowerShell
• If using Logging with Workflows, you need to set the Logging Type to SMA or Azure Automation, save the form, re-open, and then choose Workflows
• Impersonation does not work when using Workflows. It is advised to use the Active Directory User associated with the Exchange Mailbox as the Run as Account

SMLets Exchange Connector v3.0-Beta2

SMLets Exchange Connector v3.0-Beta2

Summary
Second beta release for v3.0 of the connector that introduces the ability to run the connector via the SCSM Workflow engine. Upon enabling the workflow, your Service Manager Linking Framework Configuration MP (unsealed) will be altered with the introduction of a single new Rule by the ID of SMLets.Exchange.Connector.15d8b765a2f8b63ead14472f9b3c12f0. This Rule's status (enabled/disabled) and frequency (in seconds) is then controlled through the Settings UI. If you ever want to delete the Rule you'll have to export the SCSM LFX mp, delete the rule, then re-import the MP. This behavior is identical to the stock connector.

General

• Management Pack, DLL, and PowerShell now at v3.0.0.2
• More logging introduced for functions seen throughout the connector
• The wiki article on Logging explains logging levels, how to generate your own custom logging, and finally a detailed list of Events that can be generated out of the box
• The Management Pack's Logging section features a URL to take you to the above Wiki page on logging
• Diff from v2.4

New Features

• The management pack introduces the following changes to the Administrative Settings UI:
  • Run as Account drop down on the "General" and "Cireson" pages
  • New field on the "DLL" page to define the location of the smletsexchangeconnector.ps1 file
  • New "Workflow" page to define whether or not the workflow is enabled as well as how often it runs in seconds
  • Logging level so you can modify how much data each run of the connector generates. SMA/Azure Automation will perform a mix of Write-Output and Write-Warning, while running through SCSM workflows will generate its own Windows Event Log.

Documentation on how move to SCSM workflows can be found on the wiki here

FIXED ISSUES FROM BETA1

• While the Cireson SCSM Portal Run as Account can be set, it isn't used by the PowerShell
• If using Logging with Workflows, you need to set the Logging Type to SMA or Azure Automation, save the form, re-open, and then choose Workflows

KNOWN ISSUES

• Impersonation does not work when using Workflows. It is advised to use the Active Directory User associated with the Exchange Mailbox as the Run as Account

SMLets Exchange Connector v3.0-Beta1

SMLets Exchange Connector v3.0-Beta1

Summary
First beta release for v3.0 of the connector that introduces the ability to run the connector via the SCSM Workflow engine. Upon enabling the workflow, your Service Manager Linking Framework Configuration MP (unsealed) will be altered with the introduction of a single new Rule by the ID of SMLets.Exchange.Connector.15d8b765a2f8b63ead14472f9b3c12f0. This Rule's status (enabled/disabled) and frequency (in seconds) is then controlled through the Settings UI. If you ever want to delete the Rule you'll have to export the SCSM LFX mp, delete the rule, then re-import the MP.

General
You can now optionally bring the connector under the control of the SCSM workflow engine and leverage a Run as Account to connect to Exchange on premise or online! All while still maintaining the ability to fully customize the connector at your discretion via PowerShell.

• Diff from v2.4

New Features

• The management pack introduces the following changes to the Administrative Settings UI:
  • Run as Account drop down on the "General" and "Cireson" pages
  • New field on the "DLL" page to define the location of the smletsexchangeconnector.ps1 file
  • New "Workflow" page to define whether or not the workflow is enabled as well as how often it runs in seconds
  • Logging level so you can modify how much data each run of the connector generates. SMA/Azure Automation will perform a mix of Write-Output and Write-Warning, while running through SCSM workflows will generate its own Windows Event Log.

Documentation on how move to SCSM workflows can be found on the wiki here

KNOWN ISSUES

• While the Cireson SCSM Portal Run as Account can be set, it isn't used by the PowerShell
• Impersonation does not work when using Workflows. It is advised to use the Active Directory User associated with the Exchange Mailbox as the Run as Account
• If using Logging with Workflows, you need to set the Logging Type to SMA or Azure Automation, save the form, re-open, and then choose Workflows

SMLets Exchange Connector v2.4

SMLets Exchange Connector v2.4

General
The management pack (2.0.2016.11) introduces fields for Azure Tenant and Application/Client ID fields to work with Exchange Online.

• Diff from v2.3

New Features

• Connect to Exchange Online via OAuth 2.0 instead of through Basic Authentication. A full walkthrough is available on the wiki to help you deploy and configure your own Azure AD Application.

Miscellaneous

• Autodiscover URL text field now changes visibility based on whether or not the Use Autodiscover checkbox is toggled.

SMLets Exchange Connector v2.3

SMLets Exchange Connector v2.3

General
The management pack (2.0.2016.10) introduces new fields for Azure Vision and Speech integrations.

• Diff from v2.3

New Features

• More data points for File Attachments with optional integration to Azure Vision and Speech services. This gives you the ability to perform reverse Work Item searches by attached files and introduces opportunities for new automation scenarios
  • Vision: Images (*.png, *.jpg, *.jpeg, *.bmp, *.gif) processed by the connector can optionally be submitted to Azure Vision in order to describe the image. For example, a screenshot of an error message could return "Tags:screenshot,abstract,text,design,graphic". In the event "text" is one of the tags returned, OCR extraction will be attempted. In which case the returned data would be "Tags:screenshot,abstract,text,design,graphic;Desc:Microsoft Outlook Cannot start Microsoft Outlook. Cannot open the Outlook window. The set of folders cannot be opened." In either case, the returned data is written to the "Description" field of the File Attachment.
  • Speech: Audio files (*.wav and *.ogg) processed by the connector can optionally be submitted to Azure Speech services in order to transcribe speech to text. This text will then be written to the "Description" field of the File Attachment.

Bugs

• When using the Dynamic Analyst Assignment feature, the Set-AssignedToPerSupportGroup function was incorrectly choosing the Analyst with the highest volume of assigned work as opposed to the lowest
• When using the Dynamic Analyst Assignment feature for Out of Office + Volume, the pipeline based PowerShell was using a named variable as opposed to the assumed one (i.e. $variable instead of $_)

Miscellanous

• Realigned code regions to give proper source citation for Apply-SCSMTemplate function
• File Attachments write their respective file extension to the Extension property

SMLets Exchange Connector v1.9

SMLets Exchange Connector v1.9

General
Barring a hotfix style release - this marks the last of the v1.x series of releases. This also means it is the last release fully compatible with SCSM 2012+ as the management pack included with v2.x only works with SCSM 2016+ given the shift in .NET from 3.5 to 4.5.1. Going forward all development will be targeted at the v2.x branch. The v1.x series of branches will remain on the repo for reference.

• Diff from v1.8

New Features

• More data points for File Attachments with optional integration to Azure Vision and Speech services. This gives you the ability to perform reverse Work Item searches by attached files and introduces opportunities for new automation scenarios
  • Vision: Images (*.png, *.jpg, *.jpeg, *.bmp, *.gif) processed by the connector can optionally be submitted to Azure Vision in order to describe the image. For example, a screenshot of an error message could return "Tags:screenshot,abstract,text,design,graphic". In the event "text" is one of the tags returned, OCR extraction will be attempted. In which case the returned data would be "Tags:screenshot,abstract,text,design,graphic;Desc:Microsoft Outlook Cannot start Microsoft Outlook. Cannot open the Outlook window. The set of folders cannot be opened." In either case, the returned data is written to the "Description" field of the File Attachment.
  • Speech: Audio files (*.wav and *.ogg) processed by the connector can optionally be submitted to Azure Speech services in order to transcribe speech to text. This text will then be written to the "Description" field of the File Attachment.

Bugs

• When using the Dynamic Analyst Assignment feature, the Set-AssignedToPerSupportGroup function was incorrectly choosing the Analyst with the highest volume of assigned work as opposed to the lowest
• When using the Dynamic Analyst Assignment feature for Out of Office + Volume, the pipeline based PowerShell was using a named variable as opposed to the assumed one (i.e. $variable instead of $_)

Miscellanous

• Realigned code regions to give proper source citation for Apply-SCSMTemplate function
• File Attachments write their respective file extension to the Extension property

SMLets Exchange Connector v2.2

SMLets Exchange Connector v2.2

General
The management pack (2.0.2016.9) introduces one new field on the Artificial Intelligence, AML pane for defining the new minimum percent required to predict Impacted Configuration Items per the new feature described below.

Microsoft has moved the Basic Authentication deadline for connecting to Office 365. However it still doesn't change the need to address it in the connector! If you're running your SCSM Mailbox in 365 and open to testing, then we're looking for your help. Help shape the final state of this integration and try it out for yourself here.

Next - the bounty board is open for anyone able who is able (or unable) to repro either this or that.

Finally - we're looking for your thoughts on Submitting Requests on Behalf of others. A feature that that almost made it into this release. Comment over here.

• Diff from v2.1

New Features

• It's now possible to predict the Impacted Configuration Item (i.e. the Asset in your environment) the email is about using Azure Machine Learning. This works regardless if you're using the stock Service Manager classes, imported Operations Manager classes, any 3rd party management pack classes, or even your own custom in house developed classes. You can get started with AML deployment and the required SQL queries over here.

Bugs

• When using the Multi-Mailbox feature, the Get-TemplatesByMailbox function defaulted on an incorrect variable
• If Multi-Mailbox wasn't used and the connector was run manually, PowerShell would produce visual only bugs around "items in the array cannot be null"
• The Merge Replies feature as seen through the Verify-WorkItem function has now been updated to handle a scenario where Attachment results return null