I used this as a starting point for filtering OUs. However, I filtered OUs **before** the initial sync.
Office 365 DirSync Filtering « MSExchangeGuru.com
I have started using the Azure connector with Office 365 which works pretty well (almost there M$... just copy Google a bit more) but for some reason the syncing is doing all the Ou's to the cloud and I really don't want all my controlled assessment accounts up there.
I have found an article which I think was for the previous version and changed the settings using the MIISCLIENT.EXE program in management agent > AD Connector > Configure Directory Partitions > Containers and just selected the staff OU to start with but its still syncing all the accounts and I am getting errors sent to m about the sync not working properly for these kids accounts.
I went in and disabled the AD connector online and deleted all the kids accounts and tried again but they uploaded the kids accounts again.
Is this the correct way to sync certain OU's? I have read somewhere that they want you to sync your whole org but that's a bit useless unless they start allowing us to create nice groups online to sort them out (Google again)
That's exactly how I followed my setup but its still syncing other OU's that I told it not to.
If the account is not in the OU anymore that gets synced should it get put in the deleted users bit?
The results of the upload are a bit confusing
Unchanged 165 (staff I believe)
Its just a bit confusing as I deleted everyone other than staff off the cloud last night and the first sync they have come back… but this is now saying its deleting them. I wonder if it took them out of deleted users and put them back in the main bit as the users are set for deleting after 30 days??
As for the DIRSYNC, I have doen a full sync and here is a screenie of my filtering. I must be missing something obvious here.
Last edited by Simcfc73; 12th December 2013 at 10:25 AM.
Google's approach might be more browser-based, and that's fine, but I don't think they have anything that even comes within a country mile of PowerShell.
How did you trigger a full sync?
It a new install on a different server, I had ADFS on a different one and it went belly up when I changed password so I reinstalled it fresh. I did a full sync with the right click run now, I will try with the powershell command next.
I just added a attribute field now so will see if that works.
Boooo and as if by magic its done it and I don't know what I did wrong/right.
Looking at the operations log the Windows Azure Active Directory export Export hadn't run since 8.30 even though I thought I was forcing it to which is weird.
So my question is, when you right click on the AD connector and do a Full Import Full Sync is doesn't do a upload to the cloud, you have to do a right click Azure then Export.... is this right as its the way its forcing a sync on mine but there's no documentation saying this.
Okay thanks for the help, just going through and adding the attribute so it doesn't sync everyone.
Don't mean to be overly negative and pro google.. I don't particularly like there stuff either it just some of there features are really good.. and I despair at having to use Powershell scripts to accomplish simple tasks, I have enough swimming in my head without having to remember strings of code.
There are currently 1 users browsing this thread. (0 members and 1 guests)