Professional Documents
Culture Documents
This document is for informational purposes only. MICROSOFT MAKES NO WARRANTIES, EXPRESS
OR IMPLIED, IN THIS DOCUMENT.
Microsoft, Outlook, SharePoint, Windows, Windows Server, MSDN, Active Directory, Visual Studio, FrontPage, BizTalk, Visio,
PowerPoint, OneNote, InfoPath, Great Plains, Windows NT and Visual Basic are either registered trademarks or trademarks of
Microsoft Corp., Great Plains Software Inc. or their affiliates in the United States and/or other countries.
Great Plains Software Inc. is a wholly owned subsidiary of Microsoft Corp.
The names of actual companies and products mentioned herein may be the trademarks of their respective owners.
Contents
September 2003................................................................................................................... ......................1
For more information:....................................................................................................... ........................1
Contents.................................................................................................................................. ...................2
Abstract................................................................................................................................... ...................1
Introducing Microsoft Office SharePoint Portal Server 2003....................................................... ..........4
Product Overview................................................................................................................ ......................5
Top 10 Product Benefits.................................................................................................................. ..........8
SharePoint Portal Server 2003 Features....................................................................................... .........16
Tour............................................................................................................................................. ..............25
Server Installation.................................................................................................................................. .26
Portal Configuration.............................................................................................................................. ..33
Configure Portal Home Page...................................................................................... ...........................37
Creating Sites and Libraries................................................................................................... ................42
Personalization Configuration..................................................................................... ...........................52
Integration......................................................................................................................... .....................57
Appendix A: Windows SharePoint Services and SharePoint Portal Server 2003 Integration With the
Microsoft Office System................................................................................................................. .........63
Appendix B: Windows SharePoint Services Features...................................................................... ....71
Appendix C: System Requirements....................................................................................................... .78
Abstract
Many sites and portal solutions lack end-to-end access to organizations’ institutional information, which is
typically housed in disparate sites, sources, resources and formats. A large portion of this information is
locked up in “islands” across an organization, such as these:
Line-of-business databases, such as SAP financial systems and Siebel customer relationship
management systems, which require specialized training and permissions to access and use
Enterprise project resource files, which also require specialized access
Locally hosted and managed team and document collaboration sites
Individual users’ hard disks and minds
Top-down monolithic solutions, which provide control in the form of centralized management and
administration, have proven hard for businesspeople and end users to utilize, because the tools lack the
flexibility and agility to work together and get work done.
Bottom-up, isolated solutions serve the short-term purpose of allowing end users and businesspeople to
work together, but they create other islands of information that are disconnected from the rest of the
enterprise. As a result, businesses suffer because users are unlikely to discover information, use and
reuse it, and share it across other teams and projects. Such isolation also is less than ideal from an
information technology (IT) perspective, because those offline systems are not backed up and, therefore,
are unlikely to be restored in an outage. They are vulnerable to virus attacks and cannot be archived.
Both top-down and bottom-up solutions still exclude the end user — even though 80 percent of an
organization’s information lives on individual hard disks and in personal files. And studies have shown that
employees get 50 percent to 75 percent of their relevant information directly from other people.1
The challenge to businesses is huge. Currently, many business users make critical decisions about individual
and team productivity, revenue generation, and cost reduction without incorporating key pieces of information;
it’s usually just too difficult to get the information using current tools.
In addition, when IT departments need to corral information from disparate sites, sources, resources and
formats, they either lack the tools they need to aggregate, organize and expose that information to the rest of
the company in an easily usable manner, or the available tools are difficult to use. In addition, the available
ongoing administration and maintenance tools require expensive programming expertise.
Furthermore, developers — both in-house and partners — often are asked to tie together information to build
custom applications from hundreds of back-end sources, but they frequently lack the myriad skills that are
required to tap those stores. Few developers have the knowledge to access the many back ends and
1
“The Knowledge Worker Investment Paradox,” Gartner Inc., July 17, 2002
Finally, end users have difficulty using the specialized information access tools; they want the familiar
applications that they use every day, such as Microsoft® Office, the Microsoft Outlook® messaging and
collaboration client, and Web browsers.
Clearly, a need exists to aggregate all of the information from back-end sources — enterprise project
resources, line-of-business databases, team collaboration sites and individual end-users’ desktops — to make
it accessible to everyone in an organization. This would allow the following:
Business users could make more informed decisions by having all of an organization’s information readily
available.
IT departments would have a simple method to manage, administer and track IT-hosted, business-user-
and end-user-focused sites and resources.
Developers could use a common platform with easily understood services and tools to unlock information
tied up in multiple back-end stores.
End-users could employ the tools that they are accustomed to using to do their jobs.
Both Windows SharePoint Services and SharePoint Portal Server 2003 sites take file storage tasks, such as
saving and sharing information, to a new level. They provide communities for team collaboration, empowering
users to work together on documents, tasks, contacts, events and other projects. They enable team and site
managers to easily manage site content and activity, and the environments are designed for straightforward
and flexible deployment, administration and application development.
Together, SharePoint Products and Technologies deliver highly scalable collaboration solutions with flexible
deployment and management tools. They provide out-of-the-box value and serve as a platform for
development of extended applications. Windows SharePoint Services delivers sites for team collaboration,
productivity and information-sharing, facilitating large numbers of smart teams. SharePoint Portal Server 2003
connects these sites, people, knowledge and business processes, facilitating smart organizations.
Welcome to the Microsoft Office SharePoint Portal Server 2003 customer guide. This guide provides an
overview of the collaboration solution that SharePoint Portal Server 2003 offers and design goals of the
product, a description of the new and improved product features, and a hands-on tour of the main feature
areas. The purpose of this document is to give customers a solid understanding of the design goals and
feature set for SharePoint Portal Server 2003 and a familiarity with the product implementation.
This release of SharePoint Portal Server 2003 takes full advantage of the new Microsoft Windows Server
2003 operating system technologies and the Microsoft .NET application development framework, which is
delivered as part of Windows Server 2003. This development work has greatly increased the reliability and
scalability of the portal to allow even the largest organization to deploy one platform that supports people,
teams and the enterprise as a whole. SharePoint Portal Server 2003 is built on top of Microsoft Windows
SharePoint Services (previously called SharePoint Team Services), providing rich collaborative functionality
throughout. This tight integration makes the creation of, participation in and management of team-based
applications a seamless experience.
• Online documentation is available to help install SharePoint Portal Server 2003 along with the Tour
section of this document.
• The Microsoft MSDN® Web site offers numerous technical resources from a developer perspective about
SharePoint Products and Technologies at http://msdn.microsoft.com/sharepoint/.
• The Microsoft TechNet Web site provides a clearinghouse of resources to help you deploy, maintain and
support SharePoint Portal Server 2003 at http://www.microsoft.com/technet/.
• SharePoint Portal Server 2003 is tightly integrated with Windows Server 2003 and the Microsoft Office
System business productivity applications. To obtain customer guides for these products, please contact
Microsoft.
Microsoft encourages you to use these documents as aids in installing and using SharePoint Portal Server
2003.
At the foundation of SharePoint Portal Server 2003 is Windows SharePoint Services, which SharePoint Portal
Server 2003 leverages to create portal pages for people, information and organizations. Windows SharePoint
Services is the engine for creating Web sites that enable information-sharing and document collaboration,
increasing individual and team productivity. It is also a key piece of the Information Worker Infrastructure that
Windows Server 2003 delivers, providing team services and sites to Microsoft Office System desktop
programs, as well as serving as a platform for application development. SharePoint sites take file storage
tasks, from saving to sharing information, to a new level. They provide communities for team collaboration,
empowering users to work together on documents, tasks, contacts, events and other projects. They enable
team and site managers to easily manage site content and activity, and the environments are designed for
straightforward and flexible deployment, administration and application development.
Ultimately, Windows SharePoint Services delivers sites for team collaboration and productivity, facilitating
large numbers of smart places. SharePoint Portal Server 2003 connects these places, people, knowledge and
business processes, facilitating smart organizations. Although these sites are specific to SharePoint Portal
Server 2003, they utilize technologies such as Web Parts and Document Libraries that the Windows
SharePoint Services platform delivers. This solution provided by SharePoint Products and Technologies
greatly reduces the time and cost associated with development, training and support. SharePoint Portal
Server 2003 further extends the capabilities of Windows SharePoint Services sites with its organization and
management tools, and it enables teams to share their site information with an entire organization.
Organizations can enable users to create and manage their own rich and easy-to-build SharePoint sites and
allow these sites to be discovered throughout the organization.
Moreover, SharePoint Products and Technologies add entire classes of functionality to the enterprise,
connecting people, teams and knowledge across business processes. SharePoint Portal Server 2003
integrates information from various systems into one solution with extremely flexible deployment options and
management tools. Organizations can start small with one server and then build their portal presences by
using a division-driven, bottom-up deployment methodology. When additional capacity is needed, they can
simply increase the number of servers with services to meet the demand. Alternatively, it is also possible to
implement a top-down deployment portal structure, with federated portal services to meet the needs of
SharePoint Portal Server 2003 enables a single point of access to multiple systems such as Microsoft Office
System programs, business intelligence and project management systems, and existing line-of-business
applications, including third-party and industry-specific applications such as those from SAP AG, PeopleSoft
Inc. and Siebel Systems Inc. The portal is built on a scalable, highly distributed architecture with flexible tools
for deployment, development and management, enabling it to grow with an organization’s needs. The overall
portal integration features allow users to harness information to make better use of their existing corporate
data. Users can extract and reuse timely and relevant information from systems and reports and quickly
locate and access documents, projects and best practices from across the company. In addition to its search
technology (developed by Microsoft Research), which provides the most accurate relevancy-ranked search
results available, the portal enables users to organize documents and information by topic and browse for
relevant content. To help users make better use of the data, alerts automatically notify users when information
has been added or changed.
The latest version of SharePoint Portal Server 2003 continues to enhance integration with Microsoft Office
System programs. Users can create document and meeting sites from Microsoft Outlook 2003, and
collaboration around live documents stored in SharePoint sites is enabled directly in Microsoft Office System
programs. Other SharePoint site information, such as task lists, links and team member presence, is also
available in Microsoft Office System program task panes.
SharePoint Portal Server 2003 provides a powerful collaboration environment for individuals, teams and
divisions. It enables organizations to aggregate, organize, find and provision SharePoint sites across the
enterprise. SharePoint sites for teams, documents and meetings also can be extended to customers and
partners, augmenting the reach and efficiency of existing collaboration methods. SharePoint Portal Server
2003 further facilitates end-to-end collaboration by delivering familiar document and content collaboration
tools. Document versioning, approval workflow, check-in and checkout, document profiling, and publishing
facilitate easy collaboration on documents, projects and tasks. In addition, SharePoint Portal Server 2003
enables information workers to easily find and leverage people, teams and existing best practices instead of
duplicating the work of others.
SharePoint Portal Server 2003 enables IT departments and users to customize and personalize the portal
experience. Relevant content, such as line-of-business and Microsoft Office System programs, Web services,
news, sales and other company data, is delivered to the portal through Web Parts. Users inside an
organization can use the Web Part galleries to add information to a portal site such as a My Site without
extensive Web development knowledge. They also can personalize the organizational or divisional pages
within secure boundaries set by IT departments, and the portal remembers those views and displays them
from any computer that the user accesses. In addition, IT departments can “lock down” specific Web Parts or
page zones to enable specified users to control content. Organizations can also use the portal to distribute
important information to all employees.
The portal also enables users to find relevant information quickly through customization and personalization
of portal content and layout, as well as by Audience Targeting. Audience Targeting enables delivery of
information and updates via notifications or Web Parts to individuals based on their organizational roles, team
memberships, interests, security groups or any other definable membership criteria. Users can create and
manage personal sites called My Site and personalize them with Web Parts, links that they choose to share
with colleagues, and links that they maintain for personal use.
5. Single sign-on
SharePoint Portal Server 2003 provides content and access to applications based on user credentials that are
stored in SharePoint Portal Server 2003. Single sign-on allows the mapping of account credentials so that
users do not have to sign on again when portal-based applications retrieve information from business
applications such as third-party enterprise resource planning and CRM systems.
6. Web Part pages and managed .NET Object Model and Web services
SharePoint Portal Server 2003 provides additional Web Parts and Web Part flexibility through personalization
and the ability of end users to customize portal pages in ways that make sense for them by simply dragging
and dropping Web Parts onto a page. With Microsoft Office FrontPage 2003, there is full support for Web
Parts and Web Part pages, including adding, editing and customizing Web Parts, Web Part zones, and
custom Web Part pages inside SharePoint Portal Server 2003. SharePoint Portal Server 2003 is built on
Microsoft ASP.NET, which dramatically reduces the number of lines of code necessary for similar operations
with ASP, in addition to being more responsive, scalable and secure. In addition, customers will find many
Web Parts to choose from in the Web Parts galleries that ship with SharePoint Portal Server 2003, as well as
online at http://www.microsoft.com/sharepoint/.
7. Topics
SharePoint Portal Server 2003 includes topics that provide intuitive navigation for finding and browsing all
types of content, from documents and people to sites based on Windows SharePoint Services. A document or
9. Search
SharePoint Portal Server 2003 provides a full-text search option to search document text and document
properties for the keywords that the user enters. Not only can users search for information, but they can
browse and search for people, teams and other sites on the portal.
Feature Description
.NET platform integrates information from various systems into one solution.
Team sites Team sites are integrated with the portal because they can be provisioned
New directly from the portal and appear in the site registry for easy
discoverability and scheduled indexing. Team sites can be connected to
the portal to enable such things as searching the portal from the team
site, clicking on names in the team site to get to user profile pages in the
portal, and inserting simple links to add information from the team site to
categories and personal sites on the portal.
Active Directory integration SharePoint Portal Server 2003 performs Active Directory crawls to
New capture user profiles. Once those are stored, users can add profile
information and also create alerts to profiles to see when their subscribed
person publishes or changes information. Users can manage their profile
information from the portal. This integration easily helps users create
Audiences from existing distribution lists and security groups.
.NET Enterprise SharePoint Portal Server 2003 centralizes information from different
New systems by using the Microsoft .NET Platform, Visual Studio .NET,
ASP.NET, Common Language Runtime, Web Forms and Web Part
pages, and a secure infrastructure.
ASP.NET ASP.NET dramatically reduces the number of lines of code required to do
New similar operations with ASP, in addition to being more responsive,
scalable and secure. ASP.NET has many new features that make
developing portal applications easier. For example, session states now
work in a server farm running SharePoint Portal Server 2003, and
ASP.NET code makes it much easier to both service and initiate Simple
Object Access Protocol (SOAP) application programming interface (API)
calls, allowing customers to leverage SharePoint Portal Server 2003
collaborative services in their applications.
Group-based security In SharePoint Portal Server 2003, groups can be used to control access
to content. SharePoint Portal Server 2003 also offers the option of
denying a user access to pages, sites and libraries based on group
membership or role.
Flexible people profile By providing a directory of people that is searchable, relational and
schema updatable, SharePoint Portal Server 2003 delivers a method to leverage
people and skill sets. People profiles include not only organizational
New
information such as contact information but also published information
such as related links and recent documents shared by the profile owner.
Profile properties can also be imported from Active Directory.
Distributed security SharePoint Portal Server 2003 takes the ability provided in SharePoint
Enhanced Portal Server 2001 to distribute security on a folder-by-folder basis one
step further. Ownership of the portal hierarchy can be distributed
throughout the organization to topic matter experts for the most efficient
administration of content and layout.
SharePoint Portal Server offers easy access to relevant information across multiple systems.
Full-text search SharePoint Portal Server 2003 provides a full-text search option to search
Enhanced document text and document properties for the keywords that the user
enters. SharePoint Portal Server 2003 finds all documents that match the
search and returns a list of results. For a more specific search, users can
use the Advanced Search option to find search criteria in specific
document properties, such as author. Users can also use a search scope
to search only a specific set of documents, such as a folder for press
releases or a supplier’s Web site. In SharePoint Portal Server 2003,
searching is enhanced by being able to search more sources, such as
people.
Content sources By using a wizard to add a content source, administrators have greater
Enhanced control of how content is indexed, can identify the location of the content
that should be made available for searching, and can link that content to
the portal site. SharePoint Portal Server 2003 then indexes information
from each content source for quick searches from the portal site. The
addition of content sources makes the portal site the easiest place to find
information, regardless of the content’s location or format.
Alerts for people, news, It is possible to receive alerts for a variety of atomic portal items. Users
topics, documents, Windows can request alerts about a person who is relevant to their work and be
SharePoint Services folder, notified any time that person publishes a new document or changes his or
lists items and Site Directory her profile. SharePoint Portal Server 2003 provides enhanced alert
capability through the ability to summarize alerts on the user’s personal
Enhanced
page, as well as the ability to subscribe to a person.
Crawling wide range of SharePoint Portal Server 2003 has additional searching (or “crawling”)
sources capabilities that are enhanced over those provided in SharePoint Portal
Enhanced Server 2001. SharePoint Portal Server 2003 uses protocol handlers and
the gatherer to crawl and provide searching over data from diverse
content sources. Out of the box, SharePoint Portal Server 2003 can crawl
documents from these sources:
• Windows SharePoint Services sites
• Hypertext Transfer Protocol over Secure Socket Layer (HTTPS) sites
• File systems
• Web sites
• Computers running Exchange 2003 Server, Exchange 2000 Server
and Exchange Server 5.5
• Lotus Notes servers
• Other SharePoint Portal Server 2003 workspaces
SharePoint Portal Server 2003 also can search any content source that
can be accessed programmatically via the search software development
kit (SDK) protocol handler extensions.
.NET Query provider SharePoint Portal Server 2003 uses Structured Query Language (SQL)
Enhanced full-text extensions. Queries are submitted using SOAP. More information
can be found in the SharePoint Portal Server 2003 SDK.
Grouping results by author, SharePoint Portal Server 2003 search functionality is sortable, thorough
site, date and category and integrated. Users can collapse or expand the results by site while
New pivoting the view by date, person or site. Search results return all results
necessary for information workers to find and leverage information.
Pinning Every item can be tagged to My Site so that a link for all pinned items
New appears on My Site. This allows users to easily store links of all items of
interest in one location.
Collaboration Features
• Wizard-based administration enables information workers to create SharePoint sites and invite co-
workers, partners and customers to join with appropriate levels of access.
• Users can search file servers, Web servers, Exchange public folders, Lotus Notes and databases for
relevant information.
• Users can check in and check out content, create new Document Workspaces, and see member
presence information from Microsoft Office System applications or the Web front end. Automatic
versioning, approval routing, profiling and metadata capturing of documents facilitate content
collaboration.
Feature Description
SharePoint Portal Server 2003 helps facilitate end-to-end collaboration.
Web sites based on SharePoint Portal Server 2003 allows users to create Web sites based on
Windows SharePoint Windows SharePoint Services directly from the portal. These sites provide a
Services place on the intranet where teams can communicate, share documents and
work together on a project.
New
Add/delete/edit site to The Sites Directory included with SharePoint Portal Server 2003 provides a
Sites Directory “white-pages” view of all the sites important to an organization. Users can enter
New sites, and SharePoint Portal Server 2003 provides a link to all team sites that
have been provisioned from the portal.
Rich site support The UI is modeled after the traditional ease of use found in Web-based
(save to, drag and applications. With minimal or no training, users can create, post and find
drop any list type) information while working in a productive, collaborative way with their
colleagues.
New
SharePoint Portal Server 2003 allows users to create team community through a single place to capture
ideas, information, communication and documents.
Multiple file upload Users can upload one or many files into a SharePoint Portal Server 2003 list
New through the multiple file upload feature.
Rich list editing SharePoint Portal Server 2003 builds on the great list capabilities of SharePoint
features Portal Server 2001, enabling the rapid capture and editing of team contact lists
and the creation of discussions, surveys and Document Libraries. These
Enhanced
capabilities allow for the easy creation of digital workplaces that facilitate
collaboration among teams.
Web storage system- The Web storage system Document Library features in SharePoint Portal
based document Server 2001 (such as versioning, check-in and checkout, document publishing,
libraries and approval routing) also are available in the document management portion of
SharePoint Portal Server 2003.
Discussions Through Web discussions, users can conduct online discussions about a
document without modifying it. Instead of using e-mail to discuss a document or
trying to capture conversations about a document, authors and reviewers can
now communicate with each other through Web discussions. Simultaneous
discussions about a document can occur even if one person has the document
checked out. Comments and replies are grouped and stored as threaded
conversations.
Editing in grid mode Users can use familiar Excel commands such as Fill when editing a list. This
New feature facilitates the editing of list and Document Library metadata by enabling
users to edit list data in a familiar Excel grid mode format.
Creating a list from a Custom lists can be created from Excel spreadsheets by using the spreadsheet
spreadsheet data as the source of columns and choices.
Feature Description
SharePoint Portal Server 2003 helps empower employees by enabling end-user personalization of content.
Personalized views SharePoint Portal Server 2003 stores a personalized view of the portal for each
New user. This enables the user to configure the site in the way that works for him or
her and to access the same view and layout in each portal visit.
Personalized In SharePoint Portal Server 2001, personalization was limited to Web Part login
selection of Web awareness and the Personal Dashboard page. Now users can add Web Parts to
Parts the Web Part pages for which they have personalization rights, and they can
overlay fixed pages with their own customizations. Because the Web Part library is
Enhanced
owned and maintained by a central IT organization, the Web Parts available to end
users can be tested before end users implement them. In addition, the portal
administrator can lock down certain pages or Web Parts that are necessary for
each user so that he or she has a consistent Web experience.
Alerts Users are notified of changes made to items to which they have subscribed,
Enhanced including documents, sites, people, news, lists, list items and the Sites Directory.
Users can decide whether alerts should be sent via e-mail and if they should
receive a notification for each change or a daily summary.
Alerts integration Alerts, previously knows as Subscription Notifications, sent from SharePoint
with Outlook Products and Technologies via e-mail can be managed in one place and are given
special handling by Microsoft Office Outlook 2003.
New
My Site My Site is an individual SharePoint Portal Server 2003 site that provides
New personalized and customized information. My Site has both a public and private
view, so users are able to store personal content that only they can view (such as
unfinished documents, news content and links), as well as public content to push
information to other users. My Site provides quick access to resources that users
need to do their work, such as links to documents, people or Web sites, as well as
personal alerts created to track changes to content in the portal and the
organization as a whole. Public profile information can be synchronized from
directory sources such as Active Directory.
My Site Web Parts My Site pages can be customized with Web Parts such as Documents by me, My
New Links, My News and Exchange Server 2003 Inbox, Tasks and Calendar Views.
Documents by me creates a list of recently authored documents. My Links (public
and private) allows users to publish links to their site that are visible only to them
or to a broader (defined) audience. My News is a Web Part in which news is
aggregated for each user based on interests and audience. Exchange Server
2003 Inbox, Tasks and Calendar Views expose a user’s Exchange information.
SharePoint Portal Server 2003 allows users to present specific applications and content based on the
user’s functional group and organizational role.
Audiences Contentis organized and targeted to Audiences in the portal so that users receive
New information that is most relevant to them. Links, Web Parts, lists and news items
all can be targeted to one or more specific Audiences. Examples of Audiences are
“everyone in Building One” or “all employees in the finance division.”
Audience rules Users can create Audiences by using simple rules based on Active Directory
New security groups and distribution groups. These criteria can be used alone or in a
combination of up to six clauses for complex and flexible rules. These Audience
rules allow for flexible and dynamic Audiences throughout the organization and for
the targeting of Web Parts and content to the appropriate Audience.
SharePoint Portal Server 2003 offers one place that remembers who users are and how they work.
Personalization The personalization object model enables programmatic access to personalization
object model features.
New
Installation. SharePoint Portal Server 2003 has the richest out-of-the-box experience in the portal market.
The guide walks through installation of Windows Server 2003, Microsoft SQL Server™ (if using SQL
Server), SharePoint Portal Server 2003 and key Microsoft Office System components.
Collaboration. SharePoint Portal Server 2003 is a superset of Windows SharePoint Services and provides
the best team site integration available. The tour walks through creating and importing team sites and
creating libraries to store critical business documents and data.
Personalization. SharePoint Portal Server 2003 has very rich personalization services including My Sites,
links targeting, Web Part targeting and other features.
Configuration. The tour will guide the user through many of the configuration options such as security, Web
Parts, adding metadata, and configuring areas and topics.
Integration. SharePoint Portal Server 2003 offers the richest Microsoft Office System integration in the
industry, and the tour will walk users through integration examples.
Search. Although many portal solutions offer advanced searching as a separate product to purchase,
SharePoint Portal Server 2003 provides industry-leading search out of the box.
Microsoft Office SharePoint Portal Server 2003 requires Windows Server 2003. For the richest possible tour
experience and to showcase as many of the new product features as possible, we recommend a client
computer with Office 2003 installed. To complete the tour, we recommend that you install and configure the
products on two computers as shown in Table 5. The goal of this tour is to allow a reviewer to quickly explore
the powerful portal and collaboration features available in Microsoft Office SharePoint Portal Server 2003.
For additional information please refer to the administration guide or contact your Microsoft contact.
Server Installation
The following sections will walk you through the installation and configuration of your server to review the
features in SharePoint Portal Server 2003. For the optimal user experience, you will need software for
Windows Server 2003, Microsoft SQL Server 2000 Standard or Enterprise Edition with Service Pack 3,
Microsoft Office SharePoint Portal Server 2003 and Windows SharePoint Services, Microsoft Office 2003 and
Microsoft Office FrontPage 2003.
1. Prepare system for installation (new system by installing BIOS or other hardware configuration utilities)
and format disk with NTFS file system.
2. Insert Windows Server 2003 CD.
3. At setup notification screen, select <ENTER>.
4. At the Welcome to Setup screen, select <ENTER>.
5. During setup, join your computer to a domain.
6. System Activation: After installation, obtain a valid IP address and connect to the Internet. Click on the
system activation icon and select “Yes, let’s activate Windows over the Internet now.” Or, if you are not
connected to the Internet, select, “Yes, I want to telephone a customer service representative to activate
Windows.” Select “Next.” At the “R register with Microsoft?” screen, decide whether you would like to
register. If you would, follow the instructions on the screen. If you choose not to register, select “No” and
then “Next.” When you have successfully activated the software, click on “Close.”
Note: To complete the rest of the tour setup, we recommend that your computer be a member of a domain.
You must be logged on as a local computer administrator. You may use a domain user that has local
administrator privileges, or you may use the local administrator account.
Microsoft SQL Server 2000 Standard or Enterprise Edition With Service Pack 3
SharePoint Portal Server 2003 supports both Standard and Enterprise Editions of Microsoft SQL Server 2000.
Follow these steps to install Microsoft SQL Server 2000 Standard or Enterprise Edition with Service Pack 3.
Insert the Microsoft SQL Server 2000 Standard or Enterprise Edition CD.
Select “SQL Server 2000 Components” on the autorun screen.
Select “Install Database Server.”
Note: Internet Explorer also must be configured to bypass local addresses. To do this, open Internet Explorer
and click on “Tools,” then on “Internet Options.” On the Connections tab, click on the “LAN Settings” button.
Make sure the “Bypass proxy server for local addresses” checkbox is enabled. Click on “OK” twice to close
Internet Explorer properties. Close Internet Explorer.
4. A dialog box will inform you that certain services on your computer will be stopped for the installation.
Click on “OK” to proceed with the installation.
5. Click on “Next” on the first screen in the Welcome to the Microsoft Office SharePoint Portal Server 2003
Setup Wizard. This wizard helps you install Microsoft Office SharePoint Portal Server 2003.
6. Agree to the End User License Agreement.
7. The product key screen should have a product key already entered. Click on “Next” to proceed.
8. At the Installation Type and File Location screen, select “Install without database engine” with the default
file locations as shown in Figure 9:
• Programs: C:\Program Files\SharePoint Portal Server
• Data: C:\Program Files\SharePoint Portal Server\DATA
9. Select “Next.”
10. Select “OK” in the “Microsoft SharePoint Portal Server setup has completed successfully” dialog box.
3. Create a portal for Server revguide (or whatever your preferred portal name is) as shown in Figure 10.
• In the Site Name box, type the name of the portal. The site name appears at the top of most portal
pages.
• In the virtual server list, select the existing virtual server on the machine that will host the new portal.
In most cases, the virtual server will be the default Web site.
4. In the Create Portal Confirmation for the server, you will receive the following message:
“You have chosen to create a new portal in a virtual server that is not empty. Any custom information that
you have added to this virtual server since its creation will be made unavailable. Are you sure you want to
continue? To continue creating the portal, click OK. To cancel creation of the portal, click Cancel.”
Click on “OK.”
5. Portal creation is completed, and the admin page is opened as shown in Figure 11.
6. Now that the portal has been created, the reader should establish file entries for each computer that will
be accessing the portal for URL name (e.g., http://revguide/) and local IP address.
• Configuring SMTP and SharePoint Portal Server 2003 e-mail settings to provide portal integration with
corporate e-mail systems
• Adding users and site groups as a basis for defining portal security
4. Select “Submit.”
1. Add local users to the local group if the SharePoint Portal Server is a member of a domain.
2. Add local users to the local group if no domain security groups are available.
3. Go to Site Settings.
4. Select “manage users.”
5. Within the Add Users section, do the following:
6. Choose users. Enter aliases for each user, separated by a semicolon. Select “Next.”
7. Select site roles. Assign a site role (e.g., “contributor”) to each user. Select “Next.”
8. Confirm users. Confirm users by adding e-mail addresses if appropriate. Select “Next.”
9. Send e-mail. You may choose to send e-mail to users to let them know they have been added to the site.
Select “Next.”
10. You can use both user aliases and security groups to assign permissions. For example, if you want to
grant contributor rights to the local user group, you would enter <computer name>/users for the alias, and
select the contributor site role, and select “Next.”
Manage Audiences
Managing Audiences is part of the advanced personalization capability of SharePoint Portal Server 2003.
Links, Web Parts and other content can be targeted to members of Audiences. An Audience can be defined in
the portal or imported from Exchange distribution lists.
Go to Site Settings.
Select “manage Audiences” (bottom of page).
A. From the home page, select “Sites” in the top navigation bar of the page.
F. Select “OK.”
G. For the “Add link to New Site” page, leave the defaults as they appear and select “OK.”
H. Very Important: DO NOT Select a template here. Simply close the browser window by clicking on
the “X” in the upper right-hand corner. The importing process will fail if the site has any template
selected.
B. To change to the directory with the site migration utility, copy the text between the quotes and then
paste using a right-mouse click in the command window “cd Program Files\Common Files\Microsoft
Shared\Web Server Extensions\60\Bin.”
C. Select “Enter.”
D. Begin importing the site by copying the text in quotes and right-click-pasting it into your command
window. (Note: If your server URL is not revguide, please change the command line before pasting)
“smigrate.exe -r -w http://revguide/sites/vitamins -f c:\vitaminsite.fwp.”
E. Select “Enter.” Importing should begin; the command line will display the status. Once importing is
complete, you should be able to access your new team site.
Team sites have both a shared view, which is the default view for users coming to the site, and a personal
view, which is the view for each individual who has modified the site for his or her own purposes. For each
Web Part, the site designer can decide if users should be allowed to minimize, close or change zones as
appropriate to enforce the site goals. Figure 14 shows the shared view of our Vitamin Sales site.
Web Parts
The home page is composed of a collection of Web Parts and links to other areas of the portal. You can easily
customize the look and feel of the parts on this page. The following steps will show you how to move the
“Events” Web Part above the “News” Web Part on the page.
6. Drag and drop the “Events” Web Part above the “News” Part (note the yellow bar indicates the Web Part
is ready to be dropped).
7. Click on “View Page” in the left-hand navigation bar to save it, then click on “Refresh” in the browser tool
bar to see your changes.
3. Click on the icon next to “Projects,” and drag it up to drop as the first item under “Home” (the yellow bar
shows when the item is ready to be dropped).
Notice that the “Projects” Topic is now on the top navigation bar. We will explore how to create new Topics
next.
Topics
Create a new topic called “Portal Vendors.”
Click on “Topics.”
Areas
Areas are found under Topics in SharePoint Portal Server 2003. The next section shows you how to create a
new area under the “Portal Vendors” Topic called “Pure Play Portals.”
1. From the portal home page, select “Topics” from the top navigation bar.
6. Select “OK.”
This area is now ready to be populated with links, documents, Web Parts and other important information
relevant to the category.
Adding an Alert
Users can set alerts for any number of portal items such as people, news, topics, document, Windows
SharePoint Services folder, lists items and Sites Directory; when items are changed or discovered, alerts can
be sent via e-mail or captured in My Site in the alert summary.
2. Select “OK” on the Add Area Alert Page as shown in Figure 20.
The first step to creating a new Document Library is to create a site that will house or be the repository for the
new Document Library.
From the home page, select “Sites” in the top navigation bar.
Select “OK.”
For the “Add link to New Site” page, leave the defaults as they appear and select “OK.”
Your new site is now created. Because it was provisioned from the SharePoint portal, it is findable and
searchable from the SharePoint Portal Server 2003 Sites Directory. Figure 23 shows the Site Review site in
the Sites Directory.
If you are running Office 2003, you will have the option “(Upload Multiple…).” Select this option or select the
Browse button to upload a single file.
Your documents are now available on the site. Now we can associate any document with a portal area. To do
this, follow these steps:
Click on the drop-down list for the document that you just uploaded to the Document Library and select
“Submit to Portal Area” as shown in Figure 28.
Navigate to the Pure Play Vendors area page by selecting “Up to Reviewers Guide”; select the “Portal
Vendors” Topic on the left-hand navigation bar and then select “Pure Play Vendors” to see how the
document is now listed on the associated area page.
Document security is assigned at the Document Library level. This section shows how to assign security to
your new library.
From the Portal Reviews Site home page, select the “SharePoint Portal Review” library under the
“Documents” quick-launch category on the left.
Select the “Modify settings and columns” option on the left navigation bar.
Select “Next.”
Create a Survey
Surveys are a powerful and useful feature of SharePoint Portal Server 2003 team sites. You can quickly
develop a survey and send a link to a large audience via e-mail. The tool allows graphical views of the
responses, and access to the survey can be customized by role. Creating a survey follows the same process
as creating a list or other item in a team site. The steps below demonstrate this feature.
Now you can right-click on the house graphic and replace it with the Contoso graphic.
Click on “Save.”
SharePoint Portal Server 2003 sites are, in essence, FrontPage 2003 Web sites. This enables you to take
advantage of the rich page creation, editing and design capabilities that FrontPage 2003 has to offer. More
information on FrontPage 2003 and its rich features can be found at http://www.microsoft.com/frontpage/.
1. From the SharePoint Portal Review Document Library, select “Modify settings and columns.”
5. In the “Require that this column contains information” area, select “Yes” to make this a required field. Now
documents without this field cannot be checked into the library, although they can be uploaded.
6. On separate lines, enter “Draft,” “In Review” and “Published” as the options, as shown in Figure 33.
7. Leave the rest of the default options as they appear and select “OK.”
Future document uploads trigger a prompt to enter the profile fields before checking the document in.
Personalization Configuration
Now that we have the portal and site infrastructure in place, let’s have fun with enhancing a My Site to show
off the personalization features. The next five steps walk you through personalizing a My Site page with Web
Parts and content.
Personalize My Site
A user’s “My Site” is configured the first time a user accesses the feature.
2. “Creating my site” is displayed with a message that the process could take 10 to 20 seconds.
3. If you have Office 2003 installed, you will receive a pop-up asking if you would like to set this site as your
default personal site. Select “Yes.”
1. Select “Personalize this page” in the upper right-hand area of the page. (If you are logged on as a Site
Administrator, the link will say “Modify My Page.”)
2. Select “Add Web Parts” from the pull-down menu, and then “Browse.”
3. Drag and drop the “Page Viewer” Web Part (you may need to click on “Next” to see the remainder of the
list) to the top zone on your personal site.
1. In the “My Links Summary” Web Part, select “Add new link.”
4. Select the option “Share this link on my profile.” This option allows you to share links on your public
profile. This will be explained in more detail in the next section of the tour.
Public View
Users of SharePoint Portal Server 2003 have both a private and public presence on the portal. Let’s explore
the public view.
Select “Public” on the left navigation pane. Your screen should be similar to the one pictured below in Figure
38.
2. Add some text in the “About me” field. Notice that you can edit it with rich-text tools.
Shared links from the private view will show up in the public view. As you can see, the link created in the last
exercise is displayed.
Your public profile is where others in the organization can learn about the types of documents you author,
your reporting chain and other useful information. Information from the Active Directory can be automatically
synchronized with the portal and populated in the Organization Web Part.
Office 2003
Saving and Sharing Documents
Saving documents to team sites and to your personal site is extremely easy when Office 2003 is combined
with SharePoint Portal Server 2003. Let’s save a new document to our “My Site” Shared Documents folder on
the portal.
Select “File-Save.”
The document is now available to anyone with access to the portal from your public profile’s “Shared
Documents” link.
Documents can be saved and checked in directly from Office 2003. Try saving the document created above to
the Portal Reviews Document Library you created earlier in the tour.
6. Select “Save.”
8. Select “OK” to save and check the document into the library.
On the task pane, click on the top pull-down menu and select “Shared Workspace,” as shown in Figure 42.
You should see your server name in the “Location for new workspace” pull-down menu. If it is not
there, select “Type New URL” and enter the URL name (http://revguide).
Click on “Create.”
To access your new Document Workspace, click on the link at the top of the right task pane.
Search
SharePoint Portal Server 2003 offers advanced searching capabilities developed in the labs of Microsoft
Research. Results are returned for documents, people, team sites and TIFF files (including OCR capabilities),
and are relevancy-ranked and organized into rich views to make discovering content much easier.
By default, OCR/TIFF indexing is turned off in the product. To enable the feature, do the following:
2. Copy the tiff_ocr_on.reg file to the server (if the CD isn’t in the server drive).
Note: SharePoint Portal Server 2003 also can index PDF files. To configure your server to do PDF filtering,
you must install the iFilter for Adobe Acrobat (available on Adobe Systems Inc.’s Web site) according to the
directions in the SharePoint Portal Server 2003 administrator guide.
To ensure that the content you migrated over in the Vitamins site is indexed, follow these steps:
2. Under the “Search Settings and Indexed Content” section, click on “Configure Search and Indexing.”
3. Next to the item called “Start non portal content update,” click on “Full.” This will update the index for the
Vitamins site.
4. After one or two minutes, click on “Refresh”; the page should read “Idle” for nonportal content crawling.
From the home page, put your cursor in the search box and type “multivitamin.” Your results should be similar
to those shown in Figure 43.
Notice that you receive results for sites, documents and people, and can organize the results by author, date
or area by clicking on the corresponding links in the left navigation bar. By using SQL Server as the database
server, you also have full-text search capability, so all indexed documents with the text “multivitamin” in the
document also are returned by search. Figure 44 shows the same search organized by author.
Save and open files from Yes (Excel, Yes (Excel, Enhanced (Excel,
SharePoint sites PowerPoint, Word) PowerPoint, Word) FrontPage, InfoPath,
Outlook, PowerPoint,
The following sections list the hardware and software requirements (including the recommended
configuration for the operating system) for SharePoint Portal Server 2003.
SharePoint Portal Server 2003 must be installed on a computer with at least an Intel
Pentium III-compatible 700MHz processor.
The operating system partition and any partitions on which SharePoint Portal Server 2003
components will be installed, including the paths chosen during setup for program and data files,
must be formatted using the NTFS file system.
Program and data file paths cannot point to removable or networked storage.
SharePoint Portal Server 2003 requires the following amounts of disk space for installation and data
storage.
200 MB in the Program Files installation directory that is selected during setup
Data storage after installation varies considerably depending upon usage, but the minimum
recommendation is the following:
• 700 MB free disk space in the Data Files installation directory, including the 75 MB required for
installation
• 2.0 GB free disk space in the directory used by Microsoft SQL Server 2000 or SQL Server 2000
Desktop Engine (MSDE 2000) to store data
This section outlines the operating system and browsers supported for SharePoint Portal Server
2003.
The following operating systems are supported for SharePoint Portal Server 2003:
• Microsoft Windows Server 2003, Standard Edition, and the latest service pack
• Microsoft Windows Server 2003, Enterprise Edition, and the latest service pack
• Microsoft Windows Server 2003, Datacenter Edition, and the latest service pack
• Microsoft Windows Server 2003, Web Edition, and the latest service pack
Note: If you are running SharePoint Portal Server 2003 on Windows Server 2003, Web Edition, you
must have Microsoft SQL Server installed on a separate computer. You cannot use SQL Server
Desktop Engine for database storage.
All servers in a server farm must run the same version and language of the operating system, and
(where applicable) the same version and language of SQL Server 2000, with the following exception:
The computer running SQL Server 2000 can run on any supported operating system for SQL Server
2000.
All non-English versions of SharePoint Portal Server 2003 must be installed on servers with the
matching regional settings. If the settings do not match, setup fails. For more information about
regional settings, see Windows Help.
To access the portal site, computers must have one of the following Web browsers installed:
Microsoft Internet Explorer 5.2 for Mac OS X, and the latest service pack
To manage portal sites and areas, computers must have one of the following Web browsers installed:
Database Requirements
SharePoint Portal Server 2003 includes a version of Microsoft SQL Server 2000 Desktop Engine with
Service Pack 3.
Note: MSDE 2000 has limitations in terms of data size supported and other areas. If these limitations
are exceeded, SharePoint Portal Server 2003 will not function correctly. For more information, see the
MSDE 2000 documentation.
SharePoint Portal Server 2003 requires one of the following database servers:
• Microsoft SQL Server 2000 Standard Edition, and the latest service pack
• Microsoft SQL Server 2000 Enterprise Edition, and the latest service pack
Note: You must use the version of MSDE 2000 that SharePoint Portal Server 2003 installs.
The database server can be running any of the supported operating systems for SQL Server 2000.
For more information, see the documentation for SQL Server 2000.
When installing SharePoint Portal Server 2003 on a domain controller, the option to install with the
database engine is not available. You must have Microsoft SQL Server installed on the domain
controller or on a separate computer.
Note: Please refer to http://www.microsoft.com/security/ for any security bulletins related to your SQL
Server 2000 or MSDE 2000 installation.
Network Requirements
SharePoint Portal Server 2003 is supported only on servers that are members of a Microsoft
Windows NT® 4.0, Windows 2000 or Windows Server 2003 domain.
Microsoft Visual Studio is supported on a server running SharePoint Portal Server 2003 if you are
using Microsoft Visual Studio .NET 2003 or later. You can use Visual Studio .NET 2002 on a server
running SharePoint Portal Server 2003 by installing the update available from Microsoft Product
Support Services. Search for article 822837 in the Microsoft Knowledge Base at
http://support.microsoft.com/.
Note: When installing any version of Visual Studio .NET, you are prompted to add Microsoft Office
FrontPage 2003 Server Extensions. Do not add these components on a server with SharePoint Portal
Server 2003. On an existing installation of Visual Studio .NET, ensure that FrontPage Server
Extensions are not present before installing Windows SharePoint Services or SharePoint Portal
Server 2003.
The backward-compatible document library server component of SharePoint Portal Server 2003
cannot run on servers on which the following are installed:
Note: For small, medium-sized and large server farm deployments, the component for backward-
compatible document libraries and SQL Server 2000 cannot be installed on the same computer.
The optional server components for backward-compatible document libraries must be installed on a
computer with at least an Intel Pentium III-compatible 700MHz processor.
The operating system partition and any partitions on which the server components for backward-
compatible document libraries for SharePoint Portal Server 2003 will be installed, including the paths
chosen during setup for program and data files, must be formatted using the NTFS file system.
Program and data file paths cannot point to removable or networked storage.
The optional server components for backward-compatible document libraries require the following
amounts of disk space:
Data storage after installation varies considerably depending upon usage, but the minimum
recommendation is 250 MB of free disk space in the Data Files installation directory, including the 80
MB required for installation.
The following operating systems are supported for the server components for backward-compatible
document libraries for SharePoint Portal Server 2003:
Microsoft Windows Server 2003, Standard Edition, and the latest service pack
Microsoft Windows Server 2003, Enterprise Edition, and the latest service pack
Microsoft Windows Server 2003, Datacenter Edition, and the latest service pack
All non-English versions of the server components for backward-compatible document libraries for
SharePoint Portal Server 2003 must be installed on servers with the matching regional settings. If the
settings do not match, setup fails. For more information about regional settings, see Windows Help.
The following are the minimum hardware requirements for a computer running the client components
for backward-compatible document libraries:
64 MB of RAM
50 MB of hard disk space on Microsoft Windows 98, Windows 98 Second Edition and Windows NT
4.0; 30 MB of hard disk space on Windows 2000, Windows XP and Windows Server 2003
Computers running the client components for backward-compatible document libraries must be
running one of the following operating systems:
Any version of Microsoft Windows 2000, and the latest service pack
Any version of Microsoft Windows Server 2003, and the latest service pack
Note: Computers used by coordinators for backward-compatible document libraries must be running
any version of Windows 2000, Windows XP Professional or any version of Windows Server 2003.
In addition to the operating system, client computers must have the following installed:
Note: Microsoft Visual Basic® Scripting support is required if you are running Windows 98, Windows
98 Second Edition or Windows NT 4.0. If you choose the custom installation option for Internet
Explorer when you are installing on Windows 98, Windows 98 Second Edition or Windows NT 4.0,
ensure that you install Visual Basic Scripting support.
Computers running the client components for backward-compatible document libraries must have one
of the following Web browsers installed:
Note: Microsoft Visual Basic Scripting support is required if you are running Windows 98, Windows
98 Second Edition or Windows NT 4.0. If you choose the custom installation option for Internet
Explorer when you are installing on Windows 98, Windows 98 Second Edition or Windows NT 4.0,
ensure that you install Visual Basic Scripting support.