#Goodsync vs dirsync pro how to#
#Goodsync vs dirsync pro install#
#Goodsync vs dirsync pro upgrade#
#Goodsync vs dirsync pro full#

If you use a full SQL Server for DirSync, you see this page instead:.If you use SQL Server Express and have less than 50,000 objects, the following screen is shown:.

#Goodsync vs dirsync pro how to#

When the analysis completes, you see the recommendations on how to proceed.

Click next to begin analysis of your existing DirSync installation.

Review and agree to license terms and privacy notice.

Launch the Azure AD Connect installer (MSI).

You have more than 50,000 objects in scope for synchronization.

You're currently using Full SQL Server - local or remote.

Uninstall DirSync (or temporarily disable it).

Collect credentials for an enterprise admin account (only used during the installation of Azure AD Connect).

Analysis of current DirSync configuration.

High-level steps for upgrading from DirSync to Azure AD Connect These passwords are reset during the upgrade. The passwords used by DirSync for the service accounts cannot be retrieved and are not migrated. Reapply any changes using custom configuration, as described in Azure AD Connect Sync custom configuration.

#Goodsync vs dirsync pro install#

In those cases, the recommendation is to install a new Azure AD Connect server in staging mode and verify the old DirSync and new Azure AD Connect configuration.

Unsupported DirSync changes, for example removed attributes and using a custom extension DLL.

#Goodsync vs dirsync pro upgrade#

If you have this configuration, the upgrade is blocked: Your forest/domain and Azure AD settings.Password sync and Exchange hybrid settings.

The following configuration changes are supported with upgraded DirSync: Supported DirSync configurations to be upgraded The Azure AD Connect installation attempts to estimate the downtime for the upgrade, but if you've upgraded DirSync in the past, your own experience is likely to be the best guide.

This deployment avoids any operational delays experienced by your users. If you have more than 50,000 objects, then a parallel deployment is recommended. For more information, see the parallel deployment section. You might for example take the opportunity to refresh the hardware and operating system.

If you want to do a configuration migration and do a parallel deployment, then 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 synchronization. If the number of objects in your database is less 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 expected time to complete the upgrade is displayed by the wizard. Azure AD Connect will read and migrate the configuration from DirSync and uninstall after inspecting the server. When you plan to upgrade from DirSync to Azure AD Connect, do not uninstall DirSync yourself before the upgrade. If you want to use any of the new features included with Azure AD Connect, some new URLs must be opened. For basic scenarios, those scenarios also supported by DirSync, the requirements are the same. The URLs required to be open in the proxy server.DirSync always used the proxy server configured for the user installing it, but Azure AD Connect uses machine settings instead. If you use a proxy server to reach the internet, this setting must be configured before you upgrade. Newer versions are required to be on the server than what DirSync needed. In particular, you want to read about the following, since these areas are different from DirSync: If you are still using these you MUST upgrade to AADConnect to resume your sync process.īefore you start installing Azure AD Connect, make sure to download Azure AD Connect and complete the pre-requisite steps in Azure AD Connect: Hardware and prerequisites. These steps do not work for upgrading from another release of Azure AD Connect or from Azure AD Sync.ĭirSync and Azure AD Sync are not supported and will no longer work. You find the ways you can upgrade from DirSync in this topic. Azure AD Connect is the successor to DirSync.