similar to: best practice for migrating win-dc to samba-dc

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, 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 I have a DC server (named dc-server1) with corrupted database. I transferred all FSMO to dc-server2 and now I'm trying to demote dc-server1 running "samba-tool domain demote --verbose --remove-other-dead-server=dc-server1" on dc-server2, but the following error occurred. The problem continues even after running "samba-tool dbcheck --cross-ncs --fix --yes". Samba

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'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

I’m having issues removing an old dead DC. I’m using the tool as follows: sudo samba-tool domain demote --remove-other-dead-server=OLD-SERVER-NAME I’m receiving the following error when it comes to deleting the machine: ERROR(ldb): uncaught exception - subtree_delete: Unable to delete a non-leaf node (it has 4 children)! File

Hi, I have a samba 4.7.9 DC that I am trying to remove a windows SBS dc from. In doing this I have run across several problems. For whatever reason when I try to dcpromo the windows DC it fails because it says it cannot contact the samba4 DC. I have checked replication as per https://wiki.samba.org/index.php/Verifying_the_Directory_Replication_Statuses All of the tests pass. Since we are going

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

On 30/04/16 20:31, Andrew Bartlett wrote: > On Sat, 2016-04-30 at 16:35 +0100, Miguel Medalha wrote: >>> In any case, I found and fixed the issue you hit last week, the >>> patch is at https://bugzilla.samba.org/show_bug.cgi?id=11882 The >>> syntax error should then go away (bug I have a patch for that as >>> well, it is on samba-technical if you are

> In any case, I found and fixed the issue you hit last week, the patch > is at https://bugzilla.samba.org/show_bug.cgi?id=11882 The syntax > error should then go away (bug I have a patch for that as well, it is > on samba-technical if you are curious). I found this on a post by Rowland penny (https://lists.samba.org/archive/samba/2016-March/198662.html): HI, it would seem you

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

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:

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

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

I want to replace a Windows 2003R2 DC by a Samba4 install. I installed Samba 4.0.10 and successfully joined the Windows domain. (after applying a small patch to join.py) The replication works fine, and the new DC now hosts all fileshares and successfully authenticates users and computers. Transfer of fsmo roles was also successful. The old Windows DC is still active. I want to decommission

====================================================== "The first wealth is health." Ralph Waldo Emerson ====================================================== Release Announcements --------------------- This is the latest stable release of Samba 4.4. Changes since 4.4.5: -------------------- o Michael Adam <obnox at samba.org> * BUG 11977: libnet: Ignore realm

====================================================== "The first wealth is health." Ralph Waldo Emerson ====================================================== Release Announcements --------------------- This is the latest stable release of Samba 4.4. Changes since 4.4.5: -------------------- o Michael Adam <obnox at samba.org> * BUG 11977: libnet: Ignore realm

Showing the group of a folder/file in a mounted samba share under XP(SP2)/2003R2-Server need some seconds. Only the SID of the group and the owner is shown initaly This problem occurs not on a mounted share from a Windows-Server. 'getent group' on the Samba machine (via nss-ldap from 2003-AD) works perfect. I've no idea, where should I search. Can anybody please help? Thanks.

We have been directed to move off a SAMBA domain to a server 2003R2 domain. We run roaming profiles with samba and would like to continue this on 2003R2. After bringing all the XPSP3 desktops into the 2003R2 domain, roaming profiles wont work. I'm not even trying to use the SAMBA generated profiles. The error I get when logging on is: *Windows cannot locate the server copy of your

Here's the configuration: OS: Solaris 10 11/08 OS Authentication: Sun Directory Server 5.x Samba: v3.0.32 included with Solaris 10 11/08 Samba auth: Windows 2003R2 AD Using a Windows XP client authenticated against AD mounting of home directories works fine and I'm able to perform create/modify/delete ops on files/directories in the home directory and files/directories which are