diff options
| author | Andrew Tridgell <tridge@samba.org> | 2005-10-13 06:09:37 +0000 |
|---|---|---|
| committer | Gerald (Jerry) Carter <jerry@samba.org> | 2007-10-10 13:39:48 -0500 |
| commit | 6b7d7f22e754cb8a580951ae3626bb91d4642c75 (patch) | |
| tree | e5ca7038a4e050b51d5c91adbdf24c9647d87518 | |
| parent | 0fa924bb8f446e35a0fd543cda20b23c81e7dc9e (diff) | |
| download | samba-6b7d7f22e754cb8a580951ae3626bb91d4642c75.tar.gz samba-6b7d7f22e754cb8a580951ae3626bb91d4642c75.tar.bz2 samba-6b7d7f22e754cb8a580951ae3626bb91d4642c75.zip | |
r10955: finally worked out why our computer accounts were being identified as users in mmc.
The problem was that the samdb module was auto-adding objectClass=user
for these accounts. That would be OK, as computer accounts are
supposed to be in that objectClass, but mmc cares about the order of
the values in the objectClass attribute! It looks for the last value,
and takes that as the value to use when deciding how to manipulate the record.
So, this patch adds an explicit objectClass=user to the record when it
gets created, which tells the samdb module to not add it as well. That
fixes the order. I suspect we are missing something else though - is
objectClass supposed to auto-sort based on the schema?
(This used to be commit 68c5f807fdb99fd605154d455e61a08293cbd2d0)
| -rw-r--r-- | source4/setup/provision_users.ldif | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/source4/setup/provision_users.ldif b/source4/setup/provision_users.ldif index 2e420b226a..a23943a3ef 100644 --- a/source4/setup/provision_users.ldif +++ b/source4/setup/provision_users.ldif @@ -86,6 +86,7 @@ dn: CN=${NETBIOSNAME},OU=Domain Controllers,${BASEDN} objectClass: top objectClass: person objectClass: organizationalPerson +objectClass: user objectClass: computer cn: ${NETBIOSNAME} uSNCreated: 1 |