The Samba-Bugzilla – Bug 9835
userParameters attribute not synched to other DCs
Last modified: 2013-06-27 09:01:58 UTC
when the terminal server profile path is being set this is saved in the userParameters attribute. Setting this however results in the attribute only being saved on the DC where the change was done. The attribute is not being synced to other DCs. Tested with two Samba 4.0.5 AD DCs and w2k8r2's remote admin tools
We need the output of
ldbsearch ... replPropertyMetaData userParameters
with and without "--show-binary -d 1" from both DCs.
Also the samba-tool drs showrepl <dcX> output for both DCs.
You should also check that modifying any other attribute on the same object
Created attachment 8834 [details]
ldbsearch binary from dc
Created attachment 8835 [details]
ldbsearch binary from dc2
Created attachment 8836 [details]
ldbsearch from dc
Created attachment 8837 [details]
ldbsearch from dc2
Created attachment 8838 [details]
drs showrepl dc
Created attachment 8839 [details]
drs showrepl dc2
(In reply to comment #1)
> We need the output of
> ldbsearch ... replPropertyMetaData userParameters
> with and without "--show-binary -d 1" from both DCs.
> Also the samba-tool drs showrepl <dcX> output for both DCs.
> You should also check that modifying any other attribute on the same object
> gets replicated.
I modified the "mail:" attribute. That is working as expected.
This issue might depend on bug 8077.
ihmo it's a dup of 8077.
We need to handle more correctly the userParameters attribute which is a complex structure (not a pure string).
There was a discussion with dochelp back in 2011.
it might be related but this is not obviously a dup of the " userParameters needs to be stored as utf8" bug. But non-working replication of the teminal server attributes etc. is a blocker for 4.1 i think
it's the same bug, just different views.
The issue is we need a two-way 'UCS2' to 'utf8' conversion (not following the rules about invalid sequences), rather than a proper character conversion to be applied to this attribute.
*** This bug has been marked as a duplicate of bug 8077 ***