similar to: after demoting a dc question

I have been replacing some "old" hardware and have demoted two DC's with 'samba-tool' as per the Samba wiki demotion page. When running Louis' "samba-info.sh" script, that script still finds the presence of the old, now demoted DC hostnames. Further investigation thru RSAT (W10) found the demoted both DC's still listed under the ADUC>Computers (along

I followed the "Demoting_a_Samba_AD_DC" on the Samba Wiki. After demoting the online controller and receiving a "successful" notation I scrolled down to the "Verifying The Demotion" via the listed Windows RSAT. The controller was not listed as a domain controller any more. Only the remaining two DC's appeared. Great! The "Active Directory Sites and

So, for now, should I work my way through the DNS manager and delete any references for the old dc manually or just leave it alone? On Thu, Mar 8, 2018 at 6:16 PM, Andrew Bartlett <abartlet at samba.org> wrote: > On Thu, 2018-03-08 at 17:49 -0600, Robert Wooden via samba wrote: > > Will these DNS listings clear themselves with time or do I have a problem > > here? > >

I Google searched this morning and had found this: " https://superuser.com/questions/1281015/changing-computer-name-on-dns-samba4-ad-server" which discusses a similarity to your suggestion. I was concerned because I cannot tell if the OP is referencing 'internal dns' or 'bind9'. However, what the OP is talking about doing, makes sense. (Could be later today before I

The "DNS_TYPE_NS" records show the correct DC's (both, I have two). The "DNS_TYPE_A" records show the correct DC's ip addresses. The "DNS_TYPE_SOA" shows the demoed DC FQDN in the "mname" > It should produce the SOA record (after you make the obvious changes), > what 'dnsRecord' objects does it show ? There should a

Replaced as instructed and ran the command. It claimed "success", however (RSAT) DNS Manager still shows demoted DC as SOA record. BTW, this demoted DC is now shut off. Suggestions? > Run this on a DC: > > samba-tool dns delete 127.0.0.1 samdom.example.com @ NS fqdn_string -U > Administrator > > Replace: 'samdom.example.com' with your dns domain name. >

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]:

Hello, I had tried to demote a samba DC and re-join it as a member over the weekend, but something went horribly wrong. Starting point was a samba DC which also acted as a file server. It was the single DC in that domain. I first set up a Windows 2008 R2 machine and promoted it to DC within the same domain. I then changed DNS entries on all machines to point to the new DC, transferred the FSMO

I expected to re-provision the domain. (That is easy, now.) Okay, so now the question becomes after the re-provision of the domain on the DC what needs to be changed on the MEMBER server. Obviously, the hostname needs to be corrected and check any needed changes within the smb.conf file. Thoughts? --- ------------------------- Bob Wooden of Donelson Trophy 615.885.2846 (main)

Rowland, I think you have confused my email with a different thread. Uhm . . what? --- ------------------------- Bob Wooden of Donelson Trophy 615.885.2846 (main) www.donelsontrophy.com [1] "Everyone deserves an award!!" On 2015-01-29 07:30, Rowland Penny wrote: > On 29/01/15 12:54, Bob of Donelson Trophy wrote: > Rowland, I have tried your various alteration

I am building a 64bit machine for a DC (CentOS 7) following the instructions on the Samba wiki. Installed Samba 4.3.1.tar.gz and when I try to provision the domain I get: ERROR(ldb): uncaught exception - operations error at ../source4/dsdb/samdb/ldb_modules/password_hash.c:2241 Search the string and it is bug 11573 (assigned to Andrew.) I realize that he will work on it when he gets time

On 05/01/15 14:04, Bob of Donelson Trophy wrote: > > > My shop is 10 minutes from my house. House and shop are connected by vpn > (between two IpFire firewalls.) I do a lot of configuring and testing > from home. Due to a Windows wake-on-lan issue (right now) I cannot wake > the lone DC W7 client from home. When I get to work this morning, W7 > client (thru ADUC) shows

Hi, I have searched here, and noticed some discussion lately on problems demoting a dc. In my case, all roles are on DC2, and DC1 & DC3 know that: root at DC1:/var/log/samba# samba-tool fsmo show InfrastructureMasterRole owner: CN=NTDS Settings,CN=DC2,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=samba,DC=company,DC=com RidAllocationMasterRole owner: CN=NTDS

I have recently added a DC to my AD - Former DC was Samba 4.1.6, new DC is 4.3.11 (latest supported by Ubuntu). There's also a Window 2008 server I had tried to join as an AD - that server, wouldn't completely join and replicate to the 4.1.6 samba AD, and now it will not Un-join the AD "domain" either via dcpromo. This brings me to my actual question - Now that I have

At one point, I thought the same. Tried a "sleep 5" and still got some failures. (That was before I started counting the fails.) This is a P4 3.2Ghz with 1Gb RAM. Could it be that sluggish (at that moment) and need a "sleep 10" or "sleep 15" or more? It worked on my VM (of course it is running on a multi-core Xeon processor so maybe a sleep?) I'm going to try

Thank you, Rowland. Copied your simpler ntp.conf file into my member server. Made the appropriate changes. Restarted all the ntp service on all machines (just in case.) Ran 'ntpq -p' (on member server) and got the correct answer. Proper connection to DC's. --- ------------------------- Bob Wooden of Donelson Trophy 615.885.2846 (main) www.donelsontrophy.com [1] "Everyone

I did a fresh install of Debian with the desktop. I know from Ubuntu that the network is handled differently in the desktop and the server versions. So, I am assuming it is a similar situation with Debian. I could be wrong but . . . When kerberos installs via the script it (the script) suggests accepting the 'defaults on the next three screens.' The first screen included the correct

Thank you. This helps get me closer. One machine shows rsync 3.0.9 and the other shows rsync 3.1.0. Running "rsync --version" both show "ACL, xattr" are supported. Two questions, would the two different version cause it to fail? Second, does the order rsync "receives" the switches matter. Does "-A" and "-X" need to be near the beginning of

Louis, I ran your "1-setup-sernet-samba4-ADDC-wheezy.sh" script and noticed this (during install:) ==========SE Privileges =============================== Enter administrator's password: Could not connect to server 127.0.0.1 Connection failed: NT_STATUS_CONNECTION_REFUSED This is my /etc/resolv.conf: root at dc01:~# cat /etc/resolv.conf search dts***m.dt nameserver

I have manually removed all entries of the demoted DC with the exception of the SOA record. The DNS Manager (offered by RSAT) will not allow adjustment of the SOA record. I have begun searching for a linux solution. Any suggestions would be greatly appreciated. On Thu, Mar 8, 2018 at 7:39 PM, Andrew Bartlett <abartlet at samba.org> wrote: > On Thu, 2018-03-08 at 19:02 -0600, Robert