Popular Post psydii Posted May 25, 2022 Popular Post Posted May 25, 2022 Time to check your Azure AD Connect installation! If you are on v 1.x you *must* upgrade to version 2.x before the 31st August 2022. "I am not ready to upgrade yet – how much time do I have? You should upgrade to Azure AD Connect V2 as soon as you can. All Azure AD Connect V1 versions will be retired on 31 August, 2022. For the time being we will continue to support older versions of Azure AD Connect, but it may prove difficult to provide a good support experience if some of the components in Azure AD Connect have dropped out of support. This upgrade is particularly important for ADAL and TLS1.0/1.1 as these services might stop working unexpectedly after they are deprecated." https://docs.microsoft.com/en-us/azure/active-directory/hybrid/whatis-azure-ad-connect-v2 13
3s-gtech Posted May 25, 2022 Posted May 25, 2022 Back up (export) your configuration first! This *should* transfer between versions, but you'll be cursing if you have to re-set all of your options from scratch otherwise! Ask me how I know 1
Michael Posted May 25, 2022 Posted May 25, 2022 Performing an in place upgrade has worked absolutely fine for me. Currently running version 2.1.1.0, which I believe is still the latest and no problems (touchwood).
colly72 Posted May 25, 2022 Posted May 25, 2022 Bear in mind too that Azure AD Connect v2 and above requires at least Windows 2016 Server, so if you're running on Windows 2012/r2, you'll need to upgrade the OS or migrate to a 2016+ Server 1
jthompson Posted May 25, 2022 Posted May 25, 2022 Automatic upgrades for Azure AD Connect have been working okay here. Running 2.1.1.0. Just noticed the advisory from MS that from next year, 2.x versions will get retired 12 months after release, so you'd probably want to have automatic upgrades working.
StevieM Posted May 25, 2022 Posted May 25, 2022 Bear in mind too that Azure AD Connect v2 and above requires at least Windows 2016 Server, so if you're running on Windows 2012/r2, you'll need to upgrade the OS or migrate to a 2016+ Server That's a job for the summer holidays, then.
tmoon-mint Posted May 25, 2022 Posted May 25, 2022 In place upgrade of Azure AD Connect is super easy and takes 10 minutes max. For any servers that were on 2012R2 I just built a new VM, backed up the current configuration and then imported it into the new installation but kept it in staging mode. Once I was happy that the configurations were identical I enabled staging mode on the old server and disabled it on the new one.
Foresthippy Posted May 25, 2022 Posted May 25, 2022 Or replace with Azure AD Connect cloud sync instead. 1
timbo343 Posted May 25, 2022 Posted May 25, 2022 I did the process a few months ago and posted it here http://www.edugeek.net/forums/enterprise-software/224922-upgrading-azure-ad-connect-v1-6-16-0-v2-swing-migration.html if anyone wants to know how i did it. 3
FragglePete Posted May 26, 2022 Posted May 26, 2022 I did a migration on to a new VM a few months back, went surprisingly well for me. Exported the config and imported this into the new setup which ran in staging mode for a few days, so essentially had two doing the sync (but obviously only one making changes), then put the old into the staging mode and the new into production. Worked well. Pete 1
supportman Posted June 6, 2022 Posted June 6, 2022 I upgraded this today, very easy and just a simple installer to run. Everything went fine. It appears only the internal components are upgraded, no new functionality that I saw.
Boredguy Posted June 6, 2022 Posted June 6, 2022 Only annoying thing, is if doing an in-place migration from 2012 R2 to newer OS, you have to uninstall the AD Connect app then reinstall it.
CHiLL Posted June 6, 2022 Posted June 6, 2022 I upgraded ours last week during half term. It was a vey painless experience. The only thing it moaned about was using something called the DefaultAnchor? (I can't remember exactly) It recommended using another anchor, but doing so would require going through the whole setup wizard again, redoing the configuration. I wasn't up for that task last week, so I left it as it was.
supportman Posted June 6, 2022 Posted June 6, 2022 I upgraded ours last week during half term. It was a vey painless experience. The only thing it moaned about was using something called the DefaultAnchor? (I can't remember exactly) It recommended using another anchor, but doing so would require going through the whole setup wizard again, redoing the configuration. I wasn't up for that task last week, so I left it as it was. We had this issue when we found a duplicate in our sync. From memory the only thing the defaultAnchor caused issues with was that it wasnt editable in the AD GUI properties. There was some workarounds using powershell, but I believe Microsoft changed the anchor to a new field to get around this issue. I think its fine to keep as it is, just a bit harder to fix dupes if they do arrise. 1
CHiLL Posted June 6, 2022 Posted June 6, 2022 We had this issue when we found a duplicate in our sync. From memory the only thing the defaultAnchor caused issues with was that it wasnt editable in the AD GUI properties. There was some workarounds using powershell, but I believe Microsoft changed the anchor to a new field to get around this issue. I think its fine to keep as it is, just a bit harder to fix dupes if they do arrise. Yeah, that rings a bell from when I read through the support page. Since it was only a recommendation and not mandatory, I figured it was fine to leave it as it was.
psydii Posted August 1, 2022 Author Posted August 1, 2022 Just pinging this back up - the clock is ticking!
KK20 Posted August 10, 2022 Posted August 10, 2022 interestingly I checked mine and it is on 2.0.91.0 but autoupgrade *is* on. I'll look at manually upgrading to 2.1.16.0 later...
jthompson Posted August 15, 2022 Posted August 15, 2022 Even if autoupgrade is on (i.e. Get-ADSyncAutoUpgrade returns 'Enabled'), if you don't have a premium Azure license, Azure AD Connect won't automatically upgrade itself. The documentation about Azure AD Connect automatic upgrade states: Automatic upgrade is using Azure AD Connect Health for the upgrade infrastructure. Azure AD Connect Health requires a premium Azure license. So those on the free tier will need to be upgrading manually each time.
psydii Posted August 22, 2022 Author Posted August 22, 2022 Final Call - y'all need to have done this by next Wednesday otherwise you are going to have a very bad start to the academic year. 1
BJG Posted August 23, 2022 Posted August 23, 2022 Or replace with Azure AD Connect cloud sync instead. Currently running Azure AD Connect 1.6 on 2012. Any thoughts on whether it's going to be easier to move it to a 2019 server or switch to Connect Cloud Sync...?
3s-gtech Posted August 23, 2022 Posted August 23, 2022 It’s easy enough to in-place upgrade AADC and the server itself - your choice as to order but I’d do the server first as AADC may need re-initialising afterwards anyway. 1
andy_nic Posted August 24, 2022 Posted August 24, 2022 Went to do mine today on the 17th aug it all got updated to 2.1.16.0 from 1.6 I didn’t do this as I’d noticed it back in may had planned new a server I’ll do the migration is October half term to the new server wonder if Microsoft are pushing this automatically also all the sql stuff got updated to 2019 1
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now