search for: taouser

...it is > normally a bit 'Hotel California', 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 di...

...a bit 'Hotel California', 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 cann...

...ldif_elements) All these object classes were tests we did? years ago, and which have been "deleted" (I don't even remember by what mechanism) for almost as long. No object should still be using any of these, and on graz-dc-sem that's true. 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. All servers seem to replicate without errors according to samba-tool drs showrepl. Ho...

...ve >>> you can deactivate schema objects, try reading this: >>> >>> https://docs.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 goe...

...; you can deactivate schema objects, try reading this: >>>> >>>> https://docs.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...

...ill be using any of these, and on graz-dc-sem > that's true. I would love to know how you deleted something from the schema, it is normally a bit 'Hotel California', you can add to the schema but never remove anything from the schema. > > 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...

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