I work for a non-profit and I am trying to get the local ad with passwords synced to azure ad so that our users can have the password synced for their user accounts with office 365. I’ve asked this question several times and know one seems to know the answer. I’m running server 2016 essentials and you can’t install ad connect probably because there are some features built into essentials that try’s to take care of this. In my admin council on office 365 it’s says I’m using an outdated identity sync client. I need this to be fixed so we can move foreword with this project.

1 Spice up

Where are you seeing this message? I have one client on 2016 Essentials using the built-in sync and I don’t see anything like that. In fact, you shouldn’t enable the directory sync feature on the O365 side.

Can you stick the AD Connect on a different server? DirSync is the old tool I believe that was replaced by AD Connect. I haven’;t used essentials in awhile, but I do remember in 2012r2 it was pretty easy to setup the sync.

Does this help?

The only other server software we are liscened for is server 2012 essentials which I don’t have installed on anything but I could throw it on a spare server and see if it will allow it to be installed

They still use the term “dirsync” in the management portal in a few places but they are just referring to “directory synchronization” in general, not the old Dirsync utility.

To use the password syncing feature of Server Essentials, you shouldn’t have the Directory Synchronization feature enabled in the portal.

In the o365 portal?

No need to use it at all if you just want to sync passwords.