Azure AD connect upgrade and migration

%3CLINGO-SUB%20id%3D%22lingo-sub-3363276%22%20slang%3D%22en-US%22%3EAzure%20AD%20connect%20upgrade%20and%20migration%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3363276%22%20slang%3D%22en-US%22%3E%3CP%3EHello%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20have%20an%20Azure%20AD%20Connect%20server%20with%20the%20following%20spec%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EOS%3A%202012%20R2%3C%2FP%3E%3CP%3EVersion%3A%201.1.880.0%3C%2FP%3E%3CP%3ESQL%20DB%20on%20SQL%202016%20on%20separate%20server%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20would%20like%20to%20upgrade%20to%202.X%20but%20understand%20that%20we%20can't%20put%202.X%20on%202012%20R2.%20We%20also%20can't%20put%201.X%20on%20a%202019%20server%20according%20to%20the%20version%20release%20web%20page.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESo%20how%20do%20we%20get%20to%202.X%20on%20a%20more%20recent%20Windows%3F%20Is%20the%20solution%20to%20upgrade%20the%20current%20OS%20to%202016%3F%20Or%20is%20there%20a%20way%20to%20do%20a%20swing%20migration%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EMany%20thanks%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EBrian%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-3363276%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EIdentity%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3383990%22%20slang%3D%22en-US%22%3ERe%3A%20Azure%20AD%20connect%20upgrade%20and%20migration%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3383990%22%20slang%3D%22en-US%22%3EHi%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1057586%22%20target%3D%22_blank%22%3E%40brian_nfc%3C%2FA%3E%2C%3CBR%20%2F%3E%3CBR%20%2F%3EThe%20uber%20limitation%20as%20I%20read%20it%20is%20with%20SQL.%20%22Since%20Azure%20AD%20Connect%20v2%20contains%20SQL%20Server%202019%20components%2C%20we%20no%20longer%20can%20support%20older%20Windows%20Server%20versions%22%2C%20so%20your%20external%20database%20is%20an%20issue%20as%20is%20the%20AADC%20server%20itself.%3CBR%20%2F%3E%3CBR%20%2F%3EOnce%20you've%20resolved%20the%20database%20uplift%20to%202019%20(in-place%2C%20new%20instance%20or%20opting%20for%20the%20AADC%20LocalDB)%2C%20can%20you%20redeploy%20AADC%20to%20a%20fresh%20W2019%20server%20and%20use%20the%20export%2Fimport%20tool%20to%20migrate%3F%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Factive-directory%2Fhybrid%2Fhow-to-connect-import-export-config%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Factive-directory%2Fhybrid%2Fhow-to-connect-import-export-config%3C%2FA%3E.%3CBR%20%2F%3EThis%20option%20is%20a%20shot%20at%20nothing%20because%20if%20it%20doesn't%20work%20you%20haven't%20lost%20anything%20vs%20any%20in-place%20scenario.%3CBR%20%2F%3E%3CBR%20%2F%3EHope%20this%20helps.%20Ash%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3391724%22%20slang%3D%22en-US%22%3ERe%3A%20Azure%20AD%20connect%20upgrade%20and%20migration%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3391724%22%20slang%3D%22en-US%22%3EHi%20Ash%2C%20thank%20you%20for%20pointing%20this%20out!%20Pity%20we%20didn't%20use%20the%20internal%20database!%3C%2FLINGO-BODY%3E
Occasional Contributor

Hello,

 

We have an Azure AD Connect server with the following spec:

 

OS: 2012 R2

Version: 1.1.880.0

SQL DB on SQL 2016 on separate server

 

We would like to upgrade to 2.X but understand that we can't put 2.X on 2012 R2. We also can't put 1.X on a 2019 server according to the version release web page. 

 

So how do we get to 2.X on a more recent Windows? Is the solution to upgrade the current OS to 2016? Or is there a way to do a swing migration?

 

Many thanks,

 

 

Brian

2 Replies
Hi @brian_nfc,

The uber limitation as I read it is with SQL. "Since Azure AD Connect v2 contains SQL Server 2019 components, we no longer can support older Windows Server versions", so your external database is an issue as is the AADC server itself.

Once you've resolved the database uplift to 2019 (in-place, new instance or opting for the AADC LocalDB), can you redeploy AADC to a fresh W2019 server and use the export/import tool to migrate? https://docs.microsoft.com/en-us/azure/active-directory/hybrid/how-to-connect-import-export-config.
This option is a shot at nothing because if it doesn't work you haven't lost anything vs any in-place scenario.

Hope this helps. Ash
Hi Ash, thank you for pointing this out! Pity we didn't use the internal database!