SPUserCollection is not including groups ? Or just a Bug in Wss 2.0 Object Model ?

Hey.

I wrote today a small application that need to track down all the administrators of all the websites in my client sharepoint farm ( and write the data into a list with the website url and etc ).

Anyway , just to remind you I was dealing with wss 2.0 ( 2003 ), I was doing very simple stuff as iterating via all web applications->SiteCollections->WebSites.
and then just wanted to get all the users ( including Active directory groups )

 
SPUserCollection colUser = web.AllUsers;
foreach(SPUser user in colUser)
{
   // check if admin, update list and blah blah
}

Unfortunately, it gives you back only the regular users, and not the AD groups too. I know you have under the SPWeb object the groups/sitegroups property but both of them are for Sharepoint groups and not for AD group.
Moreover, Under the SPUser object you have the property IsDomainGroup ( like I cant ask for more ) - BUT sorry, it just gives you back regular users all the time, and just "ignore" the AD gorups.

What I did at the end ? Just made a query to the SQL table ( Not so good, cause It's not supported ) - I will try now with WebService, let's hope it work via that.

If you think i'm wrong or you have another idea. Please comment.

Archive for Sharepoint ? Symantec Enterprise Vault...

You know how it is, when someone ask you a question you have never been asked before and a week later you are being asked the same question again ?

That's what happened to me today. One of my customers who still has only Sharepoint 2003 environment , wanted to try an archive product that he has for free from some vendor agreement he has.
The product is by Symantec. The name is Enterprise Vault AKA Veritas.

How it works ?

Very simple.
Application tier, DB ( sql server ) tier and Storage repository ( SAN or NAS ).

In the application tier you configure the policy ( which Sitecollection and Virtual servers you are going to archive, which files to archive and etc ).

In the DB, the application stores the location ( pointers ) of the files/item that were archived ( which is now located in the storage repository ). Yes, you the sharepoint administrator can say what the heck ? but that's the whole idea. In your sites you left with only an html link ( a stub ). When you click the item/file it goes to the Sql Server, check the pointer and retrieves the file from the storage.
Yes, The DB will shrink to a much smaller size you what it means...

What else you need to know ?
You get a webpart, for searching the files in the storage repository.
Symantec has a feature for archive in Exchange servers and it works very well ( Basically, it works in the same mechanism as Sharepoint does ).

Sounds nice, so should I go for it ?
Well, Im sorry to say but NO.
Cause this product is still not there. It has some several main issues that won't make it feasible to be deployed in any of my customers.

For example :

1. It doesn't support kerberos authentication. Only NTLM.
2. When you archive ( including the moving to the repository ), it leaves a stub which is a the "name of the file" dot HTML. Ya, You get broken links ( users who made bookmarks, links in sites and etc ).
3. The Sharepoint search engine can't crawl any of the items that were archived.