Introduction

Microsoft SharePoint Products and Technologies Overview

Introduction

Based on customer feedback and the experience of developing the first version of SharePoint Products and Technologies, Microsoft designed the next generation of Microsoft SharePoint Products and Technologies to use a common set of Microsoft Windows Server 2003 services named Windows SharePoint Services. This set of services takes advantage of the performance, stability, and security features of the Microsoft .NET Framework. The SharePoint Portal Server 2003 application is based on Windows SharePoint Services. Windows SharePoint Services is a set of services that you can use to create and maintain many team sites, and SharePoint Portal Server 2003 is a server product that adds features you can use to build and manage integrated, large-scale portal solutions.

Architecture and Design

SharePoint Team Services by Microsoft and Microsoft SharePoint Portal Server 2001 were the original versions of Microsoft Products and Technologies, released in 2001. SharePoint Team Services addressed the Web-based sharing and communication needs of teams and team Web sites, and SharePoint Portal Server 2001 addressed the document management, Web portal, and enterprise search requirements of a portal solution. To deliver these features, Microsoft used the best available (but different) technology platforms to build Windows SharePoint Team Services and SharePoint Portal Server 2001.

To determine the main design goals for the latest version of SharePoint Products and Technologies, Microsoft used feedback from customers and partners, the lessons learned from its large-scale internal deployment of SharePoint sites, and the experience gained from creating the first version of SharePoint Products and Technologies.

Customer Feedback

The Microsoft SharePoint Products and Technologies team was fortunate to receive early feedback from many types of customers and partners and to use that feedback to drive the design goals for the latest version of SharePoint Products and Technologies.

The feedback focused on three topics:

• Enterprise abilities – Greatly improve scalability, manageability, security, and performance while providing the greatest possible cost effectiveness for a wide range of customers, from the smallest project teams up to the largest organizations.
• Single, integrated platform – Base the next version of SharePoint Products and Technologies on a single, integrated set of technologies, so end users, network administrators, and developers can increase their productivity and reduce their costs.
• Advanced collaboration features – Improve the features and capabilities of SharePoint Products and Technologies to deliver the Microsoft vision of smart, connected spaces for people, meetings, teams, projects, divisions, and organizations. This includes more powerful information organization and searching capabilities, comprehensive support for enterprise application integration using Microsoft BizTalk Server, Web site personalization, and deeper integration with Microsoft Office to provide rich support for data analysis and work sharing.

Main Design Goals

The overall design goal for SharePoint Products and Technologies was to unify and integrate Windows SharePoint Services as a technology platform on which to build products such as SharePoint Portal Server 2003. This overall goal of unification and integration was divided into four areas:

• Consistent SharePoint Products and Technologies experience for users, developers, and IT professionals
• Consistency and integration with the Microsoft .NET Framework
• Integrated storage strategy
• Trustworthy Computing: security and reliability

Consistent Experience for Users, Developers, and Network Administrators

The most obvious change and improvement in the latest version of SharePoint Products and Technologies is the creation of a single, integrated technology platform named Windows SharePoint Services. SharePoint Portal Server 2003 is a server product based on Windows SharePoint Services. SharePoint Products and Technologies provides a consistent experience for users as they work with both Windows SharePoint Services-based sites and SharePoint Portal Server 2003-based portal sites.

Solution developers for SharePoint Products and Technologies now need to know only one user interface technology (ASP.NET Web pages and controls) and one SharePoint Products and Technologies object model to create advanced sharing solutions with SharePoint Products and Technologies.

Warning  Modifying the database schema or database structures is not supported. Changes that you make to the database contents may be overwritten when you install updates or service packs for Windows SharePoint Services, or when you upgrade an installation to the next product version.

Similarly, network administrators can take advantage of their existing knowledge by using well-known tools and procedures based on Windows Server 2003 and Microsoft SQL Server to deploy and manage SharePoint Products and Technologies.

Consistency and Integration with the Microsoft .NET Framework

The strategy of using the Microsoft .NET Framework, Web services, Microsoft Visual Studio .NET, and Windows Server 2003 to build SharePoint Products and Technologies is part of Microsoft's technology strategy for connecting people, information, applications, and devices.

The first advantage of using the Microsoft .NET Framework is that it is the most scalable, flexible, and secure foundation for building, deploying, and managing enterprise Web applications, including SharePoint Products and Technologies work sharing sites and portal sites.

Additionally, integrating SharePoint Products and Technologies with information from virtually any enterprise application is easy with the support for Web services included in the Microsoft .NET Framework.

Integrated Storage Strategy

The long-term strategy for storage technology at Microsoft is to take advantage of SQL Server relational database technology and XML data storage technology wherever possible, and SharePoint Products and Technologies is a showcase example. Except for the full-text search indices created by Microsoft Search technologies, all content, configuration information, and other SharePoint Products and Technologies data is stored in SQL Server databases.

Using a single, consistent, integrated data storage platform creates significant advantages for IT professionals and developers by increasing their productivity and reducing their day-to-day development, deployment, and management costs.

Trustworthy Computing: Security and Reliability

The secure, reliable operation of everyday computer systems is at the heart of the Trustworthy Computing initiative at Microsoft. All new Microsoft products, including SharePoint Products and Technologies, adhere to these Trustworthy Computing principles and take advantage of the security and reliability engineering that is part of Windows Server 2003 and the Microsoft .NET Framework. Each developer at Microsoft takes extensive software security training and applies their knowledge by performing security audits of each Microsoft software component that they are responsible for.

The development teams for SharePoint Products and Technologies groups took advantage of the built-in security and reliability of Windows Server 2003 and the Microsoft .NET Framework when they designed, implemented and tested the new version of SharePoint Products and Technologies.

Architecture and Design Decisions

Integrated Storage

SharePoint Team Services used a hybrid model of Web server, file system, Windows registry, and SQL Server-based storage to manage documents, lists, views, and configuration information. SharePoint Portal Server 2001 used a document store based on the Microsoft Web Storage System (the same storage technology used by Microsoft Exchange Server) for most data storage requirements. Both of these solutions required content to be stored on the same server that hosted the Web portal. This requirement limited the range of deployment scenarios and scalability.

Each storage solution served the original version of its product well. However, these storage solutions did not support the additional requirements for administration, management, performance, scalability, and functionality in the next generation of SharePoint Products and Technologies. For example, backup and restore operations are difficult to implement and manage when the relevant data is spread out among many different storage systems on the server.

For example, backup and restore operations are difficult to implement and manage when the relevant data is spread out among many different storage systems on the server. Windows SharePoint Services stores all documents, lists, views, and configuration information in SQL Server content stores. Because of this, Windows SharePoint Services offers true enterprise scalability and personalized Web portal experiences.

SharePoint Portal Server 2003 uses Windows SharePoint Services to take advantage of the same SQL Server content store architecture. SharePoint Portal Server 2003 also supports the option of installing backward-compatible document libraries (Web Storage System-based) for document storage. The backward-compatible document libraries are compatible with SharePoint Portal Server 2001 document approval and routing, and they support multiple document profiles for each document library folder. With the backward-compatible document libraries, you can use a phased strategy to migrate to SharePoint Portal Server 2003.

Note  SharePoint Portal Server 2003 still requires a SQL Server content store for managing ASP.NET portal Web pages, lists, views, and configuration information. Windows SharePoint Services and SharePoint Portal Server 2003 both use SQL Server content stores and require Microsoft SQL Server or Microsoft SQL Server Data Engine (MSDE). Microsoft SQL Server is a separately licensed product that is not included with Windows SharePoint Services or SharePoint Portal Server. MSDE is included with Windows SharePoint Services and with SharePoint Portal Server 2003.

ASP.NET Web Part Pages and Web Parts

SharePoint Products and Technologies now uses Web Part Pages and Web Parts based on the .NET Framework and ASP.NET.

SharePoint Team Services and SharePoint Portal Server 2001 used separate technologies to create and display (render) SharePoint sites in a Web browser. Web pages in SharePoint Team Services were based on Microsoft FrontPage and Office Web Server technologies, and Web portal pages in SharePoint Portal Server 2001 were based on Web Storage System, dashboard, and Web Part technologies.

The next generation of SharePoint Products and Technologies uses Microsoft ASP.NET Web Part Pages to create and display SharePoint sites in a Web browser. Web Part Pages are ASP.NET pages that take advantage of the performance, stability, and security of the .NET Framework and Windows Server 2003. You can easily integrate Web Parts with Web services, Microsoft Office, and Microsoft BizTalk Server to provide powerful, flexible, and cost effective solutions for work sharing, enterprise applications, and portal sites.

Common Document Management Services

SharePoint Portal Server 2001 was designed to provide document version tracking and check-in/check-out document management functions. However, SharePoint Team Services was the solution that large numbers of teams used every day to create, review, approve, and manage their Office documents, to plan and hold meetings, and to track project tasks.

Document version tracking and document check-in/check-out are now included in Windows SharePoint Services, where users need them the most and where all SharePoint Products and Technologies solutions can take advantage of these document management functions.

Document management is one of the most valuable end-user features in Windows SharePoint Services, and it is the area in which Microsoft made the most changes. The following list shows the main differences between the document management functions in SharePoint Portal Server 2001 and the document management functions in Windows SharePoint Services:

• In SharePoint Portal Server 2001, the document libraries based on the Web Storage System supported multiple document profiles for each document library folder. In Windows SharePoint Services, the SQL Server content store supports one set of properties (the equivalent of one document profile) for each document library. Because of this, you may want to store the properties of the most common document profile in the area where it would normally belong, and then store the documents that use secondary document profiles in a subarea, using one set of properties for each secondary document profile.
• SharePoint Portal Server 2001 provided both serial and parallel routing and approval processes. Windows SharePoint Services now provides a simpler, one-step moderator approval process.
• SharePoint Portal Server 2001 provided support for document version tracking using major and minor version numbers. Windows SharePoint Services and SharePoint Portal Server 2003 use major version numbers only.
• SharePoint Portal Server 2001 only supported access control at the folder level and the subfolder level (and user and group exclusions at the file level). Windows SharePoint Services and SharePoint Portal Server 2003 support access control at the site level and the document library level.

Site Creation and Management Services

The original versions of SharePoint Portal Server 2001 and SharePoint Team Services were very complementary. SharePoint Team Services sites were easily deployed in large numbers within an organization, and SharePoint Portal Server 2001 provided enterprise search and Links Web Parts to aggregate team sites into one or more portal sites.

To improve support for very large numbers of SharePoint sites, Windows SharePoint Services now provides common site creation and management features, such as site templates and self-service creation of SharePoint sites. SharePoint Portal Server 2003 adds the following deployment and management features for the large organization: a site directory that provides an easy to use site registration system; preconfigured enterprise application integration (EAI) solutions with single sign-on support for third party applications; dynamically configurable site maps; large-scale server topology management; and the ability to share multiple index and search servers.

Integrated Search Solution

For full-text content indexing and searching, SharePoint Team Services used the Windows Indexing service, an early version of Microsoft Search technologies included in Microsoft Windows 2000. When SharePoint Portal Server 2001 was released, it included an updated enterprise version of Microsoft Search technologies.

Windows SharePoint Services uses the full-text searching features from the latest version of Microsoft SQL Server SharePoint Portal Server 2003 uses the latest version of Microsoft .NET Search services in addition to SQL Server full-text search.

Personalization and Audience-Targeted Information and Applications

To help individual users find and use the information and tools they need, a portal solution must support targeted delivery of content, information, and application functionality. This includes targeting information and applications to individuals, teams, divisions, and entire organizations. This also includes effective support for personalized content and support for group-based portal page content.

Personalization is a service included in Windows SharePoint Services. SharePoint Portal Server 2003 uses Audiences to extend this service. Audiences are dynamic groups of users that share one or more common properties (for example, business function, department, or team membership). The properties that determine Audience membership can reside in an enterprise directory such as Microsoft Active Directory or any other SQL Server-based database. Audiences are used to determine which Web Parts appear on a particular Web page, and they can also act as a filter for the information displayed in those Web Parts. SharePoint Portal Server 2003 also supports creating and managing individual portal pages for each user.

Subscriptions and Alerts

In SharePoint Team Services and SharePoint Portal Server 2001, you could use Subscriptions to receive messages when your shared documents were changed. The name of the Subscriptions feature has now changed to Alerts. Windows SharePoint Services and SharePoint Portal Server 2003 both continue to support Alerts.

Simple Single Server Configurations and Highly Scalable Server Farm Configurations

SharePoint Team Services and SharePoint Portal Server 2001 were deployed as single server solutions or as groups of servers, but little support was available for creating and deploying highly scalable server farms.

In the next generation of Microsoft SharePoint Products and Technologies, Windows SharePoint Services is specifically designed to vastly improve performance for each server and to support deployment in highly scalable server farms using multiple stateless front-end servers connected to one or more back-end content servers.

Important Features and Terminology Used in SharePoint Products and Technologies

In addition to understanding SharePoint Products and Technologies technical design, understanding the new and changed terminology introduced in the latest version of SharePoint Products and Technologies is also important.

SharePoint Sites and Site Collections

The terminology used to name the components in SharePoint Products and Technologies varies depending on whether you are an end user, a developer, a Windows administrator, or a SharePoint Products and Technologies administrator.

For SharePoint Products and Technologies end users, the terminology used in the SharePoint Products and Technologies Web interface is consistent with the long-term goals and direction for SharePoint Products and Technologies.

Some of the terminology for developers is more consistent with the older SharePoint Team Services object model. The terminology for Windows administrators and SharePoint Products and Technologies administrators is a mixture of SharePoint Team Services terminology and Windows SharePoint Services terminology. Microsoft plans to increase the consistency of the terminology for developers and administrators in future versions of SharePoint Products and Technologies.

In SharePoint Team Services, the term for the top-level content directory of a Web server is "root Web site." In a multi-hosting environment, each virtual Web server that is configured on the Web server contains one top-level (root Web) site. Additionally, the term for a site within a root Web site in SharePoint Team Services is "subweb." "Subweb" is a term adopted from Microsoft FrontPage Web sites (the original technology on which SharePoint Team Services was built). You can create multiple subwebs in a root Web site, and you can create subwebs within other subwebs.

In SharePoint Portal Server 2001, the term for the top-level content directory of a Web server is "workspace." The term for a site within a workspace is "subdashboard." You can create additional subdashboards and personal dashboards for subprojects and individual users.

In the latest version of SharePoint Products and Technologies, the term "site" replaces the previous terms. There are two types of SharePoint sites that you can use to divide site content into distinct, separately manageable sites: top-level sites and subsites. A top-level SharePoint site is the parent site of all sites in a site collection. Top-level sites can contain multiple subsites, and subsites can also contain multiple subsites, continuing for as many levels as your users require.

You can use this hierarchy to create a main subsite for your entire team and create individual subsites or shared sites for side projects. Top-level Web sites and subsites permit different levels of control over site features and settings.

Single Server Scenario

SharePoint Products and Technologies supports both vertical, single server solutions and horizontal, server farm solutions. This section describes a single server configuration.

One of the minimum system requirements for Windows SharePoint Services is the Windows Server 2003 operating system. Additionally, you must install and configure Internet Information Services (IIS) and ASP.NET before you install Windows SharePoint Services. When you install Windows SharePoint Services, it creates and configures a virtual server named SharePoint Central Administration. Additionally, if you install Windows SharePoint Services in a single-server configuration, it automatically extends the existing default Web site that was created when you installed IIS.

Windows IIS Web sites are also referred to as IIS virtual Web servers, virtual servers, or v-servers. In addition to the two default IIS virtual servers that are created when you install Windows SharePoint Services, you can configure as many as nine end-user virtual servers with separate application pools or 99 end-user virtual servers with a shared application pool on a single Windows Server 2003-based computer. Each IIS virtual server can host multiple SQL Server content stores.

Each SQL Server content store for SharePoint Portal Server 2003 can only contain one portal site collection. Each SQL Server content store for Windows SharePoint Services can contain as many as 50,000 site collections, even if the site collection is hosted under a SharePoint Portal Server 2003 portal site.

A site collection is a set of Web sites that have the same owner and administration settings and that reside on the same virtual server. Each site collection contains a top-level Web site and can contain one or more subsites. A site collection serves as the administrative unit for assigning users to site groups and for granting security rights to site groups. For more information about site administration, see the next section. For a complete list of SharePoint Products and Technologies security rights, see Appendix A in this white paper.

You can nest a site within another site. The term for the nested site is "subsite" or "child site." Each site (and subsite) uses the same SQL server content database as its parent site.

Note   In SharePoint Portal Server 2003, the term "site collection" is the equivalent of the older term "site" in SharePoint Team Services, and in the new version of SharePoint Products and Technologies, the term "site" or "SharePoint site" is the equivalent of the older term "subweb" in SharePoint Team Services. Be careful to avoid confusing the overlapping terminology. For more information about terminology in SharePoint Products and Technologies, see the following table.

Note  If you are a developer, the SharePoint Products and Technologies object model uses the (sometimes overlapping) names from SharePoint Team Services for many of the new SharePoint Products and Technologies components. Use the preceding table to cross-reference terms from the old and new naming conventions.

Server Farm Scenario

In a server farm scenario, the terminology remains the same, and the requirement that all SharePoint sites use the same SQL Server content database as the top-level site remains the same. However, you can use multiple stateless front-end Web servers to support a large number of user connections and to render ASP.NET Web pages. Logically located behind these front-end Web servers, a SharePoint Products and Technologies configuration can use many back-end database servers.

You can use multiple content database servers to support multiple site collections and to provide fault-tolerant fail-over. Optionally, you can use separate database servers to store the configuration database for server farm configuration maps and site collection-to-content database maps.

Portal Sites

One of the minimum system requirements for SharePoint Portal Server 2003 is Windows SharePoint Services. When you install SharePoint Portal Server 2003, Setup automatically installs Windows SharePoint Services if it is not already installed.

You can configure only one portal site for each end-user IIS virtual Web server. The portal site corresponds to the SharePoint Products and Technologies top-level site for both the virtual server and the site collection rooted at the virtual server.

Security

Site Groups and Rights

SharePoint Products and Technologies uses a security model based on site groups and rights. Site groups are groups of users with related security requirements. Security rights are assigned to each security group. You can customize the rights assigned to these site groups or add new site groups to combine different sets of rights. By default, Windows SharePoint Services includes five site groups: Administrator, Web Designer, Contributor, Reader, and Guest.

Members of the Administrator site group have complete control over a Web site. They can configure settings, manage users and site groups, and view usage analysis data.

Members of the Web Designer site group can use a SharePoint Products and Technologies-compatible Web page editor such as Microsoft Office FrontPage 2003 to customize the Web site.

Members of the Contributor site group can interact with Web Parts, lists, and document libraries. Additionally, they can create and manage personal views and cross-site groups and personalize Web Part pages.

Members of the Reader site group can view items in lists and document libraries, view pages in the site, and create a site using Self-Service Site Creation.

The Guest site group is designed to be combined with specific permissions for specifics lists, so guest users can have access to a specific list without having access to the entire site. You cannot customize or delete the Guest site group.

If you use one of the SharePoint Products and Technologies upgrade tools to create the SharePoint Products and Technologies installation, the upgrade tool inspects the permissions granted to each role in SharePoint Team Services or SharePoint Portal Server 2001 and uses the permissions granted to each role to assign users to corresponding SharePoint Products and Technologies site groups.

Cross-Site Groups, Local Groups, and Domain Groups

Cross-site groups, local groups, and domain groups can be members of site groups.

Cross-site groups are collections of users who can be managed as a single group across multiple SharePoint Products and Technologies sites. Cross-site groups are configured in SharePoint Products and Technologies, and they can be members of a site group.

Domain groups and local groups can also be members of site groups. However, cross-site groups and site groups cannot be members of local groups or domain groups.

Authentication

Authentication is the process of verifying the identity of user or a process. Microsoft Internet Information Services (IIS) handles authentication for SharePoint Products and Technologies. To be authenticated, you need a local user account or a domain user account (if in a networked domain). In most cases, a domain account is a better choice than a local account.

You can configure authentication to operate in either pre-existing account mode or account creation mode. In pre-existing account mode, SharePoint Products and Technologies does not automatically create new user accounts. In account creation mode, SharePoint Products and Technologies can automatically create new user accounts in Active Directory. Account creation mode is a feature that you must select when you install Windows SharePoint Services or SharePoint Portal Server 2003.

Note  If you use account creation mode, make sure that IIS is configured to use basic authentication. SharePoint Products and Technologies no longer supports IIS digest authentication.

SharePoint Products and Technologies does not fully support Microsoft Passport authentication.

Authorization

SharePoint Products and Technologies stores all security metadata (groups and rights) in SQL Server content stores. User security metadata for SharePoint Products and Technologies is not stored in IIS or anywhere else in Windows.

After IIS uses a local computer account or an Active Directory account to authenticate a user, SharePoint Products and Technologies compares the rights assigned to the user by IIS with the access control information for the SharePoint site to determine which SharePoint site resources the user is permitted to use.

Note  Active Directory is not required for Windows SharePoint Services or SharePoint Portal Server 2003. However, without Active Directory, SharePoint Portal Server you cannot pre-populate and synchronize the SharePoint Portal Server profile database with the list of users from Active Directory, and users' personal sites are not registered for cross-farm synchronization in a multi-server configuration. For best results, deploy SharePoint Products and Technologies in an Active Directory environment.

Site Administration

Members of the Administrator site group for a top-level Web site can control settings and features for the top-level Web site and any subsites. For example, an administrator of a top-level Web site can:

• Add, delete, or change user permissions
• View usage statistics
• Change regional settings
• Manage Web Part catalogs and template catalogs
• Manage Web document discussions and alerts
• Change the name, description, theme, and home page organization of the site
• Configure settings (for example, regional settings) for the top-level Web site and all subsites
• Update e-mail settings for the top-level Web site and all subsites
• Configure Web Parts settings for the top-level Web site and all subsites

A member of the Administrator site group for a subsite can control settings and features only for that particular subsite, and the administrator of a site under that subsite can control settings and features for only that particular second-level subsite. For example, an administrator of a subsite can:

• Add, delete, or change user permissions
• View usage statistics
• Change regional settings
• Manage Web Part catalogs and template catalogs
• Manage Web document discussions and subscriptions
• Change the name, description, theme, and home page organization for the subsite

Document and Content Storage

SharePoint Products and Technologies supports two types of content stores. The primary store is the SQL Server content store. Based on Microsoft SQL Server technology, the SQL Server content store provides a single, consistent data storage solution for document content, list content, and metadata. You can use common Windows and SQL Server management tools and development tools to easily manage, tune, back up, and enhance SQL Server content stores.

When you install SharePoint Portal Server 2003, you have the option of installing the backward-compatible document store. The backward-compatible document store is an updated version of the Web Storage System-based document store used in SharePoint Portal Server 2001. The backward-compatible document store is provided for users who require features from SharePoint Portal Server 2001, such as complex document routing and approval, folder-level security, minor-level version numbers, and multiple document profiles for each folder.

The primary interfaces for the document management features in SharePoint Products and Technologies are document libraries, which you can add to any SharePoint site. A document library consists of the virtual folder where the files are stored, the files themselves, and the user-definable descriptive information (metadata) associated with each item in the document library.

Organizing Documents and Other Content

You can configure each SharePoint site with a document library and a corresponding list component that can display customizable views of the metadata for each document.

With SharePoint Portal Server 2003, you can associate documents and other content in a site with one or more hierarchical areas. Areas provide an alternative way to navigate and search content in a SharePoint Portal Server 2003 portal site. Areas are similar to Categories in SharePoint Portal Server 2001.

In a SharePoint Products and Technologies configuration that uses only SQL Server content stores, major version numbers are used to track document revisions (minor version numbers are not supported), and a single-step moderator approval mechanism is used to approve documents.

Search Configuration and Usage

Windows SharePoint Services keeps all content in SQL Server content stores, and it uses the Microsoft Search full-text indexing and searching technology from Microsoft SQL Server. Because of this, Windows SharePoint Services can only index and search content in SQL Server content stores.

SharePoint Portal Server 2003 uses the latest version of Microsoft Search technology to index both local and external document collections and Web sites. It supports all of the advanced indexing and searching features from SharePoint Portal Server 2001, with improved performance, scalability, and extensibility. SharePoint Portal Server 2003 can now index and search approximately 20 million documents (a five-fold improvement) and support load-balanced queries across multiple catalog servers.

Conclusion

Windows SharePoint Services and SharePoint Portal Server 2003 provide easy-to-use sharing tools for your organization. You can use Windows SharePoint Services to create and maintain many team sites, and you can use SharePoint Portal Server 2003 to build and manage integrated, large-scale portal solutions.

To achieve this significant increase in capability, performance, stability, and security, the overall architecture of Microsoft SharePoint Products and Technologies includes many significant changes. The most important of these changes are the use of the .NET Framework, Windows Server 2003, and Microsoft SQL Server for content storage.

To benefit most from the latest version of Microsoft SharePoint Products and Technologies, you must be familiar with the changes and new features in SharePoint Products and Technologies, and you must be familiar with the new, consistent terminology for SharePoint Products and Technologies. This knowledge can greatly increase your understanding of both basic and advanced SharePoint Products and Technologies concepts.

Appendix A – SharePoint Products and Technologies Security Rights

This section contains the following:

• Key Concepts and Architecture
• Security Overview