Types of Executable Files

FileDescription
normal_mode.batNormal executable script
Specify this file for scheduled executions of Directory Sync via a task scheduler.
recovery_mode.bat

Recovery mode executable script
This file deletes Directory Sync cache information and lock files and then performs synchronization with IIJ ID.
Use this file when Directory Sync does not end normally, which creates inconsistencies in cache information or when a lock file remains. You can also use this file after making changes to the config.yml file.

normal_mode_dry_run.batNormal executable test script
This file does not send a request to IIJ ID Service for differential data and does not update the cache.
You can use this file to check whether Directory Sync will run successfully and whether unexpected users or groups are changed.
recovery_mode_dry_run.bat

Recovery mode executable test script
This file executes a test after deleting Directory Sync cache information and lock files.

You can use this file to check whether Directory Sync will run successfully and whether unexpected users or groups are changed.

normal_mode_output_log.batNormal executable script (debug log output enabled)

Of the logs to be output when running, those logs whose level is higher than the log level set to config.yml are output to the following log files.
* (Directory Sync installation destination)\log\(random value)_normal_mode_stdout.log
* (Directory Sync installation destination)\log\(random value)_normal_mode_stderr.log

recovery_mode_output_log.batRecovery mode executable script (debug log output enabled)

Of the logs to be output when running, those logs whose level is higher than the log level set to config.yml are output to the following log files.
* (Directory Sync installation destination)\log\(random value)_recovery_mode_stdout.log
* (Directory Sync installation destination)\log\(random value)_recovery_mode_stderr.log

[ Note ]

Never execute Directory Sync using a different user than one created for scheduled executions of Directory Sync.

The generation of Directory Sync cache information and lock files using a user without the proper privileges can cause Directory Sync not to run correctly at the next scheduled execution.