Mart Muller's Weblog

From MS KB:

Active Directory Federation Services (ADFS) enables web single sign-on, federated identity and access management by securely sharing digital identity and entitlement rights across security and enterprise boundaries. The ADFS functionality becomes available in Windows Server 2003 R2.
SharePoint and ADFS integration is dependent on the ADFS ability to seamlessly convert the ADFS authentication token to a Windows authentication token on the server. SharePoint server side functionality is mostly compatible with ADFS authentication. Limitations on the supported features for SharePoint and ADFS integration are driven by client side incompatibilities.

ADFS is a web-based authentication mechanism which relies on a system of client-side redirects in order to authenticate the end-user. This works well when the client is a Web browser such as Microsoft Internet Explorer. However, not all client programs support redirects.

When the user is authenticated, client-side redirects are used to obtain an ADFS authentication token, which is saved in a session cookie to authenticate subsequent requests using the same client program. Since session cookies are not shared between programs running in separate processes, Microsoft Office or other programs cannot access the cookie issued for a browser. This requires re-authenticating the user, for which the necessary redirects are not guaranteed to work in non-browser programs. Even if initial authentication succeeds, the resultant authentication cookie has an associated timeout. Thus periodic re-authentication is required, which is not guaranteed to work for all programs.

Several significant ADFS and SharePoint integration problems come from attempting to use client programs that do not work with redirects. For example, the use of SharePoint with Microsoft Office Outlook 2003, Microsoft Office FrontPage 2003, Microsoft Office Word 2003, or the Windows shell commands are either outright broken or have a sub-par experience.

The remainder of this article addresses what is supported and not supported, and how to best mitigate end-user problems that result from the known issues in this configuration.

• The KB article
• Article by SharePoint Team Blog
• Reaction by Patrick Tisseghem
• Overview of ADFS in Windows 2003 R2

There has been a lot of positive resonses from the Visio template for SharePoint that Ferry has created for us. L and C have put some questionmarks on the use of this. One of the reasons is that if you want to communicate about how SharePoint will look like to a customer, it is very easy to create a site in SharePoint realtime, and show the actual site itself. Or if that isn’t possible, sketching it would be a good alternative.

They are right about that, it is very easy to give the customer an impression of the site by just demo it. There is however a difference in demo-ing/sketching and designing functionally. The main goals for us to design a SharePoint site this way are:

• It is a contract between the customer and Tam Tam how we will build the site. And I don’t mean the lists really, but it is very usefull for things like custom webparts and their way of working and visualising the flow. Everything in the template can be made clickable, and the customer can click through its future solution.
• Second reason is for developers to get a real impression on how to build those custom webparts. What should it do? How should the interface look like? What is to be expected when clicking on this or that button? Also this is a contract to the developers, is it build how it is meant to build? Visio can give a good anhancement in visualize the solution in a bigger picture.

Of course, when implementing a SharePoint site bases on standard lists and webparts only, it could be not that usefull. But in most cases (we’ve done several project this way now), it is a huge difference. For the customer and for the project team.

Steen Molberg has released a new version of the Blogparts. The Blogparts are a set of webparts for creating a blog on WSS.

• URLs (http and https only) and email-addresses are detected in comments and converted to hyperlinks when displayed
• When inserting a picture in a blog post you can decide the size by using this notation [name.jpg;100] where 100 is the width in pixels. By clicking the picture it will display in full size in another window
• RSS-picture/link is a  standard-link enabling easy entering in RSS readers by right clicking the link
• Better security setup with CAS permissions

• SharePoint blog, the custom way
• Create SharePoint weblog with FrontPage 2003

Through the last few years, I’ve been trying to organise the bulk of information that comes to me every day. Next to RSS feeds, alerts are my second best friend(s). Not only for our corporate intranet and project sites (SharePoint alerts), but also with Google Alerts I keep up to date with interesting content!

This made me browse into a new product called ‘WSS Alert Manager’, how ironic brought to me by Google Alerts. I often get questions about how to push or deal with alerts in SharePoint. People that want to assign alerts to groups of people and so on. SharePoint by default isn’t designed to push alerts.. it’s a peronalization feature after all.

However, this product might be the solution for all those questions:

“WSS Alert Manager for SharePoint enables administrators to subscribe other SharePoint users to alerts on any list, document library or document; add, change and delete alerts for one or more users on any list, document library or document in a site;
efficiently handle sites with large numbers of lists and users; and locate and select users by login, preferred name or e-mail address, or by using partial words, wildcards or pattern matching.

WSS Alert Manager is available in several languages including US English, UK English, Dutch and German. “

For more information go here or download a trial.

The Dot Net Factory released its SharePoint Explorer tool which can be a good addition in some cases, especially regarding navigation. From the release note:

“SharePoint Explorer Server Edition is a friendly tree-based navigation pane providing novice and expert users alike with a global navigation view of all their SharePoint Sites, Portal Areas, Document Libraries, and Lists at a glance.

Powerful right-click menu action items are context sensitive to list only the actions permissible to the user if they were actually browsing the Site, List, or Document Library. This eliminates wait time and reduces frustration as users have instant access to most functions without multiple clicks and page loads.

Key Features:

• Does not require client software or modifications to your SharePoint site pages or site templates
• Is always available when users are browsing your SharePoint sites
• Users see only those Sites, Areas, Document Libraries and Lists they have permission to access
• Right-Click menus provide instant access to actions on any site in a single click
• Administrative features allow server or site administrators right-click access to administrative tasks

For More Information:

• Overview
• Video Walk-Through
• Request a Demonstration or Trial”

I’m glad to announce that at Februari 21st 2006, the first Dutch Information Worker User Group meeting will take place in the Microsoft Innovation Center in Barneveld!

The User Group is a platform for people that are interested in information worker solutions. Several times a year, we organize events where members can meet, share knowledge and see interesting presentations in an informal setting.  Its goal is to activate the Dutch information worker community to:

• encourage knowledge sharing between members and organizations regarding Information Worker Solutions;
• enlarge knowledge of participants by attending presentations and workshops;
• provide a networking environment. 

During this first meeting there will be two sessions:

• Session 1: What's new in WSS "v3" (to be confirmed)
• Session 2: Windows Workflow Foundation (speaker: Pieter de Bruin, Avanade)

If you are interested in attending the first meeting, please register and subscribe on the website. Note that both sessions are in Dutch.

Robert Bogue wrote a story about choosing between developing a webpart or a usercontrol which is rendered as a webpart with a tool such as SmartPart. This is an interesting article that shows the advantages and disadvantages of both ways.

“For most people, the default answer is to build Web Parts for SharePoint — there are plenty of articles on how to do it, including a few of mine. They have the distinct advantage of being the "stock" answer to the problem. And in some cases they are the best answer for the job.

The primary advantage for creating a Web Part is that everything is available. You can manipulate the tool bar; you can change everything about the way the Web Part behaves. With a user control shim you have limited abilities to reach outside of the container that you're in.

Other than that, the user control's strengths are the Web Part's weaknesses. It's unfamiliar. It's not reusable. It is more difficult to develop and debug. Similarly, the user controls weaknesses are the Web Parts strengths. Web Parts are the best performers. Web Parts have a structured deployment mechanism supported by the core infrastructure.

In most organizations the core advantage for Web Parts turns out to be their performance over user controls. As mentioned above, this is rarely a real concern; rather it is a conditioned response to be concerned with the scalability of the platform. In terms of real performance the difference is fairly minor. “

Read the complete article here

We've been looking a while for a good solution for interaction and functional designs in our SharePoint projects.

My colleagues Ferry, Annelies en Gert have been doing a lot of work the last year, to create a standard in these designs.

Ferry has posted one of those results on his blog: a Visio template for designing SharePoint sites. Great work and more to be expected!

Download here and visit Ferry's blog here

You can subscribe to the Office "12" beta program now at the Microsoft site.

During the coming months Microsoft will be announcing exciting new capabilities that will be part of the next release of Microsoft Office products, currently code-named Microsoft Office "12." Visit this site often for the latest news, and register to get the beta when it's available.

At January 26th 2006, CMS Channel organises a Intranet & portal congress in Brussels (Belgium). Aimed at Belgian (or Dutch speaking) people:

Het Intranet & Portal Congres 2006 heeft als doel enerzijds de mogelijkheden en de noodzaak van enterprise portals en intranet systemen aan te tonen aan toekomstige gebruikers en anderzijds bestaande gebruikers te informeren over de extra mogelijkheden en markttendensen binnen deze markt.
 
Volgende voorlopige thema’s zullen naar voor geschoven worden tijdens dit congres:

• “Keep the Portal sticky”: voor de meeste werknemers moet het de moeite waard zijn om een portal te gebruiken. We zullen tijdens dit congres stilstaan bij hoe we dit “blijven plakken” gevoel kunnen optimaliseren;
• Integratie: het succes van een portal hangt af van de integratie met applicaties (zowel intern als extern) en/of processen;
• Selfservice toepassingen zoals e-HRM;
• Collaboration Tools & Knowledge Management: gezamenlijk beheer van interne documenten staat centraal bij de samenwerking in een portal;
• "Why portals are not dead yet?".

See their website for details and subscribing options to this event.

What I’ve seen so far (at the PDC and Offce 12 beta 1), WSS 3 has a lot of improvements. Some big gaps of WSS 2 are filled and this will make live a lot easier by the end of the year . One of these improvements is item level security and item level versioning. Not only for documents but for every list item in WSS!

This functionality has a lot of potention, for example issue tracking. We’ve (Tam Tam) done a lot of this in our ProjectSpaces, and this will have lot’s options for our project communcation. One of the examples is that we can have have distinct issue tracking for internal and customer use, using the item level security model.

PJ Hough wrote an article on the WSS blog about tracking application in WSS 3. This article describes a lot of the impovements that are made with WSS 3. One of the big improvements is the Gantt chart option. This function will visualise project sites in many ways and will offer lots of options for project management.

PJ also describes the use of rich aplications like Access 12 in this scenario. At Tam Tam, MS Project is more and more accepted as an project environment for our project managers. I’m curious how this will relate to WSS 3 in the future. Is this something we have to keep in mind already (i.e. wait with corperate implemetation of Project Server until Office 12 is released)?

But anyway, no doubt WSS 3 will be a major improvement with lots of options for project organisations! You really should read PJ’s article as well. 

Other related articles:

• What's New in Office 12 and the Next Version of SharePoint?
• WSS 3 enhancements
• Microsoft CMS Futures
• Office 12 beta 1 ships
• [PDC05] SharePoint v3 rocks!

Microsoft’s KB contains an article now that describes how to move a WSS site from one to another server using FrontPage 2003. The basic idea is that a package is created which is deployed on another server.

For empty sites this is a great and easy solution. Content as in listitems are not moved this way, but documents are.

“Use the Packages feature to export and to import a Windows SharePoint Services Web site
You can use the Packages feature to move a Web site as empty content. When a Web site is moved as empty content, list data that is part of the original Web site does not move with the Web pages in the package. However, documents in a document library are packaged and will be moved with the Web pages in the package.

To use the Packages feature to move a Windows SharePoint Services Web site from one server to another, follow these steps: 1. Start FrontPage 2003, click File, and then click Open site.
2. In the "Look In" list, locate your source Web site, and then click Open.
3. Click Tools, click Packages, and then click Export.
4. In the "Files in Web site" list, click the Web site folder, and then click Add.
5. Click OK.
6. In the Save in box, click the folder where you want to save your Web package, click Open, and then click Save.
7. When you receive the message that states that the Web package has been saved, click OK.
8. Click Tools, point to Packages, and then click Import.
9. In the "Look In" list, open the folder where you saved your Web package, click the Web package file, and then click Open.
10. In the Destination box, type the URL of the Web server where you want to import the Web site package.

Alternatively, you can click Browse to locate the Web server where you want to import the Web site package.
11. Click Import.
12. In the Security Warning dialog box, click Yes.
13. In the Web Package Your_Package_Name deployment complete dialog box, click OK.

Back up your Windows SharePoint Services Web site
Use the Backup and Restore feature to back up the Windows SharePoint Services Web site from one server and then restore the Web site to another server. To back up your Windows SharePoint Services Web site, follow these steps: 1. Start FrontPage 2003, click File, and then click Open site.
2. In the "Look In" list, locate your source Web site, and then click Open.
3. Click Tools, point to Server, and then click Backup Web Site.
4. In the Backup Web Site dialog box, click to select the Include subsites in archive check box, and then click OK.
5. In the File Save dialog box, click the folder where you want to save the Web site backup, and then click Open.
6. In the File Name box, type a name for the backup file, and then click Save.
7. In the Web site backup completed successfully dialog box, click OK.
8. Click File, and then click Close Site.

Restore your Windows SharePoint Services Web site
Restore your Windows SharePoint Services Web site to a new Web site that does not have a template applied. To restore your Windows SharePoint Services Web site, create a new Web site at the root of the virtual server or to a subsite of your virtual server. You can then use Restore Web Site to move your Windows SharePoint Services Web site to the new Web site.

Note Permissions will not migrate with the Web site when it is restored from backup.

To restore your Windows SharePoint Services Web site, follow these steps: 1. Start Microsoft Internet Explorer, and then locate your Team Web Site Home page on your Windows SharePoint Services Web site.
2. At the top of the Home page, click Site Settings.
3. On the Site Settings page, click Manage Sites and Workspaces.
4. On the Sites and Workspaces page, click Create.
5. On the New SharePoint Site page, in the Title box, type the title that you want to give the Web page.
6. In the URL name box, type the name that you want to use for the URL of the Web page.
7. Click Create.
8. When the Template Selector page opens, quit Internet Explorer. Do not select a template.
9. Start FrontPage 2003.
10. On the File menu, click Open Site.
11. In the Site name box, type the URL of the site that you created in steps 1 through 9, and then click Open.
12. Click Tools, point to Server, and then click Restore Web Site.
13. In the File Open dialog box, open the folder where you saved the Web site backup file.
14. Click your Web site backup file, and then click Open.
15. In the Restore Web Site dialog box, click OK.
16. In the Web site restore completed successfully dialog box, click OK. “

Ofcourse when you want to move WSS sites including all content, you can use the SMIGRATE tool that is located in in the bin directory of your SharePoint installation on the SharePoint server (\Program Files\Common Files\Microsoft Shared\web server extensions\60\bin\). You must have access to the server to use this tool.

read the complete article

Other related articles:

• SharePoint Document Level RestoreLevel Restore
• SharePoint Portal Server 2003 Sample: Back Up and Restore
• SMove for SharePoint
• About SharePoint and convincing system administrators
• SharePoint Backup & Recovery Test Plan

Some rumours about a new MS server product called Biz# Server, aimed at business intellegent. Webwereld (dutch) tells us that Biz# server contains Business Scorecard Manager and will be used for analyses and modelling using Analyses Services. Other databases can be used as well like SPSS and Siebel or SAP. The product will come with the Office 12 wave and will exist next to BSM.

“Biz# Server kan als los systeem worden gebruikt. Wel is SharePoint vereist. Voor analyses en het maken van modellen gebruikt het de Reporting en Analyses Services van Microsoft SQL Server. Gebruik in combinatie met statistische software als SPSS is ook mogelijk. Als database is SQL mogelijk, maar ook Siebel en SAP MBS. “

SharePoint is needed to run the whole thing standalone.

read the complete article here

Macaw has been working on a SharePoint Skinner application to enable “non-distructive” modifications in you SharePoint design:

“Welcome to the MacawSharePointSkinner. MacawSharePointSkinner is a tool designed to enable non-intrusive modifications to the visual and functional design of SharePoint. The tool can be used for both Windows SharePoint Services 2.0 and for Microsoft Office SharePoint Portal Server 2003. Actually, it can be used for any web site utilizing the ASP.NET technology.”

…

“The approach that MacawSharePointSkinner takes is two-fold: 

Text Replacements – MacawSharePointSkinner lets SharePoint render the final HTML, and just before this HTML is sent to the browser MacawSharePointSkinner makes the needed modifications to this HTML. This is done in such a way that no modifications are needed to the internal files of SharePoint, so it is non-intrusive. Another advantage is that it will survive service packs (although the output HTML may change in a service pack!) and template modifications.

Url Redirections – MacawSharePointSkinner can translate requested url’s into other url’s. This allows you to redirect standard SharePoint url’s to your own url’s.”

This application has a different approch of what is normally done with SharePoint syles and layouts. One to test out very soon!

Download here

Hey, first post on the SharePoint Development Team blog! Kurt DelBene is talking about what place SharePoint takes in the strategy that Microsoft had developed on collaboration.

“So our approach is to provide “pervasive” collaboration capabilities via a broad set of Microsoft products that work together to solve user problems.  We think about those solutions as falling into four large buckets:  Integrated Communications, Collaborative Workspaces, Access to People and Information, and People-driven Processes:

• Integrated Communications:  Enable people to more effectively manage their communications.  Enable them to triage their communications effectively.  Let them select whatever communications mechanism works best for them (email, IM, RTC, VOIP) and transition from one method of communicating to another effortlessly.  Many of our investments in Outlook, Exchange, and RTC are to accomplish this goal.
• Collaborative Workspaces:  Provide spaces for people to work on projects together in the context of the work they are doing.  Facilitate high value collaborative activities like collaborative authoring and meetings.  This is where Windows SharePoint Services fits in.  It also includes our investments in Groove as rich, task-oriented, peer-to-peer workspaces.
• Access to People and Information:  Enable people to find the information they need to do their jobs by either browsing to it from an organization’s portals, searching for it, or being proactively notified about it.  Since much of the information they want to find will be newly created in collaborative workspaces, we built our portal product, SharePoint Portal Server, on top of a foundation of Windows SharePoint Services.  This means customers can deploy a single infrastructure for information sharing in their organization and only have to learn a single way to manage and customize portals and collaboration spaces.  Finding people is also a key scenario for us, since often times the most topical information is the information still in people’s heads.  This is where SharePoint Portal Server “MySites” come in as a place for people to share information and expertise with others.
• People-driven Processes:  When you have a rich information sharing environment, as SharePoint is, it is natural to want to integrate business processes in with team spaces and portals.  In the Office 12 release, we have invested in integrating workflow into SharePoint and into the Microsoft Office applications, so people can build spaces that automate key business processes.  For example, a marketing team space might want to include workflows associated with approving a marketing plan or enable the team to kick off related purchase requests that are submitted directly to back-end ERP systems using rich forms, such as InfoPath, which is available as a server service in the Office 12 release.”
  

I hope to see more posts in the future on this blog.

Thanks to Wouter and Paul, Tam Tam now has a very good looking aggregate blog with all Tam Tam’s bloggers. With a blink to our new style guide

http://blogs.tamtam.nl

After several posts about why not to use subfolders in document libraries, Dustin Miller explains why subfolders are evil:

“My answer is always the same, and has never wavered.  Don't use subfolders.  Of course, that goes hand-in-hand with another of my lessons, “don't use the Explorer View,” but that's a topic for another blog post.  Separate document libraries are useful if you need separate security permission sets for a grouping of documents (since we don't have item-level or folder-level security in document libraries with the current release of SharePoint Products and Technologies), but for categorization within a site, nothing tops custom fields.”

and Bil Simser goes into more detail with it:

• There is a path limitation in SharePoint (or maybe IIS) of 260 characters in total. As you start creating the folder structure from hell, you'll find this gets wiped out very quickly and you end up staring at yet another cryptic SharePoint error message (basically "Something bad has happened") with no indication of the what the problem is. Better yet, documents just vanish into the ether and you have no idea that they're really still there, tucked away and taking up precious space in your SQL Server but you're unable to access them.
• Ever need something and try to go look for it. If you know where to find it, it kind of defeats the purpose of creating a complex organization system if you already know where it is. If you don't, search might turn it up but the vast majority of carbon-based units out there can't figure out how to search for something so that's a bit of a waste. Folders only allow you to look for things the way someone who put the stuff there. If I had a brain fart and filed the asset records for 1997 under Financials -> 1997 -> Assets would you think to look there or in Assets -> By Year -> 1997. Again, you need to know the organization structure to navigate it. Using folders for organization just compounds this as we end up with deeply nested folders upon folders and nobody can find anything (even the people that put it there).
• Folders are one-dimensional. Think of a Yellow Pages. I can open it up and look for a pizza place by looking in Pizza, Restauraunts, or maybe even Dining. I don't need to know the section that I want to look in, I can find it in various ways. Everyone is wired differently and will look for things the way they were brought up. What if I was the owner of a parts company and decided to start organizing my inventory using SharePoint. Would I put my "X89 Widget" under "Aircraft -> DC9 -> Parts" or in "Parts -> By Aircraft -> Large". I can only organize things one way with folders and if I need to slice information up differently, I either end up with links all over the place (which will easily break and become out of date) or multiple copies of the same thing because the Finance department looks for things by Asset Number and the Parts guys look for it by Part Number. Metadata is the way to please everyone.

We’ve had more then one discussions about how to store documents in SharePoint. Somehow, eveyone agrees it doens’t matter where you put documents in SharePoint, as long as the meta data is correct. The problem with this that people are lazy. Meta data is the most important thing with new documents in SharePoint, but the people that store these documents are the bottleneck. This is where most of the “errors” occur.

The main question here is: “How can SharePoint facilitate in assigning meta data to documents?” This is quite a difficult question. Should we use the context in where the documents are placed? Should we use the content of the document itself to provide the meta data? Should we force the users to set meta data (and blocking alternative ways)? I think the perfect meta data solution is not yet created…

Andre Kieft mentions that Alexandru Bold’s notes can be a good help with future issues that might arise with SharePoint. Wow, that are a lot of SharePoint Tips !

“A while ago a Sharepoint team member of mine, Alexandru Bold, started taking notes for himself in trying to remember different tips that could help customers in attacking future issues that might arise.

Many thanks for this Alex, I think this is a very helpful resource for a lot of customers.

From the Menu:

1. How to check the SPS/WSS versions:

2. Interpreting the SPS/WSS versions:

3. Allowing access to the Online Gallery from behind a proxy server or firewall

4. Manually disconnecting an SPS server from the Config DB:

5.Where to find CLSID for word breakers and steamers:

6. Creating a new Config Database:

7. Latest post-SP1 roll-up packages for WSS/SPS

8. How to increase the Timeout settings for WSS/SPS

9. How to check the versions of WSS backups

10. Considerations when installing WSS on a DC

11. SharePoint Portal Search in WSS sites:

12. Migrating SPS/WSS between domains:

13. Manually test the SMTP server:

14. The theory behind Ghosted/un-ghosted pages

15. How to configure your Default SMTP Virtual Server

16. Remove the !New Tag from New Items

17. How to add a custom theme to the list of available WSS themes

18.  How to access the Web Parts Maintenance page:

19.  Theory between the Web Client and Web Folders

20. SPS Cn Buckets theory

21. Remove the index/job components from topology

22. Paths to be excluded by the Antivirus

23. How to improve the Full-Text Search performance

24. SPS SP2 articles

25. WSS SP2 articles

26. How to manually remove SPS

27. Boost UP the MSI install logging (really useful for debugging patch installation)

28. Where to check for any mismatches regarding the Updates installed

29. Enabling TIFF OCR

30. Enabling RTF indexing

31. Out e-mail template for when sending the SPSReports”

Read the complete story

Bil Simser is ending 2005 with a clear story about VS2005, ASP.Net 2.0 and SharePoint development. This helps a lot understanding where to start.

“Here's where things get tricky. First off, forget about using the System.UI.WebControls.WebParts namespace or inheriting from that WebPart class. Those type of WebParts (very much the same as SharePoints) have their own manager and tie into various parts of the framework and the support just isn't there yet (as far as SharePoint goes). When V3 rolls around you'll be able to build WebParts using this framework and the ASP.NET 2.0 WebPart will be almost identical to the SharePoint WebPart class.”

Read the complete article

Arpan Shah wrote an article about the next version of CMS, what the changes are and where it is going to with WSS3 and Office 12. I think this article gives a good overview for people looking for the furture of CMS in the huge information wave about Offce 12 lately.

“Based on feedback from you, partners and analysts, we are building CMS functionality on top of Wndows SharePoint Services (WSS) "v3". CMS and SPS, along with a lot of other great functionality, will be one integrated set of technologies built on top of WSS "v3". The Office Server investments built on top of WSS "v3" are codenamed Office "12" SharePoint Servers. The broad investment areas include ECM, Search, Portal, Collab, BI and Forms. We're careful not to say SPS "12" or CMS 2007, because packaging and licensing decisions have not been made. While these technologies will be technically integrated (same development, deployment and end-user experience), we have not made decisions on how these will be packaged. As a current customer, rest assured that you will get what you have today.

I'd like to expand on what this specifically means for CMS 2002 customers. (Keep in mind, this is a subset of the ECM investments we are making in Office "12" SharePoint Servers.) You will no longer have to deploy two different WSS and CMS solutions; CMS functionality will be built on top of WSS allowing you to deploy a single WCM and Collaborative solution. Also, you gain a lot of other benefits b/c it's built on WSS: Web Parts, Lists, Document Libraries, Templates, Workflow , RSS, et cetera.“

Read the complete posting