A walk-through of features, set-up, and configuration
Let me be the first to declare, officially, if prematurely, “The file server is dead!” With the release of Windows SharePoint Services 3.0, Microsoft delivers simple, secure, and effective support for collaboration, knowledge management, and business processes.
To understand and implement SharePoint Services 3.0 and get a feel for some of its key new features, let's create an intranet home page and a SharePoint site for the IT department of a fictional company, Windomain.com. You'll see why I believe the grim reaper is a-knockin' on your shared folders' doors.
Microsoft's modus operandi seems to be to invest maximum effort when a product reaches version three, and SharePoint technology is no exception. Windows SharePoint Services 2.0 improved on the first version but left gaping holes in functionality and ease of use. Content Management Server morphed to become Microsoft SharePoint Portal Server 2003, which built a portal “umbrella” over SharePoint sites. Now, SharePoint Services and SharePoint Portal Server have made a significant leap: Both were completely redesigned and are now joined at the hip. SharePoint Services 3.0 is now a .NET application, leveraging all the capabilities of Microsoft .NET Framework 3.0, including workflow. And SharePoint Portal Server 2003, renamed Microsoft Office SharePoint Server 2007, has become an add-on extension to SharePoint Services 3.0, providing not only extraordinary functionality, which I'll examine in an upcoming article, but also demonstrating the robust platform for Web-application development delivered by SharePoint Services 3.0.
Although Microsoft recommends you use a dual-processor server with many gigabytes of RAM, for a small rollout of SharePoint Services 3.0 you can get by with less, depending on what you're doing with SharePoint, so don't let the published hardware recommendations prevent you from taking SharePoint Services 3.0 for a test drive. In fact, I used a 1GB virtual machine (VM) to create the prototype used in this article. I wouldn't suggest using such scant resources for a production intranet, but even a VM can provide a functional sandbox for SharePoint Services experiments.
To install SharePoint Services 3.0, you'll need to have already installed .NET Framework 3.0. Before you launch the SharePoint Services 3.0 setup, log on to the server using an account that has administrative privileges. This account will be the initial owner of the SharePoint Central Administration site and the default SharePoint Services team site. You can easily configure the account to receive alerts related to the health and usage of the SharePoint Services server farm and sites, so you might want to use a domain user account in the Administrators group on the server, rather than the local Administrator account.
The SharePoint Services 3.0 setup will automatically configure the Windows Internal Database, a “lite” instance of Microsoft SQL Server (which is listed as SQL Server 2005 Embedded Edition in SharePoint Services), on the server. However, for a production rollout you'll certainly benefit from the scalability and manageability provided by SQL Server, and SharePoint Services lets you run with a separate SQL Server installation to host the configuration and content databases.
When the installation is complete, run the SharePoint Products and Technologies Configuration Wizard from the Administrative Tools folder on the SharePoint server. The wizard initializes SharePoint Services 3.0 and creates the first two SharePoint applications: the SharePoint Central Administration site, and the default content site based on the Team Site template. You can visit the default site at the URL, http://servername, which Figure 1 shows. Take a quick look, but don't change anything until you've configured your server.
The Central Administration home page reveals a task list of important, post-setup configuration procedures, which Figure 2 shows. Click each procedure to read more about it, then mark the item as complete after you've performed the operation. I would suggest making it a priority even for this simple SharePoint site to assign a second farm administrator and to configure outbound email settings for the server farm. You can perform these tasks by using Update Farm Administrator's Group and Outbound Email Settings, respectively, at the task list or from the Operations tab. You can create, delete, and manage Web applications by using the Central Administration site's Application Management tab. Using the links on that tab, set the time zone.
Within each application is one or more site collections, each consisting of a top-level site and one or more child sites. Each site contains lists, or data tables, such as task lists, contact lists, and document libraries. Each list contains items: records or documents, for example. If you're unfamiliar with the structure of a SharePoint implementation, visit http://www.MyOfficePro.com and look for the article “Windows SharePoint Services, an out-of-box learning experience.” See also the Exchange & Outlook Administrator article, “Making Sense of SharePoint Portal Server Architecture,” August 2006, InstantDoc ID 93082.
In the example we're creating in this article, we'll make our intranet home page be the default site collection at the root URL of our default Web application. At the top-level site, we'll allow any user, even anonymous users, to have read-only access to that site. Beneath the top-level site, we'll create departmental subsites, readable by all authenticated users. Users in a department will have higher levels of access to create and manage content based on the functionality and resources in their department's site. Beneath departmental sites, we'll have project or team sites for secure collaboration and document sharing. So the URL namespace will be http://servername for the home page (site collection and top-level site), http://servername/department for the department, and http://servername/department/project-or-team for collaboration.
Where SharePoint Services 2.0 placed actions clumsily in a top-of-page bar, SharePoint Services 3.0 consolidates actions into toolbars and drop-down menus. Click the Site Actions menu box on the upper-right side of the window to expand the drop-down menu. Select Site Settings, which opens a significantly improved dashboard of site-administration options, as Figure 3 shows.
In Site Settings, look for the options listed beneath Users and Permissions. You'll see the Site collection administrators link, which you'll use to add an additional administrator for the site collection. Click People and groups to begin assigning access to the site. You'll see three default groups displayed: the Owners group, which has full control of the site and its content; the Members group, which can contribute to the site; and the Visitors group, which has read access to the site. For each group, navigate to Settings, Group Settings to rename each group to make it more meaningful for your users, then, on the toolbar, click New, and choose Add Users to add members. For the intranet home page, the Members group might include your communications team.
Alternatively, you could enable anonymous access, at least to the intranet toplevel site. To do this, open the Central Administration page, select the Application Management tab, and click Authentication Providers. Click Default and modify the authentication provider settings to enable anonymous access. Then, back in the Site Settings of the site itself, click Users and Permissions, Advanced permissions, and select Settings, Anonymous Access to determine what level of access non-authenticated users can have to the site. For an intranet, you might choose to let anonymous users access the entire site. If you choose to restrict anonymous access to lists and libraries, you'll need to continue and enable access for anonymous users to each appropriate list and library. Remember that subsites inherit permissions, so you'll want to disable anonymous access to departmental or team/project subsites, which are likely to contain more sensitive information than the intranet home page.
In SharePoint Services 3.0, you don't need to use standard IIS tools to enable or disable anonymous access. In fact, as of press time, you must use Central Administration to fully enable authentication for anonymous access. From configuring service account credentials to backing up and restoring sites, you'll find welcome new support for SharePoint Services administrative tasks within the Central Administration and Site Settings pages.
While you're still in the Shared Document Library, click the Settings menu in the toolbar and choose Document Library Settings. You can fully manage and customize all lists (and document libraries are a type of list) by using this Settings page. Use the links in the General Settings section to change the title of the document library to something like “Intranet Site Elements” and to remove it from the Quick Launch view, since users won't need easy access to the library.
Return to the home page again by clicking Team Site in the upper-left corner. In SharePoint Services 3.0, the top and left panels of a SharePoint site help you navigate. The top panel's navigation bar, which Figure 1 shows below the URL, represents the site structure by default. Initially, you'll see only one tab for the top-level site, in this case, the Home tab. But as you add sites, each site becomes a tab. Additional navigation is enabled by the site's left navigation panel, which contains the Quick Launch view by default.
You can also navigate using the “breadcrumb control,” which shows the path to the current page. Figure 3 shows the breadcrumb to the Site Settings page: Windomain Intranet>Site Settings.
Unlike SharePoint Services 2.0, in version 3.0 the Quick Launch view appears on every page, and both the top navigation and Quick Launch bar can be easily edited or hidden entirely at the Site Settings page. Click Site Actions and select Site Settings, Look and Feel, Quick Launch. Click the Edit icon and delete the headings Documents, Discussions, and People and Groups, and the Tasks list. Change the heading “Lists” to “Company.” Check out the results by returning to the home page. Alternatively, return to Site Settings, Look and Feel, and, from the Tree View link, disable the Quick Launch altogether, since the top navigation tabs will provide navigation to departmental sites.
To modify the site title and to paste in the hyperlink to your small logo as the icon, use Site Settings, Look and Feel, click the Title, description, and icon link. Experiment with color schemes by using Site Themes to find an appropriate Web-site color scheme.
Return to the home page and click Site Actions, Edit Page. The home page, a section of which Figure 4 shows in Edit Mode, is an example of a Web Part page. To modify a Web Part's properties, click the Edit link. Here is where you can change the Site Image to link to your large logo.
In our departmental site, let's leverage three great new capabilities of SharePoint Services 3.0. Click Site Actions, select Create, Wiki Page Library and name the library “IT Wiki.” Wikis are a fantastic tool for a capturing knowledge.
Link to another page by using the syntax page name can contain spaces. For example, you might have a message at your site: “Don't forget to bring your family to the upcoming corporate baseball games. The schedule is on the Baseball Schedule page.” Clicking the link Baseball Schedule brings the user to the existing Baseball Schedule page or, if that page doesn't exist, will create a new page called Baseball Schedule. So it's easy to create a new page from an existing page by creating a link to a nonexistent page, then clicking the link.
Blogs are another useful tool for unstructured knowledge capture. Click Site Actions, select Create, Sites and Workspaces and create a blog site named IT Blogs and the URL blogs/, also using unique permissions so that you can control who is allowed to blog to the site.
Security also extends to the UI, with “security trimming.” If a user doesn't have permission to see part of a SharePoint site, links to that part of the site won't be displayed in the UI. For example, you can configure permissions so that an administrator of a team site can see the Site Actions option but readers can't.