• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
SharePoint Saturday Kansas City - SharePoint 2013's Dirty Little Secrets
 

SharePoint Saturday Kansas City - SharePoint 2013's Dirty Little Secrets

on

  • 1,693 views

With over a year's experience deploying multiple SharePoint 2013 farms, I have found many things that you don't hear anyone talking about but are important. These are things buried in articles and ...

With over a year's experience deploying multiple SharePoint 2013 farms, I have found many things that you don't hear anyone talking about but are important. These are things buried in articles and blogs, and items I have run into during deployments. We will talk about things that effect setup, design, upgrade, and operation. Do you know about host named managed paths? Do you know how to quiesce the distributed cache before a server reboot? Did you know service application design guidance has changed for SP2013? Did you know workflow manager requires three instances to be highly available? Do you know how to make SharePoint 2013 able to search Lync 2013 instant messages? If not, come and learn these and more dirty little secrets.

Statistics

Views

Total Views
1,693
Views on SlideShare
1,691
Embed Views
2

Actions

Likes
1
Downloads
71
Comments
0

1 Embed 2

https://twitter.com 2

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    SharePoint Saturday Kansas City - SharePoint 2013's Dirty Little Secrets SharePoint Saturday Kansas City - SharePoint 2013's Dirty Little Secrets Presentation Transcript

    • SharePoint 2013 Dirty Little Secrets Presented by: JD Wade, Lead SharePoint Consultant Horizons Consulting Mail: jd.wade@hrizns.com Blog: http://wadingthrough.com LinkedIn: http://linkedin.com/in/jdwade Twitter: @JDWade
    • #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
    • #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
    • #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
    • #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
    • #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
    • #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)
    • #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
    • #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
    • #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
    • #7 Service Application architecture recommendations have changed for SharePoint 2013 • • Use only one web application Use host-named site collections
    • Thanks to our Sponsors!!! ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​
    • Q&A http://wadinghthrough.com/presentations http://www.hrizns.com http://twitter.com/jdwade
    • Notes
    • Notes in PDF format Located in SkyDrive