Exchange 2010 Synchronization Service Manager - Automating this with PowerShell

DustinB3403

@Mike-Davis said in Exchange 2010 Synchronization Service Manager - Automating this with PowerShell:

@DustinB3403 It should be on your dir sync server if you're running an old version of Dir Sync.

You are trying to sync your accounts with Azure, correct?

Correct, but there is no hybrid between our on-premise and Azure.

DustinB3403

As we create a user account on our On-premise DC, we then have to manually set the SMTP address which pushes the account details to Microsoft to "create" the mailbox.

But before the account syncs with Microsoft we have to run the steps in the OP to sync. (or wait 3 hours).

Which once the user is on Office365, we then can assign a license and they are all set to go.

Mike Davis

Do you have DirSync / Azure AD Connect running on your exchange server or another server?

DustinB3403

@Mike-Davis Azure AD Connect is running on our Exchange Server.

Mike Davis

you don't have any path like C:\Program Files\Windows Azure Active Directory Sync ?

DustinB3403

@Mike-Davis said in Exchange 2010 Synchronization Service Manager - Automating this with PowerShell:

you don't have any path like C:\Program Files\Windows Azure Active Directory Sync ?

These are the file paths that I have.

Edit: I do have a "Windows Azure Active Directory" folder, but it's empty.

Mike Davis

That looks like how the newer version is set up. Is it running version 1.1.343.0 or higher?

DustinB3403

@Mike-Davis said in Exchange 2010 Synchronization Service Manager - Automating this with PowerShell:

That looks like how the newer version is set up. Is it running version 1.1.343.0 or higher?

I'm an idiot.

You mean the sync manager.

It is running 1.1.380.0

DustinB3403

Mike Davis

I would upgrade it and see if it doesn't sync automatically after that.

DustinB3403

@Mike-Davis said in Exchange 2010 Synchronization Service Manager - Automating this with PowerShell:

I would upgrade it and see if it doesn't sync automatically after that.

This is a production system, and we've had a hard enough time getting back to operable.

I'm just trying to simplify my life a bit, by not having to manually run the sync process for any new hires we may have to create.

DustinB3403

Also isn't this the newest version?

https://www.microsoft.com/en-us/download/details.aspx?id=47594

Edit: which matches what we have installed.

DustinB3403

So I've found this.

Which is summarized as this.

Import-Module ADSync

Get-ADSyncScheduler

Start-ADSyncSyncCycle -PolicyType Delta

But that doesn't seem right... why would the GUI have 6 processes, and the powershell version only have 3...

DustinB3403

haha... well that was in fact the answer.

Mike Davis

When you fire that power shell script off, if you go back to the sync manager, you'll see it does all 6 things.

DustinB3403

@Mike-Davis said in Exchange 2010 Synchronization Service Manager - Automating this with PowerShell:

When you fire that power shell script off, if you go back to the sync manager, you'll see it does all 6 things.

Yep, that's how I confirmed it!