psydii Posted February 19, 2016 Posted February 19, 2016 http://blogs.technet.com/b/uspartner_ts2team/archive/2016/02/18/azure-ad-connect-1-1-is-now-ga-providing-faster-sync-times-automatic-upgrades-and-built-in-filtering-options-and-more.aspx This may be the last version you will need to install, as it adds an automatic update feature. Also: sync's can now be run as frequently as every 30 minutes. And You can now switch between password sync and federation by just re-running the wizard. 2
sparkeh Posted February 23, 2016 Posted February 23, 2016 (edited) Seems that people really need to update to this. Password sync broke for us after this was released and only fixed by updating. Also worth nothing that the scheduled task for syncing is deleted and manual syncs now need to be done via PS Delta sync: Start-ADSyncSyncCycle -PolicyType Delta Full sync Start-ADSyncSyncCycle -PolicyType Initial Edited February 23, 2016 by sparkeh 1
the_dude Posted February 23, 2016 Posted February 23, 2016 "1. Reduction in the time in between synchronizations of your on premises Active Directory and the cloud. Prior to today the lowest you could go is 3 hours, with the new iteration today you can reduce this down to a 30 minute interval. Technically you could set it to whatever you want now, but it will not honor less than 30 minutes." That's lame. I sync every 3 minutes right now.
Matt_Renato Posted February 25, 2016 Posted February 25, 2016 Just been having a play with this and there is finally an option in the wizard to filter which OUs you want sync. Much nicer than having to use the clunky old FIM interface to configure it after setup. 1
badders Posted February 25, 2016 Posted February 25, 2016 Just upgraded to this from dirsync, it all went fine and passwords are still syncing but I can't see a scheduled task for Azure AD Sync. It looks to be using the old setting (approx 30 mins) but I can't even find where it's pulling this from.
sparkeh Posted February 25, 2016 Posted February 25, 2016 (edited) Just upgraded to this from dirsync, it all went fine and passwords are still syncing but I can't see a scheduled task for Azure AD Sync. It looks to be using the old setting (approx 30 mins) but I can't even find where it's pulling this from. From above Also worth nothing that the scheduled task for syncing is deleted and manual syncs now need to be done via PS Delta sync: Start-ADSyncSyncCycle -PolicyType Delta Full sync Start-ADSyncSyncCycle -PolicyType Initial It looks to be using the old setting (approx 30 mins) but I can't even find where it's pulling this from. You need to use powershell now. To get the sync interval: Get-ADSyncScheduler To set interval: Set-ADSyncScheduler -CustomizedSyncCycleInterval 01:00:00(would set an hourly sync, edit to suit) Edited February 25, 2016 by sparkeh 1
sparkeh Posted February 25, 2016 Posted February 25, 2016 Must learn to read!! Also just edited reply to include how to get and set the sync interval 1
badders Posted February 25, 2016 Posted February 25, 2016 Just found it and can see our previously set sync interval.
spc-rocket Posted February 25, 2016 Posted February 25, 2016 Hi, If we have the old version installed, can this be installed over the top? does it need reconfiguring? Thanks, Ash.
sparkeh Posted February 25, 2016 Posted February 25, 2016 (edited) Hi, If we have the old version installed, can this be installed over the top? does it need reconfiguring? Thanks, Ash. This should help: https://azure.microsoft.com/en-gb/documentation/articles/active-directory-aadconnect-dirsync-upgrade-get-started/ Edit: I assumed you meant the old DirSync, if you mean an old version of AD Connect then yes I just ran the installer and it upgraded. Edited February 25, 2016 by sparkeh
Matt_Renato Posted February 25, 2016 Posted February 25, 2016 I installed this over the top of the previous version on our test system and it worked fine. It will run through the wizard after installation so make sure you have the details for the local and cloud accounts that you use for authentication with the tool. The only issue I've noticed so far is that if I run get-adsyncscheduler the next sync time reports back as 01/01/0001, the tool appears to be synchronising correctly every half hour though!
sparkeh Posted February 25, 2016 Posted February 25, 2016 (edited) Interestingly, I am now getting warnings in the 365 console that it hasn't synced with AD for over 24 hours, yet I can run a sync and everything appears to be successful (changes in AD are reflected in cloud). edit: Ah scheduled syncs are not running, I have the 01/01/0001 thing too :S Edited February 25, 2016 by sparkeh
psydii Posted February 25, 2016 Author Posted February 25, 2016 I had this too, and just logged a ticket with support via the Office365 Admin console. They called me back and we had it fixed within an hour. After assessing how we had it configured (very simply as it turns out), they uninstalled it and removed all traces of the old sync database and scheduled tasks, then re-installed it. Their advice was that I should have uninstalled the old version first. 1
spc-rocket Posted February 26, 2016 Posted February 26, 2016 This should help: https://azure.microsoft.com/en-gb/documentation/articles/active-directory-aadconnect-dirsync-upgrade-get-started/ Edit: I assumed you meant the old DirSync, if you mean an old version of AD Connect then yes I just ran the installer and it upgraded. Hiya, We have the AD connect tool v1.0.0.4994.xxx so as you say I can just install it over the top. Thanks, Ash.
spc-rocket Posted February 26, 2016 Posted February 26, 2016 Ah having double check the posts I think I will uninstalled the current version and then install the new version just to be sure. Ash.
sparkeh Posted February 29, 2016 Posted February 29, 2016 I had this too, and just logged a ticket with support via the Office365 Admin console. They called me back and we had it fixed within an hour. After assessing how we had it configured (very simply as it turns out), they uninstalled it and removed all traces of the old sync database and scheduled tasks, then re-installed it. Their advice was that I should have uninstalled the old version first. Logged a support ticket too. Turns out we just needed to enable scehduled sync with Set-ADSyncScheduler -SyncCycleEnabled $true Then, optionally, change the sync time to Delta so that it didn't perform a full sync on its first run Set-ADSyncScheduler -NextSyncCyclePolicyType Delta
Matt_Renato Posted March 1, 2016 Posted March 1, 2016 Looks like that issue was a bug, there is an updated version now 1.1.110 1
psydii Posted March 2, 2016 Author Posted March 2, 2016 Some more info on the initial 1.1 release, including information on how sync works now. http://blogs.technet.com/b/rmilne/archive/2016/03/02/azure-ad-connect-express-install-upgrade-build-1-1-105-0.aspx
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