Skip to content

SMLets Exchange Connector v1.8
Compare
Choose a tag to compare
@AdhocAdam AdhocAdam released this 23 May 20:29
v1.8
2d0457c
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.

SMLets Exchange Connector v1.8

General
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.

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
Assets 3