Skip to content

SMLets Exchange Connector v3.0 RC1

Pre-release
Pre-release
Compare
Choose a tag to compare
@AdhocAdam AdhocAdam released this 30 Oct 23:29
· 40 commits to dev since this release
v3.0-rc.1
8345964
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 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
Assets 3