#MIMOLIVE VERSION HISTORY HOW TO#
#MIMOLIVE VERSION HISTORY UPGRADE#
#MIMOLIVE VERSION HISTORY FULL#
#MIMOLIVE VERSION HISTORY PASSWORD#
#MIMOLIVE VERSION HISTORY WINDOWS#

#MIMOLIVE VERSION HISTORY HOW TO#

For details on how to refresh the connector configuration, refer to the article section Connector Version Release History - Troubleshooting. If you are using Azure AD Connect with non-standard connector (for example, Generic LDAP (Lightweight Directory Access Protocol) Connector and Generic SQL Connector), you must refresh the corresponding connector configuration in the Synchronization Service Manager after in-place upgrade.

#MIMOLIVE VERSION HISTORY FULL#

To defer such activities, refer to section How to defer full synchronization after upgrade.

#MIMOLIVE VERSION HISTORY UPGRADE#

If you already changed the default sync rules, please see how to Fix modified default rules in Azure AD Connect, before starting the upgrade process.ĭuring in-place upgrade, there may be changes introduced that require specific synchronization activities (including Full Import step and Full Synchronization step) to be executed after upgrade completes. To make sure that your configuration is kept between upgrades, make sure that you make changes as they're described in Best practices for changing the default configuration.

If you've made changes to the out-of-box synchronization rules, then these rules are set back to the default configuration on upgrade. If there are no changes to the out-of-box configuration with the new Azure AD Connect release, then a normal delta import/sync starts instead. You might consider doing the in-place upgrade during the weekend.

#MIMOLIVE VERSION HISTORY PASSWORD#

The normal delta synchronization scheduler (which synchronizes every 30 minutes by default) is suspended, but password synchronization continues. This run might take a few hours, depending on the number of objects that are in scope of the sync engine. This method ensures that the new configuration is applied to all existing objects in the system. If there are any changes to the out-of-box sync rules, a full import and full synchronization will occur after the upgrade. This method is preferred when you have a single server and less than about 100,000 objects. It does not work for moving from DirSync or for a solution with Forefront Identity Manager (FIM) + Azure AD Connector. In-place upgradeĪn in-place upgrade works for moving from Azure AD Sync or Azure AD Connect. Downgrading from Azure AD Connect to legacy clients, including DirSync and Azure AD Sync, is not supported and can lead to issues such as data loss in Azure AD. Sync is not interrupted and does not impose a risk to productionįor permissions information, see the permissions required for an upgrade.Īfter you've enabled your new Azure AD Connect server to start synchronizing changes to Azure AD, you must not roll back to using DirSync or Azure AD Sync.

#MIMOLIVE VERSION HISTORY WINDOWS#

Supports Windows OS (Operating Systems) upgrade. Safest approach and smoother transition to a newer version.

With two servers, you can prepare one of the servers with the new release or configuration and change the active server when you are ready If there is an issue while in-place upgrading, you cannot roll-back, and sync will be interrupted If you have a single server, you can upgrade the installation in-place on the same server This is the easiest method for customers with an express installationĪuto-upgrade version might not include the latest features There are a few different strategies that you can use to upgrade Azure AD Connect. Customers who have not upgraded in 12-18 months (about 1 and a half years) should consider a swing upgrade instead as this is the most conservative and least risky option. Servers that have been in production for several years typically have had several patches applied to them and not all of these can be accounted for. In practice, customers on old versions may encounter problems not directly related to Azure AD Connect. If you want to upgrade from DirSync, see Upgrade from Azure AD sync tool (DirSync) or the Swing migration section. In-place upgrades of DirSync or ADSync are not supported, and a swing migration is required. It is currently supported to upgrade from any version of Azure AD Connect to the current version. To see what the latest version is, and to learn what changes have been made between versions, please refer to the release version historyĪny versions older than Azure AD Connect 2.x are currently deprecated, see Introduction to Azure AD Connect V2.0 for more information.

We are constantly making upgrades to AADConnect, and these upgrades include fixes to security issues and bugs, as well as serviceability, performance, and scalability improvements. It's important that you keep your servers current with the latest releases of Azure AD Connect.

Mimolive version history