search for: the_2019_dc_shorthostname

I joined the windows 2019 domain, where among the controllers there is a Samba DC version 4.8.5, and after that the replica stopped working windows servers <--> samba DC. Upgrading to version 4.9.4 did not help Errors: ``` фев 12 14:15:28 srv-dc01 samba[24637]: [2019/02/12 14:15:28.679872,  0] ../source4/dsdb/repl/replicated_objects.c:248(dsdb_repl_resolve_working_schema) фев 12

...a hasn't got to Windows 2016 yet, never mind 2019. You may be able > to fix your domain by demoting the Windows 2019 DC. If this doesn't > work, stop the Windows 2019 DC and forcibly remove it from the domain > with 'samba-tool domain demote > --remove-other-dead-server=<THE_2019_DC_SHORTHOSTNAME> > > I fear that you may have terminally mangled your AD. > I never had to deal with this but the topic is of interest to me. According to the Samba Wiki (see 1), Samba supports a domain functional level of up to 2012_R2 with restrictions, and 2008_R2 without restrictions. According...

...; > > Samba hasn't got to Windows 2016 yet, never mind 2019. You may be able to fix your domain by demoting the Windows 2019 DC. If this doesn't work, stop the Windows 2019 DC and forcibly remove it from the domain with 'samba-tool domain demote --remove-other-dead-server=<THE_2019_DC_SHORTHOSTNAME> I fear that you may have terminally mangled your AD. Rowland

...Windows 2016 yet, never mind 2019. You may be > > able to fix your domain by demoting the Windows 2019 DC. If this > > doesn't work, stop the Windows 2019 DC and forcibly remove it from > > the domain with 'samba-tool domain demote > > --remove-other-dead-server=<THE_2019_DC_SHORTHOSTNAME> > > > > I fear that you may have terminally mangled your AD. > > > I never had to deal with this but the topic is of interest to me. > According to the Samba Wiki (see 1), Samba supports a domain > functional level of up to 2012_R2 with restrictions, and 2008_R2 >...