similar to: Samba4 Redundant DCs

Some things to check out for linux-based patch management of Windows (and other) clients: http://vfense.github.io/vFense/ <http://vfense.github.io/vFense/> http://www.opsi.org/en <http://www.opsi.org/en> Thomas Maerz Network/Systems Administrator Brewer Science, Inc. A+ NET+ CCENT MCDST tmaerz at brewerscience.com <mailto:tmaerz at brewerscience.com> work: 573-364-0444 x1402

Hello, Using this tool on a Samba 4.1.16 forest I get the following two errors. DC=ForestDnsZones,DC=domain,DC=local NamingContext 1 Failed Discovery: Property 'msds-sdreferencedomain' does not exist. DC=DomainDnsZones,DC=domain,DC=local NamingContext 1 Failed Discovery: Property 'msds-sdreferencedomain' does not exist. Replication does indeed work as I

I would set up your server as a Samba AD and use the directory. Give each user a username and password on the server that they will authenticate to the server with and when they connect the permissions will act as you are expecting. Joining the machines to the domain is not necessary; it simply integrates the workstation with the server so that the user doesn’t have to enter the credentials

You can join a Windows Server to a Samba4 Domain controller and set up the WSUS server role and it should work. HOWEVER, if you are going to point all your devices at the WSUS server, you will require CALs for the devices or the users using them to maintain licensing compliance with Microsoft. At this point, you have paid for the number of Windows Server CALs you need to run actual Active

2016-05-06 9:39 GMT+02:00 Rowland penny <rpenny at samba.org>: > On 05/05/16 21:46, Thomas Maerz wrote: > >> Hello, >> >> We have an issue we’ve been struggling with for quite some time since we >> rolled out 10 Samba4 domain controllers at our main office and all remote >> sites about 3 years ago. >> >> Simplified Current Configuration:

> Clients are not being pointed correctly, clients joined to the domain should be pointed at the DCs first, anything they do not know, they ask their forwarders. Although I agree that what you’re suggesting is a sane configuration, there are other ways to do it and I have tried it both ways. As I’ve explained in my first post, curgently all clients are pointed at BIND servers which forward all

On 01/04/16 03:09, Thomas Maerz wrote: > I know this is old, but I wanted to add one more detail: Samba v3 is > deprecated as of March 2015 with the release of Samba 4.2! From the > Samba 4.2 release notes: > https://wiki.samba.org/index.php/Samba_4.2_Features_added/changed > > "IMPORTANT NOTE ABOUT THE SUPPORT END OF SAMBA 3 > With the final release of Samba 4.2, the

I know this is old, but I wanted to add one more detail: Samba v3 is deprecated as of March 2015 with the release of Samba 4.2! From the Samba 4.2 release notes: https://wiki.samba.org/index.php/Samba_4.2_Features_added/changed <https://wiki.samba.org/index.php/Samba_4.2_Features_added/changed> "IMPORTANT NOTE ABOUT THE SUPPORT END OF SAMBA 3 With the final release of Samba 4.2, the

Hello, I can’t get a fully patched Server 2008 R2 DC to finish DCPROMO joining as a domain controller to my Samba4 AD domain. dcpromo.exe begins replication but gets stuck on “Replicating data CN=Configuration,DC=samdom,DC=contoso,DC=com: Received 1999 off of approximately 1999 objects and 74 out of approximately 74 distinguished name (DN) values… Examining the dcpromo.log file just shows

This is actually a similar scenario to mine, I neglected to mention that before this happened, I had joined a Server 2008 R2 to the domain and promoted it to FSMO, then moved FSMO back to S4 DC and demoted the Server 2008 R2 controller. I did what you suggested and it worked! I am assuming this is a bug. Thank you for your suggestion. Thomas Maerz > On Nov 9, 2016, at 3:59 AM, Kelvin Yip via

I know this is an old ‘thread’ but if you want to use the Microsoft AD Replication Status Tool, you need to add the DN of your domain to those two cross reference entries because Samba4 does not do that for some reason. Here’s a link on how to do it with RSAT: https://www.safaribooksonline.com/library/view/active-directory-cookbook/0596004648/ch17s09.html

Hello, I am currently working on a solution to replace Apple OpenDirectory on some aging Xserve hardware. I currently have CentOS Samba4 AD DC?s replicating for redundancy using sernet-samba repositories. The third one has File/Print roles defind and it works perfectly EXCEPT on OSX 10.6. IT works great on any Windows workstation and OSX 10.7,10.8, 10.9 GNOME/Nautilus and even CIFS CLI mounting

Hello, We have an issue we’ve been struggling with for quite some time since we rolled out 10 Samba4 domain controllers at our main office and all remote sites about 3 years ago. Simplified Current Configuration: 2 DCs at main site with internal DNS using subdomain ad.companyname.com 2 BIND CentOS servers serving all intranet DNS requests — main zone: companyname.com 2 BIND CentOS servers

Hello, As far as I know, there is no Wiki article for transferring FSMO Roles to Server 2008 R2 DC. This article’s focus is on joining a Server 2012 DC to a Samba4 domain, but it touches on the subject: https://wiki.samba.org/index.php/Joining_a_Windows_Server_2012_/_2012_R2_DC_to_a_Samba_AD <https://wiki.samba.org/index.php/Joining_a_Windows_Server_2012_/_2012_R2_DC_to_a_Samba_AD> I would

Hello, I am using 4.5.1, the first time I promote a Windows 2008 R2 as a domain controller, everything is fine. After that, I demote 1 Windows 2008 R2 and 1 Samba DC(4.5.1). Then I promote a Windows 2008 R2 DC again, I get the exact problem as yours. I cancel the process. Then I ran to DC with all FSMO roles, and type the following command several times: samba-tool dbcheck --cross-ncs --fix --yes

Another old thread I’m resurrecting; apologies, but I have also been experiencing this issue. I have 10 international remote sites over very lossy WAN links. Getting traffic to them from HQ is a challenge; them trying to talk directly each other over umpteen paths is even worse. They are able to accomplish this (somewhat) because we have a mesh VPN setup with direct site-to-site connectivity, but

I have a domain with multiple Samba DC, and one MS Server 2008 R2 DC. The Samba servers came first and then I added the MS DC. I am having problems replicating, it gives me a schema mismatch error. If I run ldapcmp ./samba-tool ldapcmp ldap://DC1 ldap://DC2 -Uadministrator schema --filter=whenChanged Password for [MYDOMAIN\administrator]: * Comparing [SCHEMA] context... * Objects to be

On 05/05/16 21:46, Thomas Maerz wrote: > Hello, > > We have an issue we’ve been struggling with for quite some time since we rolled out 10 Samba4 domain controllers at our main office and all remote sites about 3 years ago. > > Simplified Current Configuration: > > 2 DCs at main site with internal DNS using subdomain ad.companyname.com > 2 BIND CentOS servers serving all

Hello! It is possible to have a WSUS with Samba 4? Thanks

On 06/05/16 13:01, mathias dufresne wrote: > 2016-05-06 9:39 GMT+02:00 Rowland penny <rpenny at samba.org>: > >> On 05/05/16 21:46, Thomas Maerz wrote: >> >>> Hello, >>> >>> We have an issue we’ve been struggling with for quite some time since we >>> rolled out 10 Samba4 domain controllers at our main office and all remote >>>