Microsoft Sharepoint Refrence
Which SharePoint technology is right for you?

• Component overview

• Collaboration

• Enterprise portal

• Enterprise search

• Enterprise content management

• Forms-drive business processes

• Business intelligence

• Management

• Platform

Component overview

All servers inherit a set of shared platform and management capabilities from Microsoft Windows SharePoint Services 3.0. The following tables are broken down into functional areas and provide a comparison of features available across the different editions of Microsoft SharePoint Product and Technologies.

• Collaboration: Help keep teams connected and productive by providing easy access to the people, documents, and information users need to make more well-informed decisions within their jobs. Windows SharePoint products and technologies include collaboration and community, document life cycle capabilities, alters, task notifications, Really Simple Syndication (RSS), the basic Web-based user interface and navigation.
• Portal: The portal components of Microsoft Office SharePoint Server 2007 include features that are especially useful for designing, deploying, and managing enterprise intranet portals, corporate Internet presence Web sites, and divisional portal sites.
• Search: The search component has been significantly enhanced in this release. The new features provide a consistent and familiar search experience, increased relevance of search results, and new functionalities along with improved scalability, manageability, and extensibility.
• Enterprise Content Management: Windows SharePoint Services provides core document management functionality: major and minor versioning, check-in/check-out document locking, rich descriptive metadata, workflow, content type–based policies, auditing, and role-based-access controls at the document library, folder, and individual document levels. Office SharePoint Server 2007 builds on these capabilities to deliver enhanced authoring, business document processing, Web content management and publishing, records management, policy management, and support for multilingual publishing.
• Forms Driven Business Process: Streamline forms-driven business processes with easy-to-use, intelligent, XML-based electronic forms that integrate smoothly with existing systems. This security-enhanced, client/server platform provides rapid-solution creation and deployment, centralizes form management and maintenance, and helps to extend business processes to customers, partners, and suppliers.
• Business Intelligence: Provide business intelligence (BI) capabilities to every employee, so they can share, control, and reuse business information in order to make better business decisions. The BI features of Office SharePoint Server 2007 provide Web and programmatic access to published Microsoft Office Excel spreadsheets, programmatic reuse of critical line-of-business data, and easy development of Web-based BI dashboards that can incorporate rich, data-bound key performance indicators (KPIs), Web Parts, and published spreadsheets.
• For more information:
  • Windows SharePoint Services 3.0
  • Search Server 2008 Express
  • Forms Server 2007
  • SharePoint Server 2007

Collaboration

KEY: = Feature Included

Features	Windows SharePoint Services 3.0	Search Server 2008 Express	Forms Server 2007	SharePoint Server 2007 Standard	SharePoint Server 2007 Enterprise
Real-time presence and communication The enhanced real-time presence smart tag icon, displayed virtually everywhere a person’s name appears in the system, tells users whether a person is online and available for a telephone or audio conference call, instant messaging, or two-way video conversation.
Social Networking Web Part Include Social Networking Web Parts that use information about your organization, communities, and electronic communications in Public My Site pages to help establish connections between colleagues with common interests.
Standard site templates Windows SharePoint Services 3.0 includes the following standard collaboration site templates: Team site Document workspace Blank site Blog Wiki Meeting workspaces (five workspace types)
Wikis A wiki is a new site template in Windows SharePoint Services 3.0 that makes it easy to create, edit, link, and restore an individual Web page. Wikis can be used as creative forums to brainstorm ideas, manage knowledge bases, create designs as well as instruction guides or simply gather information in an easy-to-edit format. Wikis are easy to create, modify, and annotate in addition to tracking contributions and changes. Key features include: Fast and easy page creation Easy and automatic linking Version differences What you see is what you get (WYSIWYG) Web page editing Wikis leverage existing SharePoint functionality including search, navigation, alerts, and custom fields.
Blogs Blogs provide a publishing-oriented experience for a single user or a team. Windows SharePoint Services 3.0 includes a site template that supports: Article posting Reader comments Archive views RSS feed generation
People and Groups lists People and Groups offer a unified place to find, communicate with, and manage people and their permissions, including support for custom fields such as Department, “Office #” and Area of Focus; in addition to the new Person field type. The Person field type creates rich displays of lists of people including support for a People Picker for browsing a list of users. Member Group provides: Re-use of groups across sites Distribution list for the members of the site
Calendars Calendars have been enhanced with richer calendar views, expanded support for recurring events, and all-day events.
E-mail integration Document libraries, discussion boards, calendars, and announcements can be enabled to receive new postings via e-mail. In addition, extensible support is provided for custom e-mail handlers in Windows SharePoint Services 3.0. Similar to the functionality provided by public folders in Microsoft Exchange Server, e-mail enabled discussion boards support: A highly scalable, topic-based architecture New “super rich-text” field type Unified experience for both e-mail and Web-based discussions One-step creation of Active Directory directory service distribution lists as part of the site creation process Unified SharePoint group and Active Directory management functions
Task coordination The new Project Tasks list template provides lightweight task management functionality including Gantt charts for visualization of task relationships and status.
Surveys Surveys now include conditional branching as well as support for inserting page breaks in long surveys such as annual employee satisfaction or and customer surveys.
Document collaboration Improvements to SharePoint document libraries include: Similar to the functionality provided by public folders in Microsoft Exchange Server, e-mail enabled discussion boards support: Checking out documents locally Offline document library support in Microsoft Office Outlook 2007 Major and minor version numbering and tracking Support for multiple content types Policy, auditing, and workflow Tree view support
Issue Tracking The Issue Tracking list template has been updated to use the enhanced versioning and version-history storage features of Windows SharePoint Services 3.0.

 Top of Page

Enterprise portal

KEY: = Feature Included

Features	Windows SharePoint Services 3.0	Search Server 2008 Express	Forms Server 2007	SharePoint Server 2007 Standard	SharePoint Server 2007 Enterprise
My Site personal site The My Site personal site gives users an opportunity to aggregate information “for me,” “by me,” and “about me.” Significant enhancements include social networking, privacy controls, SharePoint Sites and Documents Aggregation Web Parts, and Colleagues and Memberships Web Parts.
Content syndication Use RSS feeds to syndicate content managed in a portal site.
Privacy and security Use authorizations to control visibility of information in a My Site public view.
Site Directory The Site Directory automatically creates a site map and presents it in an easy-to-use format. The enhanced directory now includes the option to scan for changed or deleted links to external content.
User Profiles and the Profile Store User Profiles store personal information for system users. Improvements include multi-valued properties bound to taxonomy from Office SharePoint Server 2007, property-level security controls by person or group, open and closed vocabularies, and per-site property extensions. Profile synchronization and directory import support the extended capabilities of the User Profile Store with enhanced scalability and performance.
Audience targeting Enables use of Web Part pages, Web Parts, and content to target distribution lists and groups in addition to SharePoint audiences.
Site Manager Manage a SharePoint site’s navigation, security access, and general look and feel using this easy drag-and-drop tool. Site Manager unifies site management tasks for portals and Web sites, including management of areas, pages, listings, SharePoint site lists, and associated component parts.
Mobile device support All SharePoint portal, team site, and list pages now render on international and North American mobile devices (including Web-enabled mobile phones) using a simplified text-only format.
Portal site templates Preconfigured templates streamline creating, customization, and deployment of divisional portals, organization-wide intranet portal sites, and corporate Web sites.
SharePoint Sites and Documents Aggregation Web Parts List all the SharePoint sites that a user is part of and documents the user has authored. The Documents Aggregation Web Part also supports more general capabilities for querying and filtering the documents stored in a collection of SharePoint sites.
Colleagues and Memberships Web Parts List people the user knows and people who belong to common distribution groups.
Integration with Microsoft Office Access 2007, Excel 2007, PowerPoint 2007, and Word 2007 Windows SharePoint Services 3.0 easily integrates with smart client tools through a set of Web services and documented application interfaces. Users can readily adopt these new tools because of their similarity to other familiar environments, such as the Microsoft Office system. For example, users of 2007 Microsoft Office system programs such as Word, Excel, PowerPoint, InfoPath, Project, and OneNote can directly interact with information stored in SharePoint sites without having to manually download the content. Users can create workspaces, post and edit documents, and assign tasks, all while working on documents stored in SharePoint sites.
Integration with Microsoft Office Outlook 2007 With Office Outlook 2007, users can view calendars and contact lists stored on SharePoint sites, and create and manage sites for editing documents and organizing meetings. Office Outlook 2007 and Windows SharePoint Services 3.0 support a new set of significantly enhanced functionality including: Read/write access to SharePoint items: calendars, tasks, contacts, discussions, and documents Synchronization of offline support of document library and lists Ability to check out and edit documents when offline Roll-up views of calendars and tasks across multiple lists and sites Unified view of personal and SharePoint tasks in Office Outlook 2007
Integration with Microsoft Office SharePoint Designer 2007 Office SharePoint Designer 2007, based in part on Microsoft FrontPage technology, will provide tools for rich customization of sites, and creating reporting tools and application templates, without any coding.

 Top of Page

Enterprise search

KEY: = Feature Included

Features	Windows SharePoint Services 3.0	Search Server 2008 Express	Forms Server 2007	SharePoint Server 2007 Standard	SharePoint Server 2007 Enterprise
User interface Simple, clean yet powerful user interface with industry-standard query syntax. Scopes are decoupled from content sources so users can easily broaden or narrow the scope of a content search. Search can be based on arbitrary content properties such as URL, type, and author. Actionable search results can be easily filtered and sorted; used and shared. Alerts and RSS feeds easily provide updated results for common and frequent queries.
Search results Search results are rendered more clearly. Results are security trimmed so users only see what they can access. Results include user-friendly features such as hit highlighting, duplicate collapsing, and synonym suggestion. Optional integration with real-time communications tools allow users to easily contact content authors and experts.
Enterprise content sources Searches over 200 file types in many enterprise content sources, including files shares, Web sites, SharePoint sites, Exchange Public Folders, and Lotus Notes databases out-of –the-box with the ability to extend to additional third party repositories and file types through the use of Protocol Handlers and iFilters.
Relevance New and improved search algorithms tuned for enterprise content along with the use of relevance and ranking factors such as click distance, hyperlink anchor text, URL depth, and metadata extraction yield the best results for enterprise content.
Administration and management Improved administration user interfaces and admin application programming interface (API) provides broad support for various search and indexing scenarios, central controls for resource-intensive operations, as well as tools for management and reporting.
Indexing controls Granular indexing controls for easy inclusion and exclusion of searched content as well as immediate result removal of any site or item. Continuous index propagation to keep information fresh. Improved crawl rules and crawl log; multiple start addresses per content source; and a new browse able, filterable index log provide necessary information to optimize search.
Security Administrator permissions no longer required by crawler. Access control list (ACL) and ACL-only crawls index content permissions for compliance, privacy, and protection of intellectual property (IP). Security-trimmed search results only allow users to see content they are allowed to access.
People search People search capabilities allow users to find people not only by department or job title but also by expertise, social distance, and common interests.
Business data search Search data residing in your line-of-business applications using the Business Data Catalog. Structured content sources and line-of-business application data and reports accessible through Web services or ADO.NET can be indexed and retrieved through the Business Data Catalog as search results or into a SharePoint list.

 Top of Page

Enterprise content management

KEY: = Feature Included

Features	Windows SharePoint Services 3.0	Search Server 2008 Express	Forms Server 2007	SharePoint Server 2007 Standard	SharePoint Server 2007 Enterprise
Business document workflow support Automate document review, approval, signature collection, and issue tracking using workflow applications. Approval Collect Feedback Collect Signatures Disposition Approval
Document management site templates The Managed Document Library site template defines large-scale document management sites. The Divisional Library site template includes managed document libraries, dashboards, KPIs, and other reporting tools. The Translation Library site template helps organizations manage multiple translations of a document.
Integration with Microsoft Information Rights Management (IRM) Helps ensure that access rights applied to Microsoft Office documents in a central library travel with the documents, even when they are downloaded from the library.
Document Information Panel Makes editing document properties an integral part of the Microsoft Office system document-authoring experience.
Document Action Bar Describes to users what business policy or workflow governs the current document and what action they are expected to take.
Retention and auditing policies Define customized information management policies to control retention period, expiration actions, and document-auditing settings.
Records repository Helps ensure the integrity of the files stored in the repository, and supports information management policies that consistently and uniformly enforce auditing, and expiration of records.
E-mail content as records Provides consistent, policy-based solutions for managing e-mail content across Office Outlook 2007, Microsoft Exchange Server 2007, and Office SharePoint Server 2007.
Legal holds Makes it possible for records to be searched and placed on hold during litigation discovery to override the retention schedule of the records.
High fidelity Web sites with consistent branding Provides the concept of Master Pages and Page layouts to enforce the branding and navigation of Web sites. CSS supports gives pixel level control on the look and feel of these sites.
Navigation controls Out-of-the box navigation controls that can be easily customized by end users.
Content authoring Provides the ability for information workers to create content rich Web pages using a Web browser.
Content publishing and deployment Built in approval workflow allows Web content to be sent for approval prior to publishing. Content deployment to production sites can be scheduled by setting up jobs and a "live" time period for each page can be specified within which that page is viewable.
Site templates Includes support for several new enterprise site templates: The Enterprise Portal template provides a means for a business unit to create and share content that is relevant to the ongoing operation of an enterprise, division, or business unit. The Corporate Internet Presence Site template includes tools and workflows to create and manage Web content for products and service descriptions, company news, and public filings, among other things. The Application Portal template brings together all of the tools and information related to a particular line-of-business application. The Roll-up Portal template consolidates data and content from several applications or locations and presents it in an integrated format.
Page Layouts Page Layouts simplify content authoring and publishing — site administrators define a structure that guides authors through the publishing process; content contributors focus on doing their jobs rather than on the details of publishing and deployment. Flexible Page Layouts also allow designers to mix and match ASP.NET applications, Web Parts, and Authoring Templates in any configuration to create customized sites to meet specific business needs.
Site variations A new feature of Office SharePoint Server 2007, sites can be linked together in a parent-child type of relationship providing a one-way orchestration framework for Web content. This feature allow organizations to deploy multi-lingual publishing sites in a much more structured and manageable environment.
WYSIWYG Web content editor Extends the SharePoint user interface with additional commands and status indicators for in-context Web page authoring.
Slide libraries The repository features in Windows SharePoint Services 3.0 provide the platform support for slide libraries, a feature of Office SharePoint Server 2007. Slide libraries enable the storage of individual slides in a SharePoint site. Office PowerPoint 2007 slide decks can be automatically created from a selection of slides in a slide library.
Policies, auditing, and compliance Repositories in Windows SharePoint Services 3.0 support the following policy, auditing, and compliance features. However, the features denoted with an asterisk are activated only upon the installation of Office SharePoint Server 2007. Document retention and expiration policies Highly customizable policies Workflow process to define expiration Access control and security IRM policies applied on download to secure the functional access to documents Tracking and auditing Logging of all actions on sites, content, and workflows Official document-of-record repositories Site for storing or archiving enterprise approved content types

 Top of Page

Forms-driven business processes

KEY: = Feature Included

Features	Windows SharePoint Services 3.0	Search Server 2008 Express	Forms Server 2007	SharePoint Server 2007 Standard	SharePoint Server 2007 Enterprise
Browser-based forms Microsoft Office InfoPath Forms Services available in Office SharePoint Server 2007 and Microsoft Office Forms Server 2007 makes it possible to design Web-capable forms in Office InfoPath 2007 and distribute them on corporate intranets, extranets, or the Internet. Users can fill out forms in a browser or HTML-enabled mobile device with no download or client components needed.
Centralized forms management and control Office InfoPath Forms Services provide a administrator controlled centralized form solution catalog that makes it easy for users to find a form and minimize form solution downtime when upgrades are necessary. It also provides administrators with the tools to manage form solution security and accessibility.
“Design once” development model Forms designers can design their forms once and deploy them for use both within the rich Office InfoPath 2007 client program and through a Web browser. Office Forms Server 2007 automatically converts the form into ASP.NET Web forms, with no additional work from the designer.
Form Import Wizard The designer in Office InfoPath 2007 provides an easy way to convert forms designed in Office Excel and Office Word into rich Office InfoPath 2007 forms. The Form Import Wizard handles the conversion of form fields, repeating tables, rich text boxes, and other elements, dynamically generating the underlying XML structure for the new form.
Integrated deployment model for “no-code” forms The Publish Wizard in Office InfoPath 2007 makes it easy to publish forms that do not have any managed code components to a Windows SharePoint Services library, while making the form available as a browser-based form at the same time.
Compatibility Checker The Compatibility Checker helps forms designers validate those features that need to work across the broadest range of Web browsers.

 Top of Page

Business intelligence

KEY: = Feature Included

Features	Windows SharePoint Services 3.0	Search Server 2008 Express	Forms Server 2007	SharePoint Server 2007 Standard	SharePoint Server 2007 Enterprise
Integrated, flexible spreadsheet publishing Office Excel 2007 provides an integrated publishing experience that lets information workers easily choose what they want to share with others and determine how others can interact with published spreadsheets.
Share, manage, and control spreadsheets Share business data broadly while maintaining control and helping to protect sensitive information. Provides access to spreadsheet data and analysis through server-calculated, interactive Office Excel spreadsheets from a Web browser. Use these spreadsheets to maintain and efficiently share one centralized version of the truth while helping to protect any sensitive or proprietary information embedded in documents, such as financial models, by limiting access to portions of the spreadsheet and auditing their usage.
Web-based business intelligence using Excel Services Excel Services empowers spreadsheet authors to easily and broadly share spreadsheets that use the new business intelligence (BI) functionality through the browser. Fully interactive, data-bound spreadsheets including charts, tables, and PivotTable views can be created as part of a portal, dashboard, or business scorecard, without requiring any development.
Data Connection Libraries Data Connection Libraries are centralized SharePoint document libraries that store Office Data Connections (ODC); ODCs describe connections to external data. Centralizing Office Data Connections makes it easier to share, manage, and discover data connections that can be used by any Microsoft Office program.
Business Data Catalog The Business Data Catalog (BDC) tightly integrates external data into the Office SharePoint Server 2007 user experience, providing access to external data residing within backed line-of-business applications, and enabling the display of and interaction with external data through a set of Business Data Web Parts.
Business Data Web Parts Use SharePoint Business Data Web Parts for viewing lists, entities, and related information retrieved through the Business Data Catalog.
Business Data actions With no custom coding, easily create actions that open Web pages, display the user interfaces of line-of-business applications, launch InfoPath forms, and perform other common tasks. Use the convenient links that appear beside business objects returned from the Business Data Catalog.
Integrated business intelligence dashboards Create rich, interactive BI dashboards that assemble and display business information from disparate sources by using built-in Web parts such as dynamic KPIs, Excel spreadsheets, Microsoft SQL Server Reporting Services reports, or a collection of business data connectivity Web Parts that can visualize information residing in back end line-of-business applications.
Report Center An out-of-the-box site optimized for report access and management, including a report library, data connection library, and a dashboard template. These sites, hosted by the new Report Center, provide consistent management of reports, spreadsheets, and data connections.
Key performance indicators KPIs communicate goals and status to drive results. Using the KPI Web Part, a user can create a KPI list within a Web Part page, without writing code. The KPI Web Part can display KPIs from Microsoft SQL Server Analysis Services, Excel spreadsheets, SharePoint lists, or manually entered data.
Filter Web Parts Filters enable dashboards to be personalized by communicating shared parameters among Web Parts on a dashboard. The parameters passed can be automatically applied based on user profiles, SharePoint lists, the BDC, manually entered information, and so forth.

 Top of Page

Management

KEY: = Feature Included

Features	Windows SharePoint Services 3.0	Search Server 2008 Express	Forms Server 2007	SharePoint Server 2007 Standard	SharePoint Server 2007 Enterprise
Configuration management Built on the infrastructure and services provided by ASP.NET version 2.0, Windows SharePoint Services 3.0 supports a centralized Web configuration management object model.
Administration user interface The administration Web pages have been reorganized and redesigned based on feedback from the many customers who deployed Windows SharePoint Services 2.0 Service Pack 2 (2.0 SP2) in their organizations.
Delegation In Windows SharePoint Services 3.0, delegation gives SharePoint site owners a secure, scalable, and centrally managed set of administration rights.
Re-parenting Re-parenting is the ability to dynamically re-arrange a hierarchy of SharePoint sites. Previously, in Windows SharePoint Services 2.0 SP2, a site needed to be backed up and deleted from its current location and then restored under a new parent site in the SharePoint site hierarchy.
Provisioning Provisioning is a core component of Windows SharePoint Services 3.0 that: Lets users choose their own template Defines a shared Web application SharePoint sites can be provisioned in two ways: Site templates (*.STP files) that are typically user-created Site definitions that are developer-created and stored on Web server file system
Usage analytics
Monitoring Windows SharePoint Services 3.0 provides a Microsoft Operations Management (MOM) package to support centralized monitoring and management of configurations ranging from single servers and small server farm to very large server farms.

 Top of Page

Platform

KEY: = Feature Included

Features	Windows SharePoint Services 3.0	Search Server 2008 Express	Forms Server 2007	SharePoint Server 2007 Standard	SharePoint Server 2007 Enterprise
Alert filtering Filters are supported to highlight the more relevant alerts.
Richer alert information More information about the item that has changed is included in the alert.
Alert customization Additional platform features are provided for custom formatting, events, and alerts.
Task notifications Task notifications are now sent automatically when a user is assigned a task. There is no need for the user to subscribe to the notification in advance.
Notification service Extensible platform sends customizable e-mail alerts to users. Users participating in a workflow automatically receive e-mail alerts without subscribing in advance. Improved filtering conditions now trigger more relevant alerts to all users.
RSS feeds By integrating RSS feeds for each SharePoint list, Windows SharePoint Services 3.0 provides an efficient mechanism for end users to retrieve the information using RSS-enabled programs such as Windows Internet Explorer 7 and Office Outlook 2007.
Consistent user experience Windows SharePoint Services 3.0 implements many new and enhanced features that make the Windows SharePoint Services user interface more uniform — providing a consistent user experience.
Rights trimmed user interface Users are only allowed to see the features that they have the rights to use. Previously, Windows SharePoint Services 2.0 Service Pack 2 did not inform a user they were not allowed to perform a function until they clicked its link.
Automatic breadcrumb bar Provides immediate navigational context for the user — creating a greater sense of “place” within a SharePoint site.
Quick launch bar Available on all view pages and is more easily customizable.
Top navigation bar Available on all view pages and is more easily customizable.
View improvements Ability to page forward and backward in addition to improved user interface for sorting and filtering.
Descriptive menu actions The Actions drop-down menu provides task-based descriptions of the actions that can be performed on a particular SharePoint list or document library.
Simplified Web Part user interface Simplified user interface for browsing, selecting, and adding Web Parts to a Web Part page. The Web Part catalog is presented as a scrollable list; no more paging forward and backward through the Web Part catalog.
Accessibility Windows SharePoint Services 3.0 is Section 508 and W3C compliant.
Recycle bin Enables a user to easily restore an item that was deleted accidentally. Administration tools are also available to manage the lifecycle of deleted items in the recycle bin.
Backup/restore support for Volume Shadow Copy Service (VSS) Windows SharePoint Services backup and restore functionality is enhanced with the support for VSS a feature of Windows Server 2003.
Document libraries Improvement to SharePoint document libraries include: Checking out documents locally Offline document library support in Office Outlook 2007 Major and minor version numbering and tracking Support for multiple content type Policy, auditing, and workflow Tree view support
Large-list and cross-list indexing The performance of large-lists and cross-lists can be improved through the use of indexes on specific list column properties. This significantly increases the capacity and performance of a Windows SharePoint Services 3.0 list compared to 2.0.
Metadata Users can extend document libraries and lists with custom column properties. The practical number of column properties that a list or document library may have has been significantly increased due to performance and scalability improvements in Windows SharePoint Services 3.0 Lists.
Content types Content types are reusable definitions of document types across your organization. A single document library can store content with multiple document types. A content type is used to define a group of documents that share a common set of attributes; including: Document templates What’s on the “New” button Metadata specific to the content type Shared column property templates Custom InfoPath forms in 2007 Microsoft Office system applications Enterprise defined policies Common workflows Content types are different from traditional file types (which map to physical file formats like Word documents or Excel spreadsheets). Content types are used to define and implement business documents such as functional specifications, budget planning spreadsheets, or new product concept presentation.
Application templates While standard workspaces in Windows SharePoint Services are easy to implement, organizations seeking a more customized deployment can get started quickly with application templates for addressing specific business processes or sets of tasks. A new set of application templates will be available for Windows SharePoint Services 3.0. They will highlight aspects of task coordination and will offer some pre-configured workflows. The application templates provide customers with a baseline for deploying Windows SharePoint Services in context of business processes and set of tasks. A rich ecosystem of solution providers use the application templates as the basis for deeper horizontal and vertical solutions.
Workflow Windows SharePoint Services 3.0 hosts Windows Workflow Foundation (WF) to enable customized creation of workflow solutions and use of structured workflows on document library and list items. Office SharePoint Designer 2007 can be used to design and configure custom workflow solutions with the support for WF in Windows SharePoint Services 3.0. Ready-to-use workflow templates are available with Office SharePoint Server 2007 as well as a new set of application solutions for Windows SharePoint Services downloadable from the Microsoft TechNet Web site.
Tree view Tree view controls are now supported for navigating document libraries in a manner similar to the file system.
Append-only and multi-value lookup fields Append-only fields enable a user to append text to a field without being able to modify the existing content of the field. This is useful for logging and tracking applications. Multi-valued lookup fields enable multiple values to be selected from another list field.
Extensible site and list templates In Windows SharePoint Services 3.0, site and list templates can be edited in Office SharePoint Designer 2007.
Sub-site promotion An existing sub-site can be promoted (repositioned) within the logical hierarchy of SharePoint sites (SharePoint site collection) to which it belongs.
Support for ASP.NET 2.0 Windows SharePoint Services 3.0 leverages the reliability, scalability, and functionality of ASP.NET version 2.0. This includes support for the ASP.NET version 2.0 Web Part Model (with added backward compatibility support for Windows SharePoint Services 2.0 SP2 Web Parts). Building on ASP.NET not only provides a deep technical foundation for Windows SharePoint Services, but also allows Windows SharePoint Services to leverage the Visual Studio development environment for application development.
ASP.NET master pages Each Web page in a SharePoint site references an ASP.NET version 2.0 master page. Master pages provide centralized control of the layout and style of all the pages in a SharePoint site. Each site has a master page gallery that the site owner can use to customize the look of all of the pages on the site.
Performance caching
Object model All object model changes in Windows SharePoint Services 3.0 are highly backward-compatible with Windows SharePoint Services 2.0 SP2. However, you should be aware that your old code, although it will compile, may not behave as expected in the new object-model hierarchy. The Administration object model (Microsoft.SharePoint.Administration) has been completely re-factored to allow for greater extensibility. There is now a hierarchical object store.
Field types Extensible field types allow you to use enterprise data structures within Windows SharePoint Services 3.0 by creating your own controls, which are exposed as simple fields within a list or document library by Windows SharePoint Services 3.0.
Site columns Site columns provide a central, reusable model for column definition. When you create a site column, each list that uses this column has the same definition, and you do not have to do the tedious work of reproducing the column in each list.
Content type settings Content types are a core concept used throughout Windows SharePoint Services 3.0. Content types are designed to help users organize their SharePoint content in a more meaningful way. A content type is a reusable collection of settings you want to apply to a certain category of content. Content types enable you to centrally manage and reuse the metadata and behaviors of a document or item type.
Folders in lists Folders, a popular feature in Windows SharePoint Services 2.0 SP2 document libraries, are now also available in lists. Folders allow further segregation of content within a single list, adding another level of versatility.
Folder metadata Users and developers can now assign metadata to a folder. This creates a rich content holder that contains child content, while appearing as more than a container. Essentially, this allows the folder to function as a separate, but fully functional, item type.
List indexing By allowing a column to be indexed, and stored as a simple name/value pair in a separate database, access to specific items in large lists is significantly improved. These kinds of performance improvements allow SharePoint lists to become true data stores, capable of supporting external applications as well as simple team sites.
Cross-list queries Cross-list queries allow you to use the SPQuery object to query all the lists within a Web or site collection. Previously, you had to enumerate through the parent objects to obtain a collection of SPLists, query the list to return the items, and then build your own collection of list items from the multiple lists.
List items Several new enhancements related to list items have been introduced in Windows SharePoint Services 3.0: Per-item and per-folder security Versioning Required checkout
Property Bags Property Bags are now supported on several major objects: SPWeb, SPFile, SPFolder, and SPListItem.
Web services Windows SharePoint Services 3.0 expands several existing Web services, increasing the number of methods provided through the Lists, SiteData, UserGroup, WebPartPagesWebService, and Webs services.
Change logs The change log is a repository storage feature in Windows SharePoint Services 3.0 that provides item change tracking services that are useful, for example, for data synchronization between Windows SharePoint Services and external applications. Office Outlook 2007 is an example of an external application that uses the change log to synchronize documents and list items for offline access.
Event receivers Events fall into two major categories: List events. Core events, including changes, additions, and removals of list items and list columns (schema changes) Simple site events. Deletion of sites and site collections Events are either synchronous “before” events, denoted by the “XYZing” name format, or asynchronous “after” events, denoted by the “ABCed” name format.
Job service The Job service in Windows SharePoint Services 3.0 provides facilities for setting up a timed job that executes: After a definable time interval. During a certain time period in the hour, day, week, month, or year. The Job service also provides a facility for distributing work amongst servers in a farm; for example, based on a request to create a site (which originates on a Web front end), a one-time job may run as soon as is reasonable on an indexing server.
Feature framework Windows SharePoint Services 3.0 contains a new structure called a feature. A feature is an end-user-oriented container of one or more elements. An element is an atomic Windows SharePoint Services concept. The feature is defined in an XML format, similar to other existing SharePoint structures. Each feature definition is a set of XML files. Many items that were previously contained within a site definition in Windows SharePoint Services 2.0 SP2 are now able to fit as an element. In Windows SharePoint Services 3.0, a SharePoint site definition is transformed into a list of features plus a layout page and a master page. This enables any template site to be transformed using any other site template.
Solution Deployment Model Windows SharePoint Services 3.0 also introduces a new deployment mechanism called a solution. A solution is similar to Web Part packages from Windows SharePoint Services 2.0 in that it is an aggregated CAB file containing XML instructions and files that need to be deployed on each front-end Web server. But solutions go beyond Web part packages to support the deployment of features, site definitions, and related assemblies used for event handlers and workflows. Solutions also assist in pushing deployment files to each Web server in a farm. An administrator adds a solution to a Windows SharePoint Services farm, which then copies the solution CAB file into the configuration database. When the administrator runs the command to deploy the solution, Windows SharePoint Services starts a timer job to push the solution CAB file to each front end web server to install it.
Version history Changes to the item are shown in the version history. In addition, support is provided for “append-only” comment fields.
Major and minor version tracking Tracking of both major version numbers and minor version numbers are supported in Windows SharePoint Services 3.0.
Folder-level and item-level access controls Windows SharePoint Services 3.0 extends group or role-based access controls from sites, document libraries, and lists to individual folders, documents, and list items.
Virtual server security policies An authentication zone is identified with a SharePoint (IIS) virtual server. The same content (document libraries and lists) can be made available to multiple zones (for example, intranet and extranet). Access control lists (ACLs) can have a mixture of users from different authentication providers.
Pluggable authentication Each authentication zone can have a pluggable, custom authentication provider in addition to the default support for Windows Basic, Digest, NTLM, Forms, and Kerberos authentication methods.
LDAP pluggable authentication provider
Single Sign-On (SSO) Permits a person to enter one name and password to use a variety of back-end applications.SSO is used for integrating back-office systems and line-of-business applications that require separate credentials databases. Take advantage of single sign on to authenticate users and leverage this to pre-populate InfoPath forms.
Common search technology and infrastructure Provides a single indexing and search infrastructure that scales from the desktop, through team sites and divisional portal sites, to the largest corporate intranets, extranets, and Internet sites.
Inteoperability and integration XML support SOAP support Web services Open API and Object Model
Inteoperability and integration WSRP
Extensibility and programmability of search Includes three categories of APIs for comprehensive access to Microsoft Search features: Data access: protocol handlers and IFilters Query object model, APIs, Web services, and reusable Search Center Web Parts Administration object model and APIs
Excel spreadsheet developer reuse and extensibility Spreadsheets published to SharePoint sites are accessible more securely using Web services. This means that application developers can take advantage of the logic embedded in a spreadsheet by remotely accessing spreadsheets from any platform. Business analysts can modify or update the model without affecting the business application or having to involve an application developer in the process.

The following table offers a detailed comparison between the capabilities offered by the Visual Studio 2005 Designer for Windows Workflow Foundation and Office SharePoint Designer 2007, and the workflows you can create with each.

Character Limitations

The following sections contain the character limitations that apply to various user-specified parameters in Microsoft Office SharePoint Portal Server 2003.

Portal Site

• Portal site name   The portal site name is limited to 80 Unicode characters.

  The portal site name can consist of all alphanumeric characters except for the following: \ / : * ? " < > |

• Portal site description   The portal site description is limited to 200 Unicode characters.

  The portal site description can consist of all alphanumeric characters, as well as the following: # % * + \ | " ? $ @ [ ] { } ⌂

• Portal site logo   The URL for the portal site logo is limited to 256 ASCII characters.

  The URL for the portal site logo can consist of all alphanumeric characters except for the following: # % * + \ | " ? > < $ @ [ ] { } ⌂

  The following file formats are supported for the graphics file: .gif, .bmp, .jpg, and .png. TIFF files are not supported.

• Portal site URL   The URL for the portal site is limited to 255 characters for the entire URL, including virtual directories.
• Account name for portal site owner   The account name is limited to 128 characters.
• E-mail address for portal site owner   The e-mail address is limited to 255 characters.
• Location for creating SharePoint sites   The URL for creating sites from the Site Directory is limited to 2,048 ASCII characters. In addition, no component of the URL, such as the virtual directory or virtual server, can exceed 128 characters.

  The URL must end with /_layouts/language/scsignup.aspx.

Backward-Compatible Document Library (Web Storage System-Based)

• Document library friendly name   The friendly (display) name cannot exceed 100 characters in length.

Alternate Portal Site Access Mappings

• Mapping name   The mapping name has a maximum length of 64 Unicode characters and must not be null.
• The following character limitations apply for the default, intranet, extranet, and custom URLs:
  • Each URL has a maximum length of 255 Unicode characters and a minimum length of 5 characters.
  • The user can enter the URL in any combination of uppercase and lowercase letters, but the URL is always saved in lowercase.
  • Each URL must be different from all other URLs.

Content Index

• Content index name   The content index name must be less than 50 characters.

  The content index name cannot contain the following characters: + ~ # ' % * ( ) = [ ] { } | \ " < > . ? / @ & or the euro symbol or a space.

Command-Line Operations

This topic lists and explains the operations you can perform with Stsadm.exe. For detailed information about the required and optional parameters, including short forms of the parameters, see Command-Line Parameters. For more information about using the command-line tool, see "Introducing the Administration Tools for Windows SharePoint Services" in the Windows SharePoint Services Administrator's Guide.

Note  To use stsadm.exe, you must be a member of the local Administrators group for the server computer.

You can also get a list of the command-line operations by typing stsadm.exe -help on the command line. Syntax help for specific operations is available by typing stsadm.exe -help <operation name>.

Operations in This Topic

addpath

Adds a defined path (inclusion or exclusion) to a virtual server

Sample syntax:

stsadm.exe -o addpath -url <url> 
  -type <exclusion/explicitinclusion/wildcardinclusion> 

addtemplate

Adds a site template to the template gallery.

Note  If you want the changes to the template list to take effect immediately, run the iisreset command after you run the addtemplate operation.

Sample syntax:

stsadm.exe -o addtemplate -filename <template filename> 
  -title <template title> [-description <template description>] 

adduser

Adds a user account to the specified site and assigns it to the specified site group. Use the siteadmin parameter to register the user as the site administrator.

Sample syntax:

stsadm -o adduser -url <url> -userlogin <DOMAIN\username> 
  -useremail <someone@example.com> -role <site group name>
  -username <user's display name> [-siteadmin] 

addwppack

Adds a Web Part package to your server Web Part gallery. Use the globalinstall parameter to install the Web Parts in the global assembly cache (GAC) rather than in the Bin directories of each virtual server. Assemblies installed in the GAC are available to all applications on the server. The url parameter optionally specifies the URL of the virtual server on which to install the Web Parts. To install the Web Parts on every virtual server on a server, omit theurl parameter. Use the force parameter to overwrite an existing Web Part package with a new version, or to repair a Web Part package by reinstalling it. Use the lcid parameter to specify a language for the Web Part package.

Use filename to specify the path to the cabinet file containing the Web Parts and associated resources. If the Web Part package has already been installed on another server in a server farm configuration, you can install the Web Part package from the configuration database by using the name parameter.

Sample syntax:

stsadm.exe -o addwppack -filename <Web Part Package filename> 
  [-url <url> -globalinstall -force -lcid <language>]
 

backup

Creates a backup of the site at the specified URL. Use the overwrite parameter to replace an existing backup file.

Sample syntax:

stsadm.exe -o backup -url <url> -filename <filename> [-overwrite] 

binddrservice

Registers a data retrieval service for the list of data retrieval services that pertain to a specific setting on the Data Retrieval Services Settings page. Specify the service name and then the setting. Settings include enabled, responsesize, timeout, and update.

Sample syntax:

stsadm.exe -o binddrservice -servicename <service name> -setting <enabled/responsesize/timeout/update>
 

createadminvs

Creates the administration virtual server for Microsoft Windows SharePoint Services. Use the admapid... parameters to create a new application pool for IIS, or to specify the application pool to use for the administration virtual server.

Sample syntax:

stsadm.exe -o createadminvs [-admapcreatenew] 
  [-admapidname <app pool id>] 
  [-admapiptype <configurableid/NetworkService/LocalService/LocalSystem>]
  [-admapidlogin <app pool user account>] [-admapidpwd <app pool password>] 

createsite

Creates a site at the specified URL with the specified user as owner and administrator. If you do not specify the template to use, the owner can choose the template when he or she first browses to the site.

Sample syntax:

stsadm.exe -o createsite -url <url> 
  -ownerlogin <DOMAIN\username> -owneremail <someone@example.com> 
  [-ownername <display name>] [-lcid <language>] 
  [-sitetemplate <site template>] [-title <title>]
  [-description <description>] [-quota <quota template>] 

Note  You must specify the -lcid option when using a non-English template.

createsiteinnewdb

Creates a site at the specified URL and creates a new content database with the username and password you specify. If you do not specify the template to use, the owner can choose the template when he or she first browses to the site.

Sample syntax:

stsadm.exe -o createsiteinnewdb -url <url> 
  -ownerlogin <DOMAIN\username> -owneremail <someone@example.com> 
  [-ownername <owner's name>]
  [-databaseuser <databaseusername>] [-databasepassword <databasepassword> 
  [-databaseserver <databaseserver>] [-databasename <databasename>] 
  [-lcid <language>] [-sitetemplate <site template>] 
  [-title <title>] [-description <description>]  
  [-secondarylogin <DOMAIN\username>] [-secondaryemail <someone@example.com>]
  [-secondaryname <secondary owner's name>] 

Note  You must specify the -lcid option when using a non-English template.

createweb

Creates a subsite at the specified URL. If you do not specify the template to use, the owner can choose the template when he or she first browses to the site. Use the unique parameter to specify unique permissions for the subsite.

Sample syntax:

stsadm.exe -o createweb -url <url> [-lcid <language>] 
  [-sitetemplate <site template>] [-title <title>] 
  [-description <description>] -unique] 

Note  You must specify the -lcid option when using a non-English template.

deleteadminvs

Deletes the administration virtual server for Windows SharePoint Services.

Sample syntax:

stsadm.exe -o deleteadminvs 

deleteconfigdb

Deletes the configuration database for Windows SharePoint Services.

Sample syntax:

stsadm -o deleteconfigdb 

deletepath

Removes an included or excluded path from the list of paths managed by Windows SharePoint Services.

Sample syntax:

stsadm -o deletepath -url <url> 

deletesite

Deletes the specified site. To delete users from Active Directory directory services, specify true for the deleteadaccounts parameter.

Sample syntax:

stsadm.exe -o deletesite -url <url> -deleteadaccounts <true/false> 

deletetemplate

Deletes the specified site template.

Sample syntax:

stsadm.exe -o deletetemplate -title <template title> [-lcid <language>] 

deleteuser

Deletes the specified user.

Sample syntax:

stsadm -o deleteuser -url <url> -userlogin <DOMAIN\username> 

deleteweb

Deletes the specified subsite.

Sample syntax:

stsadm.exe -o deleteweb -url <url> 

deletewppack

Removes the Web Parts in a Web Part package from a virtual server. When you delete the last instance of a Web Parts package on a server or server farm, Stsadm.exe also deletes the Web Part package from the configuration database.

The parameter name specifies the name of the Web Part package. The parameter url optionally specifies the URL of the virtual server on which to delete the Web Parts. If url is omitted, Stsadm.exe deletes the Web Parts from the Bin folder of every virtual server on the server or from the global assembly cache.

Use the lcid parameter to remove a particular language version of a Web Part package.

Sample syntax:

stsadm -o deletewppack -name <name of Web Part package> [-url <url> -lcid <language>] 

disablessc

Disables Self-Service Site Creation for the specified virtual server.

Sample syntax:

stsadm -o disablessc -url <url> 

disablestsisapis

Disables the Windows SharePoint Services ISAPI extensions. This operation is used by the Setup program for Windows SharePoint Services.

Sample syntax:

stsadm -o disablestsisapis 

email

Sets the e-mail configuration settings for your server, or for a specific virtual server (when you use the url parameter).

Sample syntax:

stsadm.exe -o email -outsmtpserver <SMTP server> 
  -fromaddress <someone@example.com> -replytoaddress <someone@example.com> 
  -codepage <codepage> [-url <url>] 

enablessc

Enables Self-Service Site Creation for the specified virtual server.

Sample syntax:

stsadm -o enablessc -url <url> [-requiresecondarycontact] 

enablestsisapis

Enables the Windows SharePoint Services ISAPI extensions. This operation is used by the Setup program for Windows SharePoint Services.

Sample syntax:

stsadm -o enablestsisapis 

enumroles

Lists the site groups that are available for use in a particular site or subsite.

Sample syntax:

stsadm -o enumroles -url <URL> 

enumsites

Lists all of the sites that have been created under a particular virtual server. The url parameter must be the URL of a virtual server.

Sample syntax:

stsadm -o enumsites -url <URL> 

enumsubwebs

Lists the subsites that have been created under a particular site.

Sample syntax:

stsadm -o enumsubwebs -url <URL> 

enumtemplates

Lists the site templates that are available.

Sample syntax:

stsadm.exe -o enumtemplates [-lcid <language>] 

enumusers

Lists the users of a particular site or subsite.

Sample syntax:

stsadm.exe -o enumusers -url <url> 

enumwppacks

Lists the Web Part Packages currently in your server Web Part gallery.

Sample syntax:

stsadm -o enumwppacks [-name <name of Web Part Package>]
   [-url <URL>] 

extendvs

Extends a virtual server with Windows SharePoint Services and creates a new content database.

Note  Extending a virtual server creates a site but does not require the createsite parameter. Use the donotcreatesite parameter if you do not want to create a site when you extend the virtual server.

Sample syntax:

stsadm -o extendvs -url <url> -ownerlogin <DOMAIN\username> 
  -owneremail <someone@example.com> [-ownername <display name>] 
  [-du <database user>] [-ds <database server>] [-dn <database name>] 
  [-dp <database user password>][-lcid <lcid>] [-sitetemplate <site template>]
  [-donotcreatesite] [-apcreatenew] [-apidname <app pool name>]
  [-apidtype <configurableid/NetworkService/LocalService/LocalSystem>] 
  [-apidlogin <DOMAIN\username>]
  [-apidpwd <app pool password>] 

extendvsinwebfarm

Extend a virtual server with Windows SharePoint Services for use in a server farm. This operation does not create a new content database, but allows you to connect to an existing virtual server (vsname) and use the same content database.

Sample syntax:

stsadm -o extendvsinwebfarm -url <url> -vsname <virtual server name>
  [-apcreatenew] [-apidname <app pool name>]
  [-apidtype <configurableid/NetworkService/LocalService/LocalSystem>] 
  [-apidlogin <DOMAIN\username>]
  [-apidpwd <app pool password>] 

getadminport

Returns the administration port for Windows SharePoint Services.

Sample syntax:

stsadm -o getadminport 

getproperty

Returns the property value for the specified property name. For a list of valid properties, see Command-Line Properties.

Sample syntax:

stsadm -o getproperty -pn <property name> [-url <url>] 

removedrservice

Removes a data retrieval service from the list of data retrieval services that pertain to a specific setting on the Data Retrieval Services Settings pages. Specify the service name, and then the setting. Settings include enabled, responsesize, timeout, and update.

Sample syntax:

stsadm.exe -o removedrservice -servicename <service name> -setting <enabled/responsesize/timeout/update>
 

renameweb

Renames the specified subsite.

Sample syntax:

stsadm.exe -o renameweb -url <url> -newname <new subsite name> 

restore

Restores a Web site from a backup file. Use the overwrite parameter to replace any existing Web site at the new location.

Sample syntax:

stsadm.exe -o restore -url <url> -filename <filename> [-overwrite] 

setadminport

Sets the port number for the administration virtual server for Windows SharePoint Services. Use the ssl parameter to specify a Secure Sockets Layer (SSL) connection to the port. Use the admap... parameters to specify the IIS application pool to use or to create a new IIS application pool for the administration virtual server.

Sample syntax:

stsadm.exe -o setadminport -port <port> [-ssl]
  [-admapcreatenew] [-admapidname <app pool id>] 
  [-admapiptype <configurableid/NetworkService/LocalService /LocalSystem>]
  [-admapidlogin <app pool user account>] [-admapidpwd <app pool password>] 

setconfigdb

Creates the configuration database or specifies the connection to an existing configuration database. Setting the configuration database is required before a virtual server can be extended.

Sample syntax:

stsadm.exe -o setconfigdb [-connect] -ds <database server> 
  [-du <database user>] [-dp <database user password>] [-dn <database name>]
  [-hh] [-adcreation] [-addomain <AD domain> [-adou <AD OU>] 

setproperty

Sets the specified property with the specified value. Use the url property to specify a virtual server or site collection to apply the property to, or omit the url parameter to apply the property at the server or server farm level. For a list of valid properties, see Command-Line Properties.

Sample syntax:

stsadm.exe -o setproperty -pn <property name>
  -pv <property value> [-url <url>] 

siteowner

Sets the owner or secondary owner of a site collection. Either the ownerlogin or secondownerlogin parameter must be used.

Sample syntax:

stsadm.exe -o siteowner -url <url>   [-ownerlogin <DOMAIN\username> | -secondownerlogin <DOMAIN\username>] 

unextendvs

Removes Windows SharePoint Services from a particular virtual server. Use the deletecontent parameter to delete the content databases for the virtual server.

Sample syntax:

stsadm.exe -o unextendvs -url <url> [-deletecontent] 

uninstall

Uninstalls Windows SharePoint Services from the default virtual server at port 80. Any other virtual servers that were extended with Windows SharePoint Services will not be unextended. Uninstall removes the Windows SharePoint Services ISAPI extensions and any virtual directories or other files from the virtual server. It does not delete the content databases unless you include the deletecontent parameter. This operation is used by the Setup program for Windows SharePoint Services.

Sample syntax:

stsadm.exe -o uninstall [-deletecontent] 

upgrade

Upgrades the server or the specified virtual server with Windows SharePoint Services. This operation is used by the Setup program for Windows SharePoint Services.

Sample syntax:

stsadm.exe -o upgrade [-url <url>] 

userrole

Specifies the site group membership for a user. Use the add and delete parameters to specify whether to add the user to a site group or remove the user from a site group.

Sample syntax:

stsadm.exe -o userrole -url <url> -userlogin <DOMAIN\username> 
  -role <site group name> [-add] [-delete]

Command-Line Parameters

The following table lists and explains the parameters you can use with operations for Stsadm.exe. For detailed information about the operations, including sample syntax, see Command-Line Operations. For more information about using the command-line tool, see "Introducing the Administration Tools for Windows SharePoint Services" in the Windows SharePoint Services Administrator's Guide.

Command-Line Properties

This topic lists and explains the properties that can be set on the command line by using the Stsadm.exe tool with the getproperty and setproperty operations. To see the current value of a property, you use the getproperty operation. To set the value for a property, you use the setproperty operation. The following examples show the syntax to use when getting or setting a property:

stsadm.exe -o getproperty -pn <property name> [-url <url>]
stsadm.exe -o setproperty -pn <property name> -pv <property value> [-url <url>]

Some properties are available for the entire server, and are called server properties. Some are only available for an individual virtual server. When you get or set a server property, you can omit the url parameter. You must include the url parameter to get or set virtual server properties. For more information about setting properties, see "Introducing the Administration Tools for Windows SharePoint Services" in the Windows SharePoint Services Administrator's Guide.

Server Properties for Windows SharePoint Services

• Antivirus properties
• Data retrieval services properties
• HTML Viewer properties
• Site confirmation and automatic deletion properties
• Usage analysis properties

Virtual Server Properties for Windows SharePoint Services

• Alert properties
• Content database properties
• Data retrieval services properties
• General properties
• Site confirmation and automatic deletion properties

Alert Properties

Use these properties to configure alerts for your server. Specify whether alerts are enabled, whether users are limited as to the number of alerts they can create, and if so, the maximum number of alerts. You can also specify the times to send out immediate, daily, and weekly alerts. For more information about alerts, see Managing Alerts.

Antivirus Properties

Use these properties to configure antivirus protection for your server. Specify whether users can download infected files to their client computers, whether antivirus cleaning is enabled, whether the download and upload scans are enabled, the timeout time for scanning, and the number of threads to take up with antivirus processes. For more information about using antivirus scanning, see Configuring Antivirus Protection.

Content Database Properties

Use these properties to set the server name, user name, and password to use for the default content database for your server. For more information about the default content database, see Managing Content Databases.

Data Retrieval Services Properties

Use these properties to configure data retrieval services for your virtual server, server, or server farm. Specify whether data retrieval services are enabled, whether to inherit the server farm settings for a virtual server, the time an adapter will wait for a response from the back-end data source, the maximum size for data returned from the back-end source, whether adapters can execute requests that contain updatable queries, and the list of supported OLEDB providers. For more information about data retrieval services, see Configuring Data Retrieval Services.

General Properties

Use the following properties to specify general settings for a virtual server. Specify how long (in days) to display the New icon for items added to a Web site, the default quota template and default time zone for Web sites, the maximum size for files posted to Web sites, and whether Web Discussions are enabled for the virtual server.

For more information about specifying virtual server general settings, see Configuring Virtual Servers.

HTML Viewer Properties

Use these properties to specify HTML Viewer options for your server or server farm. Specify whether HTML viewing is enabled, the path (URL) to the HTML Viewer server, the maximum cache size for the HTML Viewer, the maximum file size that can be viewed, and the timeout time for HTML viewing. For more information about HTML viewing, see Managing HTML Viewers.

Site Confirmation and Automatic Deletion Properties

These properties can be set either at the server (and server farm) level or at the virtual server level. Specify whether to send e-mail notifications about unused Web sites, how long to wait before sending the first e-mail notification, how many notifications to send, whether to automatically delete unused Web sites, and when to delete unused Web sites. For more information about site confirmation and automatic deletion, see Managing Unused Web Sites.

Usage Analysis Properties

This property can be set either at the server (and server farm) level or at the virtual server level. For more information about usage analysis, see Configuring Usage Analysis.

If you want the job to start at a specific time, set the beginning and end times to the same time, for example: "daily between 16:55:21 and 16:55:21".

Note  This property can be set only to "daily", not to "weekly" or "immediate".

User Rights and Site Groups

This topic explains the rights and site groups you can assign to users by using operations in Stsadm.exe and by using HTML Administration pages. Each user right or site group is listed by the name that appears in HTML Administration pages. The name used to identify a site group for the Stsadm.exe command-line tool is listed in a table. For each site group, the default rights included in that site group are listed. For each right, any rights dependent on the right are listed, as well as any default site groups that include the right.

For more information about user rights and site groups, see "Managing Site Groups and Permissions" and "Managing Users and Cross-Site Groups" in the Windows SharePoint Services Administrator's Guide. For more information about using the command-line tool, see "Introducing the Administration Tools for Windows SharePoint Services" in the Windows SharePoint Services Administrator's Guide.

Default Site Groups in Windows SharePoint Services

User Rights Available for Windows SharePoint Services

Default Site Groups

Microsoft Windows SharePoint Services includes five site groups by default. You can customize the rights available in these site groups (except for the Guest and Administrator site groups) or add new site groups to combine different sets of rights.

Guest

The Guest site group is designed to be combined with per-list permissions on particular lists to give guest users access to a specific list, without giving them access to the entire site. The Guest site group cannot be customized or deleted.

Reader

The Reader site group allows a user to view items in lists and document libraries, view pages in the site, and create a site using Self-Service Site Creation.

Contributor

The Contributor site group allows a user to interact with Web Parts and lists and document libraries. They can also create and manage personal views and cross-site groups, and personalize Web Part Pages.

Web Designer

The Web Designer site group allows a user to customize the Web site using the HTML tools or a Web page editor compatible with Windows SharePoint Services, such as Microsoft Office FrontPage 2003. For example, Web Designers can create lists from within the site or add new pages to the site by using a Web page editor.

Administrator

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

User Rights

Windows SharePoint Services includes 21 rights, which are used in the five default user site groups. You can change which rights are included in a particular site group (except for the Guest and Administrator site groups) or create a new site group to contain a specific list of rights.

Add and Customize Pages

Grants permission to create ASP.NET, ASP, and HTML pages for a Web site.

Add Items

Grants permission to add items to lists or add documents to document libraries.

Add/Remove Private Web Parts

Grants permission to add and remove Web Parts in order to personalize Web Part Pages.

Apply Style Sheets

Grants permission to apply a style sheet to the entire Web site.

Apply Themes and Borders

Grants permission to apply a theme or border to an entire Web site.

Browse Directories

Grants permission to browse the directory structure of a Web site.

Cancel Check-out

Grants permission to cancel the check-out action performed by another user.

Create Cross-Site Groups

Grants permission to create or delete cross-site groups, or to change membership of a cross-site group.

Create Subsites

Grants permission to create a new subsite or workspace site, such as a Document Workspace site or Meeting Workspace site.

Delete Items

Grants permission to delete list items and documents from the Web site.

Edit Items

Grants permission to edit existing list items and documents in the Web site.

Manage Lists

Grants permission to create, edit, or delete lists and change their settings.

Manage List Permissions

Grants permission to change permissions for a list or document library.

Manage Personal Views

Grants permission to create, edit, or delete personal views on lists.

Manage Site Groups

Grants permission to create, delete, and edit site groups, both by changing the rights assigned to the site group and by changing which users are members of the site group.

Manage Web Site

Grants permission to perform administration tasks for a particular site or subsite.

Update Personal Web Parts

Grants permission to update Web Parts to display personalized information.

Use Self-Service Site Creation

Grants permission to use the Self-Service Site Creation tool to create a top-level Web site.

View Items

Grants permission to view items in lists, documents in document libraries, and Web discussion comments.

View Pages

Grants permission to browse pages in the Web site.

View Usage Data

Grants permission to view reports on Web site usage.

Files and Permissions

This appendix lists the detailed, minimum file permission settings that must be in place for Microsoft Windows SharePoint Services to perform as designed.

Windows SharePoint Services Installation Directory

The Windows SharePoint Services installation directory is C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\60 by default.

Web Site Content Area

This listing is for a Web site content area of \inetpub\wwwroot.

Windows Directory

Windows SharePoint Services also changes permissions for two folders in the Microsoft Windows directory (%WinDir%).

Special Directories and Storage Locations

This appendix lists folders and files used by Microsoft Windows SharePoint Services.

Installation Directory Files

The following files are added to the installation directory (c:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\60) when you install Windows SharePoint Services.

Web Part Resource Files

In addition to the installation directory, there is a Web Part resources directory that contains files used to support custom Web Parts in Windows SharePoint Services. The c:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\wpresources directory contains a web.config file that is used to help control security for ASP.NET files used in Web Parts. For more information about custom Web Parts, see the Windows SharePoint Services Software Development Kit.

Web Site Content Files

The following files are added to each top-level Web site or subsite when a SharePoint site is created.

All other Web site files are stored in the content and configuration database.

Language Considerations

You use two methods to control the language settings available for Web sites based on Microsoft Windows SharePoint Services:

• Language template packs

  Language template packs allow you to use site templates designed for specific languages. When you create a site based on a site template in a language template pack, the navigation and pages for that site are displayed in that language.

• Regional settings

  Regional settings allow you to control how dates, times, and lists are displayed in a particular Web site. Regional settings do not control the language used for the navigation or pages in the site. For more information about regional settings, see Configuring Regional Settings.

About Languages and Locales

Windows SharePoint Services uses the following terms to describe the language settings that are used for a Web site:

• Language ID

  The language ID specified when a Web site is created controls the language used in the Web site itself. For example, if the site was created in French (language ID 1036), all of the toolbars, navigation bars, list and form pages, and so on, appear in French. If the site was created in Arabic (1025), the text is in Arabic, and the default left-to-right orientation of the site is change to right-to-left to properly display Arabic text.

  By default, Windows SharePoint Services has language packs that contain site templates for many language IDs. You can install one or more of these language packs to your Web server to support users creating sites in as many languages as you need. For example, if you have a server running the Japanese version (language ID 1041) of Windows SharePoint Services, you can install a U.S. English (1033) language pack with templates that allow your users to create sites configured for U.S. English. New para

• Locale ID

  The locale ID is specified on the Regional Settings page, and affects how numbers, calendars, sorting, and time are displayed in the site. For example, if you have a U.S. English language site (language ID 1033), and you change the locale ID to French (Canada) (locale ID 3084), the Events list and Calendar views reflect the French notations for dates, numbers, time, and so on. The locale ID does not affect the orientation of the site. Choosing Arabic (Egypt) (locale ID 3073) does not change the site to right-to-left orientation, but does allow you to display the Events list with dates in Arabic notation. Each language template has a default locale ID. For example, in the U.S. English (1033) template, the default locale ID is also 1033.

  Windows SharePoint Services supports all of the locale IDs supported by the Microsoft Windows Server 2003 family, which is a much larger set than the set of language IDs.

For more information about supported language IDs and locale IDs, see Regional and Language Settings.

Customizing Sites to Display Multiple Languages

When you create a site, you choose which language it is displayed in. You cannot display a site in more than one language, or change which language is used. If you need to create a site that can display more than one language, for example if you needed a site for both English and Spanish speakers, use the following method:

1. Install the language packs that you need (in this example, US English and Spanish) to your server.
2. Create sites based on each language pack you need (for example, one site in US English, one in Spanish).
3. Customize one of the sites to include the strings you need from the other site.

   For example, on the US English site, use a Web page editor compatible with Windows SharePoint Services to edit the navigation strings to include both the English strings and the strings from the Spanish site. In this example, "Home" would become "Home/Pagina principal".

4. Save the customized site as a site template, if you expect to use it again.

Because Windows SharePoint Services uses Unicode encoding, the strings from all of the languages should display correctly on the site you customize.

Installing Language Template Packs

Language template packs for Windows SharePoint Services are available as downloadable files from Windows Update. There are language template packs that you can install to support Web sites in many languages. For a list of supported languages, see Regional and Language Settings.

To install a language template pack, you simply download it from Windows Update, and then run the setup program. Note that at the end of setup, Internet Information Services (IIS) is automatically restarted. If you are in a server farm environment, you must install the language template packs to each front-end Web server in your server farm.

During installation, the site templates are added to the Windows SharePoint Services installation directory, under the \TEMPLATE\LCID directory, where LCID is the locale ID for the language. For more information about where the language template files are stored on the server, see Special Directories and Storage Locations. After installation, server administrators, members of the SharePoint administrators group, and users with the Create Subsites right or the Use Self-Service Site Creation right can create Web sites based on the language templates by selecting the language on the Create Top-Level Web Site page or the New SharePoint Site page.

If you no longer need a language template pack, you can uninstall it by using Add or Remove Programs in Control Panel. Uninstalling removes the language template files from the \TEMPLATE\LCID directories.

Caution  When you uninstall a language template pack, any sites based on that language no longer work. You can reinstall the language template pack to restore the sites.

Regional and Language Settings

This topic lists the regional and language settings you can specify from the command line by using operations in Stsadm.exe and by using HTML Administration pages. For more information about specifying regional and language settings, see Language Considerations. For more information about the syntax for command-line operations, see Command-Line Operations.

The following types of regional and language settings are used in Microsoft Windows SharePoint Services:

• Language IDs
• Locale IDs
• Time zones
• Currency IDs

Language IDs

The Language ID determines the language used for text on pages in the Web site (such as the text on the Site Settings page). The languages available for site creation depend on the language template packs you have installed to your server or server farm. Web sites based on Windows SharePoint Services can be created in the following languages.

Windows SharePoint Services also supports input and display of text in the following languages, but not site creation.

Locale IDs

The Locale ID controls the numbering, sorting, calendar, and time formatting for the Web site. You can change the locale for a Web site by using the Regional Settings page. Web sites based on Windows SharePoint Services can be set to the following Locale IDs.

Time Zones

Web sites based on Windows SharePoint Services can be set to any of the time zones recognized by Microsoft Windows Server 2003.

Currency IDs

Web sites based on Windows SharePoint Services can be set to use the following currencies.

Configuring Regional Settings

Every Web site (both top-level Web sites and subsites) based on Microsoft Windows SharePoint Services can be customized to use specific regional settings that apply to the users of your site. You can specify the following regional settings:

• Locale

  Controls how numbers and dates are displayed in the site.

• Sort order

  Controls the sort orders used for lists and libraries.

• Time zone

  Controls the time zone for the Web site.

  Note  You cannot configure a client's view to see document information in their time zone if it is different than the site's time zone. For example, if you have a site set to Eastern Time (US and Canada), and a user in Amsterdam adds a document at 1:00 PM (or 13:00) local time, the document properties show that it was added at 7:00 AM Eastern Time. If this is a problem for your site, you may want to consider creating a personalizable Web Part to show all documents and list items in a specific time zone. For example, the Web Part could list all document libraries and lists in the site, and then the user could select which document library or list to display and the time zone to display it in, and then they would see the data from that document library or list converted to their time zone. For more information about creating custom Web Parts, see the Windows SharePoint Services Software Development Kit.

• Time format

  Specifies whether to display times in 12-hour or 24-hour format.

To specify the locale ID for a site, you can use either HTML Administration pages or the command line. To change the sort order, time zone, or time format for a site, you must use HTML Administration pages. For more information about language settings in Windows SharePoint Services, see Language Considerations.

Changing Regional Settings in HTML Administration Pages

You can change the locale ID, sort order, time zone, and time format for an individual site by using the Regional Settings page in the Site Administration pages.

Server administrators and members of the SharePoint administrators group can also specify a default time zone to use for all sites on a virtual server. For more information, see Configuring Virtual Servers.

Change the regional settings for a site

1. On the site, click Site Settings.
2. On the Site Settings page, under Administration, click Go to Site Administration.
3. On the Site Administration page, under Management and Statistics, click Change regional settings.
4. On the Regional Settings page, select the settings to use, and then click OK.

Specifying Locale IDs on the Command Line

When you extend a virtual server, create a new top-level Web site, or create a new subsite from the command line, you can specify the locale ID to use. The extendvs, createsite, createsiteinnewdb, and createweb operations all accept the lcid parameter. To enter a locale ID in any of these operations, you type the numerical value for the locale (such as 1033 for U.S. English or 1036 for French/France). For example, to create a new subsite and use the French locale ID for France, you would use the following syntax:

stsadm.exe -o createweb -url http://server_name/site1/subsite1 -lcid 1036

All of these operations take several other parameters

Using the Object Model to Manage Windows SharePoint Services

You can use the object model for Microsoft Windows SharePoint Services to manage your servers, sites, users, and other resources. To access the administrative object model for Windows SharePoint Services, you must be an administrator of the local server computer or a member of the SharePoint administrators group.

If you are using a Web application (such as a billing application) to access the object model and perform administrative functions, you must be sure that the Web application is running in the same security context as Windows SharePoint Services. In other words, the Internet Information Services (IIS) application pool for the Web application must allow access to the SharePoint administrators group, or you must include the application pool account in the SharePoint administrators group, or the application pool must be the same application pool as is used for SharePoint Central Administration.

If you are relying on the SharePoint administrators group for the security context, keep in mind that there are some actions that that group cannot perform. The following actions must be performed by a member of the local administrators group for the server computer:

• Extending virtual servers or removing Windows SharePoint Services from a virtual server
• Changing the configuration database settings
• Changing the SharePoint administrators group
• Managing paths

If you want to perform these tasks from a custom application that calls the administrative object model directly, the application must be running as a member of the local administrator group.

Administrative Object Model Scenarios

There are many times when it would be useful to use the object model to perform administrative tasks for Windows SharePoint Services, rather than using the command line tool or HTML Administration pages. For example, you would use the object model when:

• You have a custom administrative application that you use to manage servers in your server farm, rather than using SharePoint Central Administration.

  If your environment is very complex, and your organization uses a special administrative application to manage servers, you can use the object model to call the Windows SharePoint Services administrative functions, rather than using the HTML Administration pages or the command line.

• You have a Web application that needs to call into Windows SharePoint Services to perform a specific set of administrative tasks.

  For example, if you have an application that coordinates online meetings, and you want to create Meeting Workspaces in Windows SharePoint Services automatically, you can use the object model to do so.

• You want to generate administrative reports to track sites, usage, or other data.

  You can use the object model to enumerate the sites owned by particular users, find out how many users or how many files are being added to sites, or determine trends and perform capacity planning to decide when it is time to add another server to your server farm.

• You want to make site creation conditional based on billing information or generate custom pages based on billing information.

  For example, you can use a billing application to verify billing information before a user can create a site. Or, you can use contact or billing information to generate a custom page that shows which sites belong to which site owners.

• You want to make site access conditional based on billing or employment status.

  You can use the quota mechanisms to automatically lock a site if a customer or group is not current in its billing, and only allow access when the billing charges are rationalized. Or if a user is no longer part of your organization, you can lock all sites owned by that user until you determine what to do with the sites. For more information about quotas and locking sites, see Configuring Site Quotas and Locks.

For more information about the administrative object model and using it to perform administrative tasks, see the Windows SharePoint Services Software Development Kit.

Design and Apply a SharePoint Database Naming Convention

Sunday, December 27, 2009 at 4:04PM