I'd like to get a view of all SharePoint groups and the members of those groups. A designer added users names to site groups, rather than Active Directory groups as required. There are at least 40 sites with this issue so I am looking for a way to get all the groups and the members to determine which ones need to be fixed. Thanks, Shane Meisner

> A designer added users names to site groups, rather than Active Directory groups as required. I hope that you mean "as required" *by your company* because there is nothing inherently wrong with having users in SP groups and not creating AD groups for them. The Best Practices (etc.) book has an interesting discussion on this and it tends towards putting them in SP groups. SP 2010 "FAQ" (mainly useful links): http://wssv4faq.mindsharp.com/default.aspx WSS3/MOSS FAQ (FAQ and Links) http://wssv3faq.mindsharp.com/default.aspx Both also have links to extensive book lists and to (free) on-line chapters

You posted this in the Admin section, so assuming you have access to the web servers and to PowerShell: Here's a quick little PowerShell script to list all groups and all users. Note that if an AD group is listed as a user, all the users in that group may not show up in this list until the user has visited SharePoint at least once. [System.Reflection.Assembly]::LoadWithPartialName("Microsoft.SharePoint") $site = New-Object Microsoft.SharePoint.SPSite("http://yourservername/sites/yoursitecollection ") $groups = $site.RootWeb.sitegroups foreach ($grp in $groups) {"Group: " + $grp.name; foreach ($user in $grp.users) {" User: " + $user.name} } Mike Smith TechTrainingNotes.blogspot.com

Yes, company requirement. Due to SOX requirements we use AD to deal with Security for our sites. That way if they leave the company, or move to a different department, thier access is automatically removed from the SharePoints site(s). Still trying to deal with the issue when libraries are set to not inherit permissions and users names are listed but right now this is working ofr sites.

Thanks I'll give that a try.. The main thing I wanted to see is SharePoint groups that have individual names added rather than Active Directory groups.

Shane, We had the same problem here. One thing I setup to make this quicker and faster is we created a group called "MOSS Deny All" Then set this group via the Web Application User Policy to have Deny All rights. Patrick

Thanks, that sounds like a very good idea. I'll bring it up to our team.. Shane