similar to: DC Upgrade Compiled to Package

Marc- Thanks for the advice. In regards to the FSMO roles, when we were originally testing, we found that in our version, FSMO roles could not be transferred (or even seized). Would you recommend adding the new versioned DC to the existing domain and attempting a seize on the new version once the old FSMO owner is offline? What about stopping samba on the old FSMO owner and copying the TDB

Hi Mike, Am 24.03.2017 um 17:19 schrieb Mike Ray via samba: > I've seen this page: https://wiki.samba.org/index.php/Updating_Samba and > intend on reading the release notes as instructed, but was > wondering if anyone had any additional things to look out > for, especially related to going from a source installed version > to a package installed version. The major important

We're upgrading (Sernet) Samba 4.2 to 4.4. As recommended on this page: https://wiki.samba.org/index.php/Updating_Samba, I have upgraded one of out 2 DCs, the one that does not have any FSMO roles. We will spend the next week making sure everything works as expected. So far, so good. One thing I'm not clear on is whether I should move the FSMO roles to the upgraded DC before upgrading

> Am 31.12.2017 um 17:32 schrieb Rowland Penny via samba <samba at lists.samba.org>: > > On Sun, 31 Dec 2017 16:18:27 +0100 > Götz Reinicke via samba <samba at lists.samba.org> wrote: > >> Hi, >> >> we have three 4.6.x AD servers in a cluster > > What do you mean by 'a cluster' ? > > If you mean an actual cluster, how are you

With some slight delay, we did actually manage to get all our old wonky compatibility solutions nuked (turned out there were a few more lurking in the shadows than expected?). Mail servers are no longer domain joined, and unencrypted LDAP is finally gone, together with the terrible PHP scripts that needed it. Which allowed me to finally cleanup all the samba setups:

Hi all, I currently have 5 DC's all running 4.1.5 and would like to upgrade them to 4.1.11. Should I upgrade the FSMO DC first and then the others or perhaps the other way around? Can anyone see any pitfalls here? Also, should I just: 1. stop samba 2. ./conffigure && make && make install 3. restart samba ? I am also planning on switching to BIND_DLZ (currently running

Hello all, Our Samba AD DC is running perfectly for years with the following basic setup (see smb.conf below) : - one DC running Samba 4.1.7 / CentOS 6.5 (compiled from sources) - internal DNS - this DC is also a Print Server - about 400 PC workstations (mainly win7 Pro / win10 Pro and some XP Pro), and about 300 users - several Synology NAS file servers

> -----Message d'origine----- > De : samba [mailto:samba-bounces at lists.samba.org] De la part de Rowland > Penny via samba > Envoyé : lundi 21 août 2017 16:34 > À : samba at lists.samba.org > Objet : Re: [Samba] DC Upgrade from 4.1.7 to 4.6.7 > > On Mon, 21 Aug 2017 15:52:01 +0400 > HB via samba <samba at lists.samba.org> wrote: > > > Hello all,

----- On Apr 23, 2019, at 11:34 AM, samba samba at lists.samba.org wrote: > On Tue, 23 Apr 2019 11:11:21 -0500 (CDT) > Mike Ray via samba <samba at lists.samba.org> wrote: > >> About a week and half ago I upgraded from 4.0.12 to 4.9.6. Overall, >> things are functioning. >> >> However, I have come across several strange behaviors and wandered if >>

Hi, we have three 4.6.x AD servers in a cluster and some member Fileservers. What is the best/savest/recomended upgrade path? Can I upgrade the AD servers one by one and run a „mixed“ setup for some time (minutes) ? Or do I have to shutdown/disable two of them first, then update the one still up and running and than updates the others? Thanks for hints and suggestion! Regards . Götz

Mandi! L.P.H. van Belle via samba In chel di` si favelave... > For the upgrade path. > Read: https://wiki.samba.org/index.php/Updating_Samba > And this text file shows some good debian specific info > http://downloads.van-belle.nl/samba4/Upgrade-info.txt > Some parts are already fixed, but its mainly making sure the smb.conf is correct for the version your upgradeing to.

Dear all, ist there any howto updating 2 samba4.1.17 Dcs/production/replicating (Cetos6 /bind_dlz) to samba 4.3.1? What steps are important to succeed? Or is Samba 4.3.1 not ready for production? Greetings Daniel

Hi, I plan to install one Samba4 DC on a virtual machine to provide services for less than 50 users: - centralized authentication on 2 or 3 Linux servers - LDAP authentication on an ownCloud server - I do not think that I will join Windows computers to the domain, but maybe one day. I know it is better to install more than one DC to have replication, but in a so small setup, would it be

Hallo, we have two dcs in one domain which is located in separate subnets. These subnets are connected by a routed vpn. How must I handle fsmo roles when one of these dcs fails and will maybe be repaired and reconnected? A transfer of the fsmo roles is not possible until the dc is repaired, so should the fsmos be seized from the other dc? Can anybody give me a hint how to handle this

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, I lost my DC with all fsmo-roles. I try to "seize" the roles to another DC. It worked four out of five roles: root at SVL-V-AD1:~# samba-tool fsmo seize --role=rid Attempting transfer... Transfer unsuccessful, seizing... FSMO seize of 'rid' role successful root at SVL-V-AD1:~# samba-tool fsmo seize --role=pdc Attempting

Hi, i want to move my DC from an amd64 debian jessie to a armhf debian jessie. My first guess is to demote the dc and rejoin the new server. Der DC has all FSMO roles and is part of a three DC setup. Would this be the right way or should i choose another way? Regards, Dirk

Hello, As far as I know, there is no Wiki article for transferring FSMO Roles to Server 2008 R2 DC. This article’s focus is on joining a Server 2012 DC to a Samba4 domain, but it touches on the subject: https://wiki.samba.org/index.php/Joining_a_Windows_Server_2012_/_2012_R2_DC_to_a_Samba_AD <https://wiki.samba.org/index.php/Joining_a_Windows_Server_2012_/_2012_R2_DC_to_a_Samba_AD> I would

I did a similar DC upgrade from 4.1.13 to 4.6.6(like your option 1, upgrade on existing AD servers, I have two, first upgrade on none-FSMO). and I don't have any issues with the DC upgrade itself. But be careful with your member servers. After the upgrade, I have to change some default values on file servers: 1. samba 3.5.10 member server(rpm from CentOS 6.2) lost connection to samba

Dear All, I've read https://wiki.samba.org/index.php/Flexible_Single-Master_Operations_(FSMO)_roles Under section https://wiki.samba.org/index.php/Flexible_Single-Master_Operations_(FSMO)_roles#How_to_handle_situations_where_a_DC_with_FSMO_roles_is_offline Let assume that DC1 is take all the roles... It tell that we should put the fail DC1 back online and do the role transfer... But below

On 11/07/16 21:43, Rowland penny wrote: > On 11/07/16 21:38, Jason Waters wrote: >> Didn't his second email show the output of fsmo show? Which showed >> all 7 roles. But you are correct, making sure things are actually >> there before he kills the old one is best! >> >> On Mon, Jul 11, 2016 at 4:13 PM, Rowland penny <rpenny at samba.org >>