Azure AD COnnect Auto-Upgrade

Question

Hello,
I am looking for some help with Azure AD Connect Auto-Upgrade. I cannot move my new Active server to Auto-Update even though the old Active server was set to Auto-upgrade. I have run the cmdlet Set-ADSyncAutoUpgrade -AutoUpgradeState Enabled I receive this error:

Set-ADSyncAutoUpgrade : Could not load file or assembly 'Microsoft.Azure.ActiveDirectory.Synchronization.UpgraderCommon, Version=2.1.0.0,
Culture=neutral, PublicKeyToken=XXXXXXXXXX' or one of its dependencies. The system cannot find the file specified.
At line:1 char:1
Set-ADSyncAutoUpgrade -AutoUpgradeState Enabled
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

• CategoryInfo : NotSpecified: (:) [Set-ADSyncAutoUpgrade], FileNotFoundException
• FullyQualifiedErrorId : System.IO.FileNotFoundException,Microsoft.IdentityManagement.PowerShell.Cmdlet.SetADSyncAutoUpgradeCmdlet
  I have moved my Active server to staging (this was set to auto-upgrade), I then moved my staging server to Active and It will not set the Auto-Upgrade to be enabled. I have found 2 things that seem to be a possible cause.

2. I am missing two folders on the new server. 'Microsoft Azure AD Connect Agent Updater' and 'Microsoft Azure AD Connect Provisioning Agent'. Can I install these separately? Is this a separate program to install? I am not finding it anywhere. I am wondering if we need to re-install it. I would prefer not to have to do that if there is an option to possibly copy the files from the server that has the files or download the required files/program from Microsoft.

Answer 1

Hi,

Thank you for asking this question on the Microsoft Q&A Platform.

Can you please check and provide the output of these command
Get-ADSyncAutoUpgrade or
Get-ADSyncAutoUpgrade -Detail

The Azure AAD Connect automatic upgrade is enabled by default for the following, so please review the below list and if any of these applies :

Express settings installation and DirSync upgrades.
Using SQL Express LocalDB, which is what Express settings always use. DirSync with SQL Express also use LocalDB.
The AD account is the default MSOL_ account created by Express settings and DirSync.
Have less than 100,000 objects in the metaverse.

Is the installation an express or custom installation? As it will be important part of this issue and troubleshooting:

In order to eligible for an automatic upgrade, you must not meet any one of the following conditions:

Result Message Description
UpgradeNotSupportedCustomizedSyncRules You have added your own custom rules to the configuration.
UpgradeNotSupportedInvalidPersistedState The installation is not an Express settings or a DirSync upgrade.
UpgradeNotSupportedNonLocalDbInstall You are not using a SQL Server Express LocalDB database.
UpgradeNotSupportedLocalDbSizeExceeded Local DB size is greater than or equal to 8 GB
UpgradeNotSupportedAADHealthUploadDisabled Health data uploads have been disabled from the portal

===

Please "Accept the answer" if the information helped you. This will help us and others in the community as well.

Answer 2

Thanks for the Reply. I have run the commands again to show them in the order I ran them. I removed the public token but everything else is the exact output from the 2 commands.

I know the two pieces of software ('Microsoft Azure AD Connect Agent Updater' and 'Microsoft Azure AD Connect Provisioning Agent') are missing on the new server and I would guess they have something that affects the Auto-upgrade. But I am not sure if it is required to do a full re-installation or if I can download or copy them from the old server. I could be wrong but I would think that is the fix. To install the programs. I just have not found the download for it so I do not know if it is part of the installation or a separate program.

PS C:\Windows\system32> Set-ADSyncAutoUpgrade
cmdlet Set-ADSyncAutoUpgrade at command pipeline position 1
Supply values for the following parameters:
AutoUpgradeState: Enable
Set-ADSyncAutoUpgrade : Could not load file or assembly 'Microsoft.Azure.ActiveDirectory.Synchronization.UpgraderCommon, Version=2.1.0.0,
Culture=neutral, PublicKeyToken=XXXXXXXXXXXXX' or one of its dependencies. The system cannot find the file specified.
At line:1 char:1

• Set-ADSyncAutoUpgrade
• ~~~~~~~~~~~~~~~~~~~~~
• CategoryInfo : NotSpecified: (:) [Set-ADSyncAutoUpgrade], FileNotFoundException
• FullyQualifiedErrorId : System.IO.FileNotFoundException,Microsoft.IdentityManagement.PowerShell.Cmdlet.SetADSyncAutoUpgradeCmdlet

PS C:\Windows\system32> Get-ADSyncAutoUpgrade -Detail

State SuspensionReason  
----- ----------------  

Suspended Unknown

Answer 3

Here is what I have found.

10:17:46.596] [ 1] [INFO ] GetInstalledPackagesByUpgradeCode {36f68a90-239c-34df-b58c-64b30153ce35}: verified product code {e642504a-44a4-4cea-ab54-76d0f34f33ba}.
[10:17:46.596] [ 1] [VERB ] Package=Microsoft Visual C++ 2019 X64 Minimum Runtime - 14.29.30036, Version=14.29.30036, ProductCode=e642504a-44a4-4cea-ab54-76d0f34f33ba, UpgradeCode=36f68a90-239c-34df-b58c-64b30153ce35
[10:17:46.596] [ 1] [INFO ] Determining installation action for Microsoft Visual C++ 2019 Redistributable Package (36f68a90-239c-34df-b58c-64b30153ce35)
[10:17:46.596] [ 1] [INFO ] Product Microsoft Visual C++ 2019 Redistributable Package (version 14.29.30036) is installed.
[10:17:46.596] [ 1] [INFO ] Performing direct lookup of upgrade codes for: Microsoft Directory Sync Tool
[10:17:46.596] [ 1] [VERB ] Getting list of installed packages by upgrade code
[10:17:46.596] [ 1] [INFO ] GetInstalledPackagesByUpgradeCode {bef7e7d9-2ac2-44b9-abfc-3335222b92a7}: no registered products found.
[10:17:46.596] [ 1] [INFO ] GetInstalledPackagesByUpgradeCode {dc9e604e-37b0-4efc-b429-21721cf49d0d}: no registered products found.
[10:17:46.596] [ 1] [INFO ] GetInstalledPackagesByUpgradeCode {545334d7-13cd-4bab-8da1-2775fa8cf7c2}: verified product code {81da1bf7-f50f-447e-b869-8c628498d192}.

I am sorry but I didnt seeanythink in the provided link for T/S the agent installation adn upgrade issue.

Answer 4

I did the original installation with a custom install from the exported configuration from the first server. It was not an express installation.

I did find this explanation that I posted below. The way I read it, the new Server in Active mode will not be set to auto-upgrade until a new version is out then it will allow you to set the auto-upgrade option.

https://www.enowsoftware.com/solutions-engine/azure-active-directory-center/understanding-auto-upgrade-options-in-azure-ad-connect

"If the current configuration is not supported by Auto-Upgrade, AAD Connect will set to state to Suspended. You can think of a Suspended state to mean, “Not possible.” If an administrator should set the Auto-Upgrade state to Enabled on a server where Auto-Upgrade is not possible, AAD Connect will set it back to Suspended on the next polling cycle.

This behavior is expected and will carry forward for each manual upgrade. AAD Connect will continue to check for updates on the regular 6-hour schedule. Once the current configuration is supported, AAD Connect will update to the latest build."

Does this sound correct?

Answer 5

I did the original installation with a custom install from the exported configuration from the first server. It was not an express installation.

I did find this explanation that I posted below. The way I read it, the new Server in Active mode will not be set to auto-upgrade until a new version is out then it will allow you to set the auto-upgrade option.

https://www.enowsoftware.com/solutions-engine/azure-active-directory-center/understanding-auto-upgrade-options-in-azure-ad-connect

"If the current configuration is not supported by Auto-Upgrade, AAD Connect will set to state to Suspended. You can think of a Suspended state to mean, “Not possible.” If an administrator should set the Auto-Upgrade state to Enabled on a server where Auto-Upgrade is not possible, AAD Connect will set it back to Suspended on the next polling cycle.

This behavior is expected and will carry forward for each manual upgrade. AAD Connect will continue to check for updates on the regular 6-hour schedule. Once the current configuration is supported, AAD Connect will update to the latest build."

Does this sound correct?