Skip to content

How to force DirSync to perform full synchronization #1

April 29, 2013

This post relates to an older version of DirSync and is no longer valid. It has been updated and replaced by the newer post How to force DirSync to perform full synchronization #2. This obsolete post will remain on this site for reference.

DirSync only performs a full import automatically when run for the very first time. After that it always defaults to a delta synchronization.

There will be times when you need to force a full import. This is usually indicated by event ID 6126 in the Application log of your DirSync server:

Log Name:      Application
Source:        FIMSynchronizationService
Event ID:      6126
Task Category: Management Agent Run Profile
Level:         Warning
The management agent "TargetWebService" completed run profile "Delta Confirming Import" with a delta import or delta synchronization step type. The rules configuration has changed since the last full import or full synchronization.
User Action
To ensure the updated rules are applied to all objects, a run with step type of full import and full synchronization should be completed.

You typically need to force a full import after making changes to Synchronization Service Manager (miisclient.exe) on your DirSync server. This includes modifying any synchronization filters (such as User or OU filters).

The only way to force a full import is by editing the registry on your DirSync server:

  1. Open regedit on your DirSync server
  2. Navigate to HKEY_LOCALMACHINE\Software\Microsoft\MSOLCoExistence
  3. Edit the dword entry FullSyncNeeded. Change the value from 0 to 1.


  4. Force directory synchronization:
  5. powershell.exe -psconsolefile "C:\Program Files\Microsoft Online Directory Sync\DirSyncConfigShell.psc1" -command "& {Start-OnlineCoexistenceSync}"

The FullSyncNeeded registry value will automatically reset to 0 once synchronization has completed

You may experience problems with Remote Move Requests for new mailboxes until a full sync is performed. For example:

The operation couldn't be performed because object '24638dc4-fe2a-492e-b531-5fd45e0d4a07' couldn't be found on ''.


  1. Paul permalink

    The DirSync directory folder changed to C:\Program Files\Windows Azure Active Directory Sync\

Trackbacks & Pingbacks

  1. Office 365 DirSync experiences: synced OUs and user deletion | gshaw0

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: