Pro SharePoint 2013 Administration

656 Pages·2013·31.94 MB·English

by  Rob Garrett

For your convenience Apress has placed some of the front
matter material after the index. Please use the Bookmarks
and Contents at a Glance links to access them.
Contents at a Glance
Foreword ���������������������������������������������������������������������������������������������������������������������������xix
About the Author ���������������������������������������������������������������������������������������������������������������xxi
About the Technical Reviewer �����������������������������������������������������������������������������������������xxiii
Acknowledgments ������������������������������������������������������������������������������������������������������������xxv
Introduction ��������������������������������������������������������������������������������������������������������������������xxvii
■ Chapter 1: SharePoint 2013 Overview and New Features �������������������������������������������������1
■ Chapter 2: New Installation and Configuration����������������������������������������������������������������21
■ Chapter 3: Working with PowerShell �������������������������������������������������������������������������������59
■ Chapter 4: Upgrading from SharePoint 2010 �������������������������������������������������������������������75
■ Chapter 5: Health Monitoring and Disaster Recovery ���������������������������������������������������105
■ Chapter 6: Users, Profiles, and Social Networking ��������������������������������������������������������151
■ Chapter 7: Security and Policy ��������������������������������������������������������������������������������������203
■ Chapter 8: Claims-Based and Federated Authentication �����������������������������������������������235
■ Chapter 9: Content Model and Managed Metadata �������������������������������������������������������279
■ Chapter 10: Publishing and Web Content Management ������������������������������������������������317
■ Chapter 11: Documents and Records Management ������������������������������������������������������371
■ Chapter 12: Business Intelligence ���������������������������������������������������������������������������������427
■ Chapter 13: Business Connectivity Services �����������������������������������������������������������������463
v
■ Contents at a GlanCe
■ Chapter 14: Microsoft Office Integration and Office Web Applications ���������������������������501
■ Chapter 15: SharePoint Search ��������������������������������������������������������������������������������������551
■ Chapter 16: SharePoint Designer and Branding ������������������������������������������������������������603
Index ���������������������������������������������������������������������������������������������������������������������������������631
vi
Introduction
Hello, and welcome to Pro SharePoint 2013 Administration. In the next sixteen chapters of this book, you will
discover administration of the latest version of SharePoint.
SharePoint administration can be intimidating to anyone looking at the platform for the first time, and so this
book was written to cover all the major areas and demonstrate configuration in a systematic fashion. Chapter 1 kicks
off with an overview of the new SharePoint 2013 platform, changes from the previous version, and what you can
expect of the new features.
In this book, you will read about the installation of SharePoint Server 2013 on a new Windows Server. Chapter 1
highlights the prerequisites for the installation and minimal hardware and operating system software requirements.
Even if you are a seasoned SharePoint administrator and have performed many installations of SharePoint before, you
might gain additional insight from this chapter. Chapter 2 also serves as a great instruction set for anyone looking to
install SharePoint 2013 for the first time.
With SharePoint installed, you will embark on a journey through the various areas of SharePoint 2013 covered
in this book, which include security and policy; user profiles; social networking; documents, records, and metadata;
business intelligence; Microsoft Office integration; health and disaster recovery; search; and user interface branding;
among others.
Thank you—for your interest in this book and SharePoint 2013 administration.
Who This Book Is For
The title gives it away that this book is focused at SharePoint administrators (or want-to-be administrators), but this is
not to say that Pro SharePoint 2013 Administration has no value for business experts or developer audiences. It should
appeal to anyone with an interest in SharePoint 2013—installing it, configuring it, and using many of the best features
the platform has to offer.
If you are new to SharePoint, congratulations on joining a large community of like-minded SharePoint
enthusiasts. You will gain a wealth of information on grassroots installations, configuration, and administration of
SharePoint 2013 from this book. For those audience members familiar with SharePoint 2013, this book serves as great
reference material and best practice for what you may already know. For the casual reader in the bookstore, this book
should, I hope, whet your palate regarding what SharePoint 2013 has to offer and provide you with an overview if you
are curious about what SharePoint is or interested in finding out how the platform has changed since the 2010 version.
Contacting the Author
Should you have any questions or comments—or even spot a mistake that you think the author should know
about—you can contact the Rob at [email protected]. Feel free to visit the author’s blog at
http://blog.robgarrett.com.
xxvii
Chapter 1
SharePoint 2013 Overview
and New Features
Hello, and welcome to SharePoint 2013. Microsoft has provided another great release of the SharePoint Server
platform. Since the earliest version of SharePoint 2001, and Content Management Server prior to that, Microsoft
has continued to expand and grow the SharePoint platform into the sophisticated information storage and retrieval
system it is today.
Thank you for buying this book (or thinking about buying it, if you are browsing it in the store or online). In
the next sixteen chapters, you will learn about the various new features and capabilities of SharePoint 2013 from an
administration point of view, and how to use these capabilities to host your own SharePoint 2013 farm.
As with all good technical books, you can read this book cover to cover or dip into the chapters that interest you
the most. I cannot make any assumptions about your previous experience with SharePoint, and so I wrote this book
to appeal to a range of experience levels, starting with new administrators through to seasoned SharePoint experts.
This book is an administration book, so if you are looking for development knowledge, then I recommend reading
one of the development books in the SharePoint series from Apress. If you fall into the category that consists of new
and upcoming SharePoint administrators, then I urge you to read all chapters in Pro SharePoint Administration 2013,
starting with this chapter, where I offer an overview of SharePoint 2013. Those with extensive experience in SharePoint
can also benefit from this chapter, because I cover the additions and enhancements in SharePoint 2013. Without
further delay, it is time to start learning SharePoint 2013.
No More Doughnut
No, you are not seeing things, and yes, this is the topic of this section. In the previous version of SharePoint—
SharePoint 2010—Microsoft liked to show off a circle diagram that described the various high-level modules in the
platform. Magazine articles and books frequently included this diagram; my previous book (Pro SharePoint 2010
Administration [Apress, 2011]) was no exception. The circle diagram, or donut, as I liked to call it, described the six
main areas of SharePoint 2010: Sites, Composites, Communities, Insights, Content, and Search. I could have included
this diagram, except that Microsoft has now adopted a new way to describe the main modules of SharePoint 2013.
I always thought the classifications in the SharePoint 2010 donut were a little lofty, which is to say they resembled
language you might expect to find in typical business literature or words used in meetings. With SharePoint 2013,
Microsoft has adopted simple terms to describe better the aims of the high-level areas of the new SharePoint platform.
The following summarizes each term that classifies the high-level capabilities of SharePoint 2013:
• Share—The term “sharing” has become ubiquitous with the explosion of social media. No longer
do we grant access to our content, we share it instead. Throughout the various pages in SharePoint
2013, you will see share icons dotted around, which give owners of content the ability to share
their content with other users. Sharing is also about empowering users to share their content
across multiple devices and platforms while maintaining content in one place—SharePoint.
1
Chapter 1 ■ Sharepoint 2013 overview and new FeatureS
• Organize—Organization is about how you store your content in SharePoint. Whether you use
lists or document libraries, it is about site hierarchy and structure to represent your content;
it is about the metadata you assign your content to make it available to search; it is about
synchronizing SharePoint content with your desktops so you can organize access to your content.
Organizing is all about how you structure your data for optimum use in SharePoint 2013.
• Discover—Discovery focuses on the capability to search for content in SharePoint. Much of
the functionality associated with content access in SharePoint 2013 utilizes search. Microsoft
has included the search platform formerly known as FAST as the default Enterprise Search
Platform in SharePoint 2013 (at no extra cost). Discovery also includes business intelligence
capabilities and ability to discover information presented after applying business intelligence
logic to related data.
• Build—Microsoft has made some significant changes in the way it builds applications
for SharePoint 2013. The new App Model supports creation of portable and lightweight
applications that host in SharePoint 2013 and other Office applications. The Microsoft
App Marketplace promotes sharing of custom applications with other organizations and
individuals, much like how the Marketplace for Windows Phone operates.
• Manage—SharePoint 2013 provides better capabilities to “manage” itself, whether as an
on-premises SharePoint farm or as part of an Office 365 account (Microsoft’s Office in the cloud).
SharePoint 2013 integrates well with Exchange and Lync 2013, and the configuration of this
integration is robust and not overcomplicated to achieve. Many of the sophisticated features
of SharePoint, such as business intelligence, records management, search, etc., have greater
flexibility in their management and configuration.
From the previous list, you should see that Microsoft has strived to describe the core capabilities of SharePoint
2013 with labels that make sense to everyone. I know I certainly appreciate the new labels when asked to provide a
simple one- to two-sentence answer to the question “What is SharePoint?”
Foundation and Server
Similar to its predecessor, SharePoint 2013 comes in two different flavors: Foundation and Server. Foundation is
the core platform for SharePoint Server and is free to install and use as long as you have proper Microsoft Windows
licenses. SharePoint 2013 Server builds atop of Foundation and includes many more features. Unlike Foundation,
Microsoft charges for SharePoint Server licenses (more on licensing shortly), and Server provides either Standard or
Enterprise license types, each offering a different set of features.
Deciding on the version of SharePoint you want usually involves determining your purpose for SharePoint. Use
of Foundation is certainly compelling at zero cost (having licensed Windows Server first), but it is very limited in
functionality out of the box. If you simply need to provide team collaboration and a location to upload documents,
with no frills, then Foundation might be enough. In my experience, organizations that are serious about implementing
an information management solution in SharePoint tend to go with SharePoint Server because it provides many
attractive features that easily justify the expense. However, I have seen some very nice working solutions running on
Foundation.
When deciding to implement SharePoint Server, organizations must choose whether to purchase a Standard or
Enterprise version. Both versions use the same installation. Which license you activate will determine the features
available for use in your farm.
Table 1-1 lists the high-level features available in Foundation, Server Standard, and Server Enterprise. Server
Enterprise provides the complete suite of features, whereas Foundation and Server Standard provide a subset. Do not
worry if you have not heard of many of the features in Table 1-1; I cover the majority of them throughout this book.
2
Chapter 1 ■ Sharepoint 2013 overview and new FeatureS
Table 1-1. Feature Comparison in SharePoint 2013
Feature Available in Available in Server Available in Server
Foundation Standard Enterprise
Access Services (2010 and 2013) No No Yes
Application Management Yes Yes Yes
Business Connectivity Services Yes Yes Yes
Business Intelligence No No Yes
e-Discovery and Records Management No Yes Yes
Excel Services No No Yes
Health Analyzer Yes Yes Yes
Managed Metadata Service No Yes Yes
PerformancePoint No No Yes
Search No Yes Yes
Secure Store Service No Yes Yes
Social Features No Yes Yes
State Service No Yes Yes
Usage and Health Data Collection Yes Yes Yes
User Authentication and Authorization Yes Yes Yes
User Profiles No Yes Yes
Visio Graphics Service No No Yes
Web Content Management No Yes Yes
Windows PowerShell Cmdlets Yes Yes Yes
Word Automation No Yes Yes
Workflow No Yes Yes
Of course, Table 1-1 is not exhaustive. SharePoint includes many features and to list them all would consume
several pages. Table 1-1 covers the high-level features, some of which include different capabilities depending on the
version and license. For example, not all capabilities of Business Connectivity Services are available in Foundation,
such as use of the Secure Store Service.
Licensing
SharePoint licensing is confusing. Depending on which Microsoft representative or SharePoint vendor/provider you
talk with, you may get a different answer on the cost of Standard and Enterprise licenses.
Like Windows, SharePoint requires a Client Access License (CAL) for every user or device accessing SharePoint.
As I mentioned earlier, Foundation is free as long as you have Windows CALs for all your users and you are not
exposing SharePoint to anonymous users on the Internet (more on this in a moment), so assume I am talking about
SharePoint 2013 Server with regards to licensing, from here on. Depending on your desired functionality from
SharePoint, you must buy either Standard CALs or Enterprise CALs, which have different prices. The cost per CAL
differs depending on the license provider, how many CALs you buy in each purchase batch, and whether you qualify
3
Chapter 1 ■ Sharepoint 2013 overview and new FeatureS
for Microsoft discounts (typically applicable only to government, not-for-profit, and charity organizations)—I did say
licensing is complicated.
Prior to SharePoint 2013, you had to decide whether to purchase Enterprise CALs or Standard CALs for all users
of your SharePoint farm. SharePoint Server 2013 introduces the ability to mix and match Standard and Enterprise
CALs in the same farm. For example, you may have a small subset of users in your organization who require use of the
Enterprise features, whereas the majority of users require only Standard features. Rather than buy all users Enterprise
CALs, you can now save expense by buying Enterprise CALs for only those users who require them. By default,
SharePoint Server 2013 operates in single license type mode. To enable per user license types, use the following
PowerShell Cmdlets on the server running Central Administration:
1. Click the Start button.
2. Click All Programs and then click Microsoft SharePoint 2013 Products.
3. Click SharePoint 2013 Management Shell (this loads PowerShell).
4. Type in the Cmdlet: Get-SPUserLicensing at the prompt and press Enter.
5. If per user licensing is disabled the Cmdlet will return False.
6. To enable per user licensing, enter the following Cmdlet at the prompt and then press
Enter: Enable-SPUserLicensing
7. You may now map different license types to users or groups.
8. Enter the following PowerShell Cmdlets to assign a license type to a set of users
in an AD group (enter each Cmdlet on a new line, followed by Enter):
$a = New-SPUserLicenseMapping -SecurityGroup "AD group" -License Type
Add-SPUserLicenseMapping -Mapping $a
9. In the previous Cmdlets, you can provide the license type as Unlicensed, Standard,
Enterprise, Project, and WACEdit.
■ Note discussion of the various license types available in per user licensing is outside the scope of this book,
but Standard and enterprise correlate to those license types listed in table 1-1.
User and device CALs work for on-premise scenarios when you know exactly how many users to support, and
all your users authenticate with your SharePoint 2013 farm, but what about scenarios involving anonymous users for
public-facing solutions in SharePoint? The good news is that Microsoft has finally addressed this need in SharePoint
2013. In prior versions, you had to buy a different type of license called “SharePoint for Internet Sites,” which came at
a high premium because it assumed use of all Enterprise features. With SharePoint 2013, Microsoft requires you to
buy only the SharePoint Server product. Of course, if you use your farm for both Internet-facing and internal-facing
sites, you still need to provide CALs for users authenticating with SharePoint from within the office.
■ Note to understand more on Sharepoint Server 2013 licensing, consult a Microsoft representative or third-party
vendor of Sharepoint.
4
Chapter 1 ■ Sharepoint 2013 overview and new FeatureS
System Requirements
Like any other server platform, SharePoint 2013 has a number of hardware and software requirements. Hardware
requirements are strongly recommended by Microsoft but open for deviation, depending on your deployment plan for
SharePoint. Adherence to hardware requirements ensures optimal operation and good user experience and caters to
most situations involving all features enabled in the platform. On the other hand, you must meet the minimal software
requirements to install and operate SharePoint 2013 (both Foundation and Server).
Hardware Requirements
When Microsoft devises the hardware requirements for SharePoint, it assumes typical scenarios that account for
average user load and availability of features. Of course, what may work for one organization may not work for
another—the hardware requirements to support thousands of concurrent users, utilizing search and business
intelligence, with redundant hardware is very different from those of a one- or two-server farm for a small back-office
deployment (see Chapter 5 for server farm planning and redundancy). Fortunately, Microsoft published its hardware
requirements for SharePoint 2013 to account for a variety of scenarios, as shown in Table 1-2.
Table 1-2. SharePoint Web and Application Server Minimum Hardware Requirements
Scenario Deployment Type and Scale RAM Processor Hard Drive Space
Single SharePoint Server Development deployment with 8GB 64-bit, 4 cores 80GB for system drive
with built-in database or minimum number of services
separate SQL Server installed.
Single SharePoint Server Development deployment with 10GB 64-bit, 4 cores 80GB for system drive
with built-in database or minimum number of services
separate SQL Server installed and Visual Studio 2012.
Single SharePoint Server Development deployment with 24GB 64-bit, 4 cores 80GB for system drive
with built-in database or all available services installed and
separate SQL Server Visual Studio 2012.
SharePoint Server in a Staging or production deployment 12GB 64-bit, 4 cores 80GB for system drive
three-tier farm with all services installed.
I remember when Microsoft first released the beta version of SharePoint 2013 and published the hardware
requirements for development farms. I was shocked to read that my development server would need 24GB of RAM,
especially since I typically use close to this amount of RAM for complete virtual server host. However, with further
clarification, you can see from Table 1-2 that 8GB of RAM could work for most development scenarios, but it assumes
the absence of Visual Studio (an application that is heavy on RAM) and installation of a minimum number of services.
Notice the last line in Table 1-2, which caters to staging and production environments. These deployments
host SQL Server separately and assume separate SharePoint application and web servers (three-tier). To cater to
typical user load on a single web server, 12GB of RAM with a four-core CPU should provide enough horsepower.
The beauty of SharePoint is that it scales, so if you overload one server with concurrent user requests, then you may
add additional servers to the farm and load balance requests. Each new web or application server added to the farm
requires the same minimum hardware specifications as listed in Table 1-2. Just as with SharePoint 2010, SharePoint
2013 requires 64-bit hardware and operating system to operate.
■ Note See the following information for Sharepoint 2013 capacity planning:
http://technet.microsoft.com/en-us/library/Cc261700.aspx.
5