search for: fsmos

Hello, I tested to transfer all 7 FSMOs from Windows Server 2003 Enterprise to Samba 4.3.0 DC. (I think some users still use Win2K3 and want to migrate.) But unfortunately is failed. To reproduce, (1) Promoto Win2K3R2 Enterprise host to first DC. (2) Join self-built Samba 4.3.0 to the domain. (3) Run 'samba-tool fsmo transfer --r...

Hello, > On 07/10/15 00:33, TAKAHASHI Motonobu/高橋 基信 wrote: > > Hello, > > > > I tested to transfer all 7 FSMOs from Windows Server 2003 Enterprise > > to Samba 4.3.0 DC. (I think some users still use Win2K3 and want to > > migrate.) But unfortunately is failed. > > > > To reproduce, > > > > (1) Promoto Win2K3R2 Enterprise host to first DC. > > (2) Join self-built Sa...

Hi! The problem with this is that both Dcs will continue on the network ... I wanted to transfer the FSMOs, because in DC (that has today) I will perform an S.O. upgrade and if something goes wrong, it is already correct !!! Regards; On 06-06-2018 11:05, Rowland Penny via samba wrote: > On Wed, 6 Jun 2018 10:46:48 -0300 > Carlos via samba <samba at lists.samba.org> wrote: > >>...

...e 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 situation? Thanks, -Peter

...s; On 06-06-2018 11:36, Rowland Penny via samba wrote: > On Wed, 6 Jun 2018 11:24:33 -0300 > Carlos via samba <samba at lists.samba.org> wrote: > >> Hi! >> >> The problem with this is that both Dcs will continue on the >> network ... I wanted to transfer the FSMOs, because in DC (that has >> today) I will perform an S.O. upgrade and if something goes wrong, it >> is already correct !!! >> > Something already has gone wrong, for some reason it cannot find the > FSMO role owner. > > This is no reason not to seize the roles, it may...

...-01 (DC1) is the primary DC, for want of a better term, and runs samba-4.3.13_2. samab-02 (DC2) and samba-03 (DC3) are the replacement DCs that have been joined to the DOMAIN. If I can be certain that everything need has indeed come across form DC1 to DC2 then I can start the process of moving the FSMOs. It may be that rsync is just throwing a hissy fit over some non-essential flag. But I can hardly take that chance on a live domain with only a single DC remaining. Thank you for your time and attention. -- *** e-Mail is NOT a SECURE channel *** Do NOT transmit sensiti...

Hi! I have two Dcs, with Samba 4.7.7, i need tranfer(dont seize) fsmo between dcs, but dont work samba-tool fsmo transfer --role=domaindns -Uadmin Password for [XXXX\admin]: ERROR: Failed to delete role 'domaindns': LDAP error 16 LDAP_NO_SUCH_ATTRIBUTE -  <attribute 'fSMORoleOwner': no matching attribute value while deleting attribute on

Hi All, After reading the list for a while I have a question myself. I have the task of upgrading a couple of systems and one of them is the office AD infrastructure from a Samba-4.1 installation to the latest stable version. I already did a concept of proof by incrementally compiling versions 4.2/3/4/5/etc to the then latest stable 4.10 and it seemed to work out OK but was a lot of work. I had a