search for: replicaton

...bian (I'm using the latest 4.1.x sernet packages). Everything is running perfectly but I've found that I also have to configure sysvol replication (that I didn't), looking at https://wiki.samba.org/index.php/SysVol_Replication I've found this statement: ... for rsync-based SysVol replicaton, you have to choose one DC, on which you do all modifications (GPO edits, logon script changes, etc.) What this exactly means? I have to only connect to the select DC to do antyhing (like creating users, joining computers to the domain, etc)?

Hey guys I have a generic questions about local / domain groups. We have 1 Domain and 20 sites. In each site is a domain controller and a member server. The user have only access to share on the memberserver on their site. Should a share be accessible for a local group or a domain group? (replicaton, traffic, failure safety, security) user -> domain group -> share or user -> domain group -> local group -> share Karl Heinz

...tasks. More details: CPU: mostly only one CPU core from all system-assigned cores is utilized at 100%: BW utilization: you can see example here (peak starts once the Azure AD connector connects to particular DC server) (notice the "uploaded" data - 54GB - value from DC system): Replicaton errors: repeating messages (example above) every each 4-5 seconds. the "last_dn" is changing during time slowly: it is changed to another (user) object each several hours. no other issues observed. - If we deactivate this Azure connector, all issues stopped (but of course we are out...

...is >> utilized at 100%: >> >> >> BW utilization: you can see example here (peak starts once the Azure >> AD connector connects to particular DC server) (notice the "uploaded" >> data - 54GB - value from DC system): >> >> >> >> Replicaton errors: repeating messages (example above) every each 4-5 >> seconds. the "last_dn" is changing during time slowly: it is changed >> to another (user) object each several hours. >> >> no other issues observed. >> >> - If we deactivate this Azure conne...

...yesterday)  4.4.5 => 4.5.3 The only log message and looks ok. log.smbd [2016/12/20 08:00:45.047802,  0] ../source3/smbd/smbd_cleanupd.c:172(smbd_cleanupd_process_exited)   smbd_cleanupd_process_exited: got 0 cleanup events, expected at least 1   Time : 13:15 in the midday. Both database replicatons tested are without errors. samba-tool ldapcmp --filter='whenChanged' ldap://dc1.internal.domain.tld ldap://dc2.internal.domain.tld samba-tool drs showrepl   Time : 13:20 in the midday. After i noticed the log messages i did ran: samba-tool dbcheck --cross-ncs --fix and that fixed...

...CPU core from all system-assigned cores is > utilized at 100%: > > > BW utilization: you can see example here (peak starts once the Azure > AD connector connects to particular DC server) (notice the "uploaded" > data - 54GB - value from DC system): > > > > Replicaton errors: repeating messages (example above) every each 4-5 > seconds. the "last_dn" is changing during time slowly: it is changed > to another (user) object each several hours. > > no other issues observed. > > - If we deactivate this Azure connector, all issues stopped...

Hi folks! I'm having some trouble replicating a domain. I followed the steps in this guide: https://wiki.samba.org/index.php/Samba4/HOWTO/Join_a_domain_as_a_DC I followed the steps and everything worked fine for me. but... If I make changes on the PDC, these changes are replicated to the Secondary DC, but if I make changes to the Secondary, these are not seen in the PDC. Is there any way

...;>> BW utilization: you can see example here (peak starts once the >>>> Azure AD connector connects to particular DC server) (notice the >>>> "uploaded" data - 54GB - value from DC system): >>>> >>>> >>>> >>>> Replicaton errors: repeating messages (example above) every each >>>> 4-5 seconds. the "last_dn" is changing during time slowly: it is >>>> changed to another (user) object each several hours. >>>> >>>> no other issues observed. >>>> >...

...gt;> >>> >>> BW utilization: you can see example here (peak starts once the Azure >>> AD connector connects to particular DC server) (notice the >>> "uploaded" data - 54GB - value from DC system): >>> >>> >>> >>> Replicaton errors: repeating messages (example above) every each 4-5 >>> seconds. the "last_dn" is changing during time slowly: it is changed >>> to another (user) object each several hours. >>> >>> no other issues observed. >>> >>> - If we dea...

...: you can see example here (peak starts once the >>>>> Azure AD connector connects to particular DC server) (notice the >>>>> "uploaded" data - 54GB - value from DC system): >>>>> >>>>> >>>>> >>>>> Replicaton errors: repeating messages (example above) every each >>>>> 4-5 seconds. the "last_dn" is changing during time slowly: it is >>>>> changed to another (user) object each several hours. >>>>> >>>>> no other issues observed. >&...

...ular, there are warnings about invalid parameters from the two respective parameter parsing engines. - Replication of DNS data from one AD server to another may not work. The DNS data used by the internal DNS server and bind9_dlz is stored in an application partition in our directory. The replicaton of this partition is not yet reliable. - Replication may fail on FreeBSD due to getaddrinfo() rejecting names containing _. A workaround will be in the next beta. - upgradeprovision should not be run when upgrading to this release from a recent release. No important database format change...

...ular, there are warnings about invalid parameters from the two respective parameter parsing engines. - Replication of DNS data from one AD server to another may not work. The DNS data used by the internal DNS server and bind9_dlz is stored in an application partition in our directory. The replicaton of this partition is not yet reliable. - Replication may fail on FreeBSD due to getaddrinfo() rejecting names containing _. A workaround will be in the next beta. - upgradeprovision should not be run when upgrading to this release from a recent release. No important database format change...

...ular, there are warnings about invalid parameters from the two respective parameter parsing engines. - Replication of DNS data from one AD server to another may not work. The DNS data used by the internal DNS server and bind9_dlz is stored in an application partition in our directory. The replicaton of this partition is not yet reliable. - Replication may fail on FreeBSD due to getaddrinfo() rejecting names containing _. A workaround will be in the next beta. - upgradeprovision should not be run when upgrading to this release from a recent release. No important database format change...

...re (peak starts once the >>>>>> Azure AD connector connects to particular DC server) (notice the >>>>>> "uploaded" data - 54GB - value from DC system): >>>>>> >>>>>> >>>>>> >>>>>> Replicaton errors: repeating messages (example above) every each >>>>>> 4-5 seconds. the "last_dn" is changing during time slowly: it is >>>>>> changed to another (user) object each several hours. >>>>>> >>>>>> no other issues...