search for: seizi

But, if you use the "seizi" dc that no longer has the FSMO should be removed from the network, right? Regards; 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...

Hi! In wiki -> https://wiki.samba.org/index.php/Transferring_and_Seizing_FSMO_Roles#Difference_of_Transferring_and_Seizing_FSMO_Roles "If the DC is broken (e. g. hardware defect) and will never come back again, then you can seize the role on a remaining DC. It is very important that the old DC will never be connected to the network again, if it is connected a...

So in theory, you should be able to seize the roles onto the server that you expected would have the role, right? On Wed, Jun 6, 2018 at 11:35 AM, Carlos via samba <samba at lists.samba.org> wrote: > Hi! > > In wiki -> https://wiki.samba.org/index.php/Transferring_and_Seizing_FS > MO_Roles#Difference_of_Transferring_and_Seizing_FSMO_Roles > > "If the DC is broken (e. g. hardware defect) and will never come back > again, then you can seize the role on a remaining DC. It is very important > that the old DC will never be connected to the network again...

...restDnsZones,DC=xxxx,DC=xxxx,DC=com,DC=br'> <> >> >> Others fsmo is trafering ok. >> >> >> Any idea ? >> >> >> Regards >> >> > This used to happen quite some versions ago, cannot remember why though. > > You could try seizing the roles on the DC you want to transfer them to. > > Rowland >