With the connectivity to Azure AD verified, it is time to look into the eventlogs. Also test the Health connectivity to Azure AD. If you use a proxy, make sure Health has been configured to use a proxy server. Automatic update is using Azure AD Connect Health as described in the overview. Then, make sure you have opened the required URLs in your proxy or firewall. 'AADHealthEndpointNotDefined' or 'DirSyncInPlaceUpgradeNonLocalDb'. It is also possible to get a result that is not an UpgradeResult i.e. A compound value may also be returned, such as UpgradeFailedRollbackSuccess-GetPasswordHashSyncStateFailed. The suspension reason can contain any string value but will usually contain the string value of the UpgradeResult, that is, UpgradeNotSupportedNonLocalDbInstall or UpgradeAbortedAdSyncExeInUse. If the state is suspended, you can use the Get-ADSyncAutoUpgrade -Detail to view the reason. If you think something is not right, then first run Get-ADSyncAutoUpgrade to ensure automatic upgrade is enabled. There is an intentional randomness before an upgrade is attempted so don't be alarmed if your installation isn't upgraded immediately. If your Connect installation does not upgrade itself as expected, then follow these steps to find out what could be wrong.įirst, you should not expect the automatic upgrade to be attempted the first day a new version is released. Health data uploads have been disabled from the portal UpgradeNotSupportedAADHealthUploadDisabled Local DB size is greater than or equal to 8 GB You are not using a SQL Server Express LocalDB database. The installation is not an Express settings or a DirSync upgrade. You have added your own custom rules to the configuration. In order to eligible for an automatic upgrade, you must not meet any one of the following conditions: Result Message For more information, see the article Azure AD Connect: Version release history. If auto upgrade was enabled on your Azure AD Connect server then that server will automatically upgrade to the latest version of Azure AD Connect released for auto upgrade if your configuration is eligible for auto upgrade. The release status indicates if a release is available for auto upgrade or for download only. Not all releases of Azure AD Connect are made available for auto upgrade. If the Synchronization Service Manager UI is running on the server, then the upgrade is suspended until the UI is closed. For automatic upgrade to work, make sure you have opened the URLs in your proxy server for Azure AD Connect Health as documented in Office 365 URLs and IP address ranges. This functionality has now changed so it does not block AutoUpgrade.Īutomatic upgrade is using Azure AD Connect Health for the upgrade infrastructure. Prior to 1.1.750.0 the Set-ADSyncAutoUpgrade cmdlet would block Autoupgrade if the auto-upgrade state was set to Suspended. Only the system should set the state Suspended. You can change between Enabled and Disabled with Set-ADSyncAutoUpgrade. The system is not currently eligible to receive automatic upgrades. The current state of automatic upgrade can be viewed with the PowerShell cmdlet Get-ADSyncAutoUpgrade. Have less than 100,000 objects in the metaverse.The AD account is the default MSOL_ account created by Express settings and DirSync.DirSync with SQL Express also use LocalDB. Using SQL Express LocalDB, which is what Express settings always use.Express settings installation and DirSync upgrades.When a new version is released, your installation is automatically upgraded.Īutomatic upgrade is enabled by default for the following: This feature is enabled by default for express installations and DirSync upgrades. Making sure your Azure AD Connect installation is always up to date has never been easier with the automatic upgrade feature. Customers must take the latest update to remain supported.įor products and services governed by the Modern Lifecycle Policy, Microsoft's policy is to provide a minimum 30 days' notification when customers are required to take action in order to avoid significant degradation to the normal use of the product or service. Product governed by the Modern Policy follow a continuous support and servicing model. Changes for products and services under the Modern Lifecycle Policy may be more frequent and require customers to be alert for forthcoming modifications to their product or service. Azure Active Directory (AD) Connect follows the Modern Lifecycle Policy.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |