samba - Jan 2018 - Replication Problem win2k8r2 uppercase Attribute

Hi,


have the same Problem described in,
https://lists.samba.org/archive/samba/2016-November/204659.html



it should be fixed already,
https://bugzilla.samba.org/show_bug.cgi?id=12399


my version 4.5.15 on Debian 8 i have one win DC and 10 samba DC's  



is there a solution via "samba-tool dbcheck" or how is the procedure
to fix it ?
 i did compare the databases and tried to replicate via "samba-tool
replicate" but no changes



thanks

On Fri, 26 Jan 2018 15:43:40 +0100
Matthias Gassner via samba <samba at lists.samba.org> wrote:
>     Hi,
> 
> 
> have the same Problem described in,
> https://lists.samba.org/archive/samba/2016-November/204659.html
> 
You haven't really got a problem, it is more of an annoyance, ;-)

The thing that caused it has been fixed, but I don't think there is a
way to change the attribute case yet.

Rowland

Am Freitag, den 26-01-2018 um 16:37 schrieb Rowland Penny via
samba:


On Fri, 26 Jan 2018 15:43:40 +0100
Matthias Gassner via samba  wrote:
>     Hi,
> 
> 
> have the same Problem described in,
> https://lists.samba.org/archive/samba/2016-November/204659.html
> 
You haven't really got a problem, it is more of an annoyance, ;-)

The thing that caused it has been fixed, but I don't think there is a
way to change the attribute case yet.

Rowland

-- 
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/options/samba







Hi Rowland,

my some how strange problem is after join the windows as DC the
objects created on linux, do not get replicated to the win DC, every
thing else looks fine also
from "samba-tool drs repl show".
just the replications by  "samba-tool drs  replicate " with the
destination windows DC does show the error. 

funny part is my customer is migrating towards windows, before then
everything worked out fine for 8 years starting with alpha 0.8 samba4
domain, and years of upgrades to 4.5.1 :D 

i guess there is something happening thanks again on this topic,
thanks to the samba team 
https://bugzilla.samba.org/show_bug.cgi?id=12399#c12

As far as I know (tried it myself :) ), dbcheck won't fix it. I had the 
same issue in samba 4.5. The way I dealt with it, was when updating to 
4.7.x. I added new temporary DC with 4.7.x, allowed it to replicate all 
data (no uppercase errors in this DC), then for all DC's i one by one: 
demoted DC, removed samba (complete wipe), and installed fresh 4.7 and 
re-joined it as DC (same hostname and IP). Of course I had to be careful 
with FSMO roles, that is I had to move them between reinstalls.

In the end all my DC's were updated and database without this ou/OU or 
cn/CN error.

Of course You can do this without actual samba update, you just have to 
install "fresh" samba with version not affected by this error and join
as DC, then recreate all DC's.

Maybe there is less "invasive" method, but I didn't know about it,
and
anyway I wanted to update DC's, so wasn't an issue for me. And now 
ldapcmp shows everything in order.

Regards,

Kacper Wirski


W dniu 26.01.2018 o 16:37, Rowland Penny via samba
pisze:
> On Fri, 26 Jan 2018 15:43:40 +0100
> Matthias Gassner via samba <samba at lists.samba.org> wrote:
>
>>      Hi,
>>
>>
>> have the same Problem described in,
>> https://lists.samba.org/archive/samba/2016-November/204659.html
>>
> You haven't really got a problem, it is more of an annoyance, ;-)
>
> The thing that caused it has been fixed, but I don't think there is a
> way to change the attribute case yet.
>
> Rowland
>