search for: ucsus

It's amazing how long Samba just keeps running even when apparently everything's broken. In preparation of finally upgrading our DCs to 41.0, I ran dbcheck on all of them, resulting in: graz-dc-sem: > Checking 3861 objects > Error: governsID CN=ucsUser,CN=Schema,CN=Configuration,DC=ad,DC=tao,DC=at on 1.3.6.1.4.1.19414.3.2.2 already exists as an attributeId or governsId > Error: governsID CN=taoSharedFolder,CN=Schema,CN=Configuration,DC=ad,DC=tao,DC=at on 1.3.6.1.4.1.19414.3.2.4 already exists as an attributeId or governsId > Error: govern...

...ornia', you can add to the schema but never > remove anything from the schema. Hence "deleted", they're still around, just disabled. Which caused the ID reuse problem in the first place. >> There is, however, a new class called taoUser with the same X500 OID as >> ucsUser that's only used in one domain account (mine, of course); on >> graz-dc-sem the object correctly has the taoUser class assigned, on the >> other servers it's still an ucsUser. > > That is probably your problem, you cannot have different names for what > seems to be t...

...t; It's amazing how long Samba just keeps running even when apparently > everything's broken. > > In preparation of finally upgrading our DCs to 41.0, I ran dbcheck on > all of them, resulting in: > > graz-dc-sem: >> Checking 3861 objects >> Error: governsID CN=ucsUser,CN=Schema,CN=Configuration,DC=ad,DC=tao,DC=at on 1.3.6.1.4.1.19414.3.2.2 already exists as an attributeId or governsId >> Error: governsID CN=taoSharedFolder,CN=Schema,CN=Configuration,DC=ad,DC=tao,DC=at on 1.3.6.1.4.1.19414.3.2.4 already exists as an attributeId or governsId >> Error...

...microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2003/cc773309(v=ws.10) >>> >> They already are disabled. > > Have you extended the schema to use 'taouser' ? Yes. > I ask this because (from what you posted) it uses the same X500 OID as > 'ucsUser', another name for X500 OID is 'governsID', so this may be your > problem, try deleting 'taouser' from your AD object (this is allowed) > and see if your problem goes away. That fixed the dbcheck crashes on the other three servers, they now complete successfully. Still...

...o the schema but never >> remove anything from the schema. > Hence "deleted", they're still around, just disabled. Which caused the > ID reuse problem in the first place. > >>> There is, however, a new class called taoUser with the same X500 OID as >>> ucsUser that's only used in one domain account (mine, of course); on >>> graz-dc-sem the object correctly has the taoUser class assigned, on the >>> other servers it's still an ucsUser. >> That is probably your problem, you cannot have different names for what >> see...

...evious-versions/windows/it-pro/windows-server-2003/cc773309(v=ws.10) >>>> >>> They already are disabled. >> Have you extended the schema to use 'taouser' ? > Yes. > >> I ask this because (from what you posted) it uses the same X500 OID as >> 'ucsUser', another name for X500 OID is 'governsID', so this may be your >> problem, try deleting 'taouser' from your AD object (this is allowed) >> and see if your problem goes away. > That fixed the dbcheck crashes on the other three servers, they now > complete suc...

On 04.07.19 15:54, Rowland penny via samba wrote:>> Still left are the three governsId collisions, which are now identical >> across all DCs: >> >>> Checking 3861 objects >>> Error: governsID >>> CN=ucsUser,CN=Schema,CN=Configuration,DC=ad,DC=tao,DC=at on >>> 1.3.6.1.4.1.19414.3.2.2 already exists as an attributeId or governsId >>> Error: governsID >>> CN=taoSharedFolder,CN=Schema,CN=Configuration,DC=ad,DC=tao,DC=at on >>> 1.3.6.1.4.1.19414.3.2.4 already exists as...

...tion. Well this is you change... Get it, setup a clean server. Join the domain, Seize the FSMO roles after AD syncs are done. Push this AD DB to the other servers. s > On graz-dc-sem, samba-tool dbcheck shows zero errors. > --cross-nc gives: > > > Error: governsID > > CN=ucsUser,CN=Schema,CN=Configuration,DC=ad,DC=tao,DC=at on > > 1.3.6.1.4.1.19414.3.2.2 already exists as an attributeId or > governsId > > Error: governsID > > CN=taoSharedFolder,CN=Schema,CN=Configuration,DC=ad,DC=tao,DC=at on > > 1.3.6.1.4.1.19414.3.2.4 already exists as an...

Hai Sven, > -----Oorspronkelijk bericht----- > Van: Sven Schwedas [mailto:sven.schwedas at tao.at] > Verzonden: dinsdag 5 september 2017 17:13 > Aan: L.P.H. van Belle > CC: samba at lists.samba.org > Onderwerp: Re: [Samba] Server GC/name.dom/dom is not > registered with our KDC: Miscellaneous failure (see text): > Server (GC/name/dom at DOM) unknown > > On

...... Get it, setup a clean server. Join > the domain, Seize the FSMO roles after AD syncs are done. Push this > AD DB to the other servers. s > >> On graz-dc-sem, samba-tool dbcheck shows zero errors. --cross-nc >> gives: >> >>> Error: governsID >>> CN=ucsUser,CN=Schema,CN=Configuration,DC=ad,DC=tao,DC=at on >>> 1.3.6.1.4.1.19414.3.2.2 already exists as an attributeId or >> governsId >>> Error: governsID >>> CN=taoSharedFolder,CN=Schema,CN=Configuration,DC=ad,DC=tao,DC=at >>> on 1.3.6.1.4.1.19414.3.2.4 alread...