Trying to upgrade Azure AD Connect v2.2.1.0 to v2.2.8.0 from windows 2019 server

Question

Trying to upgrade Azure AD Connect v2.2.1.0 to v2.2.8.0 from windows 2019 server

Benton Chan 30

Givens:

Vmware virtual servers:

W2k19 member server 1 running Azure AD Connect v2.2.1.0 in stagging mode.

W2k19 member server 2 running Azure AD Connect v2.2.1.0 non-stagging mode.

Both servers are running in our production environment.

Downloaded Azure (Entra) AD Connect v2.2.8.0 into each server.

Took vmware snaphot of server 1 prior to any app installs.
Clicked on install for v2.2.8.0, but could not complete the upgrade and could not use the previous button to reverse the install.
Had to revert back to vmware snaphot to resolve problem.
Problems encountered during install attempt.

User's image

Will there be another release to resolve the upgrade problem?

What is another option to resolve this problem?

Navya 20,100 Reputation points Microsoft External Staff Moderator

2023-12-15T09:22:58.98+00:00

Hi @Benton Chan

Just checking in to see if the below answer provided by @Thameur-BOURBITA helped. If this answers your query, do click Accept Answer and Yes for was this answer helpful. And, if you have any further query do let us know.
Navya 20,100 Reputation points Microsoft External Staff Moderator

2023-12-19T13:32:34.19+00:00

Hi @Benton Chan ,

Following up to see if the below answer was helpful. If this answers your query, do click Accept Answer and Yes for was this answer helpful. And, if you have any further query do let us know.
Benton Chan 30 Reputation points

2024-01-11T19:37:47.57+00:00

A newer 2.3.2.0 version of Azure AD Connect was released, so I had tried to install it for the upgrade. However, it failed with similar error results already mentioned. I had tried using the MigrateSettings.ps1 script for collecting all the required data from the syncing server, but this only partially collected it. Running the script outputted no problems. I ended up stopping the syncing server, so I can export the synchronizationpolicy.json file that has approximately 5 times more data. I had installed this using customize mode with the imported synchronizationpolicy.json file. Enter all the credentials required for the install the complete. Checked the ADSyncAdmin group on the server to verify the domain accounts match with what is already running in our production environment. Rebooted the server, then accessed it again to check on the status of the Microsoft Azure AD Sync service. The service was not running, so I had to access it , entered the password, and restarted the service. Verified the service was running. Brought up the Azure(Entra) AD Connect Synchronization manager to verify it was working. Went to entra.microsoft.com and verified the new server was showing up healthly under Microsoft Entra Connect Servers area of the Microsoft Entra Admin Center.

Accepted answer

0 additional answers

Your answer

Navya 20,100 Reputation points Microsoft External Staff Moderator

2023-12-15T09:22:58.98+00:00

Hi @Benton Chan

Just checking in to see if the below answer provided by @Thameur-BOURBITA helped. If this answers your query, do click Accept Answer and Yes for was this answer helpful. And, if you have any further query do let us know.
Navya 20,100 Reputation points Microsoft External Staff Moderator

2023-12-19T13:32:34.19+00:00

Hi @Benton Chan ,

Following up to see if the below answer was helpful. If this answers your query, do click Accept Answer and Yes for was this answer helpful. And, if you have any further query do let us know.
Benton Chan 30 Reputation points

2024-01-11T19:37:47.57+00:00

A newer 2.3.2.0 version of Azure AD Connect was released, so I had tried to install it for the upgrade. However, it failed with similar error results already mentioned. I had tried using the MigrateSettings.ps1 script for collecting all the required data from the syncing server, but this only partially collected it. Running the script outputted no problems. I ended up stopping the syncing server, so I can export the synchronizationpolicy.json file that has approximately 5 times more data. I had installed this using customize mode with the imported synchronizationpolicy.json file. Enter all the credentials required for the install the complete. Checked the ADSyncAdmin group on the server to verify the domain accounts match with what is already running in our production environment. Rebooted the server, then accessed it again to check on the status of the Microsoft Azure AD Sync service. The service was not running, so I had to access it , entered the password, and restarted the service. Verified the service was running. Brought up the Azure(Entra) AD Connect Synchronization manager to verify it was working. Went to entra.microsoft.com and verified the new server was showing up healthly under Microsoft Entra Connect Servers area of the Microsoft Entra Admin Center.

Answer 1

Thameur-BOURBITA 36,261 Moderator

Hi @Benton Chan •

Please check if the requirement version of .net is already installed on each server before the upgrade as mentioned in the link below:

2.2.8.0

If the .net is ok , and you still have the error ,you can start by upgrade the staging server by following the steps below: :

Export settings configuration using the following command MigrateSettings.ps1 as mentioned in the following link : Migration process
Uninstall staging server and reinstall it using the exported json file generated in the previous step
Switch staging mode between your server
Uninstall then reinstall the other server using exported file generate in step 1

Please don't forget to accept helpful answer

Thameur-BOURBITA 36,261 Reputation points Moderator

2023-12-26T10:33:34.18+00:00

Hi @Benton Chan

Just cheking if there is any progess or update

Please don't forget to accept helpful answer and close this thread
Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Benton Chan 30 Reputation points

2024-01-11T19:52:57.7633333+00:00

Don't forget you can have multiple stagging servers, but you can only have one synching server. My new stagging server is running W2k22 with the most current updates.
Benton Chan 30 Reputation points

2024-01-12T01:36:25.6833333+00:00

If you do use the MigrateSettings.ps1 script, do a comparison between this one and manually exported one from the sync server. If they are not the same, use the one that has more data in it. For me, I ran the script and didn't encounter any error messages. I looked at the contents of the SynchornizationPolicy.json file and noticed a bunch of things missing, so I accessed Azure AD Connect app from the server. I had exported the SynchornizationPolicy.json file into my new W2k22 Azure(Entra) AD Connect server. For the stagging and sync servers, don't forget to enable TLS1.2 either by registry setting or using a powershell script, which can be found by googling.
Benton Chan 30 Reputation points

2024-01-12T14:56:04.9633333+00:00

Thameur, Thank you for responding to my query last month and providing me alternatives I was thinking about. However, I could not respond right away. I had to wait for management authorization for a change order before proceeding. Anyway, I had created a HowTo doc for others who might run into the same issues. PleaAzureADConnectStaggingServer2024-Public.pdfse refer to the attached pdf file.

Share via

Trying to upgrade Azure AD Connect v2.2.1.0 to v2.2.8.0 from windows 2019 server

0 additional answers

Your answer