similar to: Error removing Windows DC from AD

Hi, On 20/06/2018 20:38, Andrew Bartlett wrote: > To be clear, we don't replicate sysvol, you need to work that out > yourself (yes, this sucks). > Right, I'm doing that with Robocopy from the Windows DC initially, then with rsync. >> Is there any further preparation I need to do on the Windows server side >> to make a clean demotion possible? I can force the

Hi Pietro, I noticed this problem removing a Windows DC the other day. I've sent a patch to the samba-technical mailing list that should fix this. https://lists.samba.org/archive/samba-technical/2018-June/128703.html I also raised a bug for it: https://bugzilla.samba.org/show_bug.cgi?id=13484 The patch should hopefully be delivered soon. If you feel comfortable patching the Samba code

Hi, I'm trying to remove a DC from a site we have shutdown. The demote command is throwing up this message: [root at aragorn ~]# samba-tool domain demote --remove-other-dead-server=pippin Removing nTDSConnection: CN=eca08dbb-1f34-476e-96dd-33ec22b2bc94,CN=NTDS Settings,CN=GANDALF,CN=Servers,CN=SAOPAULO,CN=Sites,CN=Configuration,DC=e-trust,DC=com,DC=br Removing nTDSDSA: CN=NTDS

Hi all, We were trying the new --remove-other-dead-server coming with the 4.4.0rc. The domain is a brand new one with several DC added and two Windows clients, no user yet. Here is the smb.conf: [global] workgroup = SAMBA realm = SAMBADOMAIN.TLD netbios name = DC200 server role = active directory domain controller server services = -dns

Hi: I want to test migrating windows dc to samba dc (without considering sysvol replication). I installed brand new 2003R2, 2008R2, 2012R2 (with 2008R2 functional level). I compiled samba 4.7.7, 4.8.1 at centos 7.4. 1. I tried to join samba as DC to windows with command: samba-tool domain join samdom.example.com DC -U"SAMDOM\administrator"

Hi folks, Yet another upgrade question! Reading the mailing list regarding upgrades in the past few months has made me a little apprehensive. After now running a single Samba DC for a few months and excising the last remnants of the old Windows DC, I would like to join another Samba DC to the existing one. Current one (DC2) is running Samba 4.5 on Debian Stretch. samba-tool dbcheck looks clean

Hi folks, Does anybody have experience using ADCS in conjunction with Samba? I would like to create certificates using ADCS as a CA to create certificates to be deployed to servers running web applications. It would be very convenient to have joined Windows computers automatically trust certificates issued my own CA instead of having to import certificates manually on every browser on every

On Thu, 5 Oct 2017 14:14:56 -0500 (CDT) Mike Ray via samba <samba at lists.samba.org> wrote: > Recently tried transferring roles from Samba 4.3.11 to Samba 4.7.0. > Ultimately, both dcs agreed that the 4.7.0 dc (dc3) had all the roles > and replication and the databases were in good shape. However, during > the process, I got a lot of errors that seemed to magically >

Thanks Rowland. Have submitted a bug report (No 11818). spindles7 On Thu, 31 Mar 2016 09:38:02 +0100, Rowland penny <rpenny at samba.org> wrote: >On 30/03/16 23:26, spindles7 wrote: >> Hi all, >> I am consistently getting the error: >> >> root at dc2:~# samba-tool domain demote -Uadministrator >> Using dc1.microlynx.com as partner server for the demotion

Recently tried transferring roles from Samba 4.3.11 to Samba 4.7.0. Ultimately, both dcs agreed that the 4.7.0 dc (dc3) had all the roles and replication and the databases were in good shape. However, during the process, I got a lot of errors that seemed to magically disappear. Should I be worried? root at dc3:~# samba-tool fsmo show SchemaMasterRole owner: CN=NTDS

Could you run : samba-tool ldapcmp ldap://dc3 ldap://dc4 --filter=cn,CN,dc,DC And compair that output? Greetz, Louis > -----Oorspronkelijk bericht----- > Van: samba [mailto:samba-bounces at lists.samba.org] Namens > Elias Pereira via samba > Verzonden: dinsdag 7 mei 2019 15:48 > Aan: samba > Onderwerp: [Samba] DN lists have different size: 4065 != 4029 > >

Hello guys, Why did you upgrade the schema to '69' ? > > That is the schema from 2012R2 and is still marked as experimental. I do not know why I did this update. Maybe I thought I could use DC as 2012R2. <sad> Could you run : > samba-tool ldapcmp ldap://dc3 ldap://dc4 --filter=cn,CN,dc,DC > And compair that output? I made the comparison. It has a jumble of

Hello, dc3: http://pasted.co/6b703479 dc4: http://pasted.co/5068fc6e diff: http://pasted.co/025c3242 On Tue, May 7, 2019 at 12:08 PM L.P.H. van Belle via samba < samba at lists.samba.org> wrote: > Hai, > > Now, differences is fine, but can you see if one of the 2 servers is > correct, and for that it might be handy to share the output. > > You can push the good DB to the

im on phone, had a quick small look at the dc3 output. is your time in sync, it looks like a 3 - 10 min different. gr. Louis Op 7 mei 2019, om 18:34, Elias Pereira <empbilly at gmail.com> schreef: Hello, dc3: http://pasted.co/6b703479 dc4: http://pasted.co/5068fc6e diff: http://pasted.co/025c3242 On Tue, May 7, 2019 at 12:08 PM L.P.H. van Belle via samba <samba at

Hai,   Now, differences is fine, but can you see if one of the 2 servers is correct, and for that it might be handy to share the output.   You can push the good DB to the other DC. ( a forced replication )   And i can understand why you upgrade ...  Did you see :    samba-tool domain schemaupgrade --help Usage: samba-tool domain schemaupgrade [options] Domain schema upgrading Options:   -h,

Hello, dc3 = principal DC dc4 = secondary DC I had this problem last month after updating samba to version 4.10.x. and also the schema from 45 to 69. But it looked like it had been corrected. Today I noticed that on dc4 there are computers that are not on dc3. I updated: 4.7.x to 4.8.x 4.8.x to 4.9.x and only after that I upgrade to 4.10.x version. When I run these commands: samba-tool

Hi Rowland, Have tried your patch, and now the Demote succeeds: root at dc3:~# samba-tool domain demote -Uadministrator Using dc1.microlynx.com as partner server for the demotion Password for [MICROLYNX\administrator]: Deactivating inbound replication Asking partner server dc1.microlynx.com to synchronize from us Changing userControl and container Removing Sysvol reference:

hi, Some time ago I transferred the roles from DC3 to DC1. After transferring and checking with the 'samba-tool fsmo show' command, all the roles were transferred. root at dc1:~# samba-tool fsmo show SchemaMasterRole owner: CN=NTDS Settings,CN=DC1,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=campus,DC=sertao,DC=ifrs,DC=edu,DC=br InfrastructureMasterRole owner:

Hello all- I am trying to upgrade a old domain to a newer version. The old DCs are a custom compiled version of Samba, so instead of upgrading the DCs in place, the plan is to upgrade by joining new DCs to the domain, replicating data and then shutting down the old ones after transferring the FSMO roles. I had the new DC (dc3, version 4.9.4-12) replicating to the other DCs (dc0, versions

----- On Mar 1, 2019, at 3:35 AM, samba samba at lists.samba.org wrote: > > I wonder if this has anything to do with the 'you cannot upgrade > directly from 4.7.x to 4.9.x' bug ? I was not aware of this bug. Do you think I should scrap this upgrade and try again jumping like so? 4.0.6-12 -> 4.7 -> 4.8 -> 4.9 > I know this might seem strange, but try running