Thank you for your reply.
> *oneWaySync: fromWindows*
> *nsDS5ReplicaUpdateSchedule: 1200-1210 4*
> *WinSyncInterval: 300 (default)*
So what's the meaning of these attributes?
In my mind, if I set oneWaySync: fromWindows, the data flow will be from
Windows to 389DS. no data from 389ds to Windows
Thank you for your reply.
> *oneWaySync: fromWindows*
> *nsDS5ReplicaUpdateSchedule: 1200-1210 4*
> *WinSyncInterval: 300 (default)*
So what's the meaning of these attributes?
In my mind, if I set oneWaySync: fromWindows, the data flow will be from
Windows to 389DS. no data from 389ds to Windows
On 09/04/2019 08:21 AM, DaV wrote:
Hi William,
I set nsslapd-errorlog-level to 8192 and see one line:
[04/Sep/2019:14:15:00.264779375 +0800] - DEBUG - NSMMReplicationPlugin
- windows sync - windows_inc_run - agmt="cn=ou1" (win2k16dc:389):
State: wait_for_window_to_open ->
Hi William,
I set nsslapd-errorlog-level to 8192 and see one line:
[04/Sep/2019:14:15:00.264779375 +0800] - DEBUG - NSMMReplicationPlugin -
windows sync - windows_inc_run - agmt="cn=ou1" (win2k16dc:389): State:
wait_for_window_to_open -> wait_for_window_to_open
So I will check why win2k16 can't
> On 27 Aug 2019, at 11:25, DaV wrote:
>
> OK.
> 1. I have win2016 AD and 389ds 1.3.8.4 on CentOS 7.6
> 2. the data flow is from AD to 389ds, I don't want any data from 389ds to AD
Great, this helps a lot.
> 3. The time interval sync from 389ds to AD controlled by
>
OK.
1. I have win2016 AD and 389ds 1.3.8.4 on CentOS 7.6
2. the data flow is from AD to 389ds, I don't want any data from 389ds to AD
3. The time interval sync from 389ds to AD controlled by
nsDS5ReplicaUpdateSchedule. This is why I set it as 1200-1210 4 (actually I
want to disable it at
> On 27 Aug 2019, at 10:44, DaV wrote:
>
> Thanks for your reply.
> This is my configuration on 389ds server.
> Please tell me if the attribute of "oneWaySync: fromWindows" is correct.
>
> Now, the new users in AD can't be synced to 389ds every 5 minutes, I have to
> click "Initiate full
Thanks for your reply.
This is my configuration on 389ds server.
Please tell me if the attribute of "oneWaySync: fromWindows" is correct.
Now, the new users in AD can't be synced to 389ds every 5 minutes, I have to
click "Initiate full Re-synchronized" manually. I'm stuck for days.
Thanks in
On 8/23/19 5:38 AM, DaV wrote:
Hi all,
For OneWaySync, AD to 389ds.
I have read this guide
https://access.redhat.com/documentation/en-us/red_hat_directory_server/10/html/administration_guide/using_windows_sync-modifying_the_sync_agreement
Synchronization works two ways. The Directory Server
In fact, if I don't set nsds5replicaupdateschedule attribute, the sync from
389ds to AD is always trying.
So I have to set this attribute.
For sync from AD to 389ds, default it's 5 minutes according to 389ds/RHDS
documents, but it happens nothing on my instance, no log. I have to click the
> On 23 Aug 2019, at 19:38, DaV wrote:
>
> Hi all,
> For OneWaySync, AD to 389ds.
>
> I have read this guide
> https://access.redhat.com/documentation/en-us/red_hat_directory_server/10/html/administration_guide/using_windows_sync-modifying_the_sync_agreement
>
>> Synchronization works two
Hi William,
Thanks for your reply.
Sorry for incorrect message yesterday.
My windows sync agreement exactly is:
agreement1:
>> DS Host: 389ds:389
> >> Windows Host: dc01.example.com:389
> >> DS Subtree: ou=Users,dc=example,dc=com
> >> Windows Subtree: ou=ou1,OU=Accounts, DC=example,DC=com
> >>
> On 21 Aug 2019, at 22:10, DaV wrote:
>
> Hi guys,
> Just update for this issue.
>
> Finally, I create multi windows sync agreement for each OU to sync the user
> account.
> like this:
>
>> DS Host: 389ds:389
>> Windows Host: dc01.example.com:389
>> DS Subtree:
Hi guys,
Just update for this issue.
Finally, I create multi windows sync agreement for each OU to sync the user
account.
like this:
> DS Host: 389ds:389
> Windows Host: dc01.example.com:389
> DS Subtree: ou=ou1,ou=Users,dc=example,dc=com
> Windows Subtree: OU=Accounts, DC=example,DC=com
>
14 matches
Mail list logo
