Azure AD Connect v2.1.1.0 fixes a database corruption issue
Yesterday, Microsoft released an update to Azure AD Connect v2.x. that fixes two issues: v2.1.1.0.
Note:
None of the Azure AD Connect v2.x releases are released for automatic upgrade. Manual upgrades are required to gain the new functionality and security levels once you’re on the Azure AD Connect v2 path.
Note:
Azure AD Connect v1.x releases will no longer be supported after August 31st, 2022.
What’s New
Here’s what’s new in Azure AD Connect v2.1.1.0:
Parsing surrogate pairs
Microsoft addressed an issue where some sync rule functions were not parsing surrogate character pairs properly.
Model DB Corruption
Microsoft addressed an issue where, under certain circumstances, the Azure Active Directory Connect Sync service would not start after a reboot. At that time, event ID 528 is recorded in the Application event log with source SQLLocalDB 15.0.
The error is caused by database corruption to the model.mdf and model.ldf database files, as described in the Microsoft Azure AD Sync service fails to start – event id 528 article by fellow-Veeam Vanguard Didier van Hoye.
Version information
This is version 2.1.1.0 of Azure AD Connect.
This release in the 2.x branch for Azure AD Connect was made available for download as a 153 MB weighing AzureADConnect.msi on March 24th, 2022.
You can download the latest version of Azure AD Connect here.
The post Azure AD Connect v2.1.1.0 fixes a database corruption issue appeared first on The DirTeam.com / ActiveDir.org Weblogs.
windows,microsoft
via The DirTeam.com / ActiveDir.org Weblogs https://dirteam.com
March 26, 2022 at 02:00PM
Sander Berkouwer
Stack IT News 