[Samba] Windows 2019 DC and samba dc

Rowland Penny rpenny at samba.org
Tue Feb 12 10:16:51 UTC 2019


On Tue, 12 Feb 2019 14:28:44 +0500
Шигапов Денис Вильданович via samba <samba at lists.samba.org> wrote:

> 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 14:15:28 srv-dc01 samba[24637]:   Can't continue Schema load: 
> didn't manage to convert any objects: all 1 remaining of 133 objects 
> failed to convert
> фев 12 14:15:28 srv-dc01 samba[24637]: [2019/02/12 14:15:28.680036,
> 0] ../source4/dsdb/repl/replicated_objects.c:361(dsdb_repl_make_working_schema)
> фев 12 14:15:28 srv-dc01 samba[24637]: 
> ../source4/dsdb/repl/replicated_objects.c:361: 
> dsdb_repl_resolve_working_schema() failed: WERR_INTERNAL_ERRORFailed
> to create working schema: WERR_INTERNAL_ERROR
> 
> ```
> 
> 
> 

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



More information about the samba mailing list