Schemus Synchronization Tool – Mandatory Upgrade
Article ID: 171384
Updated On:
Products
Issue/Introduction
Urgent: Upgrading Schemus from version 1.50 to 1.52.4
This affects only existing clients syncing from an O365 source type: Azure AD, Office 365, Exchange Online v1.
Due to Microsoft's retirement and replacement of Azure AD Graph by June 20th 2022 the end of year, 2022 (retirement delayed by Microsoft, more info here).
We have updated our synchronization application to work the new Microsoft Graph. As such, Schemus, which extracts user information (email addresses, users, and groups) from your O365/Azure LDAP directory service and provides user identity data to your Email Security.cloud services must be upgraded to v1.52.04 or later.
For existing Azure AD, Office 365, Exchange Online Powershell synchronizations, the Schemus update will be mandatory. After the update the old configurations will still show up in the application, but these will stop working when Azure AD graph is retired by Microsoft. The update can be delayed, although note that as of this moment new Azure AD graph configurations are no longer permitted as the option within Azure itself has been removed already by Microsoft, and you'll will be required to update the application in order to use synchronize with O365.
For the foreseeable future the update can be delayed if you're not using O365. With your synchronization using any of the following sources: a local Active Directory, a local text file, Lotus Domino, a generic LDAP source, or Google Apps.
Notable changes in 1.52.3:
- Added Microsoft Graph new unified source for MS products – called “Microsoft 365” in app.
- Added Exchange Online EXO v2 support
- Retired Azure AD Graph as a source, became Microsoft 365
- Retired Office 365 as a source, became Microsoft 365
- Retired Exchange Online Powershell v1 as a source, became Microsoft 365
- Updated embedded JRE to OpenJDK 1.8.0_302
- New sync option under “Data repository” > “Domain” called “Ignore unconfigured” this option ensures non configured domains are ignored by default without the need for complex regexes in the “Filters” menu.
- New Button padding configuration in startup.properties file, this to help adapt the UI to avoid wrongful clicks in the wrong button.
Location: C:\ProgramData\Schemus\application\settings\startup.properties
With the buttons numbered from top to bottom as 1-5, the bottom padding is configured as follows:- com.metanate.schemus.java.laf.configbuttonspacing.1=25
- com.metanate.schemus.java.laf.configbuttonspacing.2=10
- com.metanate.schemus.java.laf.configbuttonspacing.3=10
- com.metanate.schemus.java.laf.configbuttonspacing.4=10
- com.metanate.schemus.java.laf.configbuttonspacing.5=25
Notable changes in 1.52.4:
- Added ClientNet API update – called “Microsoft 365” in app.
Recommended for new O365 configurations and synchronizations Microsoft O365 (using MS Graph), only use case where this recommendation changes is if Dynamic DLs need to be synchronized, in that case instead use Exchange Online v2.
Environment
- Email Security.cloud
Resolution
Required Action
We urge customers to upgrade to the latest Schemus 1.52.04 version
Checking current version: Open Schemus>Help>About Schemus>Schemus Synchronizer Version
Important notes before upgrading
- If upgrading a 64-bit Windows application to a 32-bit application, the 64-bit version will not be uninstalled. We recommend uninstalling the 64-bit version first if re-installing or upgrading to a 32-bit version.
- Windows scheduled tasks will need to be recreated if installing for a different architecture (64/32 bit).
- The bundled java certificate store will be replaced. Any custom certificates (e.g. for SSL communication to the directory) will be lost.
- Download version with JRE. If you download a version without JRE you may need to enable Java versions above 1.0 in the Java applet.
Upgrading Schemus
- Make a backup of the existing Schemus folder which can be found here:
Windows XP & Server 2003:
C:\Documents and Settings\ AllUsers\ApplicationData\Schemus
Windows 7, 8, Vista & Server 2008, 2012:
C:\programdata\Schemus
Linux:
$HOME/.schemus/configurations/
or
~/.schemus/configurations/
*You may need to enable the view of hidden files and folders in Windows
- Ensure that all other applications running on the computer are closed before you start the installation process.
- Download the latest version of Schemus from https://clients.messagelabs.com > Tools > Downloads
- Start the installer
- For Windows systems, click the executable file that you downloaded from the portal
Synchronization Scheduler
If you have scheduled synchronization task, verify the settings are still correct or follow the steps below to create a new synchronization schedule. Windows scheduled tasks will need to be re-created if installing for a different architecture (64/32 bit).
To remove a synchronization schedule
- Open Schemus
- Click on Configuration > Schedule
- Click Clear
The calendar icon is grayed to show that the synchronization is no longer scheduled.
To schedule a synchronization:
- Click Schedule to set a time for the synchronization profile to run
- Specify a time in Run at
- Specify a recurring time in then run every
- Choose the days to run from on the drop-down list
- Click Day of Month or Day of Week and make your selections. If you select both Days of Month and Day of Week, the Synchronization Tool runs as follows:
Every month on the chosen date, and Every week on the chosen day.
Click Schedule to save the changes.
Using the PowerShell script:
- Download the attached file and rename the extension to .ps1
- Run the script provided, and insert credentials when prompted for O365 login details
- Wait for script to finish creating and setting up the app in Azure
- Copy the respective Tenant ID, Client ID and Secret for use in Schemus
- In Schemus go to Edit > Settings > Microsoft O365
- Insert the values copied previously and hit "Apply", followed by OK.
Attached files:
- Schemus 1.52.3 Release notes
- Schemus Powershell O365 Setup script
Attachments
Feedback
