similar to: Demoting offline DC on 4.3.11-Ubuntu

Hi Mickey, Am 06.04.2017 um 00:50 schrieb Mickey Bankhead via samba: > I thought I would shut down the old 2k8 broken DC and the 4.1.6 DC > servers, and then demote these "offline" servers? BUT The samba.org howto > for demoting offline servers > https://wiki.samba.org/index.php/Demoting_a_Samba_AD_DC > says if you are running older than samba 4.4, then upgrade samba

I inherited an AD "domain" which is running Ubuntu 14.04, with Samba 4.1.6 with "built-in" AD-DNS. The network has only one AD server, which runs on KVM as a guest - (convenient so I can make backups and test stuff without breaking my network. We have around 500 users on the system, and I'm trying to upgrade to 16.04 and a more current version of Samba without making all

Mandi! Denis Cardon via samba In chel di` si favelave... > what version of Samba are you running? Recent versions do a much better job > at DNS cleaning during demote. Eh, domain controllers are still on samba 4.5... > I also advise you to run the demote on another DC than the one you are > demoting (samba-tool doamin demote --remove-other-dead-server=xxxxx). > Running a

Following: https://wiki.samba.org/index.php/Demoting_a_Samba_AD_DC i've demoted and removed a DC. Seems all went as expected: root at vdcud1:~# samba-tool domain demote --server=vdcsv1.ad.fvg.lnf.it -U gaio Using vdcsv1.ad.fvg.lnf.it as partner server for the demotion Password for [LNFFVG\gaio]: Deactivating inbound replication Asking partner server vdcsv1.ad.fvg.lnf.it to synchronize

Hi, I have jointed 2 Samba 4 servers in my domain and transferred FSMO roles to the primary Samba 4 server. I have verified that the Samba 4 servers are OK, but I am having trouble removing the latest DC Windows Server 2008. It reports that there is no other DC to transfer data from the directory DC = DomainDNSZones, DC = Enterprise, DC = com, DC = br However the functions are all on my DC

Hi, I demoted an outdated and offline DC following to: https://wiki.samba.org/index.php/Demoting_a_Samba_AD_DC Everthing appears to work well but there is still one, perhaps minor, question regarding to the dns SOA-record: The zone _msdcs.samdom.example.com still lists the demoted server in the SOA record. Is it ok to manually change it to fsmo holder dc or an other dc? Thanks in advance

I’m looking to replace a DC within a small network by adding a new DC and transferring FMSO roles, then demoting the old DC (https://wiki.samba.org/index.php/Demoting_a_Samba_AD_DC). I am able to successfully deploy the new DC following directions in https://wiki.samba.org/index.php/Joining_a_Samba_DC_to_an_Existing_Active_Directory. However, I am struggling with ID mappings – I’m not really

On 02/10/2019 13:52, L.P.H. van Belle via samba wrote: > samba-tool dbcheck --cross-ncs --fix > Yes, should be possible, but i normaly do that after i do the following. > > search for : > CN=58eba604-07e5-4c5d-a104-9e6f4907248f > And > CN=16b8c008-6c59-4b65-9f1b-530751904a75 > > In _msdc.dom.tld. > Verify which GUID is removed, you can see that, then remove the old

Hello, I am in the process of upgrading one single DC (internal DNS) to 4.8.12. I have followed the procedure of adding a new DC, transfert FSMO roles and demote the old DC. Everything gone right (except at the tranfert FSMO step where I faced the problem described here https://lists.samba.org/archive/samba/2017-August/210140.html , this bug subsists in 4.8.12 , maybe it has been fixed in later

On 26/11/2019 19:44, Stefan G. Weichinger via samba wrote: > Am 26.11.19 um 20:39 schrieb Rowland penny via samba: > >>> I assume I have to start over: demote that DC2 etc >>> >>> Should have left office when I could an hour ago. >>> >> Definitely sounds like you should, you are probably tired and it is >> easy? to make mistakes when you are

Am 26.11.19 um 20:53 schrieb Stefan G. Weichinger via samba: > Am 26.11.19 um 20:50 schrieb Rowland penny via samba: >> On 26/11/2019 19:44, Stefan G. Weichinger via samba wrote: >>> Am 26.11.19 um 20:39 schrieb Rowland penny via samba: >>> >>>>> I assume I have to start over: demote that DC2 etc >>>>> >>>>> Should have left

I'm testing to a seamless upgrade from 4.3.11 to 4.8.3 on my test setup. Database migrating from 4.3.11 was successful. After "samba-tool dbdcheck --cross-ncs --fix --yes", 4.8.3 was launching ok except replication (4.3.11 to 4.8.3 : WERR_BADFILE). After demoting older ones and seize (transfer doesn't work) all roles to 4.8.3, dns (bind_dlz) service won't start anymore

On 05.06.2018 20:39, lingpanda101 wrote: > On 6/5/2018 2:11 PM, Ole Traupe via samba wrote: >> Hi list, >> >> I have a domain in production on two sites (subnets, via "Sites and >> Services") with originally two DCs. One went down due to HDD (-> old >> hardware) error. Now, occasionally, clients cant access/find the file >> server (domain

Hi list, I have a domain in production on two sites (subnets, via "Sites and Services") with originally two DCs. One went down due to HDD (-> old hardware) error. Now, occasionally, clients cant access/find the file server (domain member). This does not occur on all clients at the same time, however, so I am rather sure it is not the file server itself, but a DNS problem. I

Hello, I have two Samba DCs currently on Ubuntu 18.04 LTS with Samba version 4.7 I would like to move to Ubuntu 24.04 LTS with Samba version 4.19. I don't want to do in place upgrade and iterate trough software versions I think there is to many changes. I thought I demote one DC give all FSMO rolls to the other do a clean install with the newer version then rejoin the domain keeping the

Am 13.08.19 um 17:52 schrieb Stefan G. Weichinger via samba: > Am 13.08.19 um 08:20 schrieb Stefan G. Weichinger via samba: >> Am 12.08.19 um 17:07 schrieb L.P.H. van Belle via samba: >>> Hai Stefan, >>> >>> Why make DC2 a member?? >>> Leave it as is, setup a new member, much better, and i'll bet less work/stress. >> >> In fact

In the event demoting a DC caused an issue due to an error (yes, on the user part) could the demoted DC be re-joined to allow correction of the issue? Or should one never rejoin a demoted DC? -- Thank you. Bob Wooden

Hi Rowland - thank you for replying. I have now demoted and removed the temporary DC with the intention of repeating the exercise from scratch later this week. It was a Ubuntu Server 18.04.1 and the smb.conf was very vanilla: [global] workgroup = ACASTA realm = ACASTA.INTRA netbios name = UBUNTU server role = active directory domain controller dns forwarder - 192.168.200.3 idmap_ldb:use rfc2307 =

On 02/10/2019 14:42, Marco Gaiarin via samba wrote: > Mandi! Rowland penny via samba > In chel di` si favelave... > >>> samba-tool dbcheck --cross-ncs --fix >>> Yes, should be possible, but i normaly do that after i do the following. >> Yes, but why wasn't it removed in the first place ? > [...] >>> Run : >>> dig CNAME

Am 12.08.19 um 17:07 schrieb L.P.H. van Belle via samba: > Hai Stefan, > > Why make DC2 a member?? > Leave it as is, setup a new member, much better, and i'll bet less work/stress. In fact it's even DC1 but anyway: because of the hardware. Specific RAID arrays etc needed for backups and snapshots.