Displaying 20 results from an estimated 5000 matches similar to: "How to cleanly remove a DC from Samba domain?"
2023 May 29
1
How to cleanly remove a DC from Samba domain?
I connected to LDAP via Apache Directory Studio and it seems that the child node under the computer account is an RID set:
????????CN=RID Set,CN=DC2,CN=Computers,DC=ad,DC=home,DC=lan
Is this an omission of the demotion process? Should this havfe been removed? Is it safe for me to delete this and try the "sambal-tool computer delete DC2" again?
2023 May 29
1
How to cleanly remove a DC from Samba domain?
On 29/05/2023 11:12, Alexandros Karypidis via samba wrote:
> I connected to LDAP via Apache Directory Studio and it seems that the child node under the computer account is an RID set:
>
> ????????CN=RID Set,CN=DC2,CN=Computers,DC=ad,DC=home,DC=lan
>
> Is this an omission of the demotion process? Should this havfe been removed? Is it safe for me to delete this and try the
2016 Apr 01
0
Demote a working DC fails with uncaught exception
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:
2023 May 29
1
How to cleanly remove a DC from Samba domain?
I used Apache Directory Studio to remove the "RID Set" node and after that a simple "samba-tool computer delete DC2" worked just fine.
Perhaps the version of Samba in TurnKey Linux V16.1 has a bug (4.9.5-Debian)? Likely demotion should remove leaf nodes from domain controllers as part of the process.
I have now recreated DC2 using TurnKey Linux V17.1 (4.17.6-Debian) and so
2016 Apr 02
1
Demote a working DC fails with uncaught exception
On 01/04/16 22:38, spindles7 wrote:
> 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
>
2018 Jun 22
2
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
2018 Jun 26
0
Error removing Windows DC from AD
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
2018 Jun 20
2
Error removing Windows DC from AD
Hi,
I'm preparing to move a small business environment away from
Windows-based AD (Windows Server 2012R2, Domain and Forest downgraded to
Win2008R2 level) to Samba. So far in my lab environment joining Samba as
a DC works, including DNS and Sysvol replication.
OS: Debian 9
Samba versions 4.5.12 (Debian repository) and 4.8.2 (latest release
compiled from source), same behavior on both
2016 Mar 31
2
Demote a working DC fails with uncaught exception
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
2015 Mar 09
2
ad dc demotion fails trying to use non-existent dc as 'partner server for the4 demontion'
I'm trying to demote dc3 from msad dc service.
As the root user, I type this command:
samba-tool domain demote -Uadministrator
which fails with this error:
"Using dc2.infinity.local as partner server for the demotion"
The problem is that dc2 was demoted some weeks ago, and is no longer running samba4.
Is there a way I can force dc3 to use a different dc as the
2015 May 10
0
bind fails to start w/missing records
On 10/05/15 15:34, Steve Thompson wrote:
> On Sun, 10 May 2015, Rowland Penny wrote:
>
>> Have you really got 19 reverse zones for your samba 4 active directory ?
>
> Yep :-)
Why ? And why don't they show up when you ask for the zones with
samba-tool ?
>
>> Can you try running 'samba-tool ldapcmp ldap://<YOUR_FIRST_DC>
>>
2015 Feb 25
2
replication problems in samba4 ad domain
I started with one dc, 'dc1', running samba v4.0.21, in subnet1.
I successfully added two more dc's, 'dc2' and 'dc3', both running samba v4.0.24, both in subnet2.
There are several firewalls between subnets 1 & 2.
I continued to make firewall holes on behalf of msad after I added dc's 2 & 3. I.e. when they were added, there were patterns of communication
2016 Mar 30
2
Demote a working DC fails with uncaught exception
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
Password for [MICROLYNX\administrator]:
Deactivating inbound replication
Asking partner server dc1.microlynx.com to synchronize from us
Changing userControl and container
ERROR(<type 'exceptions.TypeError'>): uncaught
2015 May 10
4
bind fails to start w/missing records
On Sun, 10 May 2015, Rowland Penny wrote:
> Have you really got 19 reverse zones for your samba 4 active directory ?
Yep :-)
> Can you try running 'samba-tool ldapcmp ldap://<YOUR_FIRST_DC> ldap://<YOUR_SECOND_DC>
Interesting. DC1 and DC2 have many differences; DC1 and DC3 are the same.
Maybe I will demote DC2 and join it again.
> Check if you actually have dns
2018 May 25
5
Demoting troublesome DC
Hello,
I am running in a duplicate test environment of my work domain.
I have 2 x 4.1 DCs and 2 x 4.7 DCs.
I have transferred FSMO role to #3 and it is replicating to #4 fine.
I have demoted #1 which appeared to go fine and have turned it off.
When I try to demote #2 it fails with the error...
Using dc3.domain.com as partner server for the demotion
Password for [DOMAIN\administrator]:
2023 Apr 03
1
WARNING: no target object found for GUID component link lastKnownParent in deleted object
hi,
I have this DC in aws to fulfill the authentication need of our moodle.
# samba -V
Version 4.17.7-Debian
DNS with SAMBA_INTERNAL
The replication of the users and groups happens correctly. Some errors in
running samba_dnsupdate, but it is ok anyway.
When I ran the command samba-tool dbcheck, I got the return below.
# samba-tool dbcheck --cross-ncs --reset-well-known-acls --fix --yes
2016 Mar 31
0
Demote a working DC fails with uncaught exception
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
> Password for [MICROLYNX\administrator]:
> Deactivating inbound replication
> Asking partner server dc1.microlynx.com to synchronize from us
> Changing userControl
2018 May 25
0
Demoting troublesome DC
Set on the newest DCs the following.
ldap server require strong auth = no
Should help but its adviced to remove it when your done.
Greetz,
Louis
> -----Oorspronkelijk bericht-----
> Van: samba [mailto:samba-bounces at lists.samba.org] Namens Paul
> Littlefield via samba
> Verzonden: vrijdag 25 mei 2018 16:46
> Aan: samba at lists.samba.org
> Onderwerp: [Samba]
2018 May 25
0
Demoting troublesome DC
On Fri, 25 May 2018 14:46:21 +0000
Paul Littlefield via samba <samba at lists.samba.org> wrote:
> Hello,
>
> I am running in a duplicate test environment of my work domain.
>
> I have 2 x 4.1 DCs and 2 x 4.7 DCs.
>
> I have transferred FSMO role to #3 and it is replicating to #4 fine.
>
> I have demoted #1 which appeared to go fine and have turned it off.
>
2023 Apr 04
1
WARNING: no target object found for GUID component link lastKnownParent in deleted object
While this should work, neither is this particularly harmful. ?Links to
objects that don't exist are ignored at runtime.
Andrew Bartlett
On Tue, 2023-04-04 at 14:39 -0300, Elias Pereira via samba wrote:
> hi,
>
> Any clue?
>
> On Mon, Apr 3, 2023 at 10:17?AM Elias Pereira <empbilly at gmail.com> wrote:
>
> > hi,
> >
> > I have this DC in aws to