70-331: Core Solutions of Microsoft SharePoint Server 2013

2 | SharePoint Saturday St. Louis 2013 Session Evaluations Schedule and evaluate each session you attend via our mobile app that can be used across devices at azurewebsites.nethttp://spsaturday. azurewebsites.net You will be able to evaluate sessions added to your “My Sessions” 25 minutes before the scheduled end time Evaluations are stored anonymously and your feedback is appreciated The app will be the only method available to submit session evaluations for the event and we hope you find it intuitive and convenient

Becky Bertram Owner, Savvy Technical Solutions Microsoft SharePoint Server MVP Microsoft Certified Trainer MCSD, MCPD, MCITP, MCTS,MCTA Co-author of Wrox SharePoint Six-in-One

Certification Overview

5 | SharePoint Saturday St. Louis 2013 Microsoft Next Gen Certification Microsoft Certified Solutions Expert (MCSE) You can’t be a “stand-alone” MCSE. You’re in an MCSE in a specialty, such as Server Infrastructure Desktop Infrastructure Private Cloud Data Platform Business Intelligence Messaging Communication SharePoint For each MCSE, you must pass 3 core exams: : Installing and Configuring Windows Server : Administering Windows Server : Configuring Advanced Windows Server 2012 Services

6 | SharePoint Saturday St. Louis 2013 MCSE: SharePoint To become a SharePoint MCSE, you must pass two additional exams: : Core Solutions of Microsoft SharePoint Server : Advanced Solutions of Microsoft SharePoint Server 2013 If you are already an MCITP for SharePoint, you can pass exam : Upgrading Your Skills to MCSA Windows Server 2012 This exam covers the topics of the three core MCSE exams. You’ll still need to pass the additional SharePoint 2013 exams to earn your MCSE: SharePoint. You must be an existing MCITP to be eligible to take this exam.

7 | SharePoint Saturday St. Louis 2013 It’s Tough! Previously, the exams covered SharePoint-specific infrastructure questions. The exams didn’t cover basic server farm infrastructure topics such as DHCP, DNS, firewalls, Active Directory, OS settings, etc. The Microsoft Certified Master certification was introduced with the last product cycle. Becoming a Master is HARD! You’re expected to know anything related to basic server infrastructure that could affect your SharePoint farm. Since the last SharePoint exams didn’t cover these details, people coming into the MCM program felt unprepared. The current exam objectives were written by current SharePoint MCMS (yes, the smartest folks in our field!) The resulting exam covers many topics not necessarily directly related to SharePoint, but that could affect the performance of your SharePoint farm.

Taking the Exam

9 | SharePoint Saturday St. Louis 2013 Register with Prometric You must register for your exams through Prometric. You can register online at or you can call their customer service line. Choose a testing center and an exam time. Not all exams are available in every location. “Second Shot” means you can retake the exam for free.

10 | SharePoint Saturday St. Louis 2013 Interactive Exam The new SharePoint 2013 exams are more interactive than before. Not just multiple choice. More thoroughly tests your knowledge but can be a little intimidating because it feels like there are more opportunities for wrong answers. Drag and drop servers into a server configuration Drag and drop words into a fill-in-the-blank sentence Arrange items in their correct order

11 | SharePoint Saturday St. Louis 2013 Tips for Choosing Answers For some exams, there will be right answers and wrong answers. For other exams, all the answers will be right, but not in the circumstance described in the question. If more than one answer seems right, read the question closely. The answer usually lies in the question.

Studying for the Exam

13 | SharePoint Saturday St. Louis 2013 Read the Objectives The exam writing process goes like this: Your best (and free) way of studying is to read up on each objective. The exam questions are written directly from them!

14 | SharePoint Saturday St. Louis 2013 Study Materials Exam study guide at %20Study%20Guide/AllItems.aspx %20Study%20Guide/AllItems.aspx Exam Ref : Core Solutions of Microsoft SharePoint Server do Out in May

Design a SharePoint Topology

16 | SharePoint Saturday St. Louis 2013 Design Information Architecture This objective may include but is not limited to: Design an intersite navigational taxonomy Design site columns and content types Design keywords, synonyms, best bets, and managed properties Plan information management policies Plan managed site structures Plan term sets

17 | SharePoint Saturday St. Louis 2013 Navigation in SharePoint 2013 Managed metadata-driven navigation Top and left nav driven by terms in the term store Friendly-URLs All pages in live in a single site and have a URL that appears right off the root, like (instead of Still possible to use legacy model of navigation based on site hierarchy

18 | SharePoint Saturday St. Louis 2013 Design a Logical Architecture This objective may include but is not limited to: Plan application pools Plan web applications Plan for software boundaries Plan content databases Plan host-header site collections Plan zones and alternate access mapping

19 | SharePoint Saturday St. Louis 2013 Software Boundaries Understand the limits of things like: Max number of content databases, site collections, web applications in a farm; list and libraries, site columns in a site collection, etc. Max database size, max app pools per web server, max managed paths per web app, etc.

20 | SharePoint Saturday St. Louis 2013 Design a Physical Architecture This objective may include but is not limited to: Design a storage architecture Configure basic request management Define individual server requirements Define service topologies Plan server load balancing Plan a network infrastructure

21 | SharePoint Saturday St. Louis 2013 Storage Architecture How much physical disk space do you need? How much database space do you need? How do you do capacity planning to ensure you have enough throughput to your storage devices?

22 | SharePoint Saturday St. Louis 2013 Network Infrastructure Don’t be surprised if this goes into: DNS and DHCP Configuration IPv4 and IPv6 Configuration Firewall configuration

23 | SharePoint Saturday St. Louis 2013 Plan a SharePoint Online (Microsoft Office 365) Deployment This objective may include but is not limited to: Evaluate service offerings Plan service applications Plan site collections Plan customizations and solutions Plan security for SharePoint Online Plan networking services for SharePoint Online

24 | SharePoint Saturday St. Louis 2013 Office 365 Infrastructure Hybrid scenarios Migration scenarios

Plan Security

26 | SharePoint Saturday St. Louis 2013 Plan and Configure Authentication This objective may include but is not limited to: Plan and configure Windows authentication Plan and configure identity federation Configure claims providers Configure site-to-site (S2S) intra-server and OAuth authentication Plan and configure anonymous authentication Configure connections to Access Control Service

27 | SharePoint Saturday St. Louis 2013 OAuth Oauth is an open standard that enables users to approve an application to act on their behalf without sharing their user name and password OAuth enables users to authorize the service provider (in this case, SharePoint 2013) to provide tokens instead of credentials (for example, user name and password) to their data that is hosted by a given service provider (that is, SharePoint 2013). Each token grants access to a specific site (for example, a SharePoint document repository) for specific resources (for example, documents from a folder) and for a defined duration (for example, 30 minutes). This enables a user to grant a third-party site access to information that is stored with another service provider (in this case, SharePoint), without sharing their user name and password and without sharing all the data that they have on SharePoint. (Taken from us/library/office/apps/fp142384(v=office.15) us/library/office/apps/fp142384(v=office.15

28 | SharePoint Saturday St. Louis 2013 Windows Azure Access Control Services (ACS) Used in conjunction with OAuth to provide authentication for SharePoint apps Free Know how to configure a connection to ACS

29 | SharePoint Saturday St. Louis 2013 Plan and Configure Authorization This objective may include but is not limited to: Plan and configure SharePoint users and groups Plan and configure People Picker Plan and configure sharing Plan and configure permission inheritance Plan and configure anonymous access Plan web application policies

30 | SharePoint Saturday St. Louis 2013 Content Sharing SharePoint Server 2013 introduces the concept of sharing for all document libraries. By using this simplified experience, users can specify permissions for a specific document without having to understand the inheritance model. Slightly different than SharePoint Online’s Share Content with External Users functionality. Can’t hurt to know how both work.

31 | SharePoint Saturday St. Louis 2013 Plan and Configure Platform Security This objective may include but is not limited to: Plan and configure security isolation Plan and configure services lockdown Plan and configure general firewall security Plan and configure antivirus settings Plan and configure certificate management

32 | SharePoint Saturday St. Louis 2013 Firewalls Make sure you know how to open the right ports in your firewall so that SQL Server can communicate. Know how to use both the standard point and a non-standard port.

33 | SharePoint Saturday St. Louis 2013 Certificate Management Certificates become more important in 2013 Used for Azure Workflow Manager, SharePoint Apps, SSL, and creating trust between farms Know how to export, import, and install certificates using PowerShell Understand how to add a certificate to the SharePoint Trusted Root Certificate Authority

34 | SharePoint Saturday St. Louis 2013 Plan and Configure Farm-level Security This objective may include but is not limited to: Plan rights management Plan and configure delegated farm administration Plan and configure delegated service application administration Plan and configure managed accounts Plan and configure blocked file types Plan and configure web part security

Install and Configure SharePoint Farms

36 | SharePoint Saturday St. Louis 2013 Plan Installation This objective may include but is not limited to: Identify and configure installation prerequisites Implement scripted deployment Implement patch slipstreaming Plan and install language packs Plan and configure service connection points Plan installation tracking and auditing

37 | SharePoint Saturday St. Louis 2013 Plan and Configure Farm-wide Settings This objective may include but is not limited to: Configure incoming and outgoing Plan and configure proxy groups Configure SharePoint Designer settings Plan and configure a corporate catalog Configure Office Web Apps integration Configure Windows Azure workflow server integration

38 | SharePoint Saturday St. Louis 2013 Configuring a Corporate Catalog

39 | SharePoint Saturday St. Louis 2013 Workflow Server Integration Install and configure Workflow Manager Use the PowerShell command Register-SPWorkflowService Install the Workflow Manager Client on each Web Front End (WFE) server The order of actions and exact PowerShell command you use depends on whether your Workflow Server is in your SharePoint farm or not, and whether you’re using HTTP or HTTPS to communicate

40 | SharePoint Saturday St. Louis 2013 Create and configure Enterprise Search This objective may include but is not limited to: Plan and configure a search topology Plan and configure content sources Plan and configure crawl schedules Plan and configure crawl rules Plan and configure crawl performance Plan and configure security trimming

41 | SharePoint Saturday St. Louis 2013 Create and Configure a Managed Metadata Service (MMS) Application This objective may include but is not limited to: Configure proxy settings for managed service applications Configure content type hub settings Configure sharing term sets Plan and configure content type propagation schedules Configure custom properties Configure term store permissions

42 | SharePoint Saturday St. Louis 2013 Create and Configure a User Profile Service (UPA) Application This objective may include but is not limited to: Configure a UPA application Set up My Sites and My Site hosts Configure social permissions Plan and configure sync connections Configure profile properties Configure audiences

43 | SharePoint Saturday St. Louis 2013 Social Permissions Activities are publicly accessible unless the activity refers to content that the user does not have access to. If feed functionality is required for a restricted group of users, a site feed should be used. Site feeds display posts and replies among the users of the group. Site feed posts and replies display in the Newsfeed of a user only if the user has access to the site feed. Site feeds do not display system-generated activities. By default, the site feed feature on a team site is enabled. When you assign permissions to a team site that hosts a site feed, consider the following: Access to the site feed is restricted to the users specified in the permissions list. Users can post or reply only if they have the appropriate permissions. Security trimming is enforced. This means that no site feed activities will appear in the search results of a user who doesn't have access to the team site. Site feed activities appear in a user's Newsfeed if the user has access to the team site.

44 | SharePoint Saturday St. Louis 2013 Distributed Cache Service The Distributed Cache service provides caching features in SharePoint Server The microblog features and feeds rely on the Distributed Cache to store data for very fast retrieval across all entities. The Distributed Cache service is built on Windows Server AppFabric, which implements the AppFabric Caching service. Windows Server AppFabric installs with the prerequisites for SharePoint Server Any server in the farm running the Distributed Cache service is known as a cache host. A cache cluster is the group of all cache hosts in a SharePoint Server 2013 farm.

Create and Configure Web Applications and Site Collections

46 | SharePoint Saturday St. Louis 2013 Provision and Configure Web Applications This objective may include but is not limited to: Create managed paths Configure HTTP throttling Configure List throttling Configure Alternate Access Mappings (AAM) Configure an authentication provider Configure SharePoint Designer settings

47 | SharePoint Saturday St. Louis 2013 Create and Maintain Site Collections This objective may include but is not limited to: Configure Host header site collections Configure self-service site creation Maintain site owners Maintain site quotas Configure site policies Configure a team mailbox

48 | SharePoint Saturday St. Louis 2013 Manage Site and Site Collection Security This objective may include but is not limited to: Manage site access requests Manage App permissions Manage anonymous access Manage permission inheritance Configure permission levels Configure HTML field security

49 | SharePoint Saturday St. Louis 2013 App Permissions One App site collection per Web Application You can assign an App site collection from one Web App to another Web App Farm administrators can determine whether users can purchase apps from the SharePoint Store. This setting is at the web application scope. If users cannot purchase apps, they can still browse the SharePoint Store, and request an app. Farm administrators and the App Catalog site owner can view and respond to app requests (either in CA or in the App site collection)

50 | SharePoint Saturday St. Louis 2013 HTML Field Security In SharePoint Server 2013, content authors can insert an iframe element into an HTML field on a page. This lets content authors embed dynamic content from other sites, such as videos or map directions. By default, certain trusted external domains are already approved for use in iframes. Site collection administrators can customize the field security settings by changing the default trusted external domains. They can also allow content authors to insert iframes for any external domain, or prevent them from inserting iframes on any page. To change the field security settings for a site collection, click HTML Field Security on the Site Settings page. (From us/library/jj219688(office.15).aspx) us/library/jj219688(office.15).aspx

51 | SharePoint Saturday St. Louis 2013 Manage Search This objective may include but is not limited to: Manage result sources Manage query rules Manage display templates Manage Search Engine Optimization (SEO) settings Manage result types Manage a search schema

52 | SharePoint Saturday St. Louis 2013 SEO Settings New SEO settings allow you specify meta tags in your pages as well as create “canonical” URLs (which uniquely identify your page in search engine indexes). You can add SEO tag values to your publishing pages in the ribbon (which will get added within the publishing pages as tags). You can manage SEO settings from the Site Settings page.

53 | SharePoint Saturday St. Louis 2013 Manage Taxonomy This objective may include but is not limited to: Manage site collection term set access Manage term set navigation Manage topic catalog pages Configure custom properties Configure search refinement Configure list refinement

54 | SharePoint Saturday St. Louis 2013 Topic Catalog Pages Category pages and catalog item pages are page layouts that you can use to show structured content consistently across a site. They are often used when displaying catalog content on a site that uses managed navigation. This saves you from having to create many individual pages for content that you want to show in the same manner across your site. You can assign a category page or a catalog item page to all terms in a term set, or to specific terms in a term set. To assign a category page and a catalog item page to a term, go to the Term Store Management Tool page, and click on the TERM-DRIVEN PAGES tab.

Maintain a Core SharePoint Environment

56 | SharePoint Saturday St. Louis 2013 Monitor a SharePoint Environment This objective may include but is not limited to: Define monitoring requirements Configure performance counter capture Configure page performance monitoring Configure usage and health providers Monitor and forecast storage needs

57 | SharePoint Saturday St. Louis 2013 Tune and Optimize a SharePoint Environment This objective may include but is not limited to: Plan and configure SQL optimization Execute database maintenance rules Plan for capacity software boundaries Estimate storage requirements Plan and configure caching Tune network performance

58 | SharePoint Saturday St. Louis 2013 Troubleshoot a SharePoint Environment This objective may include but is not limited to: Establish baseline performance Perform client-side tracing Perform server-side tracing Analyze usage data Enable a developer dashboard Analyze diagnostic logs

Q & A

60 | SharePoint Saturday St. Louis 2013 Housekeeping Follow SharePoint Saturday St. Louis on and hashtag #spsstl Play “Sponsor Bingo” to register for your chance to win one of the many great giveaways at the end of the day Schedule and evaluate each session you attend via our mobile app that can be used across devices at azurewebsites.nethttp://spsaturday. azurewebsites.net

Thanks to Our Sponsors!