Monday, September 12, 2022

[389-users] Re: Procedure to change the AD used to sync users

On Fri, Sep 9, 2022 at 10:31 PM Mihai Carabas <> wrote:

On Wed, Aug 31, 2022 at 8:25 PM Mark Reynolds <> wrote:

Start with the docs:

# dsconf slapd-INSTANCE repl-winsync-agmt list

# dsconf slapd-INSTANCE repl-winsync-agmt set --help

# dsconf slapd-INSTANCE repl-winsync-agmt set --host=<NEW HOSTNAME>

# dsconf slapd-INSTANCE repl-winsync-agmt init <AGREEMENT NAME>

I did this:

[root@ldap ~]# dsconf slapd-ldap repl-winsync-agmt list --suffix "dc=curs,dc=xxx,dc=yy" | grep Host
But in the logs:

[09/Sep/2022:22:23:43.366356845 +0300] - INFO - NSMMReplicationPlugin - windows sync - windows_tot_run - Beginning total update of replica "agmt="" (ad:636)".

And it connects to the old server (ad:636) [the old was]. From where is getting that ad?

Any input here? A reboot is needed? Dropping changelog?



On 8/31/22 4:22 AM, Mihai Carabas wrote:
> Hello,
> We are planning to decommision our current PDC AD (Windows 2012R2).
> This AD is also used to sync users from our 389ds instance to this AD.
> What would be the correct procedure to update the WinSync agreement?
> Just update the hostname and run a full sync?
> Thank you,
> Mihai Carabas
> _______________________________________________
> 389-users mailing list --
> To unsubscribe send an email to
> Fedora Code of Conduct:
> List Guidelines:
> List Archives:
> Do not reply to spam, report it:

Directory Server Development Team

No comments:

Post a Comment