In this part of the tutorial about Domino V11 Directory Synchronization, we want to take a closer look at the actions that can be performed on DirSync configuration documents.
To enable a DirSync configuration, select it in the view and click the Enable button.
You will be presented a dialog box where you can select from 2 options.
Select Run in test mode to simulate the actions that Directory Sync would take but without changing any Domino® data. Make any adjustments needed to the Directory Sync configuration. When you are ready to enable synchronization for real, select Synchronize data.
Next, click OK to close the Activate Directory Sync dialog
DirSync will recognise the new configuration on the next scheduled run.
To disable a DirSync configuration, select the document in the view and click the Disable button.
Next, click OK to close the Deactivate Directory Sync dialog
A “Disable” request document will be created.
DirSync will disable the configuration on next scheduled run and also delete the request document.
You also have to disable a Directory Sync configuration before changing it. You will get a warning message if you try to edit an enabled Directory Sync configuration.
You can resync all of the Active Directory data.Resync if you make changes to the Directory Sync Configuration document that affects which data is synced. Resyncing occurs through a Dirsync thread that runs in the background, in parallel with the usual incremental sync.
Next, click OK to close the Resynchronize Selected Directories dialog
A “Resync” request document will be created.
On the server console you will see the following entries when the DirSync task processes the resync request.
[1BE0:0004-1D10] DirSync Updating SyncAll Request's DirSyncRequestState to 1 [1BE0:0004-1D10] 20.01.2020 06:56:19 DIRSYNC From Active Directory (AD) - Summary (0.001 sec, Start=234776, Adds=0, Modifies=0, Deletes=0, Skips=0, Errors=0, End=234775) [1BE0:0005-0284] DirSync Sync all request calling SyncFromLDAPToNAB. [1BE0:0005-0284] DirSync resyncall - SyncFromLDAPToNAB completed in: 0.363 seconds [1BE0:0005-0284] DirSync Updating SyncAll Request's DirSyncRequestState to 2 [1BE0:0005-0284] 20.01.2020 06:56:26 DIRSYNC Full Resync From Active Directory (AD) - Summary (0.363 sec, Start=0, Adds=3, Modifies=0, Deletes=0, Skips=0, Errors=0, End=234775) [1BE0:0004-1D10] DirSync Deleting SyncAll Request [1BE0:0004-1D10] 20.01.2020 06:57:19 DIRSYNC From Active Directory (AD) - Summary (0.001 sec, Start=234776, Adds=0, Modifies=0, Deletes=0, Skips=0, Errors=0, End=234775)
There is a small issue with resync when you accidently flag a disabled DirSync configuration for resync.
After you confirm to resynchronize selected Directories, the configuration will be flagged for resync by setting the item DirSyncReset=”1″.
When you now enable the configuration, you would expect a resync of the selected configuration, right?
But that does not happen. The DirSync task starts as soon as it detects the new configuration, but it does neither perform the requested resync nor it resets the DirSyncReset item value.
Even trying to reinitiate the resync fails. You need to remove the DirSyncReset item value by either using an agent or another tool of your choice.
I have created a case with HCL for this (Case# CS0081445)
Issue with Domino Directory file name
If you see the following error message on the server console
[1BE0:0004-1D10] CSyncFromAD::ProcessEntry could not open customer directory - reason File does not exist
check the Domino Directory file name item value in DirSync configuration. Most likely, the file name is misspelled or the file does not exist on the server. In the BETA version, this resulted in an enabled configuration to be prevented from being disabled. This has been tracked under SPR# MOBNBHUHGD and fixed in Domino V11 GA.