![]() For more information, see Parallel deployment. For example, you might use the upgrade as an opportunity to refresh the hardware and operating system. If you want to do a configuration migration and do a parallel deployment, you can override the in-place upgrade recommendation. If you decide to continue, your current settings are automatically applied during upgrade and your server automatically resumes active sync. If the number of objects in your database is fewer than 50,000, then Azure AD Connect recommends an in-place upgrade. This estimate is based on the assumption that it takes three hours to complete an upgrade for a database with 50,000 objects (users, contacts, and groups). The wizard displays the expected time to complete the upgrade. Azure AD Connect will read and migrate the configuration from DirSync and uninstall it after it inspects the server. When you plan to upgrade from DirSync to Azure AD Connect, do not uninstall DirSync yourself before the upgrade. The upgrade scenarios are summarized in the following table: Expected upgrade time We estimate that if you have 50,000 or more objects, it takes more than three hours to do the upgrade. If the expected upgrade time is more than three hours, then we recommend that you do a parallel deployment on a separate server. If the expected upgrade time is less than three hours, then we recommend that you do an in-place upgrade. Upgrade from DirSyncĭepending on your current DirSync deployment, you have different options for the upgrade. If you aren't upgrading from DirSync, see related documentation for other scenarios. Downgrading from Azure AD Connect to legacy clients, including DirSync and Azure AD Sync, is not supported and can lead to issues like data loss in Azure AD. If you want to use any of the new features in Azure AD Connect, some new URLs must be opened.Īfter you have enabled your new Azure AD Connect server to start syncing changes to Azure AD, you must not roll back to using DirSync or Azure AD Sync. ![]()
0 Comments
Leave a Reply. |