search for: replicatons

Hi, I've created an Active Directory domain with 2 samba 4 running in debian (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

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

hello our AD domain is hosted by two samba AD domain controllers version 4.12.6 - replication between controllers is fine, no problems. - no schema errors. - no database errors, all fine. - no CPU utilizations - wthout noticeable bandwidth utilization Recently we have deployed Azure AD connector on dedicated windows system (system is domain member server). since this deployment we are observing

Hi Michal, Seems we are doing similar things at the moment: getting samba to work with azure AD. We also see the high CPU usage on the DC that the Azure AD Connect server connected to. Between 70 - 100 percent in our case. We are not seeing any replication issues after azure AD Connect, and I have a script that automatically checks replication every few minutes. I was the one reporting the

...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 9...

ups, seems pictures (attachments in general) are not accepted here, screen (graph) is available here: https://i.postimg.cc/xCk6k038/image-2020-10-21-190940.png On 10/21/2020 6:00 PM, Michal Bruncko wrote: > hello > > our AD domain is hosted by two samba AD domain controllers version 4.12.6 > - replication between controllers is fine, no problems. > - no schema errors. > - no

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

just small update: - idfix tool (Directory Synchronization Error Remediation Tool / https://github.com/microsoft/idfix) shows just small issues like empty/missing displayName attrib in some of objects which I have corrected and no more issues present at all. - no errors from AAD connect event viewer: final log message is "Scheduler::SchedulerThreadMain : Completed configured scheduler

hello mj we are school - we are syncing approx 500 users and several groups. we use pass-through authentication because AAD authentication was not working (that time we used samba 4.8.12, but since moving to 4.12 I didnt tested this), we have (as recommended) one AAD connector plus two authentication agents deployed in our environment. the thing what I dont understand is the amount of data

hello all just to summarize this topic for anybody else. after some time spent with tshooting there seems is a sufficient workaround for this issue: disable "sync of password hashes" option within Azure AD connect tool. with disabling this option all three issues (CPU/Bandwidth utilization/replication logs) are gone! seems that for now the only working option for samba and Azure

We are proud to a announce our first beta release of Samba 4.0, beta 1 What's new in Samba 4 beta1 ============================= Samba 4.0 will be the next version of the Samba suite and incorporates all the technology found in both the Samba4 alpha series and the stable 3.x series. The primary additional features over Samba 3.6 are support for the Active Directory logon protocols used by

We are proud to a announce another beta release of Samba 4.0, beta 2 What's new in Samba 4 beta2 ============================= Samba 4.0 will be the next version of the Samba suite and incorporates all the technology found in both the Samba4 alpha series and the stable 3.x series. The primary additional features over Samba 3.6 are support for the Active Directory logon protocols used by

We are proud to a announce another beta release of Samba 4.0, beta3 What's new in Samba 4.0 beta3 ============================= Samba 4.0 will be the next version of the Samba suite and incorporates all the technology found in both the Samba4 alpha series and the stable 3.x series. The primary additional features over Samba 3.6 are support for the Active Directory logon protocols used by

Hi Michal, Thanks for updating, I can confirm your findings on our site. Pass-through auth works nicely here as well. However, when reading the ticket, we understand that Ralph B?hme claims that password-hashes should also work, after making the sync account MSOL_604447e... a member of "domain admins". (instead of keeping the default rights that are granted by the installer, which