34,79 €
Collaboration and content management are the major business needs of every organization in this increasingly global and connected environment. Microsoft SharePoint is a solution to these needs that offers a software platform that facilitates collaboration and provides content management features for the effective implementation of business processes. With a vast amount of functionality available with SharePoint, it is easy to get confused in carrying out administrative tasks.
Microsoft SharePoint 2010 Administration Cookbook starts off by demonstrating the various upgrading and post-upgrading tasks to be performed in SharePoint 2010. Next come recipes for managing SharePoint service-level applications and for monitoring the SharePoint environment. The book introduces one of the best new tools that should be in your arsenal, PowerShell, and the commands you will need to script your tasks with Powershell.
Collaboration and content management are the most important features of SharePoint and this book contains many recipes that focus on improving them. Enterprise monitoring and reporting are also covered in detail so that you can ensure that your SharePoint implementation is up and running all the time. You will find recipes to manage and customize SharePoint Search.
When you are half way through the book, you will explore more advanced and interesting topics such as customizing and securing the SharePoint environment. You will learn to extend SharePoint to include features similar to social networking sites such as Facebook and Twitter. Lastly, the book covers backup and recovery solutions for SharePoint so that you can ensure that your system is protected from data loss and virus attacks.
Das E-Book können Sie in Legimi-Apps oder einer beliebigen App lesen, die das folgende Format unterstützen:
Seitenzahl: 312
Veröffentlichungsjahr: 2011
Copyright © 2011 Packt Publishing
All rights reserved. No part of this book may be reproduced, stored in a retrieval system, or transmitted in any form or by any means, without the prior written permission of the publisher, except in the case of brief quotations embedded in critical articles or reviews.
Every effort has been made in the preparation of this book to ensure the accuracy of the information presented. However, the information contained in this book is sold without warranty, either express or implied. Neither the author, nor Packt Publishing, and its dealers and distributors will be held liable for any damages caused or alleged to be caused directly or indirectly by this book.
Packt Publishing has endeavored to provide trademark information about all of the companies and products mentioned in this book by the appropriate use of capitals. However, Packt Publishing cannot guarantee the accuracy of this information.
First published: January 2011
Production Reference: 1170111
Published by Packt Publishing Ltd.
32 Lincoln Road
Olton
Birmingham, B27 6PA, UK.
ISBN 978-1-849681-08-7
www.packtpub.com
Cover Image by David Guettirrez ( <[email protected]> )
Author
Peter Serzo
Reviewers
Marius Constantinescu
Michael Nemtsev
Ivan Wilson
Development Editor
Wilson D'souza
Technical Editor
Gaurav Datar
Indexer
Monica Ajmera Mehta
Editorial Team Leader
Gagandeep Singh
Project Team Leader
Priya Mukherj
Project Coordinator
Sneha Harkut
Proofreaders
Stephen Swaney
Kelly Hutchison
Graphics
Geetanjali Sawant
Production Coordinator
Alwin Roy
Cover Work
Alwin Roy
Peter Serzo is an English major from Kent State, who started his technical career with EDS after finishing college. After working for 20 years as a consultant in organizations of all sizes, he is now a national speaker on SharePoint. His next challenge is to bring SharePoint to children and teach them. He has been working with SharePoint since 2003, in companies such as Microsoft, Ford, and ADP, along with many others throughout the United States.
Currently, Peter is working as a Senior SharePoint Architect for High Monkey Consulting. The name "High Monkey" refers to an old Jamaican proverb that means the higher up you go, the more responsible you must be. High Monkey takes pride in its accountability and excellence toward work, with regard to the client's needs.
I dedicate this book to my wife Stacy, for her patience, love, and support as I took much of our time to write. She is my rock. I also thank my children—Philip, Zachary, and Stefan—for their support and belief in me. I hope this book inspires them to exceed in their lives (Think Avisha!). Finally, I want to thank my Mom, for giving me a love for the written word, and my Dad, for giving me a love and appreciation for all things technical. A perfect balance. All of you are my source of inspiration and will always have my love.
With experience in commercial software development dating back to the late nineties, Marius Constantinescu currently works as the Lead Architect on Microsoft Solutions, for a professional IT services company based in Geneva, Switzerland.
Having worked with .NET from its very early beta stages, as well as with the SharePoint platform since 2003, Marius has played a major part in developing useful tools for large international organizations and private companies, providing consulting expertise on architectures based on .NET, SharePoint, and other related technologies.
His passion for technology has made him recipient of various prestigious awards such as "Technology Scout for 2005" and "Siemens Certified Architect" while working as the Microsoft Solution architect for Siemens. Currently his focus has shifted again to latest .NET technologies such as Silverlight, SharePoint Server, and Cloud Computing.
Marius has been working as a Technical Reviewer of .NET technologies for almost a decade, with multiple publishing houses and prestigious authors around. He has quite a few credits added to his name, including the two best sellers on ASP.NET 2.0, written by the popular author Dino Esposito, back in 2005.
Marius is also a frequent speaker in management briefings and technology conferences, and maintains a blog, available at http://nettitude.spaces.live.com.
I'd like to thank my fiancé, Réka K., for her immense patience and support thorough the long late nights I had to spend away, and all the weekends traded in favor of my other passion, .NET technologies.
Michael Nemtsev is a Microsoft Most Valued Professional (MVP) in SharePoint Server and has held this status since year 2009. Previously, he had held the same award in .NET/C# area since year 2005. Michael has expertise in the Enterprise Integration Platform and Collaborations areas, and is currently working as a Senior Information Management Consultant at Gen-I in Sydney, Australia.
Ivan Wilson has been working as a consultant on Microsoft technologies for the last 15 years and has been focusing on the SharePoint platform for the last seven years. He has five Microsoft Most Valued Professional (MVP) awards to his credit—winning continuously since 2006 until 2010. Originally from Ireland, he moved to Sydney, Australia in 1999. He now co-runs SharePoint Gurus, a consultancy business focused on helping organizations collaborate in a better way.
You might want to visit www.PacktPub.com for support files and downloads related to your book.
Did you know that Packt offers eBook versions of every book published, with PDF and ePub files available? You can upgrade to the eBook version at www.PacktPub.com and as a print book customer, you are entitled to a discount on the eBook copy. Get in touch with us at <[email protected]> for more details.
At www.PacktPub.com, you can also read a collection of free technical articles, sign up for a range of free newsletters and receive exclusive discounts and offers on Packt books and eBooks.
http://PacktLib.PacktPub.com
Do you need instant solutions to your IT questions? PacktLib is Packt's online digital book library. Here, you can access, read and search across Packt's entire library of books.
If you have an account with Packt at www.PacktPub.com, you can use this to access PacktLib today and view nine entirely free books. Simply use your login credentials for immediate access.
Get notified! Find out when new books are published by following @PacktEnterprise on Twitter, or the Packt Enterprise Facebook page.
SharePoint 2010 enables businesses to set up collaboration with, and for, many types of entities (employees, vendors, customers, and so on) while integrating disparate technologies. It has proved so valuable a tool at many organizations that its growth has led it to become a mission-critical application. As SharePoint has grown through each version, it has assimilated several technologies. It now encompasses technologies such as content management, Microsoft Access, and Visio to name a few.
The administrator's challenge with SharePoint 2010 is recognizing where to perform vital tasks in a product that is as vast as it is deep. The recipes here represent common tasks that an administrator must be knowledgeable about. These are foundational tasks that, in most cases, can be combined and built upon. Features are titled so that even if the task is performed sporadically, you can look at the title and use the book as a reference guide. It is my hope that the book becomes a resource that is referenced often.
Chapter 1, Upgrading and Configuring SharePoint 2010, contains recipes that deal with configuring and getting SharePoint up and going. These recipes not only cover upgrading from a previous version but also contain explanations on how to create new web applications and associated components.
Chapter 2, Service Applications, covers recipes involving service applications, which is a new concept to SharePoint 2010. These recipes cover the main service applications such as managed metadata and Excel. It also covers the components of a service application, such as custom groups, that can be configured.
Chapter 3, Farm Governance, covers different items that relate to managing SharePoint 2010. These recipes will be implemented based on guidance from your organization. The recipes support the rules that govern your organization, such as how to restrict web parts or setting up a managed account.
Chapter 4, Site Administration, contains key recipes for managing the site-level components. Error pages, content types, retention policies, and records management are some of the topics that are covered.
Chapter 5, Monitoring and Reporting, covers recipes involving the different tools in SharePoint 2010 that assist the administrator in managing SharePoint. These tools are critical to knowing how the SharePoint 2010 installation operates. The recipes show how to manage the tools.
Chapter 6, Search, covers the core components within SharePoint 2010. The topics here range from how to scale out the Search components to customizing search. Search is a broad foundational topic in SharePoint and the recipes here provide a granular view into what an administrator can do.
Chapter 7, Security Administration: Users and Groups, contains recipes related to user access. The list of topics range from site collection-level access to site-level access.
Chapter 8, Content Management, is about different aspects of SharePoint 2010. These recipes range from term sets, setting up a content type hub, routing documents, to managing external content types.
Chapter 9, Social Architecture, is a new topic for SharePoint 2010. The features covered in the recipes have to do with setting up a tag cloud managing the social features for a user. The recipes give the administrator a broad range of where and how the social environment can be managed in SharePoint.
Chapter 10, Backup and Restore, is a topic that should be familiar to all administrators. The recipes here cover everything from the recycle bin to a farm backup and restore.
Chapter 11, Performance Monitoring, covers some lesser-known ways to monitor SharePoint. The recipes here introduce tools, some of which are not native to SharePoint, but the functionalities they provide assist the administrator without requiring a financial investment. The recipes show how to use these readily available tools.
In order to perform the recipes within this book, a functional installation of SharePoint 2010 Standard is required. SharePoint 2010 is resource intensive on hardware. The recipes in this book have been tested using a laptop with 8 gigabytes of RAM and a 500 gigabyte hard drive. The environment includes Windows 2008 R2, with SharePoint 2010 Enterprise, using SQL Server 2008 R2 Standard. The environment has been created using a native boot virtual hard disk (VHD), which is supported by Windows Server 2008 R2.
The configuration that you choose will most likely use some type of virtualization software such as VMWare or Hyper-V. Also you can choose the native boot solution as I have done while writing this book.
The following are the core software components you will need to perform the recipes in this book:
This book does not cover installation and configuration. In order to perform these tasks, refer to an online resource such as Microsoft's Technet: http://technet.microsoft.com/en-us/sharepoint.
If you are a SharePoint Administrator looking for solutions to the many problems faced while managing SharePoint, then this book is for you. This book is written for SharePoint administrators, who are either already working on SharePoint, or have recently started working and are eager to learn more about SharePoint administration. You need to have some basic knowledge of SharePoint in order to follow the recipes in this book.
In this book, you will find a number of styles of text that distinguish between different kinds of information. Here are some examples of these styles, and an explanation of their meaning.
Code words in text are shown as follows: "Create a site collection called sites\ContentTypeHub, based on the Publishing Site Template, and make yourself the owner."
A block of code is set as follows:
Any command-line input or output is written as follows:
New terms and important words are shown in bold. Words that you see on the screen, in menus or dialog boxes for example, appear in the text like this: "Under the Site Actions section, click Manage site features."
Warnings or important notes appear in a box like this.
Tips and tricks appear like this.
Feedback from our readers is always welcome. Let us know what you think about this book—what you liked or may have disliked. Reader feedback is important for us to develop titles that you really get the most out of.
To send us general feedback, simply send an e-mail to <[email protected]>, and mention the book title via the subject of your message.
If there is a book that you need and would like to see us publish, please send us a note in the SUGGEST A TITLE form on www.packtpub.com or e-mail <[email protected]>.
If there is a topic that you have expertise in and you are interested in either writing or contributing to a book, see our author guide on www.packtpub.com/authors.
Now that you are the proud owner of a Packt book, we have a number of things to help you to get the most from your purchase.
Although we have taken every care to ensure the accuracy of our content, mistakes do happen. If you find a mistake in one of our books—maybe a mistake in the text or the code—we would be grateful if you would report this to us. By doing so, you can save other readers from frustration and help us improve subsequent versions of this book. If you find any errata, please report them by visiting http://www.packtpub.com/support, selecting your book, clicking on the errata submission form link, and entering the details of your errata. Once your errata are verified, your submission will be accepted and the errata will be uploaded on our website, or added to any list of existing errata, under the Errata section of that title. Any existing errata can be viewed by selecting your title from http://www.packtpub.com/support.
Piracy of copyright material on the Internet is an ongoing problem across all media. At Packt, we take the protection of our copyright and licenses very seriously. If you come across any illegal copies of our works, in any form, on the Internet, please provide us with the location address or website name immediately so that we can pursue a remedy.
Please contact us at <[email protected]> with a link to the suspected pirated material.
We appreciate your help in protecting our authors, and our ability to bring you valuable content.
You can contact us at <[email protected]> if you are having a problem with any aspect of the book, and we will do our best to address it.
In this chapter, we will cover:
SharePoint 2010 requires 64-bit architecture on the servers, with a minimum of 8 gigabytes of RAM. The result of this requirement is that there will be installations upgrading their 32-bit architecture and then upgrading/migrating their sites.
Upgrading SharePoint 2010 is optimally a one time job. In reality, this is not always the case as there may be business reasons one web application is upgraded and another is left in MOSS 2007. This could be due to software integration with SharePoint, components that are not ready for SharePoint 2010, or a segment of users that need time before upgrading to SharePoint 2007.
SharePoint 2010 has been architected with the capability to migrate sites methodically. With this in mind, every recipe in this chapter approaches the upgrade from the viewpoint of iterative tasks after an upgrade. This means that a majority of the tasks can be performed several times against different web applications.
Every recipe here (except the first one) should be performed and understood by the administrator of the SharePoint 2010 farm. There are many new items in SharePoint 2010 that will become common tasks; some more than others depending on the size of your environment.
One of the best new tools that should be in your arsenal is PowerShell. The recipes in this section outline the commands you will need. However, after reviewing and trying these recipes, look at scripting your tasks with PowerShell. This will enable you to become a more effective and proactive IT Professional.
In order to upgrade to SharePoint 2010 from your current Windows SharePoint Services 3.0 (WSS) or Microsoft Office SharePoint Server 2007 (MOSS) implementation, you need to plan your new infrastructure carefully. When thinking about planning your new architecture, take into account the logical design and the physical design of the new SharePoint 2010 installation.
Issues need to be identified, resolved, and requirements need to be met. Issues can range from addressing 32-bit architecture to custom site definitions. These items need to be resolved before being able to update to SharePoint 2010.
Begin your planning by identifying and documenting your current infrastructure. Review the hardware, WSS/MOSS configurations, and potential customizations.
A typical farm installation will have multiple servers with diverse roles: web front ends, applications servers, database servers, among others. Extrapolating from there, an installation can have multiple content databases, web applications, site collections, Shared Service Providers, to name a few of the components.
In order to manage your infrastructure and plan for the SharePoint 2010 upgrade, Microsoft has provided organizations with a tool called preupgradecheck. This tool is shipped as part of MOSS Service Pack 2. As long as this service pack is applied, the tool is available.
This tool documents the current installation, checks your MOSS/WSS installation against SharePoint 2010 requirements, and applies best practice rules identifying areas of concern.
In order to execute this tool, the WSS 3.0/MOSS 2007 installation must have the Office 2007 Service Pack 2 installed. This tool is native to the SharePoint installation and an extension of the stsadm command.
You must be a member of the Farm Administrators SharePoint Group, with administrator permissions on the server.
You should see a report that looks similar to the following screenshot:
The pre-upgrade application leverages rules that can be found in the following two files: OssPreUpgradeCheck.xml and WssPreUpgradeCheck.xml.
These files were created in 12\CONFIG\PreUpgradeCheck when the Microsoft Office SharePoint 2007 Service Pack 2 was installed. Refer to the next screenshot:
In the command prompt window shown in step 4 of the previous section, a summary of the operations is shown. The objects marked with the colors yellow and red must be addressed. The farm will not get upgraded until objects in red color are addressed.
As you can see from the preceding screenshot, an HTML file is created in the 12\Logs folder, which contains the information the pre-upgrade application produced. The first part of the report produces important information as shown in the following screenshot:
Other information collected includes the SharePoint version, supported upgrade types, along with information on your servers, including roles, amount of data, number of web applications, site collections, and number of servers.
The rest of the HTML report lists the checks that were done and any issues that were found. If an issue is found, the report will include a description on fixing the issue or a link to a Microsoft Knowledge Base article that corresponds to the issue.
The pre-upgrade application performs read-only operations against the database. No changes are made to your SharePoint installation. This means you can run the application multiple times and there is no adverse effect on your SharePoint installation. As you resolve issues, it is advisable that you rerun the pre-upgrade application.
Using the preupgradecheck rule files parameter, you can create your own custom rules to identify items that are specific to your installation.
There are two approaches to upgrading your WSS 3.0/MOSS 2007 farm to SharePoint 2010. They are:
The latter method of upgrading your MOSS 2007 farm is the preferred method and the one that this recipe outlines. It has many advantages over the in-place upgrade method. Some of these advantages are:
SharePoint 2010 has a completely different Services architecture as compared to MOSS 2007 Shared Services. This new architecture must be planned carefully and implemented according to the organization's needs. By doing a database attach, your farm will correctly consume the new architecture as architected.
The preupgradecheck should already have been run on your current installation and any issues should have been resolved. Be sure to identify the content database that is being upgraded.
A new SharePoint Server 2010 farm must be set up and configured using a web application.
You must have access to SQL Management Studio with the ability to create databases.
Here is the screenshot I get when I run this command:
When the operation finishes successfully, navigate to the SharePoint 2010 Central Administration site.Click the Application Management option. Under Site Collections, click the Change Site Collection Administrators option.Ensure that there is a valid site collection administrator.Navigate to the new site.
Steps 1 through 7 showed how to take a backup of the content database that was being upgraded. Step 8 is copying the physical file that is created from the backup to the new server. Using file storage and rights, the file may not have to be copied. The important part of this process is that the new SQL instance for SharePoint 2010 has access to this file.
Steps 9 through 11 performed a restore to put the backup file into the new SQL database instance.
Steps 12 through 14 ran the command that performs the physical upgrade of the file. An upgrade of the content database is nothing more than schema changes, table changes, and stored procedure changes. It also adds the content database to the specified web application.
In steps 15 and 16, we, as Farm Administrators, ensured that the Site Collection Administrator from MOSS 2007 is still a valid account in the now upgraded SharePoint 2010 farm.
The database attach method is the least intrusive upgrade when it comes to your SharePoint Farms. For SharePoint 2010, upgrading with addcontentdb can be done only through the stsadm command; its functionality is not found in the Central Administration User Interface.
Finally, there is a parameter called preserveolduserexperience in the addcontentdb command. This is an optional parameter and set to true by default. When the site is upgraded to SharePoint 2010, it will contain the same look as it did in MOSS 2007. If you want the site to use the new SharePoint 2010 look, then ensure that you use this parameter and set it to false.
