As you probably say in my previous blog post, Microsoft recently had a big update to Azure AD Connect.

NOTE: Since then, they have released 1.1.119.0 here

As of that revision, they have moved the Scheduler function into the sync engine from scheduled tasks. So that begs the question, what if I need to force a sync due to testing or other reasons?

Well, let’s go find out.

First let’s open up PowerShell and check what modules are installed

040616_1326_Forcesyncin1.png

Now let’s run a get-command to see what functions I can perform with that module. Looks like there are quite a few!

040616_1326_Forcesyncin2.png

Looks like there’s a cmdlet for starting a sync cycle, let’s try it out

Start-ADSyncSyncCycle

040616_1326_Forcesyncin3.png

Let’s see if anything happened

040616_1326_Forcesyncin4.png

Looks like our sync worked!

  1. I would also add that you can add the parameter -PolicyType and choose whether you are doing an Initial (full) sync or a Delta (Incremental) sync. You can also use Unspecified, which I assume just means it runs whatever the next one is that is scheduled (whether it is Initial or Delta).

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes:

<a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>