I typically don't enumerate groups with this command, but an internal auditor is using it and found a discrepancy between what ADUC shows, and using NET GROUP or NET GROUPS. For example
GROUP1 (a domain global group) has 3 members, one global group and 2 user accounts. When viewing this in ADUC it shows correctly, using PowerShell it shows correctly. When using the following: h:\Utilities>net groups GROUP1 /domain The request will be processed at a domain controller for domain contoso.com. Group name GROUP1 Comment Group for testing Members ------------------------------------------------------------------------------- User1 User2 The command completed successfully. It doesn't enumerate the name of the global group. the group it's not enumerating does have a space in the name. And I did find this: http://support.microsoft.com/kb/150295 It doesn't specifically say that it can't enumerate the name of a group member if it has a space in it. Can someone verify this for me? Thanks, Chris Bodnar, MCSE, MCITP Technical Support III Distributed Systems Service Delivery - Intel Services Guardian Life Insurance Company of America Email: [email protected] Phone: 610-807-6459 Fax: 610-807-6003 ----------------------------------------- This message, and any attachments to it, may contain information that is privileged, confidential, and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient, you are notified that any use, dissemination, distribution, copying, or communication of this message is strictly prohibited. If you have received this message in error, please notify the sender immediately by return e-mail and delete the message and any attachments. Thank you. ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to [email protected] with the body: unsubscribe ntsysadmin
