- Directory Sync – Filtering OU’s to Sync to Office 365 – http://office365support.ca/directory-synchronization-filtering-ous-…
- Office 365 Mailbox Users Not Showing in On-Premise GAL – http://community.office365.com/en-us/f/613/t/26641.aspx
- Manage directory synchronisation – https://technet.microsoft.com/en-us/library/jj151821.aspx
When DirSync is enabled, synchronization is automatically set to occur every three hours. However, there are instances were its not acceptable. For example, a new user requires access to their mailbox, but you know it typically takes about 20 minutes for the synchronization to finish. What would be the best option to speed up the process to allow the user to access their mailbox? Choose the best option(s) from those listed below.
A: Change the default time to 30 minutes
B: Change the default time to 15 minutes
C: Force synchronization with Windows PowerShell
D: Force synchronization from Office 365 user settings
Explanation: Since DirSync is set to synchronize every three hours, this can cause issues in some situations where you need a new object to be synchronized faster. For these situations, you can manually force synchronization. This is done by logging into the synchronization server, browsing to C:\Program Files\Microsoft Online Directory Sync, and double-clicking on the DirSyncConfigShell.psc1 file. Using PowerShell, type the following cmdlet: Start-OnlineCoexistenceSync and press ‘Enter”.
Correct Option(s): C: Force synchronization with Windows PowerShell
- A: Change the default time to 30 minutes – Although it is possible to change the default sync time, this would not be the best solution as the user would still need to wait 30 minutes.
- B: Change the default time to 15 minutes – Changing the default sync time to less than what it normally takes to complete synchronization is not recommended.
- D: Force synchronization from Office 365 user settings – It is not possible to force synchronization through the Office 365 user settings. To manually force synchronization, Windows PowerShell is required.