Bug description: If an invalid value is set to ds5BeginReplicaRefresh
in an agreement, it does not affect the behaviour, but it does not get
purged from the agreement and causes an error if "ds5BeginReplicaRefresh:
start" is added.
Fix description: Adding an invalid ds5BeginReplicaRefresh is rejected
with "DSA is unwilling to perform" and the following error is returned:
ldap_modify: additional info: Invalid value (junk_value123) value
supplied for attr (nsds5BeginReplicaRefresh); Ignoring ...
Bug description: Some account names (e.g. "service") is reserved
in Active Directory. If DS has an entry having such an NT user ID
and the entry is synchronized to the AD, it fails with LDAP_ALREADY_
EXISTS, but the error is gracefully ignored. In the total update,
updating Account Control bit follows the failed add, which fails
since the AD entry WinSync expects does not exist and it aborts
the total update.
Fix description: If adding a DS entry to AD fails and the updating
Account Control bit also fails, the following note is logged in
the error log and the total update continues:
windows_process_total_add: Creating AD entry "cn=service service,
cn=Users,dc=EXAMPLE,dc=COM" from DS entry "uid=service,ou=People,
dc=example,dc=com" failed. AD reserves the account name. Ignoring
In addition, in windows_parse_config_entry, if the attribute values
in the agreement is retrieved before the agreement is started, the
following error is logged, which is not necessary. This patch
stops logging it if the agreement does not set "protocol" yet.
Replication agreement for agmt="cn=WinSync" could not be updated.
For replication to take place, please enable the suffix and restart