Solved Exchange 2010 Synchronization Service Manager - Automating this with PowerShell
-
@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.
-
That looks like how the newer version is set up. Is it running version 1.1.343.0 or higher?
-
@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
-
-
I would upgrade it and see if it doesn't sync automatically after that.
-
@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.
-
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.
-
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...
-
haha... well that was in fact the answer.
-
When you fire that power shell script off, if you go back to the sync manager, you'll see it does all 6 things.
-
@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!