If you are unable to run the automatic updater for AD Connect, download and run the install wizard to manually upgrade to the latest version.
When upgrading AD Connect with IIS:
- Updating from 1.x
- The update converts all group names to the full distinguished names (DNs). The
conversion completes after the new version of AD Connect registers with PingOne.
Thereafter, group names sent during single sign-on (SSO) use the full DN instead
of the short name. Note:
If any connections require short group names to be passed during SSO, you will need to update the attribute mapping for these connections to convert from full DNs to short names.
- Updating from 2.x
- If AD Connect is configured for high availability, schedule a maintenance window for this upgrade because SSO might be interrupted during the upgrade process. Perform any necessary server upgrades at this time because earlier versions of AD Connect might not continue to work after one of the servers has been upgraded.
- Upgrading to 5.x
- Upgrading to 5.0.1 or later requires .NET Framework 4.7.2.
If you're uncertain whether you're running AD Connect or AD Connect with IIS, see the Knowledge Base article Differentiating between AD Connect and AD Connect with IIS.
When the new installer runs, the AD Connect SSO and Provisioner services will be stopped and the installer will guide you through the installation process. The AD Connect SSO and Provisioner services will restart when the installation is complete.