DirSync/Azure AD Sync - End of Support 2017

[Steve21]

Morning All,

 

Not sure if this has been posted but got this email this morning. Guess it's about time I upgrade ours (Summer job as not going to trust doing it in February Halfterm!)

 

Microsoft Azure Active Directory (AD) Connect is the best way to connect your on-premises directory with Azure AD and Office 365. This is a great time to upgrade to Azure AD Connect from Windows Azure Active Directory Sync (DirSync) or Azure AD Sync as these tools are now deprecated and will reach end of support on April 13, 2017.

 

The two identity synchronization tools that are deprecated were offered for single forest customers (DirSync) and for multi-forest and other advanced customers (Azure AD Sync). They will reach end of support on April 13, 2017.

 

These older tools have been replaced with a single solution that is available for all scenarios: Azure AD Connect. It offers new functionality, feature enhancements, and support for new scenarios. To be able to continue to synchronize your on-premises identity data to Azure AD and Office 365, we strongly recommend that you upgrade to Azure AD Connect.

 

For more information about this transition, please visit the Azure AD Connect webpage.

 

 

Thank you,

 

Your Azure Team

 

Steve

Edited April 14, 2016 by Steve21

[Boredguy]

Yes we got the same e-mail so I've pencilled it in for May half term since it should be straight forward enough

[win]

We're using AD connect and the install was straight forward, no issues so far - touch wood!

[Davit2005]

Morning All,

 

Not sure if this has been posted but got this email this morning. Guess it's about time I upgrade ours (Summer job as not going to trust doing it in February Halfterm!)

 

 

 

Steve

 

Just got our email this morning.

 

The inplace upgrade looks easy from the Video ( too easy for my liking). I'm going to be looking at Parallel deployment I think as I want to install on a newer server OS at the same time

 

If anyone has done this allready can you let me know how it went??

[Steve21]

I started having a look and decided it's better to wait till downtime. As I want to do parallel to new server too and if it goes wrong it'll break o365 haha

 

Steve

[Davit2005]

I'd thought they would automate the assigning of Licences so I don't need to worry about the PowerShell script that I spent weeks getting working.

 

No doubt after the upgrade I will have to spend another who knows how many weeks getting the script working again

Edited April 14, 2016 by Davit2005

[Matt_Renato]

I did the upgrade for a secondary school before Easter and it took around 20-30 minutes. It's a much better tool than DirSync so I'd upgrade when you get the chance.

 

I'd thought they would automate the assigning of Licences so I don't need to worry about the PowerShell script that I spent weeks getting working.

 

No doubt after the upgrade I will have to spend another who knows how many weeks getting the script working again

 

The upgrade shouldn't break your PowerShell script, I've been using the same scripts on sites with DirSync and Azure AD Connect and they work fine on both.

[Cache]

I did it one night after school as DirSync developed a bug where it wouldn't sync new users passwords and the only way to fix it was to upgrade so bit the bullet.

 

Was suprisingly easy compared to what I expected, it just did it after answering it's questions.

[Matt_Renato]

I did it one night after school as DirSync developed a bug where it wouldn't sync new users passwords and the only way to fix it was to upgrade so bit the bullet.

 

Was suprisingly easy compared to what I expected, it just did it after answering it's questions.

 

Interesting you mention problems with password sync as I have seen similar cases with DirSync where an upgrade to Azure AD Connect has fixed the issue. There was a bug I found in DirSync years ago where the password sync option would randomly uncheck itself.

[Cache]

Ah it wasn't that one, Dirsync started erroring when trying to sync a certain new users password up, tried to force a resync of everybody and then I broke half the users password sync with errors in the event viewer.

 

Upgrading was my only option at that point!

[uke]

Sorry if this is the wrong place, if I need more detailed info I will start a new thread. I am about to install for the first time, so am new to using this. Previously I had kept my AD and 365 separate but we are going to start using pupil accounts so this makes sense. Just a few questions;

* I currently don't enforce strong policies on my AD (its a primary school), will it sync these unseucre accounts to 365? or will it give warnings?

* When I run it will it let me choose which part of AD gets synced?

* If I already have users in 365 will it recognise a conflict, put them as two users or merge them together?

 

Thank you

[Cache]

Sorry if this is the wrong place, if I need more detailed info I will start a new thread. I am about to install for the first time, so am new to using this. Previously I had kept my AD and 365 separate but we are going to start using pupil accounts so this makes sense. Just a few questions;

* I currently don't enforce strong policies on my AD (its a primary school), will it sync these unseucre accounts to 365? or will it give warnings?

* When I run it will it let me choose which part of AD gets synced?

* If I already have users in 365 will it recognise a conflict, put them as two users or merge them together?

 

Thank you

 

1. Yes, it will sync these without issue

2. Yes, when configuring it or afterwards you can go back and configure OU filtering on it

3. I believe so, as long as the email address is set in AD in the email field and possibly the proxyaddress, it should recognise it. I can't say for certain as I started our office 365 from DirSync, but I'm sure that's the way it's supposed to work. Any that conflict it should give you an error report for.