SharePoint Farm Solutions

A farm solution is a special kind of code set used in SharePoint. Some items to be aware of:

-          It is used as a server side code which runs against the SharePoint server side object model.

-          It is only available for an on-premise deployment.

-          It is used for branding solutions, central administration customizations, application pages, custom services and timer jobs, etc.

-          A farm solution is deployed with:

Add-SPSolution   to upload the package

Install-SPSolution to deploy the solution package

Video on SharePoint Farm Solutions:

SharePoint Solution Package

A solution package is a deployment mechanism for code in regard to SharePoint.

-          The package allows for the reuse, deployment and versioning of code.

-          The package is a set of files that has a manifest that contains the needed installation instructions.

-          The package is a *.cab file with a *.wsp extension.

Note: sometimes it’s best to change the extension to a .zip so that the contents of the .wsp can be viewed.

-          The solution package can contain:

o   Features definitions

o   Images

o   Assemblies

Video on SharePoint Solution Packages:

Registering a New App Principal

Five pieces of information are needed to register an app principal used by a cloud-hosted SharePoint app. Navigate to http://<SharePointWebsite>/_layouts/15/AppRegNew.aspx on the farm then:

ClientID – identifying GUID for the app. Example: b044e104-7de2-4a05-aacf-63119009c55e

Client Secret – base64 encoded string which encrypts and decrypts messages between Windows Azure Access Control Service (ACS). Example: xyZpG0AgVIJfch6ldu4dLUlcZyysmGqBRbpFDu6AfJq=.

Title – caption that appears for a registered app principal. Example: KMO Video Uploader

App URI – base URL used to access the cloud-hosted app. Example: www.kmo.name

Redirect URL – optional items for a landing page SharePoint can use for additional requests (example a callback to another site for information the app was need). Must use https:// Example: https://www.kmo.name/RedirectAccept.aspx

Video is here:

OAuth and SharePoint Overview

The following are some quick bullet points that review OAuth:

OAuth – Internet protocol for authenticating apps and authorizing such apps – to access content on behalf of a specific user.

OAuth – allows SharePoint 2013 and greater versions to typically authenticate a cloud hosted app – which is calling to a SharePoint site – from across a network and to establish an identity for the app.

SharePoint 2013 and greater use OAuth to authenticate apps and establish app identity.

Windows Azure Access Control Services (SCS) is a requirement for using OAuth.

Video is here:

SharePoint Designer – Why Not for End Users

The following are my core list of items why end-users should not have SharePoint Designer installed:

1)      Powerful tool

2)      Need owners access to fully utilize

3)      Spent a lot of time on governance and want governance to stay intact

4)      Designer can make master page and page layout changes

5)      Don’t want end users – creating workflows

6)      If SharePoint Designer is installed on one end users PC – others will follow (need governance then just on using SharePoint Designer)

7)      Delete site easily

8)      Training issues (keeping up training users with basics)

9)      Corrupt site easier and break it with just a chance of some tags

10)   Outside scope of many job titles – end users shouldn’t be pseudo developers/coders

 

See Video:

SharePoint 2016 - Deprecated Items

The following are some key SharePoint 2016 that have been deprecated.

Note: Deprecated doesn’t mean un-available anymore it just means the functionality will not be updated.

1)      Tags and notes

2)      Excel Services – lose functionality when one upgrades from SharePoint 2010 to 2016

(Part of Excel online in Office Online Server)

3)      SQL Server Express

4)      SharePoint Foundation

5)      AppFabric (used in newsfeeds) – provides caching services that are distributed

See Video:

SharePoint Search Planning

SharePoint Search Planning

The following are some core search planning items to consider and plan for:

·         Where is the information located to be crawled (file share, SharePoint, other location)?

·         What content sources need to be set-up?

·         If full or incremental crawls are utilized what are the schedules?

·         Will continuous crawl be utilized?

·         What words will be utilized in a best bet

·         Who will monitor search to ensure that crawls are running successfully?

·         When and where will reports on search usage be run and placed?

View Video: