The document discusses several "dirty little secrets" about configuring and setting up SharePoint 2013. It notes that SharePoint 2013 has optional software that must be installed for certain features to work properly. It also discusses how to configure SharePoint 2013 to search Exchange and Lync messages and support Access 2013 databases, but that these require non-trivial configurations. The document outlines several other requirements for properly configuring services, workflows, and other elements of a SharePoint 2013 implementation.
2. #1 SharePoint 2013 has "optional" software
•
•
•
•
•
•
Data Sources
.NET Framework Data Provider for SQL Server (part of Microsoft .NET Framework)
.NET Framework Data Provider for OLE DB (part of Microsoft .NET Framework)
SQL Server Analysis Services ADOMD.NET
Oracle client
SQL Remote BLOB Storage (RBS) Provider
3. #2 SharePoint 2013 can search Exchange and
Lync messages…if you know the "secret squirrel
password"
•
•
•
•
•
•
Works with 2013 version of server software only
Configure Lync archiving to Exchange
Install Exchange Web Services
Setup S2SA between SharePoint and Exchange
Give SharePoint permissions to search Exchange
Create eDiscovery site
4. #3 You can configure SharePoint 2013 to support Access 2013
databases…if you like poking yourself in the eye
All you need to do is read the 22 page whitepaper
•
•
Server side
Setup SQL Server for Access Services
• Requires contained databases only available in SQL 2012
• Add the following features
• Database Engine Services
• Full-Text and Semantic Extractions for Search
• SQL Management Tools feature (for troubleshooting)
• Client Tools Connectivity
• Set SQL Server to mixed mode authentication
• Need to "Allow Triggers to Fire Others"
• Enable both TCP/IP and named pipes
5. #3 You can configure SharePoint 2013 to support Access 2013
databases…if you like poking yourself in the eye
•
•
•
•
Setup SharePoint Server for Access Services
• Install just a couple SQL components on the SharePoint server
• SQL Server 2012 Local DB
• SQL Server 2012 Data-Tier Application Framework
• SQL Server 2012 Native Client
• SQL Server 2012 Transact-SQL ScriptDom
• SQL Server 2012 Reporting Services Add-in for SharePoint
• Microsoft System CLR Types for SQL Server 2012
• Setup SharePoint for SP2013 Apps
• Set Access Services application pool to "Load User Profiles"
• Allows external SharePoint lists to be used
• LocalDB used by Access Services requires a user profile
• Need to reboot server for change to take effect
Client side
Use Access 2013 to build Access app
Use browser to view and update data
6. #4 SharePoint 2013 has a distributed cache which changes many things
What is distributed cache
What is it used for in SharePoint 2013
•
•
•
You no longer need affinity (sticky sessions, stateful) provided by the load
balancer
You need to perform a graceful shutdown of the distributed cache before
rebooting SharePoint servers with it
• Done through PowerShell
• Can take up to 15 minutes or more
• If you don't do this
• Users can start to receive login prompts or see slowness for a
bit
• If using MySites you will have to wait for health rules to find
problem or run "User Profile Service Application - Feed Cache
Repopulation Job"
You need to use PowerShell to remove or stop Distributed Cache on a
SharePoint server
7. #5 SharePoint 2013 and workflow doesn't work like you may think it does.
•
•
•
•
•
•
•
•
Have to install "optional software" in order to enable SharePoint 2013 workflows
You have to install Workflow Manager somewhere
Workflow Manager requires three instances to be highly available
Have to install the Workflow Client on all other SharePoint servers
SharePoint 2013 workflows cannot be associated with content types
SharePoint Designer 2013 workflows cannot use InfoPath forms
Nintex Workflow 2013 doesn't use SharePoint 2013 workflows
New solutions for Office 365 and SharePoint 2013 workflows (Nintex Live)
8. #6 You probably haven't heard about these "to do's" when setting up
SharePoint 2013
•
•
•
•
•
•
Install IIS Media Services and enable BLOB caching on your web applications
Recommend making the search account local administrator during build
Search Administration component can be run on more than one server in SharePoint 2013
Install Remote Differential Compression on the server
In 2012, install Windows server feature if you need .Net Framework 2.0/3.5
Need to do additional steps after the March 2013 PU related to SharePoint Apps and workflow
9. #6 You probably haven't heard about these "to do's" when setting up
SharePoint 2013
•
•
•
•
•
Install IIS Media Services and enable BLOB caching on your web applications
Recommend making the search account local administrator during build
Search Administration component can be run on more than one server in SharePoint 2013
Install Remote Differential Compression on the server
In 2012, install Windows server feature if you need .Net Framework 2.0/3.5
10. #7 Service Application architecture recommendations have changed for
SharePoint 2013
Most service applications move to the web server
Access Database Service 2010
Access Services
App Management Service
Business Data Connectivity Service
Central Administration
Skip Distributed Cache service (handled later in the document)
Document Conversions Load Balancer Service
Excel Calculation Services
Lotus Notes Connector
Machine Translation Service
Managed Metadata Web Service
Microsoft SharePoint Foundation Incoming E-Mail
Microsoft SharePoint Foundation Sandboxed Code Service
Microsoft SharePoint Subscription Settings Service
PerformancePoint Service
Request Management
Secure Store Service
User Profile Service
User Profile Synchronization Service
Visio Graphics Service
11. #7 Service Application architecture recommendations have changed for
SharePoint 2013
•
•
Use only one web application
Use host-named site collections