Upgrade issue with 3.0.21b->3.0.22

[Gerald (Jerry) Carter]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Gerald (Jerry) Carter wrote:
> Backing up a little.  The concept of a primary group
> has been deprecated in AD unless you have "Mac or
> POSIX compliant applications" (from the MMC Users and
> Computer plugin in Windows 2003).

This was surprising to me.  Connect to a standalone NT4
workstation.

rpcclient $> lookupnames test
test S-1-5-21-1924756635-1969438570-313073093-1001 (User: 1)
rpcclient $> queryusergroups 1001
group rid:[0x201] attr:[0x7]

rpcclient $> lookupsids S-1-5-21-1924756635-1969438570-313073093-513
S-1-5-21-1924756635-1969438570-313073093-513 TEST1\None (2)

rpcclient $> enumalsgroups domain
rpcclient $> enumalsgroups builtin
group:[Administrators] rid:[0x220]
group:[Backup Operators] rid:[0x227]
group:[Guests] rid:[0x222]
group:[Power Users] rid:[0x223]
group:[Replicator] rid:[0x228]
group:[Users] rid:[0x221]

And yet in the NT4 musrmgr.exe, the user 'test' appears in
only one group--'Users'






cheers, jerry
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFD6nv3IR7qMdg1EfYRAhRdAJ9/qYVdJMAvOmwsOeQlEBHHbxAZ3wCeMAWX
JnZ4IdvJmJFBtj2KIu9rX9Q=
=hXzn
-----END PGP SIGNATURE-----