Tuesday, October 25, 2016

Waiting for Resources? – What happens when you provision a new Project Web Access site

Waiting for Resources? – What happens when you provision a new Project Web Access site

One problem I have seen a few times is the Project Web Access site provisioning running into issues.  If it fails completely then the error messages are pretty good – and you can generally resolve the issue and re-try and everything will be good.  
However, what do you do when it just sits on “Waiting for Resources” and nothing happens?  The quick answer is that this relies on the SharePoint Timer Service and a couple of Shared Service Provider services that can be viewed through Timer Job Definitions (Shared Services Timer Job and Project Server Synchronizing Job for ‘SharedServices1’ – or whatever yours is called). 
If these are not running then you will be “Waiting for resources” for a very long time!  Also there could be multiple versions of the timer jobs if you have multiple SSPs so it can get confusing, particularly as the first one does not differentiate by name.  (Clue – the JobId in the URL for the job is the Id of the timer job row in the Objects table in SharePoint_Config database, and the Properties column from this row will lead you to the Guid of the TargetSharedResourceProvider – which will be the Id of the Shared Services Provider also in the same table.)
So to dig a little deeper so you can understand where it might be stuck I’ll explain what is going on in the background which hopefully will help you find what is stopping it from working.
So, step 1 – you have been on the Create a Project Web Access Site page (CreatePWA.aspx) and entered all the details, and it goes back to the Manage Project Web Access Sites (ManagePWA.aspx) page and just sits there.  At that point a row has been added to the MIPScheduledJob table in the SharedService1_DB (your database name may vary – this is the default).  This is a pre-synchronizing job for the site, and is added to the database by the account running the Shared Services Provider application pool.
Step 2.  The Shared Service Timer Job picks up the row from this database table and adds a row to the SharePoint_Config database Objects table.  In the properties field of this table is some XML describing the site to be built, database names etc.  This timer job will run as the account of the farm administrator (i.e. the account running the OWSTIMER service)
Step 3.  The Project Server Synchronizing Job for ‘SharedServices1’ sees this row and actions it by creating the site, creating the database and then configuring the instance of PWA.  If everything is working you see the status change on the ManagePWA page as these different stages are processed, and finally it will say Provisioned!  Again, this timer service runs as the farm administrator.
Waiting for resources will be seen until the early stages of step 3.
So check all your services are running and your timer jobs are present and enabled and all should be good.
One other workaround that generally gets things moving again is to create  a new Shared Services Provider – which will then create new timer jobs and overcome any underlying issues.  The web applications can then be associated with the new SSP, the new SSP can be made the default if you are not using the old one for anything else, and the old one could be deleted.
I mention the databases here on the condition that you can look – but don’t touch! 
Hope this help,

Friday, October 21, 2016

Install and Configure Workflow For SharePoint Server 2013

Install and Configure Workflow For SharePoint Server 2013

The only platform available when you first install SharePoint Server 2013 is the SharePoint 2010 Workflow platform. The SharePoint 2013 Workflow platform and the Project Server platform require additional steps.

The SharePoint 2010 Workflow platform installs automatically when you install SharePoint Server 2013. The SharePoint 2013 Workflow platform requires the Workflow Manager and must be installed separately and then configured to work with your SharePoint Server 2013 farm.

The Workflow Manager is a new kind of application server that hosts/manages workflow execution. The SharePoint 2013 workflow is based on the .Net Framework 4.0.

Now we will learn the procedure for installing and configuring the workflow.

In the first step open the Web Platform Installer and add the Workflow Manager 1.0.

Add the Workflow Manager

Click on the "Install" button;

Install button

Then "Continue".

Install continue

The next step is the Workflow Manager configuration wizard. We have three options here to configure the workflow. Here I am selecting the second option "Configure Workflow Manager with custom setting".

workflow manager configuration

Enter the credentials here:


Click on "Next".

Next Step

Enter the certificate credentials.

certificate credentials

Service Bus Configuration steps:

Service Bus Configuration

Configure the certificates,

Configure the certificates

Get the summary of the configuration.

summary of the configuration

Get the PowerShell Commands for the configuration.

PowerShell Commands

Configuration progress window:

Configuration progress window

And we have the option for updating the configuration.

update the configuration

Looking goodAfter the preceding steps, open the IIS and we can see the new WorkflowManagement Site has been created.

open the IIS

We need to check that the new service Workflow Manager has been started.

new service Workflow manager

The new tables are created in the SQL Server.

tables created in the SQL Server

Run the following command in the SharePoint 2013 Management Shell:
Register-SPWorkflowService -SPSite http://sptest/ -WorkflowHostUri http://sptest:12291 -AllowOAuthHttp 

Run the command in SharePoint Management Shell

We have now completed the workflow configuration, open the SharePoint designer and create a new workflowYes here we have the options for creating a SharePoint 2013 Workflow.
completed the workflow configuration

That it!

Hope this help,

“Sharepoint 2013 Workflow - Project Server” not showing in SharePoint Designer

“Sharepoint 2013 Workflow - Project Server” not showing in SharePoint Designer

You have to use a 'Site Workflow' in order for the option to appear for Project Server.

Hope this help,

Failed to register because the farm or partition is already registered with a workflow service

Failed to register because the farm or partition is already registered with a workflow service

I was recently training a colleague on administering SharePoint and he was encountering issues with being unable to publish SharePoint Workflows after he applied an SSL certificate to his SharePoint site.

Well, immediately after checking his IIS bindings and his AAM settings, the next thing I thought of was that he would have to re-register his SharePoint site with the Workflow Service.

Of course, he ran the following command:

Register-SPWorkflowService -SPSite "https://spse/sites" -WorkflowHostUri "https://spse:12290" 

But he received the following error message: 
Failed to register because the farm or partition is already registered with a workflow

Well, fortunately, there was an easy solution to this!!  All he had to do was run the command with the -Force parameter:

 Register-SPWorkflowService -SPSite "https://spse/sites" -WorkflowHostUri "https://spse:12290" -Force

That was all that was needed to resolve his issue!! 

Hope this help,

Monday, October 17, 2016

Studying for Exam 70-331: Core Solutions of Microsoft SharePoint 2013

Studying for Exam 70-331: Core Solutions of Microsoft SharePoint 2013

This post is a study guide for exam 70-331: Core Solutions of Microsoft SharePoint 2013. I passed this exam on the 14th October 2016 with a score of 843/1000. Yay!🙂

When I do Microsoft Certification exams I like to do everything I can – read the books, read the articles, practice exams, online prep exams… anything at all that can help! But 70-331 is still pretty new, and while there seems to be plenty of sites out there trying to sell their information, I wanted a 
set of reliable sources that match the content of the exam. Hence this post.

The exam itself has 53 questions with a total score of 1,000 possible. The pass mark is 700. The format of the exam is:
  1. 43 general SharePoint 2013 questions comprising multiple choice, single choice, and do-things-in-the-right-order question types
  2. 2 case studies with varying numbers and types of questions i.e. 8, 10, 12, etc.
There is a focus on SharePoint Online and Office 365 integration with on-premise SharePoint farms, particularly in the case studies, so it is worth focusing some attention in this area (which I quickly found out I was woefully underprepared for :/). There is more information for Hybrid environments on TechNet under Hybrid for SharePoint Server 2013, and I would strongly advise understanding all the content available on this subject. See the Case Studies section in part 2 of this post for more information.

Articles are sourced from TechNet and Microsoft blogs, with some additional content added where I felt it helped with my study.

The 70-331 Microsoft information page has the “Skills Being Measured” section, which has a list of the exam topics being covered. I will be working my way through the sections of the skills list and collecting links to relevant references that provide information on the topic. Hoping this is useful to other people too! These articles were gleaned from Bing using the search terms: “site:technet.microsoft.com -site:social.technet.microsoft.com sharepoint 2013 [keywords]”, replacing [keywords] with the content I was looking for. This searches only TechNet, ignores social.technet, includes sharepoint 2013, plus my keywords.

Design a SharePoint Topology (20-25%)

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

design an intersite navigational taxonomy:

design an site columns and content types:

design keywords:


  1. Key powershell command from this article is:
    $searchApp = Get-SPEnterpriseSearchServiceApplication
    Import-SPEnterpriseSearchThesaurus -SearchApplication $searchApp -Filename <Path>
best bets (NOTE now referred to as promoted results):

managed properties:

  1. Crawled property: value or attribute extracted from an indexed item, document, etc. Crawled properties must be mapped to managed properties to be searchable.
  2. Managed property: a user-searchable property that can be mapped to one or more crawled properties.
  3. Office 365 and Site Collections allows you to create new management properties for Text and Yes/No field types only. Use existing unused managed properties if you want a property with a different type.

plan information management policies:

plan managed site structure:

plan term sets:

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

plan application pools:

plan web applications:

plan for software boundaries:

plan content databases:

plan host-header site collections:
Powershell commands: Set-SPSiteURLRemove-SPSiteUrlGet-SPSiteUrl
plan zones:
Claims-based authentication: supports multiple authentication providers on a single zone. You can also use multiple zones.
Classic mode: discouraged. Only one type of authentication per zone. Only supports windows authentication methods.
alternate access mapping:
“Alternate access mappings are automatically created when you create a zone.”
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
design a storage architecture:
“Dataset describes the volume of content stored in the system and how it can be distributed in the data store”
configure basic request management:
“Request manager has two supported deployment modes: Dedicated and Integrated”
“Request Manager has two configurable parts: General settings and Decision information”
Powershell: Set-SPRequestManagementSettings, Set-SPLogLevel “Request Management” –TraceSeverity Verbose
define individual server requirements:
  1. Minimum hardware requirements: 8GB RAM, 64-bit 4 cores, 80GB system drive
  2. Minimum OS requirements: Windows 2008 R2 with SP1 standard/enterprise/datacentre OR Windows 2012 standard/datacentre
  3. Minimum SQL version: 64-bit SQL 2012 OR 64-bit SQL 2008 R2 with SP1
define service topologies:
Tips: Scale out with new index partitions every 10Million items
To add an index partition:
  1. Start the search service instance on the new server
  2. Clone the search topology
  3. Add the new index component and associate it with a partition
  4. Active the (cloned) topology
plan server load balancing:
plan a network infrastructure:
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
evaluate service offerings:
  1. Small Business service family (Maximum of 25 users)
    Office 365 Small Business, Office 365 Small Business Premium
  2. Midsize service family (Maximum of 300 users)
    Office 365 Midsize Business
  3. Enterprise service family
    Office 365 Enterprise E1/E3/K1, Office 365 Education A2/A3/A4, Office 365 Government G1/G3/G4/K1
plan service applications:
plan site collections:
plan customizations and solutions:
plan security for SharePoint Online:
Tip: for Single Sign-On, the New-MsolFederatedDomain adds a new single sign on domain to Microsoft Online Services and configures the relying party trust settings between the on-premises AD FS server and Microsoft Online Services.
Powershell: Connect-SPOService
plan networking services for SharePoint Online:

Plan Security (20-25%)

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
plan and configure Windows authentication:
plan and configure identity federation:
Steps to config AD FS with the web application as a relying party:
  1. Configure AD FS for a relying party
  2. Configure claim rules in AD FS
  3. Export a token signing certificate from AD FS
  4. Import the AD FS token signing certificate in SharePoint
  5. Define identity and role claim mappings in SharePoint
  6. Add a new authentication provider (powershell New-SPTrustedIdentityTokenIssuer)
  7. Configure SAML claims-based authentication in SharePoint CA
  8. Enable SSL for the SharePoint web app in SharePoint CA
configure claims providers:
configure site-to-site (S2S) intra-server and OAuth authentication:
plan and configure anonymous authentication:
configure connections to Access Control Service:
App permission request scopes: SPSite, SPWeb, SPList, Tenancy
App permission requests: Read-Only, Write, Manage, Full Control
App authorization policies: User and app policy, App-only policy, User-only policy
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
plan and configure SharePoint users and groups:
plan and configure People Picker:
The stsadm.exe command is used to configure the people picker at the zone level
plan and configure sharing:
plan and configure permission inheritance:
plan and configure anonymous access:
plan web application policies:
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
plan and configure security isolation:
Security Tip: use a separate domain to host SharePoint Apps because some browsers don’t support sub-domain isolation i.e. *.contosoapps.com instead of apps.contoso.com
plan and configure services lockdown:
plan and configure general firewall security:
plan and configure antivirus settings:
plan and configure certificate management:
Tip: SharePoint CA or PowerShell can be used to manage trust certificates. In the SharePoint CA it is located via Security, General Security, Manage Trust.
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
plan rights management:
plan and configure delegated farm administration:
Server or farm level: Farm Administrators group, Windows Administrators group
Shared services level: Service application administrators, Feature administrators
Web application level: (web policy via CA)
Site level: Site collection administrators, Site owners
plan and configure delegated service application administration:
Tip: Assigning administrators can be done via SharePoint CA or Powershell
User Profile service application features: Manage Profiles, Manage Audiences, Manage Permissions, Retrieve People Data for Search Crawlers, Manage Social Data
plan and configure managed accounts:
plan and configure blocked file types:
Tip: Set at the web application level. Use SharePoint CA, Security, General Security, Define blocked file types
plan and configure web part security:

Install and Configure SharePoint Farms (20-25%)

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
identify and configure installation prerequisites:
  1. Minimum hardware requirements: 8GB RAM, 64-bit 4 cores, 80GB system drive
  2. Minimum OS requirements: Windows 2008 R2 with SP1 standard/enterprise/datacentre OR Windows 2012 standard/datacentre
  3. Minimum SQL version: 64-bit SQL 2012 OR 64-bit SQL 2008 R2 with SP1
implement scripted deployment:
Tips: Create an arguments file PrequisiteInstaller.Arguments.txt and save to the same directory as PrerequisiteInstaller.exe
Command line: PrerequisiteInstaller.exe /IDFX: “\\<path>\Windows6.1-KB974405-x64.msu” /sqlncli: “\\<path>\sqlncli.msi” /Sync: “\\<path>\Synchronization.msi
Powershell: New-SPConfigurationDatabase
implement patch slipstreaming:
Tip: Extract patches into the Updates folder to create a slipstream version
plan and install language packs:
Tip: The SharePoint 2013 Configuration Wizard must be run after installing language packs
plan and configure service connection points:
plan installation tracking and auditing:
Plan and configure farm-wide settings.
This objective may include but is not limited to: configure incoming and outgoing email, 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
configure incoming and outgoing email:
Tips: Only SharePoint CA can be used to configure outgoing email – Powershell cannot be used.
Requirements: Exchange Server 2013, User Profile Synchronisation, App Management Service Application, SSL configured for the default zone
plan and configure proxy groups (aka Service Application Connection Group):
Using SharePoint CA: Application Management, Service Applications, Configure service application associations, Web applications
configure SharePoint Designer settings:
Tips: Configures SharePoint Designer support for a web application. Valid settings are AllowDesigner, AllowMasterPageEditing, AllowRevertFromTemplate, ShowURLStructure
plan and configure a corporate catalog (aka app catalog):
Tips: Increase security by creating a separate domain name. This limits unauthorised access and reduces cross-site scripting attacks, and is known as app isolation.
Configuration steps: Set up wildcard DNS domain, create wildcard certifications, configuration subscription settings and the app management service, create app URLs
Overview of steps to configure an environment for apps for SharePoint:
  1. Purchase a domain for apps (contosoapps.com)
  2. Create a forward lookup zone for apps (contosoapps.com)
  3. Create a CNAME alias from the app domain to the SharePoint domain (*.contosoapps.com -> sharepoint.contoso.com)
  4. Create a wildcard SSL certificate for the new app domain (https://*.contosoapps.com)
  5. Configure the Subscription Settings service application by using Powershell
  6. Configure the App URLs in CA (domain: contosoapps.com prefix: apps)
Tips: Set at the web application level, only one app catalog per web app. Only available via SharePoint CA
SharePoint CA: Apps, App Management, Manage App Catalog
configure Office Web Apps integration:
Tips: Requires claims-based authentication
Licensing: View-only (free), Edit and view (editing license required via Volume Licensing program)
configure Windows Azure workflow server integration:
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
plan and configure a search topology:
Search components are:
  1. Analytics processing component
  2. Content processing component
  3. Crawl component
  4. Search administration component
  5. Query processing component
Powershell: Get-SPEnterpriseSearchServiceInstance, Start-SPEnterpriseSearchServiceInstance, Get-SPEnterpriseSarchServiceApplication, Get-SPEnterpriseSearchTopology, Get-SPEnterpriseSearchComponent, New-SPEnterpriseSearchTopology, New-SPEnterpriseSearchAdminComponent, New-SPEnterprseSearchAnalyticsProcessingComponent, New-SPEnterpriseSearchContentProcessingComponent, New-SPEnterpriseSearchCrawlComponent, New-SPEnterpriseSearchQueryProcessingComponent, Set-SPEnterpriseSearchTopology
plan and configure content sources:
plan and configure crawl schedules:
plan and configure crawl rules:
Crawl configurations:
  1. Exclude all items in this path (refine with Exclude complex URLs that contain question marks(?))
  2. Include all items in this path (refine with Follow links on the URL without crawling the URL itself, Crawl complex URLs, Crawl SharePoint content as http pages)
  1. Use the default content access account
  2. Specify a different content access account
  3. Use client certificate for authentication
  4. Use form credentials
  5. Use cookies
  6. Use anonymous access
plan and configure crawl performance:
“In SharePoint Server 2010, host distribution rules are used to associate a host with a specific crawl database. Because of changes in the search system architecture, SharePoint Server 2013 does not use host distribution rules. Instead, Search service application administrators can determine whether the crawl database should be rebalanced by monitoring the Databases view in the crawl log”
plan and configure security trimming:
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
configure proxy settings for managed service applications (aka proxy groups):
The following service applications can be published:
  1. Business Data Connectivity
  2. Machine Translation
  3. Managed Metadata
  4. User Profile
  5. Search
  6. Secure Store
To publish and consume service applications across farms:
  1. Exchange trust certificates between the farms
  2. On the publishing farm, publish the service application
  3. On the consuming farm, set the permission to the appropriate service applications
  4. On the consuming farm, connect to the remote service application
  5. Add the shared service application to a Web application proxy group on the consuming farm
  6. Configure server-to-server authentication between the publishing and consuming farms
configure content type hub settings:
configure sharing term sets:
plan and configure content type propagation schedules:
configure custom properties:
configure term store permissions:
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
configure a UPA application:
UPA databases are:
  1. Profile database
  2. Synchronisation database
  3. Social tagging database
set up My Sites and My Site hosts:
Tips: Naming options for site collections are User name (do not resolve conflicts), User name (resolve conflicts by using domain_username), Domain and user name (will not have conflicts)
Tips: User permissions for My Sites are Create Personal Site, Follow People and Edit Profile, and User Tags and Notes
  1. Create a My Site host site collection
  2. Add a wildcard inclusion managed path to the web application
  3. Connect the web application to service applications
  4. Enable self-service site creation for the web application
  5. Configure My Site settings for the User Profile service application
  6. Enable the User Profile Service Application – Activity Feed Job
Tip: The maximum number of site collections in a My Sites content database is 10,000
configure social permissions:
  1. In CA, Application Management, Service Applications group, click Manage Service Applications
  2. Set the User Profile service application
  3. In the Operations group, click Manage
  4. On the Manage Profile Service page, in the My Sites Settings section, click Manage Following
  5. Configure Max number of followed people, max number of followed docs, max number of followed sites
  6. Click OK
plan and configure sync connections:
configure profile properties:
configure audiences:

Create and Configure Web Applications and Site Collections (15-20%)

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
create managed paths:
SharePoint CA: Application Management, Manage web applications, Managed Paths
Powershell: New-SPManagedPath
configure HTTP throttling:
The Request Manager can be configured to prioritize requests and throttle requests (such as when requests are from bots)
Three major components of Request Manager:
  1. Request Routing
  2. Request Throttling and Prioritizing
  3. Request Load Balancing
configure List throttling:
Options to assist with large lists include:
  • Creating SharePoint indexed columns (up to 20 columns)
  • Creating filtered views based on column indexes
  • Organising items into folders
  • Controlling the display of data on the page (item limits per page, use the preview pane, use group by)
  • Using the daily time window
  • Using offline synchronisation
  • Use the search box
  • Using Access with SharePoint products (Access App)
  • Using indexed and fallback queries
  • Using the document center site
  • Using external data
configure Alternate Access Mappings (AAM):
Powershell: Get-SPSiteUrl, Set-SPSiteUrl, Remove-SPSiteUrl
configure an authentication provider:
Supported authentication types: Windows (NTLM, Kerberos, Basic, Digest), Forms (AD DS, database, LDAP), SAML
Configure: Central Admin, Web Application, Authentication Providers, Zone, Edit Authentication
configure SharePoint Designer settings:
Tips: Configures SharePoint Designer support for a web application. Valid settings are AllowDesigner, AllowMasterPageEditing, AllowRevertFromTemplate, ShowURLStructure
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
configure Host header site collections:
Powershell: Get-SPSiteUrl, Set-SPSiteUrl, Remove-SPSiteUrl
configure self-service site creation:
maintain site owners:
maintain site quotas:
configure site policies:
configure a team mailbox:
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
manage site access requests:
  1. In Site Settings, Users and Permissions, select Site permissions
  2. Click Access Request Settings
  3. Click Allow Access Requests
  4. Enter an email address to send requests to and click OK
manage App permissions:
manage anonymous access:
manage permission inheritance:
configure permission levels:
configure HTML field security:
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
manage result sources:
Tips: Search experiences OOTB are Everything, People, Conversations and Video.
Tips: Result sources OOTB are Conversations, Documents, Items matching a content type, Items matching a tag, Items related to current user, Local People Results, Local Reports and Data Results, Local SharePoint Results, Local Video Results, Pages, Pictures, Popular, Recently changed items, Recommendations, Wiki
Tips: Result source protocols are Local SharePoint, Remote SharePoint, OpenSearch 1.0/1.1, Exchange
Tips: Create a result source via SharePoint CA using Application Management, Manage service application, Search service application, Queries and Results, Results Sources
manage query rules:
Tips: Query rules can be configured for one or more result sources, and over a particular time period.
manage display templates (aka Best Bets and Visual Best Bets):
manage Search Engine Optimization (SEO) settings:
manage result types:
manage a search schema:
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
manage site collection term set access:
manage term set navigation:
manage topic catalog pages:
configure custom properties:
configure search refinement:
configure list refinement:

Maintain a Core SharePoint Environment (15-20%)

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
define monitoring requirements:
Tips: Load Test Kit (LTK) with Visual Studio Team System (VSTS) for load testing of SharePoint farms
configure performance counter capture:
configure page performance monitoring:
Tip: The SharePoint Developer Dashboard lets you analyse issues with page performance
configure usage and health providers:
monitor and forecast storage needs:
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
plan and configure SQL optimization:
Tips: 0=server decides, 1=no parallel plan generation, n=number of processor cores to use, max+=use all. Should be set to 1.
execute database maintenance rules:
plan for capacity software boundaries:
estimate storage requirements:
plan and configure caching:
Tips: There are four types of cache:
  1. BLOB cache
  2. Page output cache profiles
  3. Object cache
  4. Anonymous search results cache
Powershell: Get-SPWebApplication
Tip: To change the Distributed Cache configuration and maintain the cache, you need to:
  1. Run the Stop-SpDistributedCacheServiceInstance-Graceful command
  2. Run the Set-CacheHostConfig command
  3. In CA, start the Distributed Cache service instance
Powershell: Update-SPDistributedCacheSize, Stop-SPDistributedCacheServiceInstance, Remove-SPDistributedCacheServiceInstance
tune network performance:
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
establish baseline performance:
perform client-side tracing:
perform server-side tracing:
Powershell: Set-SPDiagnosticConfigSet-SPLogLevel, Clear-SPLogLevel
analyze usage data:
enable a developer dashboard:
analyze diagnostic logs:

Hope this help,