On Fri, Sep 9, 2022 at 10:31 PM Mihai Carabas <mihai.carabas(a)gmail.com>
wrote:
On Wed, Aug 31, 2022 at 8:25 PM Mark Reynolds <mareynol(a)redhat.com> wrote:
> Mihai,
>
> Start with the docs:
>
>
>
https://access.redhat.com/documentation/en-us/red_hat_directory_server/11...
>
> # 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>
> <AGREEMENT NAME>
>
> # 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
nsDS5ReplicaHost: ad-tttt-01.curs.xxx.yy
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="cn=ad.curs.xxx.yy" (ad:636)".
And it connects to the old server (ad:636) [the old was ad.curs.xxx.yy].
From where is getting that ad?
Any input here? A reboot is needed? Dropping changelog?
> HTH,
> Mark
>
> 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 -- 389-users(a)lists.fedoraproject.org
> > To unsubscribe send an email to 389-users-leave(a)lists.fedoraproject.org
> > Fedora Code of Conduct:
>
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> > List Guidelines:
https://fedoraproject.org/wiki/Mailing_list_guidelines
> > List Archives:
>
https://lists.fedoraproject.org/archives/list/389-users@lists.fedoraproje...
> > Do not reply to spam, report it:
>
https://pagure.io/fedora-infrastructure/new_issue
>
> --
> Directory Server Development Team
>
>