Ms Press - Moc3370A First Look Getting Started With Microsoft Office Sharepoint Server 2007 (2008)

3370A: First Look: Getting
Started with Microsoft Office

®
SharePoint Server 2007

®
Information in this document, including URL and other Internet Web site references, is subject to
change without notice. Unless otherwise noted, the example companies, organizations, products,
domain names, e-mail addresses, logos, people, places, and events depicted herein are fictitious,
and no association with any real company, organization, product, domain name, e-mail address,
logo, person, place or event is intended or should be inferred. Complying with all applicable
copyright laws is the responsibility of the user. Without limiting the rights under copyright, no
part of this document may be reproduced, stored in or introduced into a retrieval system, or
transmitted in any form or by any means (electronic, mechanical, photocopying, recording, or
otherwise), or for any purpose, without the express written permission of Microsoft Corporation.
The names of manufacturers, products, or URLs are provided for informational purposes only and
Microsoft makes no representations and warranties, either expressed, implied, or statutory,
regarding these manufacturers or the use of the products with any Microsoft technologies. The
inclusion of a manufacturer or product does not imply endorsement of Microsoft of the
manufacturer or product. Links are provided to third party sites. Such sites are not under the
control of Microsoft and Microsoft is not responsible for the contents of any linked site or any link
contained in a linked site, or any changes or updates to such sites. Microsoft is not responsible for
webcasting or any other form of transmission received from any linked site. Microsoft is providing
these links to you only as a convenience, and the inclusion of any link does not imply endorsement
of Microsoft of the site or the products contained therein.
Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual
property rights covering subject matter in this document. Except as expressly provided in any
written license agreement from Microsoft, the furnishing of this document does not give you any
license to these patents, trademarks, copyrights, or other intellectual property.
© 2006 Microsoft Corporation. All rights reserved.
Microsoft, Active Directory, BizTalk, Excel, FrontPage, InfoPath, Internet Explorer, MS-DOS,
MSN, Outlook, PivotChart, PivotTable, PowerPoint, SharePoint, Visual Basic, Visual C#, Visual
Studio, Windows, Windows Media, Windows NT, and Windows Server are either registered
trademarks or trademarks of Microsoft Corporation in the United States and/or other countries.
All other trademarks are property of their respective owners.
Clinic: 3370A
Released: 04/2006
END-USER LICENSE AGREEMENT FOR OFFICIAL MICROSOFT LEARNING PRODUCTS – STUDENT EDITION
PLEASE READ THIS END-USER LICENSE AGREEMENT (“EULA”) CAREFULLY. BY USING THE MATERIALS AND/OR USING
OR INSTALLING THE SOFTWARE THAT ACCOMPANIES THIS EULA (COLLECTIVELY, THE “LICENSED CONTENT”), YOU
AGREE TO THE TERMS OF THIS EULA. IF YOU DO NOT AGREE, DO NOT USE THE LICENSED CONTENT.
1. GENERAL. This EULA is a legal agreement between you (either an individual or a single entity) and Microsoft Corporation
(“Microsoft”). This EULA governs the Licensed Content, which includes computer software (including online and electronic documentation),
training materials, and any other associated media and printed materials. This EULA applies to updates, supplements, add-on components, and
Internet-based services components of the Licensed Content that Microsoft may provide or make available to you unless Microsoft provides other
terms with the update, supplement, add-on component, or Internet-based services component. Microsoft reserves the right to discontinue any Internet-
based services provided to you or made available to you through the use of the Licensed Content. This EULA also governs any product support
services relating to the Licensed Content except as may be included in another agreement between you and Microsoft. An amendment or addendum
to this EULA may accompany the Licensed Content.
2. GENERAL GRANT OF LICENSE. Microsoft grants you the following rights, conditioned on your compliance with all the terms and
conditions of this EULA. Microsoft grants you a limited, non-exclusive, royalty-free license to install and use the Licensed Content solely in
conjunction with your participation as a student in an Authorized Training Session (as defined below). You may install and use one copy of the
software on a single computer, device, workstation, terminal, or other digital electronic or analog device ("Device"). You may make a second copy of
the software and install it on a portable Device for the exclusive use of the person who is the primary user of the first copy of the software. A license
for the software may not be shared for use by multiple end users. An “Authorized Training Session” means a training session conducted at a
Microsoft Certified Technical Education Center, an IT Academy, via a Microsoft Certified Partner, or such other entity as Microsoft may designate
from time to time in writing, by a Microsoft Certified Trainer (for more information on these entities, please visit www.microsoft.com). WITHOUT
LIMITING THE FOREGOING, COPYING OR REPRODUCTION OF THE LICENSED CONTENT TO ANY SERVER OR LOCATION FOR
FURTHER REPRODUCTION OR REDISTRIBUTION IS EXPRESSLY PROHIBITED.
3. DESCRIPTION OF OTHER RIGHTS AND LICENSE LIMITATIONS
3.1 Use of Documentation and Printed Training Materials.
3.1.1 The documents and related graphics included in the Licensed Content may include technical inaccuracies or
typographical errors. Changes are periodically made to the content. Microsoft may make improvements and/or changes in any of the components of
the Licensed Content at any time without notice. The names of companies, products, people, characters and/or data mentioned in the Licensed
Content may be fictitious and are in no way intended to represent any real individual, company, product or event, unless otherwise noted.
3.1.2 Microsoft grants you the right to reproduce portions of documents (such as student workbooks, white papers, press
releases, datasheets and FAQs) (the “Documents”) provided with the Licensed Content. You may not print any book (either electronic or print
version) in its entirety. If you choose to reproduce Documents, you agree that: (a) use of such printed Documents will be solely in conjunction with
your personal training use; (b) the Documents will not republished or posted on any network computer or broadcast in any media; (c) any
reproduction will include either the Document’s original copyright notice or a copyright notice to Microsoft’s benefit substantially in the format
provided below; and (d) to comply with all terms and conditions of this EULA. In addition, no modifications may made to any
Document.
“Form of Notice:
© 2006. Reprinted with permission by Microsoft Corporation. All rights reserved.
Microsoft and Windows are either registered trademarks or trademarks of Microsoft Corporation in the US and/or other
countries. Other product and company names mentioned herein may be the trademarks of their respective owners.”
3.2 Use of Media Elements. The Licensed Content may include certain photographs, clip art, animations, sounds, music, and video
clips (together "Media Elements"). You may not modify these Media Elements.
3.3 Use of Sample Code. In the event that the Licensed Content include sample source code (“Sample Code”), Microsoft grants
you a limited, non-exclusive, royalty-free license to use, copy and modify the Sample Code; if you elect to exercise the foregoing rights, you agree to
comply with all other terms and conditions of this EULA, including without limitation Sections 3.4, 3.5, and 6.
3.4 Permitted Modifications. In the event that you exercise any rights provided under this EULA to create modifications of the
Licensed Content, you agree that any such modifications: (a) will not be used for providing training where a fee is charged in public or private
classes; (b) indemnify, hold harmless, and defend Microsoft from and against any claims or lawsuits, including attorneys’ fees, which arise from or
result from your use of any modified version of the Licensed Content; and (c) not to transfer or assign any rights to any modified version of the
Licensed Content to any third party without the express written permission of Microsoft.
3.5 Reproduction/Redistribution Licensed Content. Except as expressly provided in this EULA, you may not reproduce or
distribute the Licensed Content or any portion thereof (including any permitted modifications) to any third parties without the express written
permission of Microsoft.
4. RESERVATION OF RIGHTS AND OWNERSHIP. Microsoft reserves all rights not expressly granted to you in this EULA. The
Licensed Content is protected by copyright and other intellectual property laws and treaties. Microsoft or its suppliers own the title, copyright, and
other intellectual property rights in the Licensed Content. You may not remove or obscure any copyright, trademark or patent notices that appear on
the Licensed Content, or any components thereof, as delivered to you. The Licensed Content is licensed, not sold.
5. LIMITATIONS ON REVERSE ENGINEERING, DECOMPILATION, AND DISASSEMBLY. You may not reverse engineer,
decompile, or disassemble the Software or Media Elements, except and only to the extent that such activity is expressly permitted by applicable law
notwithstanding this limitation.
6. LIMITATIONS ON SALE, RENTAL, ETC. AND CERTAIN ASSIGNMENTS. You may not provide commercial hosting services
with, sell, rent, lease, lend, sublicense, or assign copies of the Licensed Content, or any portion thereof (including any permitted modifications
thereof) on a stand-alone basis or as part of any collection, product or service.
7. CONSENT TO USE OF DATA. You agree that Microsoft and its affiliates may collect and use technical information gathered as part of
the product support services provided to you, if any, related to the Licensed Content. Microsoft may use this information solely to improve our
products or to provide customized services or technologies to you and will not disclose this information in a form that personally identifies you.
8. LINKS TO THIRD PARTY SITES. You may link to third party sites through the use of the Licensed Content. The third party sites are
not under the control of Microsoft, and Microsoft is not responsible for the contents of any third party sites, any links contained in third party sites, or
any changes or updates to third party sites. Microsoft is not responsible for webcasting or any other form of transmission received from any third
party sites. Microsoft is providing these links to third party sites to you only as a convenience, and the inclusion of any link does not imply an
endorsement by Microsoft of the third party site.
9. ADDITIONAL LICENSED CONTENT/SERVICES. This EULA applies to updates, supplements, add-on components, or Internet-
based services components, of the Licensed Content that Microsoft may provide to you or make available to you after the date you obtain your initial
copy of the Licensed Content, unless we provide other terms along with the update, supplement, add-on component, or Internet-based services
component. Microsoft reserves the right to discontinue any Internet-based services provided to you or made available to you through the use of the
Licensed Content.
10. U.S. GOVERNMENT LICENSE RIGHTS. All software provided to the U.S. Government pursuant to solicitations issued on or after
December 1, 1995 is provided with the commercial license rights and restrictions described elsewhere herein. All software provided to the U.S.
Government pursuant to solicitations issued prior to December 1, 1995 is provided with “Restricted Rights” as provided for in FAR, 48 CFR 52.227-
14 (JUNE 1987) or DFAR, 48 CFR 252.227-7013 (OCT 1988), as applicable.
11. EXPORT RESTRICTIONS. You acknowledge that the Licensed Content is subject to U.S. export jurisdiction. You agree to comply
with all applicable international and national laws that apply to the Licensed Content, including the U.S. Export Administration Regulations, as well
as end-user, end-use, and destination restrictions issued by U.S. and other governments. For additional information see
<http://www.microsoft.com/exporting/>.
12. TRANSFER. The initial user of the Licensed Content may make a one-time permanent transfer of this EULA and Licensed Content to
another end user, provided the initial user retains no copies of the Licensed Content. The transfer may not be an indirect transfer, such as a
consignment. Prior to the transfer, the end user receiving the Licensed Content must agree to all the EULA terms.
13. “NOT FOR RESALE” LICENSED CONTENT. Licensed Content identified as “Not For Resale” or “NFR,” may not be sold or
otherwise transferred for value, or used for any purpose other than demonstration, test or evaluation.
14. TERMINATION. Without prejudice to any other rights, Microsoft may terminate this EULA if you fail to comply with the terms and
conditions of this EULA. In such event, you must destroy all copies of the Licensed Content and all of its component parts.
15. DISCLAIMER OF WARRANTIES. TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, MICROSOFT
AND ITS SUPPLIERS PROVIDE THE LICENSED CONTENT AND SUPPORT SERVICES (IF ANY) AS IS AND WITH ALL FAULTS,
AND MICROSOFT AND ITS SUPPLIERS HEREBY DISCLAIM ALL OTHER WARRANTIES AND CONDITIONS, WHETHER
EXPRESS, IMPLIED OR STATUTORY, INCLUDING, BUT NOT LIMITED TO, ANY (IF ANY) IMPLIED WARRANTIES, DUTIES OR
CONDITIONS OF MERCHANTABILITY, OF FITNESS FOR A PARTICULAR PURPOSE, OF RELIABILITY OR AVAILABILITY, OF
ACCURACY OR COMPLETENESS OF RESPONSES, OF RESULTS, OF WORKMANLIKE EFFORT, OF LACK OF VIRUSES, AND
OF LACK OF NEGLIGENCE, ALL WITH REGARD TO THE LICENSED CONTENT, AND THE PROVISION OF OR FAILURE TO
PROVIDE SUPPORT OR OTHER SERVICES, INFORMATION, SOFTWARE, AND RELATED CONTENT THROUGH THE
LICENSED CONTENT, OR OTHERWISE ARISING OUT OF THE USE OF THE LICENSED CONTENT. ALSO, THERE IS NO
WARRANTY OR CONDITION OF TITLE, QUIET ENJOYMENT, QUIET POSSESSION, CORRESPONDENCE TO DESCRIPTION OR
NON-INFRINGEMENT WITH REGARD TO THE LICENSED CONTENT. THE ENTIRE RISK AS TO THE QUALITY, OR ARISING
OUT OF THE USE OR PERFORMANCE OF THE LICENSED CONTENT, AND ANY SUPPORT SERVICES, REMAINS WITH YOU.
16. EXCLUSION OF INCIDENTAL, CONSEQUENTIAL AND CERTAIN OTHER DAMAGES. TO THE MAXIMUM EXTENT
PERMITTED BY APPLICABLE LAW, IN NO EVENT SHALL MICROSOFT OR ITS SUPPLIERS BE LIABLE FOR ANY SPECIAL,
INCIDENTAL, PUNITIVE, INDIRECT, OR CONSEQUENTIAL DAMAGES WHATSOEVER (INCLUDING, BUT NOT LIMITED TO,
DAMAGES FOR LOSS OF PROFITS OR CONFIDENTIAL OR OTHER INFORMATION, FOR BUSINESS INTERRUPTION, FOR
PERSONAL INJURY, FOR LOSS OF PRIVACY, FOR FAILURE TO MEET ANY DUTY INCLUDING OF GOOD FAITH OR OF
REASONABLE CARE, FOR NEGLIGENCE, AND FOR ANY OTHER PECUNIARY OR OTHER LOSS WHATSOEVER) ARISING
OUT OF OR IN ANY WAY RELATED TO THE USE OF OR INABILITY TO USE THE LICENSED CONTENT, THE PROVISION OF
OR FAILURE TO PROVIDE SUPPORT OR OTHER SERVICES, INFORMATION, SOFTWARE, AND RELATED CONTENT
THROUGH THE LICENSED CONTENT, OR OTHERWISE ARISING OUT OF THE USE OF THE LICENSED CONTENT, OR
OTHERWISE UNDER OR IN CONNECTION WITH ANY PROVISION OF THIS EULA, EVEN IN THE EVENT OF THE FAULT,
TORT (INCLUDING NEGLIGENCE), MISREPRESENTATION, STRICT LIABILITY, BREACH OF CONTRACT OR BREACH OF
WARRANTY OF MICROSOFT OR ANY SUPPLIER, AND EVEN IF MICROSOFT OR ANY SUPPLIER HAS BEEN ADVISED OF THE
POSSIBILITY OF SUCH DAMAGES. BECAUSE SOME STATES/JURISDICTIONS DO NOT ALLOW THE EXCLUSION OR
LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES, THE ABOVE LIMITATION MAY NOT APPLY
TO YOU.
17. LIMITATION OF LIABILITY AND REMEDIES. NOTWITHSTANDING ANY DAMAGES THAT YOU MIGHT INCUR FOR
ANY REASON WHATSOEVER (INCLUDING, WITHOUT LIMITATION, ALL DAMAGES REFERENCED HEREIN AND ALL
DIRECT OR GENERAL DAMAGES IN CONTRACT OR ANYTHING ELSE), THE ENTIRE LIABILITY OF MICROSOFT AND ANY
OF ITS SUPPLIERS UNDER ANY PROVISION OF THIS EULA AND YOUR EXCLUSIVE REMEDY HEREUNDER SHALL BE
LIMITED TO THE GREATER OF THE ACTUAL DAMAGES YOU INCUR IN REASONABLE RELIANCE ON THE LICENSED
CONTENT UP TO THE AMOUNT ACTUALLY PAID BY YOU FOR THE LICENSED CONTENT OR US$5.00. THE FOREGOING
LIMITATIONS, EXCLUSIONS AND DISCLAIMERS SHALL APPLY TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE
LAW, EVEN IF ANY REMEDY FAILS ITS ESSENTIAL PURPOSE.
18. APPLICABLE LAW. If you acquired this Licensed Content in the United States, this EULA is governed by the laws of the State of
Washington. If you acquired this Licensed Content in Canada, unless expressly prohibited by local law, this EULA is governed by the laws in force
in the Province of Ontario, Canada; and, in respect of any dispute which may arise hereunder, you consent to the jurisdiction of the federal and
provincial courts sitting in Toronto, Ontario. If you acquired this Licensed Content in the European Union, Iceland, Norway, or Switzerland, then
local law applies. If you acquired this Licensed Content in any other country, then local law may apply.
19. ENTIRE AGREEMENT; SEVERABILITY. This EULA (including any addendum or amendment to this EULA which is included with
the Licensed Content) are the entire agreement between you and Microsoft relating to the Licensed Content and the support services (if any) and they
supersede all prior or contemporaneous oral or written communications, proposals and representations with respect to the Licensed Content or any
other subject matter covered by this EULA. To the extent the terms of any Microsoft policies or programs for support services conflict with the terms
of this EULA, the terms of this EULA shall control. If any provision of this EULA is held to be void, invalid, unenforceable or illegal, the other
provisions shall continue in full force and effect.
Should you have any questions concerning this EULA, or if you desire to contact Microsoft for any reason, please use the address information
enclosed in this Licensed Content to contact the Microsoft subsidiary serving your country or visit Microsoft on the World Wide Web at
http://www.microsoft.com.
Si vous avez acquis votre Contenu Sous Licence Microsoft au CANADA :
DÉNI DE GARANTIES. Dans la mesure maximale permise par les lois applicables, le Contenu Sous Licence et les services de soutien
technique (le cas échéant) sont fournis TELS QUELS ET AVEC TOUS LES DÉFAUTS par Microsoft et ses fournisseurs, lesquels par les
présentes dénient toutes autres garanties et conditions expresses, implicites ou en vertu de la loi, notamment, mais sans limitation, (le cas
échéant) les garanties, devoirs ou conditions implicites de qualité marchande, d’adaptation à une fin usage particulière, de fiabilité ou de
disponibilité, d’exactitude ou d’exhaustivité des réponses, des résultats, des efforts déployés selon les règles de l’art, d’absence de virus et
d’absence de négligence, le tout à l’égard du Contenu Sous Licence et de la prestation des services de soutien technique ou de l’omission de la
’une telle prestation des services de soutien technique ou à l’égard de la fourniture ou de l’omission de la fourniture de tous autres services,
renseignements, Contenus Sous Licence, et contenu qui s’y rapporte grâce au Contenu Sous Licence ou provenant autrement de l’utilisation
du Contenu Sous Licence. PAR AILLEURS, IL N’Y A AUCUNE GARANTIE OU CONDITION QUANT AU TITRE DE PROPRIÉTÉ, À
LA JOUISSANCE OU LA POSSESSION PAISIBLE, À LA CONCORDANCE À UNE DESCRIPTION NI QUANT À UNE ABSENCE DE
CONTREFAÇON CONCERNANT LE CONTENU SOUS LICENCE.
EXCLUSION DES DOMMAGES ACCESSOIRES, INDIRECTS ET DE CERTAINS AUTRES DOMMAGES. DANS LA MESURE
MAXIMALE PERMISE PAR LES LOIS APPLICABLES, EN AUCUN CAS MICROSOFT OU SES FOURNISSEURS NE SERONT
RESPONSABLES DES DOMMAGES SPÉCIAUX, CONSÉCUTIFS, ACCESSOIRES OU INDIRECTS DE QUELQUE NATURE QUE CE
SOIT (NOTAMMENT, LES DOMMAGES À L’ÉGARD DU MANQUE À GAGNER OU DE LA DIVULGATION DE
RENSEIGNEMENTS CONFIDENTIELS OU AUTRES, DE LA PERTE D’EXPLOITATION, DE BLESSURES CORPORELLES, DE LA
VIOLATION DE LA VIE PRIVÉE, DE L’OMISSION DE REMPLIR TOUT DEVOIR, Y COMPRIS D’AGIR DE BONNE FOI OU
D’EXERCER UN SOIN RAISONNABLE, DE LA NÉGLIGENCE ET DE TOUTE AUTRE PERTE PÉCUNIAIRE OU AUTRE PERTE DE
QUELQUE NATURE QUE CE SOIT) SE RAPPORTANT DE QUELQUE MANIÈRE QUE CE SOIT À L’UTILISATION DU CONTENU
SOUS LICENCE OU À L’INCAPACITÉ DE S’EN SERVIR, À LA PRESTATION OU À L’OMISSION DE LA ’UNE TELLE
PRESTATION DE SERVICES DE SOUTIEN TECHNIQUE OU À LA FOURNITURE OU À L’OMISSION DE LA FOURNITURE DE
TOUS AUTRES SERVICES, RENSEIGNEMENTS, CONTENUS SOUS LICENCE, ET CONTENU QUI S’Y RAPPORTE GRÂCE AU
CONTENU SOUS LICENCE OU PROVENANT AUTREMENT DE L’UTILISATION DU CONTENU SOUS LICENCE OU
AUTREMENT AUX TERMES DE TOUTE DISPOSITION DE LA U PRÉSENTE CONVENTION EULA OU RELATIVEMENT À UNE
TELLE DISPOSITION, MÊME EN CAS DE FAUTE, DE DÉLIT CIVIL (Y COMPRIS LA NÉGLIGENCE), DE RESPONSABILITÉ
STRICTE, DE VIOLATION DE CONTRAT OU DE VIOLATION DE GARANTIE DE MICROSOFT OU DE TOUT FOURNISSEUR ET
MÊME SI MICROSOFT OU TOUT FOURNISSEUR A ÉTÉ AVISÉ DE LA POSSIBILITÉ DE TELS DOMMAGES.
LIMITATION DE RESPONSABILITÉ ET RECOURS. MALGRÉ LES DOMMAGES QUE VOUS PUISSIEZ SUBIR POUR QUELQUE
MOTIF QUE CE SOIT (NOTAMMENT, MAIS SANS LIMITATION, TOUS LES DOMMAGES SUSMENTIONNÉS ET TOUS LES
DOMMAGES DIRECTS OU GÉNÉRAUX OU AUTRES), LA SEULE RESPONSABILITÉ ’OBLIGATION INTÉGRALE DE
MICROSOFT ET DE L’UN OU L’AUTRE DE SES FOURNISSEURS AUX TERMES DE TOUTE DISPOSITION DEU LA PRÉSENTE
CONVENTION EULA ET VOTRE RECOURS EXCLUSIF À L’ÉGARD DE TOUT CE QUI PRÉCÈDE SE LIMITE AU PLUS ÉLEVÉ
ENTRE LES MONTANTS SUIVANTS : LE MONTANT QUE VOUS AVEZ RÉELLEMENT PAYÉ POUR LE CONTENU SOUS
LICENCE OU 5,00 $US. LES LIMITES, EXCLUSIONS ET DÉNIS QUI PRÉCÈDENT (Y COMPRIS LES CLAUSES CI-DESSUS),
S’APPLIQUENT DANS LA MESURE MAXIMALE PERMISE PAR LES LOIS APPLICABLES, MÊME SI TOUT RECOURS
N’ATTEINT PAS SON BUT ESSENTIEL.
À moins que cela ne soit prohibé par le droit local applicable, la présente Convention est régie par les lois de la province d’Ontario, Canada. Vous
consentez Chacune des parties à la présente reconnaît irrévocablement à la compétence des tribunaux fédéraux et provinciaux siégeant à Toronto, dans
de la province d’Ontario et consent à instituer tout litige qui pourrait découler de la présente auprès des tribunaux situés dans le district judiciaire de
York, province d’Ontario.
Au cas où vous auriez des questions concernant cette licence ou que vous désiriez vous mettre en rapport avec Microsoft pour quelque raison que ce
soit, veuillez utiliser l’information contenue dans le Contenu Sous Licence pour contacter la filiale de succursale Microsoft desservant votre pays,
dont l’adresse est fournie dans ce produit, ou visitez écrivez à : Microsoft sur le World Wide Web à http://www.microsoft.com
3370A: First Look: Getting Started with Microsoft® Office SharePoint® Server 2007 vii
Contents
Introduction
Clinic Materials .......................................................................................................2
Prerequisites ............................................................................................................3
Clinic Outline ..........................................................................................................4
Microsoft Learning ..................................................................................................5
Microsoft Certification Program .............................................................................7
Facilities ................................................................................................................10
Session 1: Office SharePoint Server 2007 Functional and Architectural
Overview
Session 1: Office SharePoint Server 2007 Functional and Architectural
Overview .................................................................................................................1
Design Goals Behind Office SharePoint Server 2007 .............................................2
Office SharePoint Server 2007 Features..................................................................9
Office SharePoint Server 2007 Software Components..........................................19
Office SharePoint Server 2007 Administrative Architecture ................................25
Office SharePoint Server 2007 Security Requirements.........................................33
Office SharePoint Server 2007 Physical Architecture...........................................39
Session Summary ..................................................................................................48
Next Steps..............................................................................................................49
Questions and Answers .........................................................................................50
Session 2: Enterprise Content Management with Office SharePoint
Server 2007
Session 2: Enterprise Content Management with Office SharePoint
Server 2007..............................................................................................................1
Document Management Using Office SharePoint Server 2007 ..............................2
Using Document Workflows ...................................................................................8
Using Records Management Features ...................................................................14
Web Content Management Overview ...................................................................21
Creating Web Pages...............................................................................................31
Advanced Web Content Management ...................................................................37
Session Summary ..................................................................................................44
Next Steps..............................................................................................................45
Session 3: Organizing and Finding Resources with Office SharePoint
Server 2007
Session 3: Organizing and Finding Resources with Office SharePoint
Server 2007..............................................................................................................1
Building Portals by Using Office SharePoint Server 2007......................................2
Building Personal SharePoint Sites by Using Office SharePoint Server 2007......11
Managing Search ...................................................................................................20
Search Relevance...................................................................................................30
Search Syntax ........................................................................................................37
Session Summary ..................................................................................................40
Next Steps..............................................................................................................41
viii 3370A: First Look: Getting Started with Microsoft® Office SharePoint® Server 2007
Session 4: Business Solutions Using Office SharePoint Server 2007

Session 4: Business Solutions Using Office SharePoint Server 2007 .....................1
Using the Business Data Catalog.............................................................................2
Using Forms Server ...............................................................................................14
Using Excel Services .............................................................................................25
Creating Report Center Sites .................................................................................35
Session Summary ..................................................................................................42
Next Steps..............................................................................................................43
Questions and Answers..........................................................................................44
Clinic Evaluation ...................................................................................................45
3370A: First Look: Getting Started with Microsoft® Office SharePoint® Server 2007 ix
About This Clinic

This section provides you with a brief description of the clinic, audience,
suggested prerequisites, and clinic objectives.
Description At the end of this one-day clinic, the students will have a high-level
understanding of the features and technologies available in Microsoft® Office
SharePoint® Server 2007. This clinic describes the design goals and features of
Office SharePoint Server 2007. The features explained include enterprise
content management, portals, and Search. In addition, building business
solutions using Office SharePoint Server 2007 is discussed.
Audience The primary audience for this clinic is the IT Professional who generally works
with both Microsoft Windows® and Office technologies. The types of duties
that are typical of this IT Pro are admin and support duties—for example,
planning and deployment of Office server products in a Windows environment;
configuration and security administration; and updates of Office upgrades
and/or patches. The target audience for this clinic is IT Pros that want an
overview of what Microsoft Office SharePoint Server 2007 is and how to
deploy it.
Student prerequisites This clinic requires that students meet the following prerequisites:
1 year experience with Office system technologies
1 year experience with Windows client and server operating systems
Experience installing, configuring, and supporting Microsoft Office
technologies
Working knowledge of Windows SharePoint Services 3.0
Objectives After completing this clinic, the student will be able to:
Describe the design goals and features of Office SharePoint Server 2007
Describe how to manage documents and Web content using Office
Describe the Office SharePoint Server 2007 features for organizing and
finding resources.
Describe how to implement business solutions using Office SharePoint
Server 2007
x 3370A: First Look: Getting Started with Microsoft® Office SharePoint® Server 2007
Document Conventions
The following conventions are used in clinic materials to distinguish elements
of the text.
Convention Use
Bold Represents commands, command options, and syntax that must

be typed exactly as shown. It also indicates commands on menus
and buttons, dialog box titles and options, and icon and menu
names.
Italic In syntax statements or descriptive text, indicates argument
names or placeholders for variable information. Italic is also
used for introducing new terms, for book titles, and for emphasis
in the text.
Title Capitals Indicate domain names, user names, computer names, directory
names, and folder and file names, except when specifically
referring to case-sensitive names. Unless otherwise indicated,
you can use lowercase letters when you type a directory name or
file name in a dialog box or at a command prompt.
ALL CAPITALS Indicate the names of keys, key sequences, and key
combinations — for example, ALT+SPACEBAR.
monospace Represents code samples or examples of screen text.
[] In syntax statements, enclose optional items. For example,
[filename] in command syntax indicates that you can choose to
type a file name with the command. Type only the information
within the brackets, not the brackets themselves.
{} In syntax statements, enclose required items. Type only the
information within the braces, not the braces themselves.
| In syntax statements, separates an either/or choice.
Ç Indicates a procedure with sequential steps.
... In syntax statements, specifies that the preceding item may be
repeated.
. Represents an omitted portion of a code sample.
.
.
THIS PAGE INTENTIONALLY LEFT BLANK

Introduction
Contents
Introduction 1
Clinic Materials 2
Prerequisites 3
Clinic Outline 4
Microsoft Learning 5
Microsoft Certification Program 7
Facilities 10

Introduction 1
Introduction
2 Introduction
Clinic Materials
The following materials are included with your kit:

Clinic evaluation. To provide feedback on the clinic, training facility, and instructor, you will have
the opportunity to complete an online evaluation near the end of the clinic.
To provide additional comments or feedback on the clinic, send e-mail to
support@mscourseware.com. To inquire about the Microsoft® Certified Professional program,
send e-mail to mcphelp@microsoft.com.
Introduction 3
Prerequisites
This clinic requires that you have general knowledge and competence in managing Microsoft
Windows Server™ 2003 environment, and it requires that you have the following knowledge of and
experience with the following:
Microsoft Office system technologies
Microsoft Windows® client and server operating systems
Experience installing, configuring, and supporting Microsoft Office technologies
Working knowledge of Windows SharePoint® Services 3.0
4 Introduction
Clinic Outline
Session 1, “Office SharePoint Server 2007 Functional and Architectural Overview,” provides a
summary of the design goals and features of Office SharePoint Server 2007. It also includes an
overview of the administrative architecture, security requirements, and physical architecture.
Session 2, “Enterprise Content Management with Office SharePoint Server 2007,” provides an
overview of managing documents and Web content using Office SharePoint Server 2007. This
session explains document management, document workflows, and records management features.
This session also explains Web content management, creating Web pages, and advanced Web
content management features.
Session 3, “Organizing and Finding Resources with Office SharePoint Server 2007,” provides an
overview of the portal and search capabilities in Office SharePoint Server 2007. This session
explains how to build portals and personal SharePoint sites. It also explains how to manage search
and describes search relevance features.
Session 4, “Business Solutions Using Office SharePoint Server 2007,” provides an overview of
how to implement business solutions using Office SharePoint Server 2007. This session explains
how to use Forms server, Microsoft Excel® Services, Business Data Catalog, and Report Center
Sites.
Introduction 5
Microsoft Learning
Introduction
Microsoft Learning develops Official Microsoft Learning Products for computer professionals who
design, develop, support, implement, or manage solutions by using Microsoft products and
technologies. These learning products provide comprehensive, skills-based training in instructor-led
and online formats.
Additional recommended learning products

Each learning product relates in some way to another learning product. A related learning product
may be a prerequisite, a follow-up in a recommended series, or a learning product that offers
additional training.
It is recommended that you take the following learning products in this order:
HOL 3373: First Look: Getting Started with Windows SharePoint Services Hands-On Lab
Course 3370: First Look: Getting Started with Microsoft Office SharePoint Server 2007
Course 3199: First Look: Getting Started with the 2007 Microsoft Office System
Other related learning products may become available in the future, so for up-to-date information
about recommended learning products, visit the Microsoft Learning Web site.
Microsoft Learning information

For more information, visit the Microsoft Learning Web site at
http://www.microsoft.com/learning/.
6 Introduction
Microsoft Learning Product Types
Microsoft Learning offers four instructor-led product types. Each type is specific to a particular
audience type and level of experience. The different product types also tend to suit different
learning styles. These types are as follows:
Courses are for information technology (IT) professionals and developers who are new to a
particular product or technology and for experienced individuals who prefer to learn in a traditional
classroom format. Courses provide a relevant and guided learning experience that combines lecture
and practice to deliver thorough coverage of a Microsoft product or technology. Courses are
designed to address the needs of learners engaged in the planning, design, implementation,
management, and support phases of the technology adoption lifecycle. They provide detailed
information by focusing on concepts and principles, reference content, and in-depth, hands-on lab
activities to ensure knowledge transfer. Typically, the content of a course is broad, addressing a
wide range of tasks necessary for the job role.
Workshops are for knowledgeable IT professionals and developers who learn best by doing and
exploring. Workshops provide a hands-on learning experience in which participants can use
Microsoft products in a safe and collaborative environment based on real-world scenarios.
Workshops are the learning products in which students learn by doing through scenario and through
troubleshooting hands-on labs, targeted reviews, information resources, and best practices, with
instructor facilitation.
Clinics are for IT professionals, developers, and technical decision makers. Clinics offer a detailed
presentation that may describe the features and functionality of an existing or new Microsoft
product or technology, provide guidelines and best practices for decision making, and/or showcase
product demonstrations and solutions. Clinics focus on how specific features will solve business
problems.
Stand-alone Hands-On Labs provide IT professionals and developers with hands-on experience
with an existing or new Microsoft product or technology. Hands-on labs provide a realistic and safe
environment to encourage knowledge transfer by learning through doing. The labs provided are
completely prescriptive so that no lab answer keys are required. There is very little lecture or text
content provided in hands-on labs, aside from lab introductions, context setting, and lab reviews.
Introduction 7
Microsoft Certification Program
Introduction
Microsoft Learning offers a variety of certification credentials for developers and IT professionals.
The Microsoft Certified Program (MCP) program is the leading certification program for validating
your experience and skills, keeping you competitive in today’s changing business environment.
MCP certifications
The MCP program includes the following certifications.
MCDST on Microsoft Windows XP
The Microsoft Certified Desktop Support Technician (MCDST) certification is designed for
professionals who support end users and successfully troubleshoot desktop environments
running on the Microsoft Windows operating system.
MCSA on Windows Server 2003
The Microsoft Certified Systems Administrator (MCSA) certification is designed for
professionals who implement, manage, and troubleshoot existing network and system
environments based on the Windows Server 2003 platform. Implementation responsibilities
include installing and configuring parts of the systems. Management responsibilities include
administering and supporting the systems.
MCSE on Windows Server 2003
The Microsoft Certified Systems Engineer (MCSE) credential is the premier certification for
professionals who analyze the business requirements and design and implement the
infrastructure for business solutions based on the Windows Server 2003 platform.
Implementation responsibilities include installing, configuring, and troubleshooting network
systems.
8 Introduction
MCAD
The Microsoft Certified Application Developer (MCAD) for Microsoft .NET credential is
appropriate for professionals who use Microsoft technologies to develop and maintain
department-level applications, components, Web or desktop clients, or back-end data services
or who work in teams developing enterprise applications. The credential covers job tasks
ranging from developing to deploying and maintaining these solutions.
MCSD
The Microsoft Certified Solution Developer (MCSD) credential is the premier certification for
professionals who design and develop leading-edge business solutions with Microsoft
development tools, technologies, platforms, and the Microsoft Windows DNA architecture. The
types of applications MCSDs can develop include desktop applications and multi-user, Web-
based, N-tier, and transaction-based applications. The credential covers job tasks ranging from
analyzing business requirements to maintaining solutions.
MCDBA on Microsoft SQL Server™ 2000
The Microsoft Certified Database Administrator (MCDBA) credential is the premier
certification for professionals who implement and administer Microsoft SQL Server databases.
The certification is appropriate for individuals who derive physical database designs, develop
logical data models, create physical databases, create data services by using Transact-SQL,
manage and maintain databases, configure and manage security, monitor and optimize
databases, and install and configure SQL Server.
MCP
The Microsoft Certified Professional (MCP) credential is for individuals who have the skills to
successfully implement a Microsoft product or technology as part of a business solution in an
organization. Hands-on experience with the product is necessary to successfully achieve
certification.
MCT
Microsoft Certified Trainers (MCTs) demonstrate the instructional and technical skills that
qualify them to deliver Microsoft Learning Products through Microsoft Certified Technical
Education Centers (Microsoft CTECs).
Certification requirements
Requirements differ for each certification category and are specific to the products and job
functions addressed by the certification. To become a Microsoft Certified Professional, you must
pass rigorous certification exams that provide a valid and reliable measure of technical proficiency
and expertise.
Note For additional information see the Microsoft Learning Web site at
http://www.microsoft.com/learning.
You can also send e-mail to mcphelp@microsoft.com if you have specific certification
questions.
Introduction 9
Acquiring the skills tested by an MCP exam

Official Microsoft Learning Products can help you develop the skills that you need to do your job.
They also complement the experience that you gain while working with Microsoft products and
technologies. However, no one-to-one correlation exists between the learning products and MCP
exams. Microsoft does not expect or intend for learning products to be the sole preparation method
for passing MCP exams. Practical product knowledge and experience are also necessary to pass
MCP exams.
To help prepare for MCP exams, use the preparation guides that are available for each exam. Each
Exam Preparation Guide contains exam-specific information, such as a list of the topics on which
you will be tested. These guides are available on the Microsoft Learning Web site at
http://www.microsoft.com/learning/.
10 Introduction
Facilities

Session 1: Office SharePoint Server 2007
Functional and Architectural Overview
Contents
Session 1: Office SharePoint
Server 2007 Functional and Architectural
Overview 1
Design Goals Behind Office SharePoint
Server 2007 2
Office SharePoint Server 2007 Features 9
Office SharePoint Server 2007 Software
Components 19
Office SharePoint Server 2007
Administrative Architecture 25
Office SharePoint Server 2007 Security
Requirements 33
Office SharePoint Server 2007 Physical
Architecture 39
Session Summary 48
Next Steps 49
Questions and Answers 50

Session 1: Office SharePoint Server 2007 Functional and Architectural Overview 1
Session 1: Office SharePoint Server 2007 Functional and

Architectural Overview
Overview
Microsoft® Office SharePoint® Server 2007 is a new and better method for storing and
disseminating information in your organization. The first topics in this session describe the design
goals and features of Office SharePoint Server 2007 to help you understand how Office SharePoint
Server 2007 can benefit you and your organization. Later sections describe the technical
architecture and components.
After completing this session, you will be able to:
Describe reasons to deploy Office SharePoint Server 2007.
Describe the features of Office SharePoint Server 2007.
Describe the software components of Office SharePoint Server 2007.
Describe the administrative architecture of Office SharePoint Server 2007.
Describe the security requirements of Office SharePoint Server 2007.
Describe the physical architecture of Office SharePoint Server 2007.
2 Session 1: Office SharePoint Server 2007 Functional and Architectural Overview
Design Goals Behind Office SharePoint Server 2007
Overview
Contemporary organizations are finding that traditional mechanisms for storing, organizing, and
retrieving data face a number of limitations. In many cases, it is difficult to find information in file
shares even when you know it exists. Microsoft Windows® SharePoint Services 3.0 addresses some
concerns by providing a core infrastructure for collaboration and data storage. Office SharePoint
Server 2007 builds on the core infrastructure of Windows SharePoint Services 3.0 to provide
enhanced information management and organizational productivity features.
Specifically, this section will cover:
Organizational challenges.
Organizational responses to challenges.
Reasons solutions fail.
2007 Microsoft Office system goals.
The New Workplace: What Are the Challenges?
Over the past several years, the workplace has changed dramatically for the information worker.
There has been a major increase in the amount of information made available as well as the need
for multiple organizations or teams to work together to achieve results. This has resulted in the need
for new processes and technology to assist in content control, collaboration techniques, searching,
and security.
The following points discuss the challenges that the new workplace presents for organizations.
Economic transformation. The developed world is in the middle of a transformation from a
manufacturing-based economy to a services-based economy. To thrive in this economy,
organizations need to create value with ideas: intellectual property, process innovation, strategic
insights, and personalization of services. In this environment, successful organizations will find
new ways to empower information workers with tools that amplify their talents, connecting them
to an information infrastructure that allows them to understand their role in the context of larger
strategic objectives, find and collaborate with the right people, and make the best use of available
data in their decision making and work activities.
One world of business. The workplace is part of a single global market, a global workforce, and
global customers, partners, and suppliers. This creates challenges for organizations, as they must
enable collaboration across time zones, across organizations, across firewalls. Organizations will
be challenged to maintain the security and confidentiality of information when users from any
location might need to gain access to information at any time by using a wide variety of devices.
Always on, always connected. Because information workers can now work from anywhere, by
using a variety of mobile devices, the amount of information that can be created and accessed has
grown exponentially. The challenge now is to sift through that immense flow of e-mail, reports,
instant messages, and raw data to prioritize work and get the information needed to make smart
business decisions. Users need to have tools to find the right information and connect with the
right people in an organization.
Legal accountability. Organizations are under increasing pressure to focus on accountability and
governance, from a legal and fiduciary responsibility perspective and from a regulation
perspective. Companies need to balance being transparent with protecting their own intellectual
property.
Internet generation entering the workforce. As young workers enter the workforce, they are
already accustomed to working with technology. They are rapid adopters of new information
technology and are not only comfortable but also expect to work collaboratively with others. The
Internet generation expects modern work tools and is already used to working with such tools as
instant messaging, e-mail, and cell phones and naturally inclined to multitasking.
Competing for talent in a shrinking workforce. Because demographics show an aging, shrinking
workforce in most of the developed world over the next 50 years, maximizing the productivity of
the workers that are available is critical. Competition for talent will be strong, and the ability to
provide young workers with the kinds of tools and technology that meet their expectations and
make their work productive and rewarding, while also providing older workers with accessible
tools that enable them to take advantage their experience and skills, will be a key competitive
differentiator among employers.
How Organizations Respond to the Challenges
Many organizations respond to the new workplace by providing tools for users to collaborate.
These tools include:
Web access to business applications. With Web access to business applications, users can access
information using a Web browser and any Internet connection.
Web and mobile access to e-mail. Users can now access e-mail by using Web browsers on
computers and Web browsers on mobile devices and by synchronizing e-mail to mobile devices.
The connections to the e-mail servers might be through a cellular network connection, a wireless
connection at a wireless hot spot, a wireless home network, or an Internet kiosk.
Web sites for customer information. Almost all organizations provide some content for customers
on Web sites. This content ranges from simple information sites to highly complex sites that
provide multiple customer services.
Collaboration solutions for internal employees. Many organizations have developed collaborative
solutions for employees to make it easier for them to work together. This ranges from simple
calendar and contact sharing to complex applications that provide online presence information,
online collaboration, and information sharing tools.
Why Do the Solutions Fail?
The collaboration and productivity solutions implemented by many organizations are custom-
developed solutions or pieced-together components from multiple vendors. These solutions are
developed as a single instance to solve a specific problem.
Single-instance solutions create the following problems:
They do not provide a framework for future development to meet new needs.
User adoption is low because the solutions do not have a consistent user interface.
The solutions are not integrated, so they create islands of information and applications.
Implementing and supporting multiple applications is costly and complicated.
With multiple solutions, it is difficult to find the appropriate content, data, and people.
Most solutions do not provide secure and convenient tools for sharing outside the organization.
Solutions do not provide integrated security, so organizations are concerned about the information
management risk.
Users are slow to adopt the new solutions because they cannot see the business benefits.
2007 Office System Goals
The 2007 Microsoft Office system is designed to increase not just personal productivity, but also
organizational productivity. The addition of server-based services to the Microsoft Office system
boosts organizational productivity by:
Making information and knowledge sharing intuitive and easy.
Controlling and reusing content while reducing information management risk.
Enabling faster and more insightful decision making.
The design of the 2007 Microsoft Office system is not based on a set of features or functionality.
The 2007 Microsoft Office system was designed based on meeting productivity goals.
The 2007 Microsoft Office system defines six goals designed to provide an end-to-end solution—
from the individuals working in familiar Office programs to enterprise servers providing
capabilities to address organizational content management needs. These six goals are:
Personal productivity. Increase employee self-sufficiency and effectiveness. The 2007 Microsoft
Office system continues to provide tools for individuals to be productive and effective. The 2007
Microsoft Office system will make individuals more self-sufficient by performing more-
sophisticated tasks themselves and having more self help and community-based help options.
Enterprise content management. Make it simple to author, publish, organize, and find content in a
managed environment. The 2007 Microsoft Office system expands on what was introduced in
Microsoft Office 2003 for document management to allow better policy management of content
across the organization. This includes keeping the overhead of document management to a
minimum and making it simple for end users to participate in document management processes.
Collaboration. Enable better communication and more efficient information sharing to keep
coworkers, customers, and partners synchronized. Microsoft will continue to develop
collaboration tools and will be expanding the tools to include integrated communications and the
ability to work easily with partners and customers.
Knowledge discovery and insight. Make existing expertise, information, and business data
available to more people within an organization. The 2007 Microsoft Office system makes it easy
to find and use the expertise and data hidden within an organization and its business systems to
make better-informed decisions.
Information worker solutions. Make it easier to provide self-service and electronic forms
applications with integrated workflow that integrate familiar Office programs. For corporate
developers, the 2007 Microsoft Office system provides a platform on which they can easily build
and deliver rich solutions that incorporate workflow, business system integration, and Office client
familiarity.
Fundamentals. Make 2007 Office system more secure, reliable, and easier to deploy.
Office SharePoint Server 2007 Features
Overview
Office SharePoint Server 2007 is an integrated suite of server applications that improves
organizational effectiveness. The server applications in Office SharePoint Server 2007 provide
comprehensive control over electronic content, accelerate shared business processes, and facilitate
better-informed decisions and information sharing across organizational boundaries. These features
and capabilities go significantly beyond the capabilities of SharePoint Portal Server 2003. Office
SharePoint Server 2007 is much more than a portal server.
The benefits of Office SharePoint Server 2007.
Collaborating by using Office SharePoint Server 2007.
Managing content by using Office SharePoint Server 2007.
Creating portals by using Office SharePoint Server 2007.
Searching by using Office SharePoint Server 2007.
Managing business processes by using Office SharePoint Server 2007.
Providing business intelligence by using Office SharePoint Server 2007.
Benefits of Office SharePoint Server 2007
Office SharePoint Server 2007 integrates with 2007 Microsoft Office system clients to provide a
wide variety of benefits to organizations. Office SharePoint Server 2007 provides better control
over business data while broadening availability by making data available over the Internet. The
functionality and benefits of Office SharePoint Server 2007 are expanded well beyond those found
in SharePoint Portal Server 2003.
Some of the benefits provided by Office SharePoint Server 2007 are:
Effective management and repurposing of information. Documents can be managed through
policies that control access rights and retention periods. In addition, Office SharePoint
Server 2007 provides a central location to store, manage, and access documents.
Acceleration of shared business processes. Workflows and forms are used to manage business
processes. This simplifies everyday tasks and allows you to extend business processes to
customers, partners, and suppliers by using the Web.
Better-informed decisions through centralized access to information. Business intelligence portals
provide a live view of data in your organization, even data in enterprise systems such as SAP and
Siebel. Enterprise search allows you to find the information and people you need.
Sharing business information inside and outside the organization. Microsoft Office Excel®
services enable you to provide Web-based access to spreadsheets while protecting proprietary
information such as financial models. In addition, you can easily provide Web-based and secure
data access to customers, partners, and suppliers.
What Are the Collaboration Features?
Collaboration is the base component of Office SharePoint Server 2007. It is provided in Windows
SharePoint Services 3.0 and is thus available to Office SharePoint Server 2007. For more
information, please refer to Clinic 3369, First Look: Getting Started with Windows SharePoint
Services 3.0.
Among the many collaboration features provided by Windows SharePoint Services 3.0 to Office
SharePoint Server 2007 are:
Discussions. A discussion provides a forum for teams to discuss current projects where previous
responses can be easily accessed. Discussions can be viewed by discussion thread.
Calendars. A calendar provides a centralized place for team members to see when team events are
occurring.
Document libraries. A document library provides a central repository for team documents. This is
an alternative to storing files in shared folders.
Contacts. Teams can centrally store contacts in an Office SharePoint Server 2007 site. These
contacts are available through Microsoft Office Outlook®.
Blogs. A blog provides an informal way for team members to document and discuss team issues.
Wikis. A Wiki is a user-maintained knowledge base that teams can use to capture and retain
information.
What Is Content Management?
The content management capabilities built into Office SharePoint Server 2007 are designed to
perform document management, records management, and Web content management. All types of
content management can be controlled by workflow processes.
Document Management
Document management lets you control how documents and their contents are used in your
organization. Building on the document collaboration features in Windows SharePoint Services 3.0,
Office SharePoint Server 2007 adds the following features:
A wide variety of ready-to-use content types for different kinds of business scenarios
Ready-to-use workflows centered around document production, approval, retirement, and review
Custom site templates for sites devoted specifically to editing and managing large amounts of
document content
Records Management
Records management is the process of collecting, managing, and disposing of corporate records.
The following features are included:
Policies for large-scale operations on documents, including retention, expiration, auditing, adding
permanent identification labels, barcoding, and more
E-mail content can be stored as records where policies can be applied and content archived
Support for formal records repositories, with default providers included, and support for third-
party records management products
Web Content Management

The Web content management features in Office SharePoint Server 2007 provide a standardized
way to create and manage Web sites and their content. Web content management allows content to
be reused and content owners to incorporate advanced features without the intervention of technical
workers. All of the features found in Content Management Server 2002 have been incorporated into
Office SharePoint Server 2007, and many of the features have been enhanced.
Whenever possible, Office SharePoint Server 2007 uses common services to manage both
document content and Web content, including workflow, security, policies, versioning, and so on.
Therefore, organizations do not need to master and maintain multiple infrastructures for multiple
kinds of content.
Features unique to Web content management and provided in Office SharePoint Server 2007
include:
Site templates designed to be completely customizable to fit specific requirements.
Page templates for a wide variety of layout scenarios.
Rendering of a wide variety of content as Hypertext Markup Language (HTML) for browser-only
scenarios.
What You See Is What You Get (WYSIWYG) Web content editor for HTML content and support
for custom field controls to allow for browser-based in-place editing of other kinds of content as
well.
Rich client support for custom editing environments.
Systematic authoring and publishing workflow for managing the staging and deployment of
content from authoring to testing to production scenarios.
Support for treating multiple sites as known variations of each other and automating both updates
of content between variations and the assignment of tasks for translation or post update editing.
This feature allows for treating multiple physical sites as one virtual site that automatically
redirects browsers to the correct site for a given language or device type.
What Is a Portal?
A portal is a central Web site that your company can use to organize and distribute company
information. The portal components in Office SharePoint Server 2007 make it easy to connect
people within the organization who have the required skills, knowledge, and project experience.
Office SharePoint Server 2007 incorporates the features formerly available in Windows SharePoint
Portal Server 2003.
Some of the portal features provided in Office SharePoint Server 2007 are:
User profiles. Each user has a set of attributes, such as a phone number or workgroup that
constitutes a user profile. Users can control which attributes in their user profile can be viewed by
others. In addition, user profiles can be used when creating audiences to control content viewing.
Audiences. An audience is a group of users defined based on their user profiles. Portal content can
be targeted to specific audiences.
Content targeting. The portal content displayed is customized depending on the group
membership or SharePoint audience of the person accessing the portal. This increases productivity
by ensuring that everyone gets information that is relevant to them.
My Site. Each user can have his or her own personal site named My Site. This site allows users to
store their own content and can serve as a central starting point when they are looking for
information. Content in My Site can be designated as private or public to control whether other
users have access to the content.
Enhanced Notification Services. Basic notifications can be sent by e-mail to inform users about
changed items in lists or document libraries. Users participating in a workflow automatically
receive e-mail notifications related to the workflow. Office SharePoint Server 2007 adds the
ability to be notified when the results of a search query change.
What Is Search?
The Search component in Office SharePoint Server 2007 is significantly enhanced from what was
available in Windows SharePoint Portal Server 2003. It is now faster and easier to find both the
information and the people you need.
Some of the Search features provided in Office SharePoint Server 2007 are:
Revised relevance algorithms. The relevance algorithms used when searching have been optimized
for searching corporate data. When users perform a search, they receive only results that they have
access to.
Content sources. In addition to information stored in SharePoint sites, additional content sources
can be searched. Additional content sources include line-of-business application data, databases,
and file shares.
People searching. Like Windows SharePoint Portal Server 2003, you can search for the people
you need, not just data. Any Lightweight Directory Access Protocol (LDAP) directory can be
searched as well as user profiles within a site. New in Office SharePoint Server 2007 is people
search results grouped by “social distance” from you and your common interests. Social distance
gives higher priority to users that you know.
Content scopes. Users can broaden or narrow the scope of their searches by using content scopes.
In addition to content scopes based on content sources, as were available in SharePoint Portal
Server 2003, scopes can now be based on arbitrary content properties such as document type and
author.
What Is Business Process Management?
Business processes are a set of activities or events that are required to complete a business task,
such as providing a particular product or service to a customer. Office SharePoint Server 2007
automates forms-based business processes by using electronic forms and workflows.
Some of the business process management features provided in Office SharePoint Server 2007 are:
Built on the Extensible Markup Language (XML) industry standards. Microsoft Office
InfoPath® 2007 forms are based on XML schemas that you define. Each completed form is an
XML file that can be used by any XML-capable application or Web service.
Browser-based forms. Microsoft Office SharePoint Server 2007 InfoPath Forms Services allow
you to create Web-capable forms. The forms can be used internally on a corporate intranet, by
partners on an extranet, or by customers on the Internet. No client downloads are required.
Design-once development model. Forms designers can design their forms once and deploy them
for use both within the Office InfoPath client and through a Web browser. Microsoft Office
SharePoint Server 2007 InfoPath Form Services automatically converts the form into ASP.NET
Web forms.
Form Import Wizard. The Form Import Wizard converts forms designed in Microsoft Office Word
or Office Excel to Office InfoPath 2007 forms. Converting existing forms is much more efficient
than creating new forms.
Multiple form views. Forms can be defined with a different view for the full Office InfoPath 2007
client or a browser. For example, a loan application form might include a basic view available to
clients through a browser, while the loan office has access to a view with additional information
through the full Office InfoPath 2007 client.
What Is Business Intelligence?
Business intelligence is the process of gathering and analyzing data and then distributing the results
to help organizations make better decisions. Microsoft Office SharePoint Server 2007 provides
business intelligence capabilities to every employee, allowing them to share, control, and reuse
business information to make better business decisions.
Some of the business intelligence features provided in Office SharePoint Server 2007 are:
Web access to published spreadsheets. Office SharePoint Server 2007 Excel Services enable you
to publish spreadsheets to SharePoint sites. These spreadsheets can include rich information such
as graphs and PivotTable® and PivotChart® dynamic views. All of the calculations are performed
on the server to keep any proprietary algorithms secure. Users require no software other than a
Web browser.
Programmatic access to published spreadsheets. Custom applications can access a published
spreadsheet as a Web service. This allows you to embed business logic in a central, easily
accessible location rather than in the application.
Business Data Catalog. You can include data from back-end systems in SharePoint lists, Web
Parts, and search results by using the Business Data Catalog. The Business Data Catalog also
allows access to data by using Microsoft ADO.NET.
Dashboards. Office SharePoint Server 2007 makes it easy to create business intelligence
dashboards that include key performance indicators, Office Excel workbooks, and SQL-based
reports. Dashboards are an intuitive way to convey complex information.
Report Center Web sites. Pre-built Web sites optimized for report access and management are
included in Office SharePoint Server 2007. These sites provide a consistent way to manage
reports, spreadsheets, and data connections.
Demonstration 1: Office SharePoint Server 2007 Features
Demonstration
The user interface in Office SharePoint Server 2007 is consistent with Windows SharePoint
Services 3.0. The same terminology and components apply in many cases—for example, Web page
components are called Web Parts. In this demonstration, you will see an overview of the features of
and the user interface in Office SharePoint Server 2007, including Web Parts, Search, and My Site.
Office SharePoint Server 2007 Software Components
Overview
Windows SharePoint Services 3.0 provides platform and collaboration services to Office
SharePoint Server 2007. Office SharePoint Server 2007 integrates with and extends the
functionality available in Windows SharePoint Services 3.0. This section explains which services
are required for and included in Office SharePoint Server 2007.
Operating system and database services required by Office SharePoint Server 2007.
Services provided by Windows SharePoint Services 3.0.
Services provided by Office SharePoint Server 2007.
Operating System and Database Services
Microsoft Windows Server™ 2003 Service Pack 1 (SP1) includes many services for application
development. Office SharePoint Server 2007 takes advantage of and relies on services that are
included in Windows Server 2003 SP1. In addition, Microsoft SQL Server™ is required to provide
database services.
Operating System Services

The operating system services required by Office SharePoint Server 2007 are:
Microsoft .NET 2.0 Framework, which includes:
• Microsoft ASP.NET master pages, content pages, and Web Parts.
• Pluggable service-provider models for personalization, membership, navigation, and security.
• Database access services.
Internet Information Services (IIS).
Windows Workflow Foundation (WF).
Windows desktop indexing and search services.
Database Services
SQL Server is required to store all of the content and configuration information for Office
SharePoint Server 2007. SQL Server 2005 is recommended. SQL Server 2005 Express Edition is
included as part of a default installation; however, other editions and SQL Server 2000 can also be
used.
Windows SharePoint Services 3.0 Services
Windows SharePoint Services 3.0 provides both platform and collaboration services that are used
by Office SharePoint Server 2007. These services allow you to build team sites for workgroups or
large enterprise solutions.
Platform Services
The platform services provided in Windows SharePoint Services 3.0 are:
Storage. Functions provided by storage services include acting as a repository for data, capturing
and storing document metadata, versioning, recycle bin, and indexing.
Security. Functions provided by security services include server policies, pluggable authentication,
folder and item security, and a user interface that exposes only options to which users have rights.
Management. Functions provided by management services include the administrative interface,
delegation of management ability, provisioning of new sites, and monitoring of sites.
Deployment. Functions provided by deployment services include migration of data, configuration
management, Web farm services, feature policies, and extranet support.
Site model. Functions provided by site model services include templates, HTML rendering of
content, navigation components, and a consistent user interface.
Extensibility. Functions provided by extensibility services include forms, the object model, SOAP
access site objects, event handlers, and migration application programming interfaces (APIs).
Collaboration Services
The collaboration services provided in Windows SharePoint Services 3.0 include:
Document collaboration.
Wikis and blogs.
Really Simple Syndication (RSS) support.
Discussions.
Project task management.
Contacts, calendars, and tasks.
E-mail integration.
2007 Microsoft Office system client integration.
Offline support for lists and document libraries.
Office SharePoint Server 2007 Services
Office SharePoint Server 2007 provides shared services in addition to five server applications. The
shared services are used by all Office SharePoint Server 2007 applications. The five server
applications provide the functionality that users see and use.
Shared Services
The shared services provided in Office SharePoint Server 2007 are:
Full-text indexing, property indexing, and search services.
Business Data Catalog.
User profile store.
Audiences for customizing content.
Usage reporting.
Single sign-on (SSO) services.
Server Applications
The server applications provided in Office SharePoint Server 2007 are:
Content management.
Portal.
Search.
Business intelligence.
Business process management.
Note The details of the server applications provided in Office SharePoint Server 2007 are
covered in Session 2, “Enterprise Content Management with Office SharePoint Server 2007”;
Session 3, “Organizing and Finding Resources with Office SharePoint Server 2007”; and
Session 4, “Business Solutions Using Office SharePoint Server 2007.”
Office SharePoint Server 2007 Administrative

Architecture
Overview
Office SharePoint Server 2007 introduces a new, three-tier administrative structure for controlling
the configuration of central administration, shared services, and site settings. In Windows
SharePoint Services 2.0 and Windows SharePoint Portal Server 2003, the administrative interface
was inconsistent between the two products. The administrative interface is now consistent between
Windows SharePoint Services 3.0 and Office SharePoint Server 2007. In addition, the
administrative interface has been redesigned to emphasize simplicity, extensibility, resource
optimization, and delegation.
An overview of the administrative architecture of Office SharePoint Server 2007.
Central administration.
Shared services providers.
Multiple shared services providers.
Site settings.
Administrative Architecture Overview
Office SharePoint Server 2007 has a three-tier administrative architecture for central
administration, shared services, and site settings. All of the administration interfaces are Web-
based.
Administration is broken into three tiers to achieve the following:
Separation of roles and tasks. The tasks that are managed in each administrative tier apply to
different management roles. Having three administrative tiers ensures that the tasks are organized
appropriately for each management role.
Controlled delegation. When management abilities are delegated, they apply only to a given
administrative interface. For example, being granted central administration rights does not
automatically give site administration rights.
Secure isolation. Each administrative tier is isolated as its own Web site and databases to ensure
proper security.
What Is Central Administration?
Central administration is typically performed by IT administrators. The central administration tasks

are farm-level tasks such as configuring database locations or logging. There is only one central
administration tier per farm.
The central administration tier is not unique to Office SharePoint Server 2007. It is a component of
Windows SharePoint Services 3.0 that Office SharePoint Server 2007 builds on.
The major elements in the central administration tier are:
Administrative task list. A list of tasks to be completed is displayed as part of the central
administration tier. This informs administrators which configuration tasks need to be performed at
the farm level and provides links to perform those tasks.
Home page topology view. This view provides a quick way to see a list of servers in the farm and
what is running on them.
Services on server page. This page lists the components running on a server and provides the
opportunity to manage the components.
Flat menu structure. Tasks are divided between an operations page and an application
management page. Each page has only a single level of menus. The operations page has tasks
affecting farm resources. The application management page has tasks specific to a single
application or service in the farm. Security trimming is used to reduce clutter in the user interface.
Remote administration. Central administration is easy to perform remotely because of the Web-
based interface. There is no requirement to install an administrative application on workstations.
Timer-based system updates also aid remote administration.
What Is a Shared Services Provider?
A shared services provider (SSP) is a group of shared services used by sites within a farm.
Grouping the shared services as an SSP separates the shared services as a logical and secure
partition of the farm. It also enhances the scalability of portals by removing the services from the
portal server. The shared services are installed as part of Office SharePoint Server 2007 and are not
a part of Windows SharePoint Services 3.0.
SSP Components
The components of an SSP are:
SSP administration site. There is a separate Web site running on its own port number for
administering SSPs.
SSP databases. Each SSP includes two databases—one database contains the SSP configuration
data and the other contains the content crawled and indexed by the Search component in the SSP.
Crawling is the process of indexing content.
Shared Web service hosting. Web services, such as the Office Excel calculation service, are also
hosted and managed by the SSP.
SSP Benefits
Separating shared services from the portal provides the following benefits:
Resource optimization and flexibility. For smaller implementations, the SSP can be placed on the
same server as the portal or the SQL Server. For larger implementations, the SSP can be separated
from the portal and SQL Server. SSP services can also be spread across multiple servers if
required.
Delegation of administration. Within a workgroup, it might be reasonable to give power users the
ability to manage shared services. For example, a power user could provide a content source to the
Search service. Allowing a user to manage the SSP does not allow that user to manage central
administration. However, users configured as central administration operators are SSP site
administrators.
Sharing across farms. A single SSP can be shared across farms when appropriate. This creates the
possibility to integrate services across farms rather than having isolated pools of information. For
example, Search could be integrated across multiple farms to provide a single index of information
that can be searched across the enterprise.
Note When Office SharePoint Server 2007 components are used in a Web farm deployment
rather than a single-server deployment, the security account used by the SSP Web application
cannot be Network Service.
Using Multiple SSPs
In most installations, only a single SSP is required. However, when secure isolation of services and
data is required, multiple SSPs can be implemented.
Situations that might require multiple SSPs are:
Hosted environments. In hosted environments, customers might want their own SSP to ensure that
their data is completely isolated from other customers.
Restricted sites. Within an organization, some SharePoint sites might contain data that must be
completely isolated from most users. This might be financial data or customer data covered by
privacy laws.
Organizational or political concerns. Occasionally, one area of an organization might require a
separate infrastructure from other parts of the organization. For example, the human resources
department might require its own SSP to address security concerns.
Web Applications
Web applications are used by IIS to isolate processes running on Web sites to enhance stability.
Each SharePoint site is associated with a Web application. By default, all SharePoint sites are part
of the same Web application; however, you can choose to spread SharePoint sites among several
applications.
Each Web application can be associated with only one SSP. However, one SSP can be associated
with multiple Web applications. To use multiple SSPs, you must have multiple Web applications.
One SSP is created during installation and is the default SSP for all new Web applications. The
default SSP cannot be changed or deleted.
What Are Site Settings?
Site settings are the interface for users to manage their SharePoint sites. Like central
administration and shared services administration, site settings are presented based on user security
settings to make them easier to use. The site settings interface is provided in Windows SharePoint
Services 3.0.
The items managed through site settings include:
Creating site users.
Managing user permissions.
Managing the site hierarchy.
Managing site components.
Demonstration 2: Office SharePoint Server 2007 Administrative

Architecture
Demonstration
Office SharePoint Server 2007 has a three-tier administrative model for management. This allows
management to be effectively delegated for different management roles. In this demonstration, you
will see central administration, shared services administration, and site administration.
Office SharePoint Server 2007 Security Requirements
Overview
Office SharePoint Server 2007 uses a number of security accounts for running services, Web
applications, and databases. To understand the security accounts used by Office SharePoint Portal
Server 2007, you must first understand the Web applications and databases that are used. After the
basic components have been described, security best practices are presented.
Infrastructure objects.
Infrastructure security.
Security best practices.
Infrastructure Objects
The three administrative tiers of Office SharePoint Server 2007 consist of infrastructure
components referred to as objects. These objects include Web applications, databases, SharePoint
sites, and IIS Web sites.
The central administration objects are:
One SharePoint Web application: _Admin
• One SharePoint database used by _Admin: ContentDB
One SharePoint site: Central Administration
One SharePoint database: ConfigDB
The shared services objects are:

One SharePoint Web application: Admin Specified
• One SharePoint database used by the SharePoint Web application: ContentDB
One SharePoint site: SSPName
Two SharePoint databases:
• SSPName_SSP_DB to store SSP configuration information
• SSPName_Search_DB to store contents from Search crawling and indexing
One IIS Web site for hosting Web services: Office Server Web Services
• One IIS virtual directory in the IIS Web site: SSPName
The site objects are:

One SharePoint Web application: Admin Specified
• One SharePoint database used by the SharePoint Web application: ContentDB
One SharePoint site = Site Name
Infrastructure Security
The three administrative tiers of Office SharePoint Server 2007 use a number of security accounts
to give the necessary permissions to various components. For example, each site has a content
process account that is used to give the Web application the necessary permissions to function.
Central Administration
A farm account is used by the central administration Web application and the SharePoint Timer
Service. The SharePoint Timer Service is responsible for sending notifications and running
scheduled tasks. Permissions required by the farm account are as follows:
DBO for all databases
DB creator
SQL security admin
There is also a SharePoint Administration account used by the SharePoint Administration service.
This service performs administrative tasks for Office SharePoint Server 2007. The SharePoint
Administration account should be configured as localsystem on all servers.
Shared Services
An SSP Administration Process account is used by the SSP Web application. This account requires
the following permissions:
DBO for the content database
Read and write to the SSP databases
Read and write to the content databases
Read access to the configuration database
Cannot be Network Service for a farm configuration
The shared services in the Web farm must also be configured with an account. They require
network service permissions and are configure to run as a network service by default.
Finally, an SSP shared Web service account is used for the shared Web services IIS site. The SSP
shared Web service account requires the following permissions:
Read and write to the content databases
Read to the configuration database
Site
At the site level, the only security account is the Content Process account used by the content Web
application. This account requires the following permissions:
DBO for the content database
Read to the configuration database
Security Best Practices
As with all products, Office SharePoint Server 2007 can be configured in a number of different
ways. However, the following are best practices for security configuration:
Use unique user accounts. The user accounts should be unique for the farm account, SSP process
account, SSP shared Web service account, and the content Web application.
Use Kerberos authentication. The default authentication method is NTLM authentication. To use
Kerberos authentication in a Web farm, you must register each process account as a Service
Principal Name (SPN).
Enable Secure Sockets Layer (SSL). Office SharePoint Server 2007 does not use SSL by default.
When SSL is enabled, all communication between clients and the SharePoint server is encrypted.
Demonstration 3: Office SharePoint Server 2007 Security Overview
Demonstration
For a single-server installation, all of the security configuration for Office SharePoint Server 2007
is performed automatically. However, for more advanced installations, you must understand the
infrastructure objects that are a part of Office SharePoint Server 2007 and their security
requirements. In this demonstration, you will see an overview of the infrastructure objects in Office
SharePoint Server 2007 and their security configuration.
Office SharePoint Server 2007 Physical Architecture
Overview
Office SharePoint Server 2007 can be deployed in a wide variety of different configurations
depending on your business needs. Software components can run off a single server or be spread
across multiple servers. Although single-server deployments frequently meet the needs of smaller
offices, enterprise deployments often require a Web farm.
Selecting a deployment topology.
Single-server deployment.
Web farm deployments.
Web farm examples.
Multiple-farm topologies.
Recommended hardware for installation.
Selecting a Deployment Topology
In Office SharePoint Server 2007, a topology defines where services are located. All services can
be located on a single server or they can be spread across multiple servers. The servers involved in
the topology take on one or more of the following roles:
Web front-end server. A Web front-end server runs IIS and is contacted by clients when they
access SharePoint sites. No data is stored on Web front-end servers.
Application server. Application servers host shared services such as indexing, Search, or Office
Excel calculation services.
Database server. The database server hosts the content and configuration databases used by Office
SharePoint Server 2007.
The selection of a topology will be based on your requirements. For example, a small workgroup
implementation of Office SharePoint Server 2007 could be installed on a single server. However, in
larger deployments, the server roles will be spread across multiple servers in a Web farm
configuration.
Some factors to consider when selecting a topology are:
Data composition.
User load.
Long-running operations.
Performance.
Availability and reliability.
Network considerations.
Single-Server Deployment
The quickest way to install Office SharePoint Server 2007 is as a single-server deployment. You
can have a site up and running without having to perform any configuration of components.
A single-server deployment has the following characteristics:
All server roles are performed by a single server.
Performance is limited, because all roles are performed by a single server.
Availability is limited, because fault tolerance and load balancing are not implemented.
Multiple sites can be hosted.
Suitable for workgroups, teams, and testing, but not for enterprise deployments.
Web Farm Deployments
A Web farm deployment gives you the flexibility to spread server roles across multiple servers.
This allows you to increase the performance and availability of Office SharePoint Server 2007.
Web Front-End Servers

To increase the scalability and availability of Web front-end servers, you can configure them in a
load-balanced cluster. In a load-balanced cluster, all servers share a single virtual IP address. When
a client accesses the virtual IP address, one of the load-balanced servers responds. If a server in the
load-balanced cluster fails, clients are unaware because other servers respond in its place.
Because any server in the load-balanced cluster can respond to a request, the configuration of all
servers in the load-balanced cluster must be synchronized. For example, they must all have the
same SharePoint sites accessible. However, because most configuration data and content is stored
on the database server, there is little data to synchronize between Web front end servers.
Application Servers
Application server scalability can be enhanced by designating a separate server as the application
server. You can further increase scalability by separating shared services and spreading them
among multiple servers. For example, you could move the Search service onto its own server
because it is heavily used.
To increase reliability and further increase scalability, you can configure applications servers in a
load-balanced cluster. Like Web front-end servers in a load-balanced cluster, the data on
application servers in a load-balanced cluster must be synchronized. For example, two servers in a
load-balanced cluster must have the same shared services running, such as the Search service or the
Office Excel Calculation Services.
Database Servers
A database server cannot be placed in a load-balanced cluster because the databases exist only as a
single instance of data. You must use server clusters to enhance the availability of database servers.
A server cluster uses virtual servers to failover services from one server to another. A service runs
on one server in the server cluster, and then if the server fails, another server loads the virtual
server. The database must be located on shared storage that can be accessed by all servers in the
server cluster.
Web Farm Examples
Office SharePoint Server 2007 can be configured as a Web farm in many ways. A Web front-end
server holds content sites, application servers are part of an SSP, and database servers hold the
databases. Different configurations increase the performance and availability of the services:
Small farm. In a small farm, two load-balanced servers could be used as both Web front-end
servers and application servers to enhance performance and availability over a single-server
solution. The database server could be a stand-alone server.
Medium farm. In a medium farm, two load-balanced servers could be used as Web front-end
servers and application servers. However, some high-utilization shared services, such as indexing,
could be placed onto a separate server to enhance performance. In addition, the database server
could be placed on a server cluster to increase availability.
Large farm. In a large farm, several load-balanced servers could be used as Web front-end servers
and application servers to further increase performance. To increase performance and availability
of application servers running shared services, you could place the servers in a load-balanced
cluster. The database server should be in a server cluster for high availability.
Multiple-Farm Topologies
Some organizations might want to implement multiple Web farms for Office SharePoint
Server 2007. Common reasons to implement multiple farms include:
Security and process isolation. Many organizations require applications, including Web
applications, to be hosted in separate development, test, and production environments. In this case,
three separate Web farms could be configured for development, testing, and production. In
addition, business demands for security might require separation of different departments or
isolating certain types of data.
Content management. Staging environments for development and testing might be on different
networks that cannot communicate. For example, development might be located on an intranet,
while production is located in a perimeter network without regular communication with the
intranet. In this case, two Web farms would be required. Office SharePoint Server 2007 supports
scheduled copying of data from one site collection to another.
Inter-Farm Shared Services

Multiple farms can share a single SSP. This allows one set of shared services to be used across an
entire organization. For many shared services, it is a benefit to configure the service one time,
rather than once per farm.
Inter-farm shared service examples include the following:
A single SSP unifies indexing and searching across multiple farms by crawling the content only
once.
Business Data Catalog sources need to be configured only once to be available to all farms.
Audiences for content targeting can be configured once and used across farms.
Note Inter-farm shared services are not supported across wide area network (WAN) links. The
level of network traffic generated is too high.
What Is the Recommended Hardware for Installation?
The hardware recommendations for Office SharePoint Server 2007 vary depending on whether the
installation is on a single server or in a Web farm. A single-server deployment has all components
including SQL Server on a single server. A Web farm deployment designates at least one server as
a Web front-end server and another as a database server. Web farms can be scaled to include
multiple servers in each role.
Single-Server Deployment
The recommended hardware for a single-server deployment is:
Dual processors.
At least 2.5 gigaherts (GHz) processor speed.
At least 2 gigabytes (GB) of RAM.
Web Farm Deployment

The recommended hardware for the Web front-end servers, application servers, and the database
server is:
Dual processors.
At least 2.5 GHz processor speed.
At least 2 GB of RAM.
Demonstration 4: Installing a Single-Server Deployment
Demonstration
In this demonstration, you will see how to install a new single-server deployment.
Session Summary
This session explored the overall capabilities of Office SharePoint Server 2007 and how to
implement Office SharePoint Server 2007. The session explored the following topics:
Design Goals Behind Office SharePoint Server 2007. This topic discussed the challenges faced by
organizations, how organizations are responding to those challenges, and why solutions fail.
Office SharePoint Server 2007 addresses the challenges faced by organizations in an easy-to-
deploy solution.
Office SharePoint Server 2007 Features. This topic discussed the benefits and features of Office
SharePoint Server 2007. The features addressed were collaboration, content management, portals,
Search, business process management, and business intelligence. Office SharePoint Server 2007
provides a new way to organize and disseminate information in your organization.
Office SharePoint Server 2007 Software Components. This topic explored the operating system
and database services required by Office SharePoint Server 2007. In addition, the specific services
provided by Windows SharePoint Services 3.0 and Office SharePoint Server 2007 were discussed.
Office SharePoint Server 2007 builds on the core services provided in Windows SharePoint
Services 3.0.
Office SharePoint Server 2007 Administrative Architecture. This topic explained the three-tier
administrative model for managing Office SharePoint Server 2007. Specifically discussed were
central administration, shared services providers, using multiple shared services providers, and site
settings. The administrative interface has been redesigned to emphasize simplicity, extensibility,
resource optimization, and delegation.
Office SharePoint Server 2007 Security Requirements. This topic examined the infrastructure
objects and security used by Office SharePoint Server 2007. In addition, security best practices
were discussed.
Office SharePoint Server 2007 Physical Architecture. This topic discussed what the different
server roles are in a deployment topology and how to select a topology. Single-server
deployments, Web farm deployments, and multiple-farm topologies were examined. Finally, the
recommended hardware for installation was listed. Office SharePoint Server 2007 can be deployed
in a wide variety of configurations depending on your business needs.
Next Steps
Next steps include going to the Microsoft Web site to do the following:
Find additional Office SharePoint Server 2007 training events.
Download and evaluate Office SharePoint Server 2007.
Questions and Answers

Session 2: Enterprise Content Management
with Office SharePoint Server 2007
Contents
Session 2: Enterprise Content
Management with Office SharePoint
Server 2007 1
Document Management Using Office
SharePoint Server 2007 2
Using Document Workflows 8
Using Records Management Features 14
Web Content Management Overview 21
Creating Web Pages 31
Advanced Web Content Management 37
Session Summary 44
Next Steps 45

Session 2: Enterprise Content Management with Office SharePoint Server 2007 1
Session 2: Enterprise Content Management with Office

Overview
Microsoft® Office SharePoint® Server 2007 is a complete solution for managing documents and
Web content. The document management features let you effectively create, store, and retrieve
documents. The Web content management features allow you to create full-featured Web sites and
maintain Web content in an organized and scalable way.
Describe the document management features in Office SharePoint Server 2007.
Describe document workflow.
Describe records management.
Describe Web content management.
Describe how to create Web pages.
Describe advanced Web content management features.
2 Session 2: Enterprise Content Management with Office SharePoint Server 2007
Document Management Using Office SharePoint

Server 2007
Overview
Office SharePoint Server 2007 adds to the features provided in Microsoft Windows® SharePoint
Services 3.0 to create a complete document management solution. An enterprise document
repository site template is included to enhance documents management. In addition, many Office
SharePoint Server 2007 features rely on content types.
Creating an enterprise document repository.
Defining a content type.
Using templates to create content types.
Using the Property Editor.
What Is a Managed Document Repository?
A managed document repository is a new site template available in Office SharePoint Server 2007.
It has a user interface specifically designed for working with a large number of documents. It also
has document management features enabled automatically.
A managed document repository has the following features:
An announcements list. This can be used to provide information to users about what type of
information is to be stored in the enterprise document repository.
A tasks list. This can be used to view what document-related tasks a user has outstanding, such as
document approvals in a workflow.
Relevant documents. This is a list of documents that the user has a connection with—for example,
through authoring and editing. It provides a quick and easy way to access the content most likely
to be required.
A document library. This holds all of the content.
Folder tree navigation. This makes it easier to browse through a large folder structure.
Document versioning enabled. This tracks the editing process of a document.
Document check in/check out enabled. This ensures that multiple users are not editing files at the
same time.
Note For more information about document versioning or document check in/check out, see
Clinic 3369, First Look: Getting Started with Windows SharePoint Services 3.0.
What Is a Content Type?
It is often difficult to find related information when you are searching through a large repository.
For example, in a file share of project plans, it would be difficult to find all of the project plans
created by a particular project manager. However, content types in Office SharePoint Server 2007
simplify the process.
A content type is a collection of settings that define a particular type of information, such as a
memo or report. Once defined, a content type can be reused across multiple document libraries and
sites.
A content type contains:
A set of properties. The properties required by a content type are metadata about a document that
can be used to categorize it. In 2007 Microsoft Office system client applications, the properties are
collected in the Property Editor displayed at the top of the document.
A document template. Document templates can be used to create documents with predefined styles
and boilerplate content. Applications such as Microsoft Office Word (.dot) or Office Excel® (.xlt)
use document templates to create new documents.
Workflows. Many document types have a consistent process associated with them for approval. A
workflow can be associated with a particular content type to automate the required process.
Policies. Most organizations have rules regarding how particular content types should be
managed. You can associate policies with a content type to manage characteristics such as
retention period.
What Are Content Type Templates?
Most organizations will reuse content types across many sites and document libraries. However,
there will also be situations where there is a requirement for a slightly modified version of an
existing content type. To ensure that content types adhere to company standards, you can use
content type templates.
Content Type Templates

A content type template associates columns, a Property Editor, workflows, and polices in a single
place for easier management. Changes to a content type template can be pushed out to content types
based on the template to centralize management of content types and enforce organizational
standards.
Column Templates
The columns in a content type template are the additional document properties (or metadata) that
you want to gather. Column templates are used to standardize the naming of document properties to
maximize the value of the metadata. It would be confusing and inefficient to search for information
when some documents use the term Author and others use the term Creator.
Column templates are used in the creation of content type templates. The column templates define
the properties that will be collected for documents that are a specific content type. Column
templates can be reused between sites, document libraries, and content types.
What Is the Document Information Panel?
When additional properties are collected with documents, there must be a mechanism for users to
enter the property values. One way to enter and edit the properties is by using the Web-based
interface provided in Office SharePoint Server 2007. However, an even better technique to collect
the property values is by using the Document Information Panel.
The Document Information Panel is displayed when you edit documents in the 2007 Microsoft
Office system client applications. The Document Information Panel consists of a form for entering
the additional properties required for a document as defined by the content type of the document.
Each content type has a Document Information Panel associated with it.
If you create a customized content type, you must create an Information Panel to collect the correct
information. The customized Information Panel for a content type is designed by using Microsoft
Office InfoPath® to create a form.
Demonstration 1: Using Content Types
Content types are a feature that is used extensively in Office SharePoint Server 2007. A content
type defines metadata that can be collected about a document to make document management
easier. Many predefined content types are included with Office SharePoint Server 2007, but you
can also create content types to suite your own specialized needs. In this demonstration, you will
see how to create an enterprise document library, create a content type, create a new document from
a content type, and use the document information panel.
Using Document Workflows
Overview
Office SharePoint Server 2007 expands on the workflow capabilities of Windows SharePoint
Services 3.0 by providing additional out-of-the-box workflows. Workflows can be used to manage
document creation, archiving, and deletion. In addition, workflows are used to control Web content
publishing. In this section, you will learn about the workflow capabilities of Office SharePoint
Server 2007.
What a workflow is.
What the workflow tasks are.
How to create a workflow.
What out-of-the-box workflows are.
What Is a Workflow?
The creation of documents within an organization typically has a business process associated
with it, whether or not this process is formally documented. Workflows in Office SharePoint
Server 2007 allow you to associate business processes with documents.
A workflow can control almost any aspect of an item in Office SharePoint Server 2007. A simple
workflow could require the approval of several users for a document such as a budget. A more
complex workflow could require information to be gathered through forms and that the workflow
branch out to perform different functions depending on the information gathered. The user interface
used by a workflow can be Web-based, created by using Office InfoPath forms and accessed by
using 2007 Microsoft Office system client applications, or accessed by a custom application.
Workflows can be applied to individual documents by end users. This is useful when only some
documents require the formal process in a workflow. However, for consistency in applications, you
can associate a workflow with a content type. Then, whenever a document of a particular type is
created, the workflow is automatically associated with the new document.
What Is the Workflow Process?
Using a workflow requires you to follow a specific process for implementation. The four steps in
the process of using a workflow are:
Workflow association. Site administrators can associate workflows with a list, document, or
content type. The workflows can also be customized by choosing a manual or automatic
application, adding a task list if the workflow specifies tasks, and adding a history list to store
workflow events.
Workflow initiation. Any user with the appropriate role, such as an administrator or a contributor,
can initiate a workflow that is configured to start manually. The user selects the item and then
selects the workflow from a list of workflows associated with that item. In some cases, the user
will need to provide additional information when starting the workflow.
Workflow status. Users can view workflow status for a document in the main document library
page or the workflow page for each item. The workflow page for an item is available from the
properties page for that item and allows you to:
• View and start available workflows.
• View the status of currently running workflows.
• View the status of completed workflows.
Workflow tasks. Tasks appear in the site task list. Tasks notifications can also be e-mailed to
participants in the workflow. After a participant has completed a task and marked it as completed,
the workflow moves on to the next task in the workflow. Status of individual tasks can be viewed
in the site task list. The information displayed in the task list is customizable.
How to Create a Workflow
Office SharePoint Server 2007 allows you to create customized workflows. To create a customized
workflow, you can use either Workflow Designer or Microsoft Office SharePoint Designer.
Workflow Designer
Workflow Designer is hosted within Microsoft Visual Studio® 2005 for creating customized
workflows and workflow activities. Activities are written in Microsoft Visual C# or Microsoft
Visual Basic® and are organized into workflows. In addition, if customized activities are created
that require user interaction, a new form must be created and published to provide a user interface
for that activity.
Office SharePoint Designer

Office SharePoint Designer is typically thought of as Web site management utility, but it can also
be used as a graphical editor to create workflows for Office SharePoint Server 2007. However,
Office SharePoint Designer is much more limited that Workflow Designer. Office SharePoint
Designer is only able to assemble existing activities into a workflow. You cannot create new
workflow activities in Office SharePoint Designer.
What Are Out-of-the-Box Workflows?
Office SharePoint Server 2007 includes a number of predefined workflows for performing specific
tasks. These predefined workflows are called out-of-the-box workflows and include all of the
necessary components, such as forms, to function properly with no configuration.
The out-of-the-box workflows included in Office SharePoint Server 2007 are:
Approval. Use this workflow to route a document or list item for approval. Each approver will be
assigned a task to approve or reject the associated document or item.
Collect feedback. This process gathers feedback about your document from people such as
coworkers or clients.
Collect signatures. This process gathers signatures needed to complete a Microsoft Office
document.
Disposition approval. This process is a system workflow for generating a disposition approval
task.
Demonstration: Using Out-of-the-Box Workflows
Office SharePoint Server 2007 includes a number of out-of-the-box workflows. These workflows
are used to control the document creation process and enforce company processes. In this
demonstration, you will see how to configure a workflow and how to use a workflow.
Using Records Management Features
Overview
Records management is the process for controlling how documents are archived and deleted from
your systems. Office SharePoint Server 2007 offers a complete records management solution for
content stored in Office SharePoint Server 2007 sites.
What the Official File Web service is.
What the Records Repository site template is.
How documents are submitted to the official file repository.
How to control documents with policies.
What Is the Official File Web Service?
When paper documents are generated as part of a business process, they are typically sent to an
archive. Many organizations still print electronic documents specifically so that they can be
archived. Office SharePoint Server 2007 provides a method for archiving documents and
automating the management of those documents. You can even scan in paper documents to
eliminate physical storage of paper documents.
The Official File Web service submits electronic documents to a repository for archiving. The
repository can be a SharePoint site created by using the official file template or a third-party
archiving solution. The service passes the document, any assigned metadata, and an audit history to
the repository.
Documents can be sent to the official file repository:
By selecting Send To Official File in the SharePoint site Web interface.
Programmatically—for example, by using a workflow.
By using Microsoft Office Outlook 2007 to send documents or e-mail messages.
What Is the Records Repository Site Template?
For organizations that have already implemented a repository for archiving electronic documents, it
makes sense that they would integrate the Official File Web service with their existing repository.
However, for organizations that do not already have a repository for archiving electronic
documents, Office SharePoint Server 2007 provides the Records Repository site template.
The Records Repository site template is customized for use as a repository for archiving electronic
documents. Reporting and document management features are highlighted. Only one records
repository can be configured per site collection.
Records Repository site template features include:
A record series table, which lets record managers specify where different types of content are
stored within the repository.
A predefined record series, named Unclassified Records, which is the default record series type.
A default document library, named Unclassified Records, for storing files assigned to the default
record series type, Unclassified Records.
Other default document libraries: Holding, Hold Reports, and Missing Properties.
The Official File Document Submission Process
The Official File Web service is responsible for submitting documents and metadata to a repository
for archiving electronic documents. This process can be initiated by users or programmatically by a
workflow. You can configure record series types and metadata requirements to control the
submission process.
Record Series Types

Within a records repository, you can have any number of document libraries. A record series directs
documents to a particular document library. Each submitted document is assigned a particular
record series type and organized accordingly. When documents are submitted through the Official
File Web service, the content type of the document becomes the record series type for that
document. For example, if a document of the content type Memo is submitted, the record series
type Memo controls which document library the document is stored in.
Each record series type can also have aliases. Documents submitted as an aliased name are stored
with the documents submitted as the original record series name. For example, if a record series
type named Meeting Minutes has an alias of Meeting Notes, documents submitted to either would
be stored in the same location.
Metadata
For a given record series type, you can require what metadata is required to be submitted. This
ensures that all appropriate metadata is collected at the time of archiving even if the metadata is not
present in the existing document.
Submitting Files
When files are submitted to the records repository, the original files are not modified. You are
sending a copy of the file. However, there is a pointer from the copy back to the original file.
What Are Policies?
Policies are a mechanism to automatically perform records management without manual

intervention. Automated records management is much more reliable than manual processes because
it does not rely on a person remembering to perform a task. In Office SharePoint Server 2007,
policies can be applied to content types or lists.
A policy feature provides a specific type of content management. The policy features included with
Office SharePoint Server 2007 are expiration, auditing, document labels, document barcodes or
alternative format. You can also program your own policy features to extend the base functionality.
Expiration
The expiration feature allows you to define when a document expires and what happens to a
document when it expires. When the expiration feature is enabled, the expiration time of a
document can be:
A time period based on the properties of a document.
Set programmatically, such as by using a workflow.
Set by a custom plug-in to calculate the expiration time.
After expiration, you can perform tasks such as deleting the document or starting a workflow to
approve deleting the document.
Auditing
The auditing feature allows you to log events and activities performed on documents or lists. The
available actions for auditing are:
View.
Edit.
Check in/check out.
Move/copy.
Delete/restore.
Other Features
Other policy features are:
Document label. This feature generates paper labels to be placed on documents for physical
storage.
Document barcode. This feature generates barcodes that can be inserted in documents as a graphic
for physically archiving paper copies.
Alternative format. This feature generates a fixed-format representation for forms.
Demonstration 2: Using Records Management
Office SharePoint Server 2007 has features specifically designed for records management. The
Official File Web service is used to submit documents for archiving. The Records Repository
template is used to create a site for archiving company content. Policies can be used to control the
expiration of documents or audit document access. In this demonstration, you will see how to create
a Records Repository site, how to use a Records Repository site, and how to apply a policy.
Web Content Management Overview
Overview
In addition to document management, Office SharePoint Server 2007 can be used to manage
Web content for intranet or Internet Web sites. The same features that make Office SharePoint
Server 2007 excellent for document management and portals are applicable to Web sites as well.
Describing site templates for Web content.
Describing Web content management features.
How to use the Web content management workflow process.
Describing the page layout model.
Managing page layouts.
Describing the authoring console.
Customizing the HTML editor.
What Are Web Content Site Templates?
Site templates for Web content have preconfigured options for Web content management that are
enabled. To ensure that Web content management features are available, you should use site
templates designed for Web content. The Web content templates are not available when creating
subsites.
The Web content site templates are:
Publishing Site. This template creates a site for publishing Web pages by using a controlled
process. It includes support for approving Web pages by using workflow and scheduling when
Web pages will be visible to site visitors. A document library and a picture library are included for
storing the assets used by the Web pages in the site.
Corporate Intranet Portal. This template creates a site that corporations can use to provide
company-wide information and applications. It includes news, site directory, and search center
features.
Blank Intranet Portal. This template creates an intranet site with a blank home page. It includes a
set of page layouts for creating welcome pages and article pages on the site.
Blank Internet Presence Web Site. This template creates a starter site for an Internet-facing
corporate-presence Web site.
What Are the Web Content Management Features?
Content management features are what makes Office SharePoint Server 2007 an excellent hosting
platform for Web sites. The Web content management features make managing a Web site in
Office SharePoint Server 2007 significantly easier than using a standard Web server.
Some of the Web content management features in Office SharePoint Server 2007 are:
Authoring console. Web sites built by using Office SharePoint Server 2007 include a WYSIWYG
Web authoring console for content providers to create content. This is much simpler than using a
separate Web authoring utility.
Reusable content. Office SharePoint Server 2007 has a list specifically designed to hold reusable
content that appears on multiple pages in a Web site. When the content is updated, it is updated on
all Web pages.
Document conversion. Existing documents can be used as a content source and converted to
Hypertext Markup Language (HTML). For each content type, you can specify how a document is
converted. After the initial conversion, you can synchronize changes in the source document to the
Web page.
Content variations. Variations are a mechanism for publishing related sites or pages for use in
multilingual content or device targeting. Content created or changed in the original source Web
site is propagated to other related Web sites.
What Is Web Content Workflow?
By default, Office SharePoint Server 2007 uses a lightweight approval workflow. More flexible and
complex workflows can be used if desired.
Workflow for Web content is based on approvals and versioning. Each time a person edits a Web
page, a new minor version is created. However, minor versions are not seen by general users of a
site; the minor versions are seen only by those with the ability to edit the site. This gives the
opportunity for other content contributors to provide comments before implementation.
To make an edited Web page visible, the page must be promoted to a major version, such as 2.0
or 3.0. This is done when a site owner approves the minor version. The creator of a minor version
must submit the minor version for approval by a site owner.
What Is the Page Layout Model?
Publishing Web pages with Office SharePoint Server 2007 displays information by using a set of
templates. This is often referred to as a template Web content management system. The two types
of templates are master pages and page layouts.
Master Pages
Master pages contain controls that are shared across multiple pages. Typical controls that are
included across multiple pages are:
Navigation
Company logos
Search
Language preferences
Page Layouts
Page layouts control the main content on a Web page. A page layout relies on a content type to
determine the kind of content that can be stored on pages using the page layout.
Content in a page layout is stored in fields on the page. When users view or edit the page, content is
displayed in field controls. When you create a page layout, you add field controls by using
Microsoft Office SharePoint Designer.
Note Office SharePoint Designer is the latest version of Microsoft Office FrontPage and has
been renamed in the 2007 Microsoft Office system.
The default content type used for Web pages is the Page content type. Some of the information that
can be stored in a Web page, as determined by the Page content type, is:
Start date. The date and time when the page will become visible.
Expiration date. The date and time when the page will no longer be visible.
Contact. The person who created the page.
Managing Page Layouts
Most Web sites will require multiple page layouts for formatting how Web page content is
displayed. Page layouts are stored in the master page gallery, a document library created during site
creation. Even though a master page gallery is created for each subsite that you create, page layouts
can be selected only from the master page gallery in the top-level site.
It is critical to control access to and modification of page layouts. Editing a single page layout can
affect the display of hundreds of Web pages. The master page gallery is secured to require designer
or higher-level permissions, which prevents unauthorized users from editing page layouts. You can
enhance this security by setting item-level permissions on some page layouts. Or you can organize
page layouts into folders and further control access to each folder.
In addition to security permissions, you can use versioning, check in/check out, and workflow to
control the creation and editing of page layouts. It is strongly recommended that all of these tools
be used to manage page layouts.
What Is the Authoring Console?
Office SharePoint Server 2007 includes an authoring console for modifying Web pages. This makes
it easy to delegate page modification to users without requiring them to learn more-advanced Web
page editing tools. Office SharePoint Designer is required only for high-level designers who are
authoring page layouts and master pages.
The authoring console consists of a page status bar, a page editing menu, and quick access buttons.
The page status bar provides status information about a page, such as whether it is checked out or
the version number. The page editing menu lets the user interact with the page, such as approving
the version or adding Web Parts. The quick access buttons provide a quick way to perform common
actions that are relevant to the current state of the page. For example, when a page is checked out,
one of the quick access buttons lets you check in the page. However, when the page is checked in,
the option to check in the page is removed and the option to edit page content is available.
You can customize the page editing menu and quick access buttons in the authoring console. This is
useful for providing your users with specific options that they need access to. For example, if a
certain Web Part is commonly used in your pages, you can create a quick access button for adding
that particular Web Part.
The contents of the page editing menu and the quick access buttons are controlled by Extensible
Markup Language (XML) files stored in the master page gallery. The page editing menu is
controlled by EditingMenu.xml, and the quick access buttons are controlled by Quick Access.xml.
Customizing the HTML Editor
The authoring console includes an HTML editor for editing the fields on a Web page. The HTML
editor is a WYSIWYG editor the functions very much like Office Word. It is suitable for end users
with little or no understanding of HTML. For more advanced implementations, you can customize
the HTML editor.
Some ways to customize the HTML editor are:
Constraints. For a particular field within a Web page, a field control can be assigned that limits the
formatting of content within the field. For example, you can disable links to external Web sites,
disable headings, or disable font changes.
Table formats. The HTML editor includes a number of predefined table formats. You can
customize this by modifying cascading style sheets referenced in the master page or page layout.
Table styles must use the prefix ms-rteTable to be recognized by the HTML editor.
Customized styles. The HTML editor has the ability to apply custom styles to a Web page. Custom
styles are read from C:\Program Files\Common Files\Microsoft Shared\Web Server\Extensions\
12\TEMPLATE\LAYOUTS\1033\STYLES\HTMLEditorCustomStyles.css. You can also add
styles with an additional customized style sheet.
Customized Summary Links, Table of Contents, and Content by Query Web Parts. These three
Web Parts are formatted based on Extensible Stylesheet Language (XSL) style sheets stored in the
site style library. Each Web Part uses several of the XSL files stored in the style library for
formatting different portions of the Web Part output from XML to HTML.
Asset pickers. Asset pickers are used by the HTML editor when users browse to insert a link or
images into a Web page. An asset picker contains certain locations by default, but you can
customize the asset picker by adding additional locations.
For some HTML editor customizations, you must add a RichHtmlField control on the page layout.
This control defines the customization and specifies a column in the content type of your Web page
that is used to perform the customized action. You must add the required column to the content type
of your Web page by using the Full HTML (Publishing) column type. The name of the column
varies depending on the customization you are performing. Adding an additional column is required
for constraints, adding customized styles by using a separate style sheet file, or customizing the
asset picker.
Demonstration 3: Creating and Configuring Web Sites
Office SharePoint Server 2007 has many features specifically designed for Web content
management. Several site templates are included that are specifically designed for Web publishing.
When you choose the Publishing Site template, all the Web content management functions are
enabled. In this demonstration, you will see how to create a new site collection.
Creating Web Pages
Overview
Office SharePoint Server 2007 provides many features to make authoring Web pages easier.
Reusable content ensures consistency between Web pages. Rich Client Authoring (RCA) allows
you to repurpose existing documents and include them as Web pages. There are also several Web
Parts that provide advanced functionality for your sites.
Specifically, this session will cover:
How to reuse content.
Using Rich Client Authoring.
Using Web Parts for advanced functionality.
What Is Reusable Content?
In many Web sites, there are certain content fragments, such as copyright statements or disclaimers,
that are repeated in multiple Web pages. Office SharePoint Server 2007 supports maintaining
reusable content fragments in a centralized list for each site collection.
Reusable content is either Reusable HTML or Reusable Text. Reusable HTML includes HTML
formatting and can include features such as boldface or italics. Reusable Text contains only plain
text.
When reusable content is placed in a Web page, it cannot be edited directly from the Web page.
The Web page contains only a pointer to the reusable content. The reusable content is stored in the
Reusable Content list and must be edited from the list.
Because reusable content is stored separately from the Web pages in a list, the security for editing
reusable content is separated from page authoring. Storing reusable content in a list also allows you
to categorize the content and associate workflows with each content fragment.
What Is Rich Client Authoring?
Rich Client Authoring (RCA) allows users to convert certain types of documents to Web pages. To
enable this feature, you must first configure document conversions on a given Web application and
then enable and configure a converter to perform the conversion. When a converter is enabled, it is
displayed as an option to document authors when they view documents in a document library.
To configure document conversions in a Web application, you must:
1. Start the Office Document Conversions Load Balancer service.
2. Start the Office Document Conversions Launcher service.
3. Enable document conversions for the SharePoint site.
When configuring a converter, you can:

Choose whether to inherit conversion settings from a parent content type or define your own.
Set any converter-specific settings.
Choose a page layout for new pages, including what fields will house converted HTML and
cascading style sheets style information.
Select a default site to create pages in.
Select a default behavior for creating pages (while users wait in the background).
Editing Converted Documents
A converted document is displayed as a normal Web page in your site and can be edited. When you
edit a converted document, you are presented with additional options:
Open Source Document. This will open the original source document for editing. After the source
document has been edited, you can update the existing page. This ensures that the content stays
synchronized between the source document and the Web page.
Update Content From Source. This option reconverts the source document and refreshes the
content of the Web page.
Edit Content. This option allows you to directly edit the content on the Web page. After you edit
the content on the Web page, it is no longer synchronized with the source document.
When you reconvert a document from within a document library, you are given the option to update
any existing Web pages based on the document. You can also view the Web pages before you
perform an update to ensure that you do want to update them.
Web Parts for Web Content Management
Office SharePoint Server 2007 includes three Web Parts specifically designed for Web content
management. These Web Parts make it easier to organize and display links, a table of contents, and
site content.
Summary Links Web Part

The Summary Links Web Part is a way to display a set of links on a Web page. The links can be
organized by placing them into groups. In addition, you can control the style of the displayed links.
For example, you can choose whether the links are bulleted, include an image, or display a
description.
Table of Contents Web Part

The Table of Contents Web Part is used to display the navigation information for your site.
Navigation information includes sites, subsites, pages, and authored links. You can configure how
many levels to display, choose styles for each level, and show or hide specific pages.
Content by Query Web Part

The Content by Query Web Part is used to display a dynamic view of content in your site. It does
this by searching for content of a particular content type and matching a set of filters. The search
scope for the content can be limited to a particular site or list. You can also configure the style of
how the results are displayed.
Demonstration 4: Creating Web Pages
Office SharePoint Server 2007 includes features to make creating Web site content easier. Reusable
content ensures consistency across Web pages and makes updating boilerplate content easier. Rich
Client Authoring lets you quickly convert existing documents to Web pages. In this demonstration,
you will see how to make use of reusable content and how to implement Rich Client Authoring.
Advanced Web Content Management
Overview
Office SharePoint Server 2007 provides advanced Web content management features for enterprise-
level Web sites. Content variations are used to reformat content for different users. Content
deployment is used to move content from one site to another, typically promoting a development
Web site into production. You can also convert a Content Management Server 2002 site to Office
Specifically, this session will cover:
Using content variations.
Using content deployment.
Describing authentication considerations.
Reasons to migrate to Office SharePoint Server 2007.
How to migrate to Office SharePoint Server 2007.
What Are Content Variations?
Content variations are a mechanism for publishing related sites or pages. Two common reasons to
implement content variations are multilanguage Web sites and device targeting. Content variations
help ensure that multilanguage Web sites update content in all languages when the source content is
updated. For sites with content that is reformatted for devices with different display capabilities,
content variations ensure that when the source content is updated, content for other devices is
updated as well.
The content variation process is as follows:
1. Create a source variation.
2. Create additional variations.
3. Update and approve content in the source variation.
4. Create a new page for each variation.
5. Edit the new page for each variation and approve.
For example, assume that you have a multilanguage Web site with the English site set as the source
variation with additional French and German variations. When a page in the English Web site is
updated and approved, that page is copied to both the French and the German Web sites as a draft.
Because the new page is a draft, it is visible only to content contributors. Translators will need to
view the new pages, translate the content, and approve the new pages for the pages to be visible to
the public.
What Is Content Deployment?
Content deployment provides a way to transfer content from one site collection to another site
collection. The site collections can exist in different farms, so content deployment can be used to
support multitiered topologies. For example, one site collection might be used internally for
development and another externally as a production Web site.
Note When content deployment is used between two site collections in the same farm, the two
site collections must use different Web applications.
Paths and jobs are used to manage content deployment. A path defines the relationship between a
source and destination site collection. A job is associated with a path and defines the specific
content to be deployed and the schedule on which to deploy the content.
Authentication Considerations
Office SharePoint Server 2007 natively supports Kerberos, NTLM, and Basic authentication. Other
authentication mechanisms can be implemented by using the Microsoft ASP.NET Membership
Provider Interface.
Authentication for Intranets

Integrated Windows authentication is preferred for intranets. This system takes the authentication
credentials from the client running Microsoft Windows and passes them through Microsoft Internet
Explorer® to the SharePoint site. This saves users the inconvenience of entering their credentials
multiple times. Both Kerberos and NTLM support integrated Windows authentication.
Kerberos is the recommended method for authenticating to SharePoint sites. It is the most secure
natively supported authentication method.
Authentication for Internet Sites

Integrated Windows authentication is not well suited for Internet sites. It is unlikely that the
authentication credentials from a remote client running Windows on the Internet are the same as the
authentication credentials required to access the Web site.
You can enable forms-based authentication to allow users to enter their authentication credentials
into a Web page. If you are using a relational database or a Lightweight Directory Access Protocol
(LDAP) server for authentication, you must enable forms-based authentication.
Anonymous Authentication
For many public Internet sites, authentication is not required to view site content. In this case, you
must enable anonymous access. You must enable anonymous authentication for the Web
application and site collection.
Reasons to Migrate to Office SharePoint Server 2007
Microsoft Content Management Server (MCMS) 2002 and SharePoint Portal Server 2003 are
integrated into a common architecture in Microsoft Office SharePoint Server 2007. The new
features in Office SharePoint Server 2007 significantly reduce the amount of custom coding
required for building Web sites. Many tasks such as navigation, summary links, and scheduled
deployment that required an MCMS developer can now be performed by users or IT professionals.
Office SharePoint Server 2007 offers significant additional functionality over MCMS 2002,
including the following:
Collaboration and tracking
Project task lists
E-mail integration
Extensible workflows
Richer authoring
Better multilingual support
No need for client installation
Really Simple Syndication (RSS) feeds
Integrated search
Process for Migrating to Office SharePoint Server 2007
Migrating to Office SharePoint Server 2007 is a two-step process. The first step is content
migration. The second step is code migration.
Content Migration
Content migration from MCMS 2002 to Office SharePoint Server 2007 is an automated process
performed by Office SharePoint Server 2007. The following parts of an MCMS 2003 installation
are migrated:
Channels, postings, and all placeholder content
Resource galleries and resources
Template galleries and template gallery items
Rights groups and users
Custom properties
After migration, the site will contain an unbranded master page and unbranded page layouts for
each template in the source channel. These files must be customized to match your desired
branding.
Code Migration
MCMS 2002 code must be rewritten. This is a significant amount of work. However, many of the
functions built into Office SharePoint Server 2007 reduce the need to develop custom code for Web
sites. Whenever possible, use the new features in Office SharePoint Server 2007 and avoid
rewriting code.
Demonstration 5: Advanced Web Content Management Features
Demonstration
Office SharePoint Server 2007 provides a number of advanced Web content management features
for enterprise-level Web sites. Content variations can be used to manage sites that are translated
into multiple languages. Content variations can also be used to manage sites that are formatted
differently to support different devices. In this demonstration, you will see how to use content
variations.
Session Summary
This session explored the content management capabilities of Office SharePoint Server 2007. The
session explored the following topics:
Document Management by Using Office SharePoint Server 2007. This topic discussed creating an
enterprise document repository, content types, scenarios for using content types, and using
templates to create content types. Many Office SharePoint Server 2007 features rely on content
types.
Using Document Workflows. This topic discussed what a workflow is, what the workflow tasks
are, how to create a workflow, and out-of-the-box workflows. Office SharePoint Server 2007
includes predefined workflows for performing specific tasks.
Using Records Management Features. This topic explored what the Official File Web service is,
what the Records Repository site template is, how documents are submitted to a Records
Respository and how to control documents by using policies. Office SharePoint Server 2007 offers
a complete records management solution for content stored in SharePoint sites.
Web Content Management Overview. This topic explained some of the Web content management
features in Office SharePoint Server 2007. Specifically discussed were site templates for Web
content, Web content management features, Web content management workflow, the page layout
model, managing page layouts, the authoring console, and customizing the HTML editor.
Creating Web Pages. This topic examined how to reuse content, Rich Client Authoring, and using
Web Parts for advanced functionality. Office SharePoint Server 2007 provides features to make
authoring Web pages easier.
Advanced Web Content Management. This topic discussed using content variations, using content
deployment, authentication considerations, reasons to migrate to Office SharePoint Server 2007,
and how to migrate to Office SharePoint Server 2007. Office SharePoint Server 2007 provides
advanced Web content management features for enterprise-level Web sites.
Next Steps
Download and evaluate Office SharePoint Server 2007.

Session 3: Organizing and Finding Resources
with Office SharePoint Server 2007
Contents
Session 3: Organizing and Finding
Resources with Office SharePoint
Server 2007 1
Building Portals by Using Office
SharePoint Server 2007 2
Building Personal SharePoint Sites by
Using Office SharePoint Server 2007 11
Managing Search 20
Search Relevance 30
Search Syntax 37
Session Summary 40
Next Steps 41

Session 3: Organizing and Finding Resources with Office SharePoint Server 2007 1
Session 3: Organizing and Finding Resources with Office

Overview
Microsoft® Office SharePoint® Server 2007 provides advanced features for organizing and finding
data. Advanced portal personalization features provide a way to organize data in exactly the form
the way users need it. You can even vary the configuration dynamically, depending on which user
is logged on. The search functionality in Office SharePoint Server 2007 is an enterprise-level search
that makes it easy to find data in SharePoint sites, file shares, external Web sites, line-of-business
applications, and many more sources.
Describe the portal features in Office SharePoint Server 2007.
Describe the personal SharePoint site features in Office SharePoint Server 2007.
Describe how to manage searching in Office SharePoint Server 2007.
Describe search relevance in Office SharePoint Server 2007.
Describe the search syntax used in Office SharePoint Server 2007.
2 Session 3: Organizing and Finding Resources with Office SharePoint Server 2007
Building Portals by Using Office SharePoint Server 2007
Overview
Portals provide a single location that brings together all of the information workers need to get their
jobs done (for example, people, teams, knowledge, applications). Office SharePoint Server 2007
provides advanced functionality that lets you easily design and maintain advanced portal solutions.
Site Manager provides an easy way to view and manage the overall site structure. Audience
targeting lets you dynamically change the data seen by users based on who they are and the roles
they perform.
After completing this section, you will be able to:
Describe the portal features in Office SharePoint Server 2007.
Describe the capabilities of Site Manager.
Describe how to configure portal security.
Describe how to manage user profiles.
Describe audiences.
Describe audience rules.
What Are the Portal Features in Office SharePoint Server 2007?
Creating a portal solution should not require coding a portal software application from scratch.
Office SharePoint Server 2007 includes pre-built components and features that make building a
portal faster and more cost-effective. Office SharePoint Server 2007 includes (among many other
elements) the features previously available in Microsoft Office SharePoint Portal Server 2003.
Some of the portal features provided in Office SharePoint Server 2007 are:
Web Parts. The pre-built components for building portals are called Web Parts. They perform
specific tasks for you, such as displaying a task list, announcements, the data from a line-of-
business (LOB) application, and so on.
Online editing. The ability to edit portal pages online through a graphical interface means that
non-IT staff can be responsible for maintaining site content.
Workflows. Changes to the portal pages can be controlled by workflows. At the simplest level,
page changes must, by default, be approved by a site owner.
Notifications. Users can be notified when a page, list, document, or any content indexed by the
portal changes. This ensures that users are aware of changes and can react appropriately.
My Site. Personal SharePoint sites allow users to create their own portal both to organize their
work resources and to publish information about themselves and their work to others in their
organizations.
Personalization. The pages in a portal can display different information, different content, and
different Web Part components for different users based on security or productivity needs.
Integrated search. Search is an integrated part of the portal making it easy for users to find the
data they need.
Integrated security. Microsoft Office SharePoint Server 2007 provides security to control user
access to view and edit content. Changing security for a user is as simple as adding the user to a
group.
What Is Site Manager?
Site Manager gives you a hierarchical structure to view all of the sites and components in a site
collection. A site collection is a hierarchy of sites that have integrated settings for characteristics
such as navigation, security, and content types. Site Manager is designed to give a macro-level view
of your portal environment. You can also use Site Manager to reorganize your overall site structure
by changing the site hierarchy.
Some of the tasks you can perform by using Site Manager are:
Create new sites.
Copy existing sites.
Move existing sites.
Edit Web Part properties.
Copy a Web Part to a different site or within a site.
Add a new Web Part.
What Is Portal Security?
When you build portals by using Office SharePoint Server 2007, you can configure permissions
to control which users are allowed to view, update, and manage content. Office SharePoint
Server 2007 defaults to using user and group accounts from Microsoft Windows® domains, but
portal users can in fact come from any security authority for which a Microsoft ASP.NET
provider exists—for example, Lightweight Directory Access Protocol (LDAP) servers, database
tables, and so on. As such, you have specific control of who can do what even in mixed
Internet/extranet/intranet deployments, including on a complete or selective basis, the option of
allowing anonymous users to access some portions of the site.
Permissions are inherited down through the site hierarchy by default. A user that is given full
control to the root site will, as a result, inherit full control to all new subsites until such time as
those subsites’ owners choose to apply unique permissions to those sites.
Groups
For each site, groups are created for members, owners, and visitors. Members are allowed to
contribute content. Owners have full control over the site and can modify all content as well as
control permissions. Visitors have the ability to read content on sites. Other groups are created to
manage the site collection and are able to complete tasks such as changing the hierarchy or
changing page layouts. Site owners can, in turn, create additional groups for their sites.
Permission Levels
Permission levels are a set of rights that have been grouped together. You can create your own
permission levels to meet specific needs and assign detailed rights to that group.
The default permission levels are:
Full Control. Can complete any tasks.
Design. Can edit lists, document libraries, and pages in the Web site.
Contribute. Can view pages and edit list items and documents.
Read. Can view pages, list items, and documents.
Limited Access. Can view specific lists, document libraries, list items, folders, or documents when
given permissions.
Approver. Can edit and approve pages, list items, and documents.
Hierarchy Manager. Can create sites and edit pages, list items, and documents.
Viewer. Can view pages and documents, but cannot view historical versions or review user rights
information.
Submitter. Can complete missing properties for submitted files.
Demonstration 1: Managing Portals
Office SharePoint Server 2007 provides many advanced functions for portals, such as Web Parts
and security. These advanced functions reduce or eliminate the need for custom code when creating
a portal. In this demonstration, you will see how to use Site Manager.
What Are Audiences?
An audience is a group of users that site content can be targeted toward. The members of an
audience can be defined by membership in an Active Directory® directory service group, users who
report to a particular manager, or user profile properties. For example, you can create an audience
named Human Resources that is defined as all users whose Department property is equal to Human
Resources.
By default, only the All Site Users audience is created. You can create as many additional
audiences as are appropriate for your organization. Audiences are often created to represent
organizational departments, such as Human Resources or Accounting.
Note Many audiences are based on user profile properties. Details about user profiles are
discussed in the next section, “Building Personal SharePoint Sites by Using Office SharePoint
Server 2007.”
Content can be targeted at the Web Part level or item level. For example, an entire Web Part, such
as a calendar, might be visible only to members of the Human Resources audience. In addition,
some items in an announcements list might be visible only to members of the Human Resources
audience.
What Are Audience Rules?
The members of an audience are defined by audience rules. Each audience must have one audience
rule, but an audience can have multiple audience rules. When there are multiple audience rules, you
can choose whether audience membership is based on matching a single rule or whether members
must match all of the audience rules.
Each audience rule is composed of:
An operand. You can specify whether the rule is evaluated based on users or a user property.
When users are specified, you can create rules based on Active Directory groups or organizational
hierarchy.
An operator. The options for the operator vary depending on the operand that has been selected.
When a user property has been selected as the operand, the most common operators available are
equals, contains, not equal, and not contains.
A value. The value is compared to the operand to define audience membership. For example, if the
Department property equals the value of Human Resources, users would be members of the
Human Resources audience.
Audience compilation is the process whereby the membership in the audience is calculated based
on the audience rules. You can define a schedule for audience compilation or trigger compilation
manually. Audience compilation does not occur dynamically.
Audience memberships are precompiled to allow for fast retrieval and thus overall server
performance. Scheduled audience compilation reduces that load to the scheduled times. If your
audiences are updated frequently, schedule audience compilation to occur frequently. By default, no
schedule is specified for audience compilation.
Demonstration 2: Audience Targeting
Personalizing content based on audiences is one of the advanced portal features included in Office
SharePoint Server 2007. You can use this feature to present the most relevant information to portal
users. In this demonstration, you will see how to create audiences and target content.
Building Personal SharePoint Sites by Using Office

Office SharePoint Server 2007 includes the ability for users to create personal SharePoint sites.
Personal SharePoint sites can be used to organize, store, and share information. In addition,
personal SharePoint sites can serve as a personal portal with all relevant information for that user
gathered in a single location.
Describe My Site.
Describe a user profile.
Describe privacy controls.
Describe social networking.
Describe the SharePoint Sites And Documents Roll-Up Web Part.
Describe the Colleagues and Memberships Web Parts.
What Is My Site?
My Site is a personal SharePoint site that can be created by each user. By default, the Authenticated
Users group is granted permissions to create a personal site. However, this can be limited to any
Active Directory security group if you prefer.
When users create their own My Site, a new SharePoint site is created for each user. My Site
consists of My Home and My Public Page. My Home is a private portal. My Public Page is a
personal Web page that is available to other users. Much of the content on both pages is the same.
For example, if a link is added to the My Links list on a user’s My Site and is not flagged as
private, that link will also be visible in the Links Web Part on that user’s My Public Page.
The lists and libraries included by default in My Home are:
My Links. An editable list of links that can take the place of the Favorites list in Microsoft Internet
Explorer®.
Colleagues. An editable list of colleagues.
A document library. A location where you can store documents instead of a home directory on a
network file share.
A shared picture library. A place to store and share pictures.
In addition to the Web Parts that display the preceding lists and libraries, some additional Web
Parts included on My Public Page are:
SharePoint Sites. A summary of documents and tasks in all SharePoint sites.
Memberships. A list of SharePoint sites that you are a member of.
My Calendar. A link to Microsoft Office Outlook® Web Access.
Contact Information. Shows information such as an e-mail address that can be used to contact this
user.
Organizational Hierarchy. A tree view that displays where this user fits into the hierarchy of the
organization.
In Common with You. Displays information that other users have in common with this user, such
as colleagues or memberships.
What Is a User Profile?
A user profile is information about a user that can be edited from within My Site. The information
in a user profile can be used as an operand in an audience rule. User profile information is also used
when searching for people in Search Center.
The only properties that are configured automatically in a profile are the preferred name, account
name, and work e-mail address. Other properties that can be configured in a profile might include
(but are not limited to):
About Me. A freeform, text-based description of the user.
Picture. Lets the user upload and display a picture.
Responsibility. A list of keywords or phrases related to the user’s responsibilities.
Skills. A list of keywords or phrases related to the user’s skills.
Past Projects. A list of past projects.
Interests. A list of other interests, such as hobbies.
School. A list of the schools a user has attended.
Birthday. The birthday of the user.
Assistant. The name of the user’s assistant.
Cell Phone. The cell phone number of the user.
Fax. The fax number of the user.
Home Phone. The home phone number of the user.
Security Clearance Level. A measure of the sensitivity of information a user can see.
What Are Privacy Controls?
You might not want certain user profile information to be available to everyone in your
organization. For example, you might want your home phone number available only to your
manager or colleagues. Privacy controls let you configure which users are able to see the properties
in your user profile.
When you configure who is able to see a property in your user profile, you must select from these
options:
Only Me. No other users are able to view this information.
My Manager. Only the user’s manager is able to view this information.
My Work Group. Only members of the user’s workgroup are able to view this information.
My Colleagues. Only users configured as colleagues are able to view this information.
Everyone. All users are able to view this information.
You can also use privacy controls to limit the display of other information in My Site to other users.
For example, you can select which memberships or links are visible to other users.
Policies
In addition to privacy controls, the shared services provider (SSP) has privacy policy settings to
control the configuration of My Site and user profile properties. In the policy, you can configure:
Property settings, such as display name and variable type.
Policy settings, such as default access and whether the policy can be overridden by users.
Display settings, such as whether to show the property in the Profile Properties section of the
user’s My Public Page.
Demonstration: Building Personal SharePoint Sites
My Site is a personal SharePoint site that users can create and manage for themselves. It can act as
a personal portal where users keep links and documents so that that they are available from any
computer. It also contains a personal home page where users can make their information available
to others. In this demonstration, you will create a My Site for a user, configure a user profile, and
configure and test privacy settings.
What Is a Social Network?
A social network is the structure of the relationships between individuals or organizations. Social
networks are unique in recognizing that the relationships between individuals are as important as
the characteristics of the individuals. For example, when looking for information, you are more
likely to trust information given by a source recommended by a friend. Office SharePoint
Server 2007 facilitates understanding the social networks within your organization.
The In Common With You Web Part shows users viewing your My Public Page things that you
both have in common. Understanding which things you have in common helps establish personal
connections with other people in your organization. This can consist of information directly
supplied by the user as well as information automatically calculated based on information in Active
Directory, the user profile shared service, and membership in SharePoint sites that the portal has
access to.
The information displayed can include:
The manager to whom you both report.
Colleagues you both know.
Memberships you both have.
Group memberships you both have.
What Is the SharePoint Sites And Documents Roll-Up Web Part?
If a user is a member of many SharePoint sites, finding relevant documents and tasks from all of
those sites can be time-consuming.
The SharePoint Sites And Documents Roll-Up Web Part provides a single place to view the
documents and tasks relevant to you across all SharePoint sites. A list of all SharePoint sites is
displayed, and relevant documents and tasks in that site are displayed when a site is selected. This
can save several minutes each time you want to find a file or review tasks.
What Is the Colleagues Web Part?
The Colleagues Web Part plays a role in social networking. It is used to display information that
you might have in common with other users.
The Colleagues Web Part displays the colleagues that you have configured for yourself. You can
organize your colleagues into categories for easier access and control their visibility by using
privacy controls.
For each colleague, you have easy access to:
View online status.
Schedule a meeting.
Send mail.
Send an instant message.
Add the colleague as an Office Outlook contact.
You can also configure alerts for the following:

Anniversaries
Key property changes
Membership changes
New documents
Out-of-office status
Demonstration 3: Using the Colleagues Web Part
One of the components included in Office SharePoint Server 2007 to enhance social networking is
the Colleagues Web Part. The Colleagues Web Part lets you see information about your colleagues,
including sites that they are members of and documents they are working on. In this demonstration,
you will see how to use the Colleagues Web Part.
Managing Search
Enterprise-level search is one of the most powerful features in Office SharePoint Server 2007.
While similar in lower-level design to the search facility provided in Microsoft Windows
SharePoint Services 3.0, the search facilities in Office SharePoint Server 2007 are enhanced both in
terms of scope and in terms of features. Office SharePoint Server search includes the ability to
search people, files shares, and line-of-business applications. It also allows for a fully customizable
search user experience.
Describe the search architecture.
Describe content sources.
Describe the options for crawling content.
Describe rules to control the crawling process.
Describe propagation of indexes.
Describe the search schema.
Describe search scopes.
Describe query reporting.
Search Architecture
The search application in Office SharePoint Server 2007 is designed to be highly scalable. It can
index large amounts of data quickly and provide search services for thousands of users. In small
environments, all of the search components can be run on a single server. However, to increase
scalability, the search components can also be hosted on separate, dedicated servers.
The search architecture is composed of the following components:
Content sources. The data to be indexed.
Index service. The components that index content sources. To speed up indexing, multiple
indexing services can be used. The index catalog (index results) is copied to one or more servers
running the query service.
Query service. The query service accepts search requests and returns results. To increase search
capacity, multiple query services can be configured in a load-balanced cluster. All query services
in a load-balanced cluster must have copies of the same index catalog from the index service. Each
query service accepts an index catalog from only one index service.
Search Center. The user interface for submitting search queries. Search Center can be configured
to submit queries to multiple query services. Results from each query service are separated onto
different tabs.
What Are Content Sources?
Office SharePoint Server 2007 supports indexing of a wide variety of documents and data. Each
location storing data to be indexed is a content source.
A content source named My Office SharePoint Servers is configured by default to index the local
server running SharePoint. People content from the user profile database is also indexed, although
the people content is not listed as a content source.
The types of content that can be crawled are varied and numerous, and third-party extensions exist
that allow for still more sources to be indexed. Content sources in Office SharePoint Server 2007
can include:
Web sites. You can index the content of any Web site by specifying the URL.
Servers running SharePoint. If there are multiple servers running SharePoint, it is beneficial to
have all of them searchable through a single index. Users can then easily find any of the content
they need.
File shares. Even if an organization starts to use SharePoint sites for all data storage, there will
likely be older data stored in file shares. You can index a file share by specifying a Universal
Naming Convention (UNC) path.
Exchange public folders. Many organizations use Microsoft Exchange public folders to store a
wide range of information. This information is accessible through SharePoint search when
configured as a content source.
Business data. Business data is made searchable through the Business Data Catalog. The Business
Data Catalog can connect to databases and line-of-business applications.
Lotus Notes databases. Lotus Notes databases are made searchable through the Business Data
Catalog.
What Is Crawling?
Crawling is the process used to index content sources. Crawling creates a full-text index of the
content source at specified intervals. Information about the crawling process is written to a log.
You configure some crawl characteristics when you create a content source:
Crawl settings. This option lets you select whether to crawl only indexes at the specified locations
or to crawl additional content under the specified locations. For example, you can choose to crawl
only a specified directory in a file share or a specified directory and all subdirectories.
Crawl schedules. This option lets you configure when a full crawl is done and when an
incremental crawl is done. Performing incremental crawls is much more efficient than performing
full crawls.
Start a full crawl. This option lets you trigger a full crawl. Forcing a full crawl is useful when you
want to crawl a content source immediately after creation.
The crawl log tracks information about the status of crawled content. You can use this log to verify
whether crawled content was added to the index successfully, whether it was excluded because of a
crawl rule, or whether indexing failed because of an error.
You can use filtering to control viewing of the crawl log. Filter options include content sources,
status type, and timestamp. This makes it easier to find the specific information you are looking for.
What Are Crawl Rules?
Some of the content that you want to index will need additional rules to control which content is
crawled. For example, there might be a large downloads directory in a Web site that you do not
want indexed. In addition, some content sources might require authentication credentials.
Crawl rules allow you to:
Prevent content within a particular path from being crawled.
Force content in a particular path to be crawled.
Force complex URLs (URLs containing a question mark) to be crawled.
Specify authentication credentials.
Rule Order
The first rule that matches the content being crawled is the rule that is applied. For this reason, placing
rules in the correct order is important. For example, if the first rule excludes \\server\share\directory1
and the second rule includes\\server\share\directory1\subdirectory, the subdirectory will never be
crawled.
File Type Inclusions

In addition to crawl rules, you can control indexing of content by using file type inclusions. Only
the listed file types will be indexed. Most common document formats are already included,
including text files, office documents, Web pages, and e-mail messages. Document types are
controlled based on file extensions.
What Is Propagation?
Office SharePoint Server 2007 allows you to separate the index service used by crawling from the
query service used by searching. If the index service and query service are running on separate
servers, search has to copy the index catalog from the server running the index service to the server
running the query service. This copying process is referred to as propagation.
When propagation is required, there is a delay between indexing content and its availability for
search. The delay depends on the propagation mode you select. If there is a problem during
crawling or propagation, the existing index catalog will be used until the problem is resolved.
The two propagation modes are:
Staged propagation. Staged propagation always performs a full copy of the index catalog between
the index server and the query server. The propagation can be triggered manually or scheduled.
Continuous propagation. Continuous propagation always performs an incremental copy of the
index catalog between the index server and the query server. The propagation is triggered each
time the index catalog changes.
What Is the Search Schema?
You will not always want all document properties to be available for searching. Some properties
might contain inaccurate information if the documents were not configured properly. For example,
the document subject might be inaccurate because users were not using it in the past. By using the
search schema, you can control which properties are available for searching.
Crawled Properties
Crawled properties are the properties discovered by the index service when content is crawled. You
cannot search for crawled properties automatically. A crawled property must be mapped to a
managed property before it can be searched.
Managed Properties
A managed property is a property that is available for searching, such as Title. Mapping a crawled
property to a managed property makes it available for searching. You can map multiple crawled
properties to a single managed property or map a single crawled property to multiple manage
properties. For example, the managed property Title can be mapped to the crawled properties for
document subject and Web page title.
What Are Search Scopes?
Search scopes allow you to control what content within an index is available to a search. In
SharePoint Portal Server 2003, search scopes were tied to content sources. Office SharePoint
Server 2007 is able to define search scopes independently of content sources for greater flexibility.
It is now possible to create a search scope that includes a subset of one or multiple content sources.
For example, you can define a search scope for all documents authored by a particular person
within a content source.
Another major improvement over SharePoint Portal Server 2003 is dynamic search scopes.
SharePoint Portal Server 2003 required a content source to be recrawled before the scope was
available. Search scopes in Office SharePoint Server 2007 are available immediately after creation.
When you create a search scope, you must define rules to control the content included in the scope.
There are four types of rules:
Web address
Property query
Content source
All content
You are also able to specify how a rule is applied to the results:
Include. Items will be included unless another rule removes them (OR).
Require. Items matching other rules must also match this rule (AND).
Exclude. Items matching this rule will be excluded from the scope (NOT).
What Is Query Reporting?
Understanding how search is being used is the key to improving search functionality in your
organization. Office SharePoint Server 2007 has a reporting function built-in to help you
understand how search is being used in your organization.
By using query reporting, you can see a wide variety of information, including:
Query volume trends.
Top queries.
Click-through rates.
Queries with zero results.
If the volume of queries on a server is becoming a problem, you can make configuration changes to
increase capacity. You can also ensure that a common query returns a particular document by using
editorial results.
Demonstration 4: Managing Search
To make search effective for your organization, you must understand the options available for
configuration. Content sources control which information is indexed. Crawl rules control which
content within a source is indexed. Search scope lets you divide indexed content in logical units to
make searching more effective. In this demonstration, you will see how to configure content
sources, crawl content, and configure
Search Relevance
The search function in Office SharePoint Server 2007 has been enhanced to improve the relevance
of search results. This increases user productivity by increasing the likelihood that the required
information appears on the first page of the search results. This section covers the search relevance
features in Office SharePoint Server 2007.
After you complete this section, you will be able to:
Describe hyperlink analysis.
Describe content analysis.
Describe other analysis types.
Describe results collapsing.
Describe keywords.
What Is Hyperlink Analysis?
You normally create links from one item to another because the linked content enhances the value
of the original item. Therefore, information about hyperlinks, such as the number of hyperlinks that
point to an item, is useful for determining relevance. Search is able to use hyperlink information
and includes it in the content index.
Click Distance
One particular hyperlink analysis method is click distance. Click distance is calculated as the
number of links between a URL and an authoritative site. As an administrator, you control this
distance by defining which sites are authoritative.
Anchor Text
Anchor text is the highlighted text that is clicked to activate a hyperlink. When search crawls the
content, the anchor text is included in the index. If search terms are part of the anchor text linking to
an item, the relevance of the item is raised.
What Is Content Analysis?
Content analysis looks at the file type of an item and the properties of an item. When a search term
is found in the properties, some properties are likely to be more relevant than others. Field boosting
allows you to modify the per-property weight assigned to the properties. By adjusting the weights,
you can emphasize the properties important for your organization.
The file type of an item can affect the relevance of an item in search results. When calculating
relevance by using a query word entered by the user, search counts the number of times that query
word appears in the body of the document and in the different properties of the document and how
frequently the word occurs overall in the indexed content.
Typically, the more times a query word appears, the greater the relevance for that item. However,
document types may have a different structure. For example, Microsoft Office Excel® files contain
fewer words than a Microsoft Office Word document, so the relevance would be skewed. To
resolve this problem, search applies file type priors to assist in the relevance calculation and
structures relevance appropriately by taking the document type into account.
What Are the Other Analysis Types?
In addition to hyperlink analysis and content analysis, several other type of analysis are used to
determine relevance. Other analysis methods include:
Authoritative sites. You can define authoritative sites to upgrade their relevance scores. You can
also define the least important sites to downgrade their relevance.
URL depth. Content located closest to the top of a site’s hierarchy are given increased relevance
scores. The greater the number of slash (/) marks in the URL, the lower the relevance for that item.
Title extraction. For properly named content, the title is an important indicator of relevance.
However, for many Microsoft Office documents, the title is not properly defined. If a title such as
Slide 1 or Document 1 is found, search attempts to find and extract a relevant title.
Languages. Users are more likely to be looking for content in their own language than in other
languages. When calculating relevance, content that is retrieved in the user’s language is
considered more relevant. In general, English is also considered more relevant because a large
percentage of users speak English.
What Is Results Collapsing?
Search results frequently contain several items that are the same or very similar. If these duplicated
or similar results are ranked highly, they are returned as the top items in the results set. The
unnecessary duplication of items forces other items that might be relevant farther down the list,
making it more difficult to find them.
Results collapsing can group duplicated or similar results together so that they are displayed as a
single entry in the results set. The collapsed results entry includes a link to display the expanded
results.
Search administrators can collapse results for the following content item groups:
Duplicates and derivatives of documents
Windows SharePoint Services discussion messages for the same topic
Microsoft Exchange Server public folder messages for the same conversation topic
Current versions of the same document
Different language versions of the same document
Content from the same site
What Are Keywords?
A keyword is a word or phrase that has been identified as important to your organization. When a
keyword is used in a search, additional information is displayed with the search results. The
additional information is referred to as editorial results.
Administrators configure keywords at the site collection level and include the following
information:
Synonyms. Partial matching of keywords is not performed. When there are multiple variations of
keyword, such as SharePoint Server and Office SharePoint Server 2007, you should enter the
variations as synonyms.
Best bets. Best bets are recommended results for the keyword and appear in the search results.
Source. When best bets are displayed, a source can be displayed as the recommender of the best
bets. A source consists of a title and a URL. Adding a source might give the results extra validity
to the users.
Keyword definition. Optional editorial text that will appear if the keyword is used in a search.
Publishing dates. Each keyword can have a start date, an end date, and a review date. After the
end date, a keyword is no longer used. After the review date, the keyword must be approved for
continued use.
Contact. When a keyword must be renewed, the contact is the person who is informed.
Demonstration 5: Search Relevance
Office SharePoint Server 2007 includes a variety of mechanisms for determining search relevance.
Two of the most important mechanisms are results collapsing and keywords. In this demonstration,
you will see results collapsing and how to configure keywords.
Search Syntax
Office SharePoint Server 2007 search includes a new keyword syntax for building queries. This
syntax is much simpler than the Microsoft SQL Server™ Search syntax required by SharePoint
Portal Server 2003. This section covers searching with keywords and property filters.
Describe search keywords.
Describe property filters.
What Are Search Keywords?
Search keywords are the most common way that users search for information. Search keywords
can be:
A word. One or more characters without spaces or punctuation is a word.
A phrase. One or more words enclosed in quotation marks is a phrase.
A prefix. Part of a word, starting from the beginning of the word, is a prefix.
If multiple keywords are included in a search, the result might have all or some of the keywords.
For more refined searches, you might want to force certain keywords to be included or excluded.
For example, when searching for information about a particular project, you can force the inclusion
of the project name but exclude similar project names.
Forcing a keyword to be in the search results is done with a plus sign (+). Excluding a keyword is
done with a minus sign (-).
What Are Property Filters?
Property filters provide you with a way to narrow your search results. However, many of the
options available through property filters are also available by selecting Advanced Search in Search
Center.
You can define property filters based on:
Managed properties.
Search scopes.
Collapsed results.
The syntax used is shown here:

PropertyName:value
ScopeName:value
CollapsedResultsType:value
For example, if you wanted to find documents with the author name John Smith, you would use the
following syntax:
author:“John Smith”
Multiple property filters can be used in a single query.
Session Summary
This session covered the portal and search capabilities in Office SharePoint Server 2007. The
Building Portals by Using Office SharePoint Server 2007. This topic discussed some of the
features in Office SharePoint Server 2007 for building portals. Specifically, Site Manager, portal
security, audiences, and audience rules were covered. Office SharePoint Server 2007 provides
advanced functionality that lets you easily design and maintain advanced portal solutions.
Building Personal SharePoint Sites by Using Office SharePoint Server 2007. This topic explored
the features available when building personal SharePoint sites by using Office SharePoint Server
2007. My Site, user profiles, and privacy controls were discussed in relation to personal portals
and public Web pages. In addition, social networks, the SharePoint Sites And Documents Roll-Up
Web Part, and the Colleagues Web Part were discussed. Personal SharePoint sites provide users
with a personal portal to organize, store, and share information.
Managing Search. This topic explained some of the tasks involved in managing the search feature
in Office SharePoint Server 2007. Content sources, options for crawling content, crawl rules,
propagation, the search schema, search scopes, and query reporting were discussed. Integrated
search is one of the most powerful features in Office SharePoint Server 2007.
Search Relevance. This topic explained some of the search relevance features available in Office
SharePoint Server 2007. Calculation of relevance by using hyperlink analysis, content analysis,
and other analysis types was discussed. In addition, results collapsing and keywords were
discussed as methods of improving results presentation. User productivity is increased by using
the search relevance enhancements in Office SharePoint Server 2007.
Search Syntax. This topic explored the search syntax used in Office SharePoint Server 2007. Both
search keywords and property filters were discussed. Office SharePoint Server 2007 search
includes a new keyword syntax for building queries.
Next Steps
Download and evaluate the Office SharePoint Server 2007.

Session 4: Business Solutions Using Office
Contents
Session 4: Business Solutions Using
Office SharePoint Server 2007 1
Using the Business Data Catalog 2
Using Forms Server 14
Using Excel Services 25
Creating Report Center Sites 35
Session Summary 42
Next Steps 43
Clinic Evaluation 45

Session 4: Business Solutions Using Office SharePoint Server 2007 1
Session 4: Business Solutions Using Office SharePoint

Server 2007
A whole new class of functionality has been introduced in Microsoft® Office SharePoint®
Server 2007 to provide solutions for Business Intelligence, business process management, business
forms, and business application integration. This includes features such as Web-delivered
spreadsheet reports, business dashboards, no-code connectivity to line-of-business applications and
data for display and search, rich client-based and Web-based forms, and much more.
Unless otherwise indicated, features in this session are exclusive to users covered by the Enterprise
Client Access License for Microsoft Office SharePoint Server 2007.
Describe how to use the Business Data Catalog.
Describe how to use Forms Server and browser-based forms.
Describe Microsoft Office Excel® Services and how to use them.
Describe using Report Center sites for Business Intelligence.
2 Session 4: Business Solutions Using Office SharePoint Server 2007
Using the Business Data Catalog
The Business Data Catalog lets you integrate business data and functions from line-of-business
applications into Office SharePoint Server 2007 sites without the need to write extensive custom
code. After you configure the connection to your application, you can display and interact with
business data in multiple ways out of the box. For example, you can pull sales information from a
line-of-business application and make it available in a SharePoint site as a list or within a Web Part.
Describe the Business Data Catalog.
Describe Business Data Web Parts.
Describe how business data can be used in Office SharePoint Server 2007.
Describe how to define a Business Data Catalog application.
Describe single sign-on.
Describe the trusted subsystem authentication model.
Describe the impersonation and delegation authentication model.
Describe authorization to access business data.
What Is the Business Data Catalog?
The Business Data Catalog is a new business integration feature in Office SharePoint Server 2007.
It is a shared service that enables Office SharePoint Server 2007 to interact with business
applications and display business data in your portal without any coding. The Business Data
Catalog allows you to bring in key data from various business applications to Office SharePoint
Server 2007 sites, lists, search, and user profiles.
The Business Data Catalog is essentially a catalog of business applications that are of interest to
Office SharePoint Server 2007 users. It provides out-of-the box support for displaying data from
databases and any business application that provides Web services for retrieving data from the
applications. For example, you can display data from your SAP or Siebel application by using Web
services.
The Business Data Catalog is the key infrastructure component that most other business data
features of Office SharePoint Server 2007 rely on. Metadata authors, who have a skill set equivalent
to a Structured Query Language (SQL) developer, describe the application programming interface
(API) of business applications by using the Business Data Catalog metadata model. Administrators
register business applications in the catalog. After a business application is registered, the
application data is immediately available to you on your portal site through other Office SharePoint
Server 2007 business data features.
Other Office SharePoint Server 2007 business data features are:
Business Data Web Parts.
Business data in lists.
Business data actions.
Business data search.
Business data in user profiles.
Business Data Web Parts
Office SharePoint Server 2007 includes four out-of-the-box Business Data Web Parts. The main
purpose of these Web Parts is to enable you to display business data on your portal without writing
any code. Any type of data registered in the Business Data Catalog can be displayed.
The Business Data Web Parts support Web Part connections that make it easier to create master-
detail applications without writing any code. For example, you can display customers and their
details by using the Business Data List and Business Data Items Web Parts.
The Business Data Web Parts are:
Business Data List. Displays a list of entity instances from a business application registered in the
Business Data Catalog. For example, you can display all of the customers or orders from a
database.
Business Data Item. Displays the details of an entity instance from a business application. For
example, you can display the details of a particular customer or order from a database.
Business Data Related List. Displays a list of related entity instances from a business application.
For example, you can display all of the orders for a particular customer.
Business Data Actions. Displays a list of actions associated with an entity as defined in the
Business Data Catalog. For example, you can display all of the actions that portal users can
perform on the customer entity, such as sending an e-mail message or editing the customer’s
address.
Ways to Use Business Data
The most basic way business data can be used is displaying it with the Business Data Web Parts.
However, you can move beyond that to more advanced integration with business data. Business
data can be integrated with other features in Office SharePoint Server 2007 such as lists or user
profiles.
Some ways to use business data:
Business data in lists. You can create columns in lists or document libraries that link to business
data. A column type named Business Data supports this process. For example, in your Request for
Proposal (RFP) document library, you can add a Business Data column to add the customer who
requested the proposal. This enables users to view customer details and perform actions associated
with the customers from within the document library.
Business data actions. You can define actions for each entity in the Business Data Catalog.
Actions are implemented as links that allow you to navigate directly to a URL from the page
where the entity or Business Data column is displayed. These links can be use to send an e-mail
message, open a line-of-business application, or launch Microsoft Office InfoPath® forms.
Business data search. By using the Business Data Catalog, the search feature of Office SharePoint
Server 2007 can crawl business data to make it searchable. For example, the database used by a
business application can be searched for customer information after the database has been indexed.
Business data in user profiles. The Business Data Catalog allows you to add properties from
business applications to user profiles. This means that you can add a spouse’s name or social
security number from an SAP or a Siebel application to the user profiles.
Defining a Business Data Catalog Application
To define an application in the Business Data Catalog, you must perform two steps. The first step is
defining the metadata for the application. The second step is importing the metadata package, also
referred to as adding an application definition.
Defining Metadata
Metadata is the data about the line-of-business (LOB) application. For each LOB application,
metadata defines the entities that applications interact with and the methods available in the LOB
applications. Metadata authors are typically developers or database administrators, because they
understand the structure of the data within the LOB application. The metadata is defined by using
Extensible Markup Language (XML). The file that stores the metadata definition is sometimes
referred to as the metadata package or application definition.
Adding an Application
After the application definition is created as an XML file, it must be imported into the Business
Data Catalog. Importing an application definition is performed in the shared services administration
page. A message is displayed indicating that the import was successful. If there are errors in the
application definition, the import will not be successful.
To help troubleshoot application definition import problems:
Use incremental imports. The Business Data Catalog allows you to import metadata
incrementally. Try importing one entity at a time to identify problems more easily.
Review the log files. The Business Data Catalog logs errors in the \Program Files\
Common Files\Microsoft Shared\web server extensions\12\LOGS folder.
What Is Single Sign-On?
The single sign-on service enables scenarios where multiple Web Parts access different enterprise
applications, which each use a different type of authentication. Each Web Part can automatically
sign on to its enterprise application without prompting the user to provide credentials each time.
This feature was included in Microsoft SharePoint Portal Server 2003, and it is a part of the
standard Office SharePoint Server 2007 client access license (CAL).
Single sign-on credentials are stored in a Microsoft SQL Server™ database. All of the credentials in
the database are encrypted. When users access a Web Part that needs to access an enterprise
application, the appropriate credentials are retrieved from the database and decrypted.
Credentials for single sign-on can be managed by either individual users or an administrator. When
a group of users share a set of credentials, the credentials must be configured by an administrator.
Note The single sign-on service is also used by Microsoft BizTalk® Server.
Trusted Subsystem Authentication Model
When the Business Data Catalog connects to business data, it must provide authentication
credentials. The authentication credentials control what business data the Business Data Catalog has
access to. If you want all users to have access to the same business data, you will configure the
Business Data Catalog to use a single set of authentication credentials regardless of the user.
In the trusted subsystem model of authentication, a fixed identity is used to authenticate to the
business data source. The fixed identity is often referred to as a service account.
Reasons to use the trusted subsystem model include the following:
Offers database connection pooling.
Reduces licensing costs on the back end.
Is less complex.
The group that owns and manages the back end gives access to one account that they manage.
Connecting to Databases
Authentication choices for the trusted subsystem model when accessing databases are:
Server process account. The Business Data Catalog reverts to Self. This is the most commonly
used option and the default. This choice does not require stored credentials.
Windows credentials from Single Sign-On (Group application). The Business Data Catalog
impersonates a Microsoft Windows® user with credentials from a single sign-on group account
and performs Windows authentication.
Database credentials from Single Sign-On (Group application). The Business Data Catalog
performs database authentication with credentials from a single sign-on group account. This
choice passes the credentials as clear text. This option should be used only if communication
between the Business Data Catalog and the business data is secured by Secure Sockets Layer
(SSL) or IP Security (IPSec). This option is available only when connecting to a database.
Connecting to Web Services

When the Business Data Catalog connects to a Web service, it always negotiates the authentication
protocol. If the credentials are in the domain\user format, it first tries Windows authentication, then
Digest, and finally Basic authentication. If your system negotiates Basic authentication, it should be
secured by SSL or IPSec.
Authentication choices for the trusted subsystem model when accessing Web services are:
Windows credentials from Single Sign-On (Group application). The Business Data Catalog
impersonates a Windows user with credentials from a single sign-on group account.
Non-Windows credentials from Single Sign-On (Group application). The Business Data Catalog
performs authentication with credentials from a single sign-on group account.
Client certificates. The Business Data Catalog authenticates by using client certificates.
Impersonation and Delegation Authentication Model
In the impersonation and delegation model of authentication, the client delegates authentication to
the Business Data Catalog. The Business Data Catalog then impersonates the client and
authenticates to the business data source. If you want the business data to vary depending on the
user credentials, you configure the Business Data Catalog to impersonate the user when accessing
business data.
Reasons to use the impersonation and delegation model include the following:
Enables operating-system-level auditing at the back end
Uses per-user authorization at the back end
Connecting to Databases
Authentication choices for the impersonation and delegation model when accessing databases are:
Logged-on user. The Business Data Catalog authenticates as the end user. This choice requires
Kerberos delegation.
Windows credentials from Single Sign-On (Individual application). The Business Data Catalog
impersonates Windows users with credentials from a single sign-on individual account and
performs Windows authentication.
Database credentials from Single Sign-On (Individual application). The Business Data Catalog
performs database authentication with credentials from a single sign-on individual account. This
choice passes the credentials as clear text. This option should be used only if communication
between the Business Data Catalog and the business data is secured by SSL or IPSec.
Connecting to Web Services

When the Business Data Catalog connects to a Web service, it always negotiates the authentication
protocol. If the credentials are in the domain\user format, it first tries Windows authentication, then
Digest, and finally Basic authentication. If your system negotiates Basic authentication, it should be
secured by SSL or IPSec.
Authentication choices for the impersonation and delegation model when accessing Web services
are:
Windows credentials from Single Sign-On (Individual application). The Business Data Catalog
impersonates a Windows user with credentials from a single sign-on group account.
Non-Windows credentials from Single Sign-On (Individual application). The Business Data
Catalog performs authentication with credentials from a single sign-on group account.
Business Data Catalog Authorization
When you use the impersonation and delegation model for authentication, the access to business
data varies depending on the user that is logged on. In the trusted subsystem model for
authentication, the Business Data Catalog authenticates to the back end as a fixed identity that
always has access to the same data. However, you can control access to business data in the
Business Data Catalog by configuring authorization, even when the trusted subsystem model is
used for authentication.
Like SharePoint sites, the Business Data Catalog has a hierarchy of securable objects. Each of these
objects has an access control list that specifies which users have which rights for that object. The
Business Data Catalog limits rights assignments to individual users. You cannot group users into
roles as you can for SharePoint sites.
Rights that can be set on an application:
Manage permissions. Equivalent of the Administrator right. This right allows the user to perform
any action on the application.
Edit. Allows the user to create, update, and delete any object. In addition, the user is allowed to
change application settings.
Rights that can be set on an entity:

Manage permissions. Allows the user to set permissions on the entity.
Edit. Allows the user to change the settings for the entity, including name, appearance, and
actions. In addition, the user can edit and delete the entity.
View items. Allows the user to view the entity and execute methods.
Rights that can be set on a metadata object:

Manage permissions. Allows the user to set permissions on the metadata object.
Edit. Allows the user to change settings for the metadata object.
View items. Allows the user to view items of the metadata object.
Demonstration 1: Using the Business Data Catalog
Office SharePoint Server includes the Business Data Catalog to integrate business data into
SharePoint sites. After you configure the connection to your applications, you can display and
interact with business data from line-of-business applications. In this demonstration, you will see
how to configure an application to connect to Office SharePoint Server using the Business Data
Catalog.
Using Forms Server
Organizations have a wide variety of business processes that are based on forms. The Forms Server
included in Office SharePoint Server 2007 helps you to automate data gathering and processing by
using forms. The newest feature, browser-enabled forms, allows you to extend form reach to mobile
devices and to users outside your organization.
Describe Office InfoPath.
Describe browser-enabled forms.
Describe Design Checker.
Describe how to customize form views.
Describe how forms are connected to data sources.
Describe the form deployment process.
Describe how forms are accessed.
What Is Microsoft Office InfoPath?
In a business setting, employees are required to fill out a wide variety of forms, such as expense
reports, time cards, employee surveys, and insurance forms. If these forms are paper-based,
compiling the data or reusing it is awkward. If the forms are electronic, such as on a Web site, they
are typically difficult to implement.
Microsoft Office InfoPath 2007 is an application for designing and filling out forms. Forms can be
published to a common location on a company network such as a shared folder, a Web server, or a
forms library in Office SharePoint Server 2007. The data collected by Office InfoPath forms is
stored as XML so that it can be reused in many ways.
The benefits of using Office InfoPath for forms are:
Reusable data. XML data collected from forms can be easily repurposed and used in other
applications.
Accurate data. Office InfoPath forms can be designed to include validation checking. The forms
cannot be submitted until the data is valid.
Low overhead. Compared to paper forms, it is easy to implement form changes because you do not
need to reprint hundreds of copies.
Offline support. Office InfoPath forms can be filled out when the user is disconnected from the
network. This is an advantage over Web-based forms in some situations.
Multiple views. Forms can be configured with multiple views for different users. For example, a
bank loan application might have additional information when viewed by a loans officer rather
than the customer.
Flexible controls. In addition to standard controls, such as text boxes and list boxes, Office
InfoPath supports advanced controls such as repeating tables, which allow users to enter as many
rows as they require.
The 2007 Microsoft Office system includes an updated version of Office InfoPath with additional
features. Some of the new features in Office InfoPath 2007 are:
Additional controls, such as horizontal tables and combo boxes.
Export to Portable Document Format (PDF).
Information rights management.
Enhanced printing.
Offline access to external data.
Read-only views.
Browser-enabled forms.
Note Microsoft Office InfoPath 2007 is an excellent solution by itself for managing
organization forms and data collection. This section focuses on Microsoft Office Forms
Server 2007, which enables browser-enabled forms.
What Are Browser-Enabled Forms?
Microsoft Office InfoPath 2003 is an excellent tool for designing and collecting forms within an
organization where all form users have Office InfoPath installed on their computers. However, for
businesses wanting to interact with customers, a Web-based solution has considerable appeal.
Businesses are not always able to depend on their customers having the Office InfoPath client
installed. Office InfoPath 2003 cannot design forms suitable for Web sites.
Microsoft Office InfoPath 2007 can create browser-enabled forms. Browser-enabled forms are
deployed to a server running Office SharePoint Server 2007 and from there can be accessed and
filled out by anyone with a Web browser.
Browser-enabled forms have the following characteristics:
Support most Office InfoPath client features, such as validation.
Must be designed as browser enabled.
Must be deployed to Office SharePoint Server 2007 by using Office Forms Server.
Are compatible with Microsoft Internet Explorer® 6, Safari, Netscape, and Firefox.
Offer cross-platform support for Windows, Macintosh, Linux, UNIX.
Can be used by mobile devices with Hypertext Markup Language (HTML) support.
Replace standard toolbars and menus with server toolbars controlled by the form designer.
What Is Design Checker?
When designing a form, the form designer is usually aware of the target users and environment for
the form. If the form will be used only by the full Office InfoPath 2007 client, all features can be
used. If the form will be used as a browser-enabled form, some features are not supported,
including the use of scripting languages, roles, custom task panes, filters, and some controls.
Design Checker is a task pane within Office InfoPath 2007 that reports compatibility issues with
browser-enabled forms and Office InfoPath 2003. Reports are issued for the following categories:
Run-time compatibility. Reports rich client-only features in a browser-enabled form.
Backward compatibility. Reports features not compatible with Office InfoPath 2003.
Import. Contains issued reported by a form template importer.
Template Parts. Lists any Template Parts that can be updated. Template Parts are reusable parts of
forms that include controls and logic but no code. Updating a Template Part updates all forms that
use that Template Part, making it easier to manage forms.
Binding. Reports invalid or incompatible control binding to data.
To help prevent run-time compatibility problems, Office InfoPath 2007 lets you select whether a
form is targeted at Web browsers. If the form is targeted at Web browsers, the dialog boxes for each
feature added to the form will indicate that the feature is not supported for the Web browsers.
Customizing Form Views
Office InfoPath 2003 was already capable of creating multiple form views. Form views are
variations of a form in which the formatting might be different or some controls hidden. Each view
can have a different layout or even display different controls. Each view can also be restricted to
certain users.
Office InfoPath 2007 adds the ability to create Web-specific views for a form. In this case, the
version of the form displayed through a Web browser would vary from the version displayed in the
Office InfoPath 2007 client.
Having multiple views of a form enables:
Using Office InfoPath 2007 client-only views for features supported only by the full Office
InfoPath client.
Optimizing form views for mobile devices.
Displaying different versions of the form to users with different needs.
Multiple versions of a form would be useful when submitting information for a credit check. The
customer would fill out all of the required personal information in a Web browser. Then an
employee performing the credit check could use the Office InfoPath client, with a different view
offering additional controls, to add comments about the customer indicating whether the application
is approved and why.
Form Data Connectivity
Office InfoPath 2007 introduces a new way of managing data connectivity for forms. Office
InfoPath 2003 embedded connection information in forms. Office InfoPath 2007 uses connection
information as an external file in a Data Connection Library (DCL).
A DCL is a new type of document library that allows applications such as Office InfoPath or Excel
Services to specify data connection settings by using external files. The data connection settings are
stored in Universal Data Connection (UDC) files. UDC files are XML files that specify data
sources and destinations.
Supported data sources are:
An XML Web service.
A SharePoint list or library.
A Microsoft SQL Server or Microsoft Office Access database.
An XML file or other XML source, such as a Microsoft ASP.NET page.
Supported data destinations are:

An XML Web service.
A SharePoint form library.
A Hypertext Transfer Protocol (HTTP) post operation.
Benefits
Storing connection information outside forms and in a Data Connection Library has the following
benefits:
Simplified reconfiguration. Data connection settings can be modified independently of the
solutions that use them. If several forms use the same UDC, the UDC needs to be modified only
once and all forms are affected.
Simplified migration. Test and production servers can specify different locations for data access,
and a solution will automatically use the server-specific location when published to that server.
Flexible authentication. Using Microsoft Office system single sign-on, you can specify alternative
authentication credentials to be used by the server when processing a form for the browser.
Cross-domain security. The DCL serves as a safe list for data connections. For forms that are not
published with full-trust, only connections specified by using the DCL can retrieve data from
outside the form.
The Form Deployment Process
Office InfoPath forms can be deployed to Office SharePoint Server 2007 either by administrators or
by form designers. The process used and form capabilities vary for each situation.
Form designers can deploy a form to a SharePoint document library directly from Office
InfoPath 2007. However, this process is available only if the form is either not browser enabled or
a codeless browser-enabled form. Browser-enabled forms that have additional code cannot be
deployed by form designers directly because extra steps are required to make them functional on
the server.
Administrator Deployment
To deploy a form template to users, administrators must verify the form template, upload it, and
activate it. The form template can be uploaded by using the command prompt window or by using
Office SharePoint Server 2007.
Form template verification checks that the form template is acceptable to be uploaded to the server.
This is a manual step that must be performed. Command-line verification must be performed on the
2007 Microsoft Office system Forms Server where the form template is being deployed.
After a form template is uploaded to the server, it is not yet available to users. The form must be
activated to make it available to users.
In a production environment, updating a form template requires more than simply replacing the old
form template with the new form template. It is possible that users will have active sessions of the
form open. You will want to control the upgrade process to allow active sessions to complete.
File Formats
A form template has the .xsn file extension and is used natively by Office InfoPath 2007. However,
this format cannot be used directly by Web browsers. To support Web browsers, the form templates
are converted to dynamic Microsoft ASP.NET web pages (.aspx), cascading style sheets (.css), and
JavaScript (.js) files. These files all work together to create browser-enabled forms. Conversion of
form templates is accomplished when forms are activated.
Accessing Forms
When users access forms from a SharePoint library, the default configuration opens the form in
Office InfoPath 2007 if it is installed on the client. Only if Office InfoPath 2007 is not installed is
the browser-enabled version of the form used. However, you can modify this behavior by disabling
the Prefer client setting in the SharePoint library holding the forms.
Customizing Form Access

By default, a browser-enabled form is loaded in the existing browser window. You can create a
customized link to a browser-enabled form that loads the form in a new browser window. You can
also embed a form in a control inside an existing Web page on a SharePoint site.
Possible reasons to customize form access:
Achieve a custom user experience.
Place other controls around the form.
Provide additional functionality.
Dynamically load forms or change data in the form.
Show a customized message after the form has been submitted.
Demonstration 2: Using Forms
Collecting and processing information from paper-based forms is difficult and time consuming.
Forms Server lets you collect form information electronically. This makes data collection faster,
easier, and more accurate. Browser-based forms extend the reach of your electronic data collection
beyond the walls of your organization and out onto the Internet. In this demonstration, you will see
how to create, deploy, and access Web-enabled forms.
Using Excel Services
Office SharePoint Server 2007 includes Excel Services for providing from within a server
environment a number of features normally found only in desktop spreadsheet applications. Excel
Services adds the ability to make use of spreadsheet calculations and presentations through a Web
browser or Web service. This means that you can make the reports and calculation models stored in
Office Excel spreadsheets available through the Web or that custom applications can use Office
Excel calculations instead of building the model into the application.
Describe Excel Services.
Describe Excel Web Services.
Describe what Excel Services is not.
Describe the architecture of Excel Services.
Describe a published spreadsheet.
Describe the Excel Web Access Web Part.
What Is Excel Services?
Excel Services is a shared service that is part of Office SharePoint Server 2007. Excel Services
enable you to view and interact with Office Excel 2007 spreadsheets in a browser, control
spreadsheet access and viewing, and integrate with the portal reporting features in Office
SharePoint Server 2007. Excel Services supports Web browsers, Office Excel 2007, and custom
applications as clients.
Web Browsers
When using a Web browser as a client, Excel Services offers the following capabilities:
Use server-side spreadsheet calculation to offload calculations.
View and interact with Office Excel spreadsheets on the server.
Limit user access to cells and formulas.
Allow remote access to a spreadsheet.
Perform data visualization by creating PivotTable® and PivotChart® dynamic views.
Integrate with Report Center to create Business Intelligence portals.
Office Excel 2007

When using Office Excel 2007 as a client, Excel Services offers the following capabilities:
Maintain one copy of the spreadsheet in a secure central place.
Secure and protect spreadsheet models and back-end data.
Create snapshots of a spreadsheet.
Custom Applications
When using custom applications as a client, Excel Services offers the following capability:
Access Office Excel functionality by using Excel Web Services.
What Is Excel Web Services?
Excel Web Services is a Web service that can be accessed by custom applications. This reduces
work for the programmer and increases maintainability. Programming work is simplified because
advanced calculation functionality that already exists in Office Excel spreadsheets does not need to
be replicated as part of the application development process. Maintainability is increased because
the spreadsheet can be maintained by a nonprogrammer who is a subject expert without modifying
the application.
Server-Side Office Excel Calculation

For server-side Office Excel calculation, a custom application uses an Office Excel model as part of
its logic. The custom application calls Excel Web Services each time it needs to perform a
calculation. For example, an Office Excel spreadsheet could store the model for evaluating credit
ratings of loan applicants. Each time an applicant is evaluated, the custom application passes
criteria to Office Excel for calculation of the credit rating.
To perform server-side calculation, Excel Web Services does the following:
Loads the specified Office Excel spreadsheet
Receives inputs from the custom application
Processes the spreadsheet (refreshes data and performs calculations)
Sends the results to the custom application
Server-Side Spreadsheet Automation

Server-side spreadsheet automation is used to track the status of a spreadsheet over time. In this
case, the spreadsheet is typically pulling data from another source and being used to display status.
For example, a spreadsheet could pull inventory and order information from a database to display
current inventory as compared to upcoming orders.
To perform server-side automation, Excel Web Services does the following:
Loads the specified Office Excel spreadsheet
Receives inputs from the custom application
Processes the spreadsheet (refreshes data and performs calculations)
Saves the resulting spreadsheet as a live spreadsheet or a snapshot
What Excel Services Is Not
Due to its name, many users envision Excel Services as simply a server-side version of Office
Excel. It is important to define what Excel Services does not do.
Excel Services does not:
Allow spreadsheet authoring in the browser. The Excel Web Part is designed to display data and
perform calculations, not create new spreadsheets.
Solve multi-user authoring. When multiple users access a spreadsheet through Excel Services,
each user has his or her own environment. Multiple users cannot collaborate on a spreadsheet at
the same time.
Support all Office Excel spreadsheets. Some Office Excel 2007 features are not supported when
viewing spreadsheets in a browser.
Excel Services Architecture
In a Web farm topology, Excel Services has components that run on the Web front end and an
application server. These components are separable to enhance scalability. Both the Web front end
servers and application servers can be load balanced.
Web Front End

The Web front end of a Web farm topology is responsible for displaying the SharePoint user
interface from which clients are able to open published spreadsheets. For browser-based clients, the
Web front end server is responsible for rendering the HTML that is displayed when accessing a
published spreadsheet. Custom applications also contact Web front end servers to access Excel
Web Services.
The components on the Web front-end servers are:
Excel Web Access. Renders the spreadsheets as HTML.
Excel Web Services. Provides access to Office Excel functions for custom applications.
Excel Calculation Services Proxy. Provides connectivity to communicate with the application
server.
Application Server
The application server is responsible for loading spreadsheets from the SharePoint library,
performing spreadsheet calculations, and refreshing data in the spreadsheet. To access a
spreadsheet, the application server must be in a data source that is configured as trusted by Excel
Services. To enhance performance, file and query caches are implemented on the application
server.
The components on the application server are:
Excel Calculation Services Interface. Provides a way for the Web front end to communicate with
the application server.
Excel Calculation Services. Loads the spreadsheet, performs calculations, and refreshes data.
What Is a Published Spreadsheet?
A published spreadsheet is an Office Excel 2007 spreadsheet that has been copied to an Office
SharePoint Server 2007 document library and is available through Excel Services. During the
publishing process, you can control which parts of the spreadsheet are shown on the server and the
parameters that are allowed to be modified.
To access a spreadsheet through Excel Services, you must configure the spreadsheet storage
location as an Excel Services Trusted Location. Excel Services Trusted Locations are configured in
Shared Services administration.
Show tab
During publishing, the Show tab specifies which parts of the spreadsheet will be visible from the
server. The options for visibility are:
The entire workbook.
Specific workbook sheets.
Named ranges in the workbook.
Parameters
Parameters allow you to specify cells that are editable when viewing the workbook on a server
running Office SharePoint Server 2007. Each parameter is defined as a cell of the spreadsheet. To
have the option of including a cell, you must give the cell a name during editing.
What Is the Excel Web Access Web Part?
The Excel Web Access Web Part allows you to embed Office Excel spreadsheets in a SharePoint
page. Like other Web Parts, you can modify the general display settings for the Web part, in
addition to settings specific to this Web Part. Two configuration areas of particular concern are the
workbook configuration and interactivity.
The workbook area lets you configure which Office Excel spreadsheet is going to be displayed.
You specify which spreadsheet to display by entering a URL to the spreadsheet. In addition, you
can specify which part of the spreadsheet will be displayed by using a named range or object.
Finally, you can specify how many rows and columns to display.
The interactivity area lets you control how users can work with the spreadsheet. Some of the
functions that can be enabled and disabled are:
Allow export to Office Excel 2007.
Allow interactivity.
Allow manual or periodic refresh.
Allow calculation.
Allow parameter modification.
Allow sorting operations.
Allow filtering operations.
Allow PivotTable operations.
Note Like all Web Parts, the Excel Web Access Web Part can be targeted to a particular
audience. In this way, you could give different audiences a different view of the same
spreadsheet.
Demonstration 3: Publishing an Excel Spreadsheet
Excel Services allows you to perform spreadsheet calculations on a server and interact with
spreadsheets through a Web browser. This lets users remotely access spreadsheets from anywhere
they have Internet access. In addition, you can secure spreadsheets used by Office Excel 2007
clients. In this demonstration, you will see how to publish a spreadsheet and view that spreadsheet
in a Web browser.
Creating Report Center Sites
Report Center is a Business Intelligence hub in Office SharePoint Server 2007. In Report Center,
you can build reports that display the status of key performance indicators (KPIs) for your
organization. These reports are automatically tracked over time. In addition, you can create
dashboards that show a summary view of key performance indicators and business health for your
organization. Report Center can also be used as a single point of access to reports produced through
a variety of sources, notably Excel Services–published spreadsheets and Microsoft SQL Server
Reporting Services.
After you complete this section, you will be able to:
Describe Report Center.
Describe the Reports Library.
Describe key performance indicators.
Describe dashboards.
Describe Web Part filtering.
What Is Report Center?
Report Center is a Business Intelligence portal that works out of the box. Report Center makes it
easy to discover and use Office SharePoint Server 2007 Business Intelligence features because
many of them are centrally located in Report Center. The default implementation gives you a
template that can be customized to create a Business Intelligence portal that meets your exact
needs.
A Business Intelligence portal is not only for generating reports. Report Center also brings together
content management and collaboration.
Like all SharePoint sites, the content in Report Center can be targeted for specific audiences. In this
way, you can create a Business Intelligence portal that gives users exactly the information they
need.
Key components of Report Center include the following:
Reports Library
Reports
Key performance indicators
Dashboards
What Is the Reports Library?
There are unique challenges for storing reports. Report histories are important because you often
want to compare past performance with current performance. The Reports Library is a document
library in Report Center that has enhanced support for storing and viewing reports.
To track performance over time, the Reports Library keeps each version of a file in the library. All
versions of a file are viewable and can be retrieved. However, the default view for the library filters
out historical versions. This process does not use the versioning feature that is used for
collaboration.
The content types in the Reports Library have features that make them ideally suited to storing and
viewing reports. The three content types are:
KPI List Page. The most important component of a key performance indicator (KPI) page is a KPI
list. A KPI list is designed to hold a list of KPI values, update the values, and display the status of
KPIs. By viewing a KPI list page you get a snapshot of KPIs and can address any issues that are a
concern.
Report. A report is similar to a KPI list page, because both have a KPI list. However, a report has
additional properties associated with it, such as parent ID, owner, category, and status.
Multi-Report Summary Page. A multi-report summary page does not include KPI lists or
additional properties. It does include the Excel Services Web Part to pull summary data from
Office Excel spreadsheets. In addition, it includes a filter that can be used to limit the content in
Web Parts. For example, a Web Part could be filtered to show sales data from only one region.
What Are Key Performance Indicators?
Key performance indicators (KPIs) are an objective and quantifiable measurement of organizational
success. Businesses use KPIs to see how their organization is progressing toward its goals. Each
organization has its own set of KPIs that vary depending on the goals. For example, a retailer might
consider average markup to be a KPI, while a shipping company might consider the percentage of
on-time deliveries to be a KPI. KPI information is typically pulled from LOB applications.
Office SharePoint Server 2007 allows information workers to create and display KPIs without
intervention from IT workers or developers. There is no coding involved. KPIs are created in KPI
lists that are found in Report Center reports and KPI list pages. When a KPI is created, you can
specify the values associated with a particular status. For example, you could indicate that status is
good if on-time deliveries are above 99.8 percent and display a warning below that level.
KPIs can be pulled from the following sources:
Data in SharePoint. This is a SharePoint list, but it could be a list built with data from the
Business Data Connector.
Data in Office Excel. This uses data in an Office Excel spreadsheet.
Data in Analysis Services. This allows you to connect to a data source defined in the Data
Connection Library. The connection is defined by an Office Data Connection (.odc) file.
Manually entered information. This allows you to manually enter a value for a KPI when it is not
practical to automatically pull it in from another source.
What Are Dashboards?
A dashboard is a meaningful way to display information about KPIs. Instead of having only lists of
KPIs and their values, a dashboard gives a graphical display of KPIs and their status. In some cases,
a dashboard has indicators for each KPI that look like a car tachometer with good, warning, and
problem indicators. However, a dashboard does not have to look so literally like a car dashboard.
Some of the things a dashboard does for you:
Displays aggregate data from Office Excel workbooks and reports
Offers the ability to drill down to more detailed information
Displays only relevant information to the user
Annotates data with additional information
Office SharePoint Server 2007 has features that allow you to build effective dashboards. For
example, Web Part filtering ensures that only relevant data is displayed to your users. In addition,
you can summarize KPI lists by having one KPI list read the status of other KPI lists.
What Is Web Part Filtering?
Web Part filtering allows you to limit the contents of a Web Part based on a defined set of filter
values. You can pull the filter values from a number of different sources and either let users select
the filter or perform filtering automatically. Ultimately, Web Part filtering is used to make data
relevant to the user.
Uses for Web Part filtering:
Automatically show only your customers in a list.
Filter dashboard data to show only your geographic region.
Sources for filter values:

User entry
Authored list
SharePoint list
SQL Server Analysis Services
Business Data Catalog
SharePoint profile
Query string
Not all Office SharePoint Server 2007 Web Parts can be filtered. Only the following Web Parts can
be connected to a filter:
Excel Web Access
KPI List
Business Data Item
Business Data List
SharePoint List View
Demonstration 4: Using Report Center
Office SharePoint Server 2007 uses Report Center as a hub for Business Intelligence. You can build
reports that display the status of key performance indicators. You can also filter Web Parts to vary
the data based on a wide variety of criteria such as regional statistics. In this demonstration, you
will see how to create a report and how to filter a Web Part.
Session Summary
This session covered the portal and search capabilities in Office SharePoint Server 2007. The
Using the Business Data Catalog. This topic explained some of the tasks involved in configuring
the Business Data Catalog. The areas discussed were an overview of the Business Data Catalog,
Business Data Web Parts, ways to use business data, and defining applications. In addition, trusted
subsystem authentication, impersonation and delegation authentication, and authorization to
business data were examined. The Business Data Catalog lets you integrate business data into
SharePoint sites.
Using Forms Server. This topic discussed some of the features in Office SharePoint Server 2007
for managing forms. Specifically, Office InfoPath, browser-enabled forms, Design Checker,
customizing form views, form data connectivity, the form deployment process, and accessing
forms were covered. Office SharePoint Server 2007 allows you to implement browser-based forms
to extend the reach of your electronic forms outside your organization and onto the Internet.
Using Excel Services. This topic explored the features available when using Excel Services.
General overviews of Excel Services and Excel Web Services were presented. In addition, the
Excel Services architecture, published spreadsheets, and the Excel Web Access Web Part were
discussed. Excel Services lets you make calculation models stored in Office Excel spreadsheets
available through the Web or to custom applications.
Creating Report Center Sites. This topic explained some of the Business Intelligence features
available in Report Center. The Reports Library, key performance indicators, dashboards, and
Web Part filtering were discussed. Report Center is a Business Intelligence hub in Office
Next Steps
Download and evaluate the Office SharePoint Server 2007 Beta.

Clinic Evaluation
Your evaluation of this clinic will help Microsoft understand the quality of your learning
experience.
Please work with your training provider to access the clinic evaluation form.
Microsoft will keep your answers to this survey private and confidential and will use your
responses to improve your future learning experience. Your open and honest feedback is valuable
and appreciated.

Ms Press - Moc3370A First Look Getting Started With Microsoft Office Sharepoint Server 2007 (2008)

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Ms Press - Moc3370A First Look Getting Started With Microsoft Office Sharepoint Server 2007 (2008)

Uploaded by

Copyright:

Available Formats

3370A: First Look: Getting

Started with Microsoft Office

SharePoint Server 2007

© 2006 Microsoft Corporation. All rights reserved.

All other trademarks are property of their respective owners.

3. DESCRIPTION OF OTHER RIGHTS AND LICENSE LIMITATIONS

3.1 Use of Documentation and Printed Training Materials.

Si vous avez acquis votre Contenu Sous Licence Microsoft au CANADA :

Session 4: Business Solutions Using Office SharePoint Server 2007

About This Clinic

Bold Represents commands, command options, and syntax that must

THIS PAGE INTENTIONALLY LEFT BLANK

© 2006 Microsoft Corporation. All rights reserved.

All other trademarks are property of their respective owners.

The following materials are included with your kit:

Additional recommended learning products

Microsoft Learning information

Microsoft Learning Product Types

Microsoft Certification Program

Acquiring the skills tested by an MCP exam

THIS PAGE INTENTIONALLY LEFT BLANK

© 2006 Microsoft Corporation. All rights reserved.

All other trademarks are property of their respective owners.

Session 1: Office SharePoint Server 2007 Functional and

Design Goals Behind Office SharePoint Server 2007

The New Workplace: What Are the Challenges?

How Organizations Respond to the Challenges

Why Do the Solutions Fail?

2007 Office System Goals

Office SharePoint Server 2007 Features

Benefits of Office SharePoint Server 2007

What Are the Collaboration Features?

What Is Content Management?

Web Content Management

What Is Business Process Management?

What Is Business Intelligence?

Demonstration 1: Office SharePoint Server 2007 Features

Office SharePoint Server 2007 Software Components

Operating System and Database Services

Operating System Services

Windows SharePoint Services 3.0 Services

Office SharePoint Server 2007 Services

Office SharePoint Server 2007 Administrative

Administrative Architecture Overview

What Is Central Administration?

Central administration is typically performed by IT administrators. The central administration tasks

What Is a Shared Services Provider?

Using Multiple SSPs

What Are Site Settings?

Demonstration 2: Office SharePoint Server 2007 Administrative

Office SharePoint Server 2007 Security Requirements

The shared services objects are:

The site objects are:

Security Best Practices

Demonstration 3: Office SharePoint Server 2007 Security Overview

Office SharePoint Server 2007 Physical Architecture

Selecting a Deployment Topology

Web Farm Deployments

Web Front-End Servers

Web Farm Examples

Inter-Farm Shared Services

What Is the Recommended Hardware for Installation?

Web Farm Deployment

Demonstration 4: Installing a Single-Server Deployment