Sharepoint - An Introduction

ANOOP [email protected]

Contents

Platform & Architecture

Accounts

Windows Server, SQL Server & Email Server

Configuring Farm

Licensing

Workflow Server

Office 365

Web Apps, Site Collections & Webs

Services Apps

Overview

Share

Access anywhere

Sync

Create

Find

SharePoint

ManageBuild

DiscoverOrganize

SHARE

• Web Application Framework• Collaboration – lists,

workflows, calendars, doc libraries

• Social Computing• Enterprise Search• Content Management• Business Intelligence • Electronic Forms

Server Roles

Exchange Server

SQL Server 2012

Windows 8 Hyper V VM

Windows Server 2012 or 2008

SHARE

• Client OS not supported• W8 client Hyper – V

supported (VM)• Dedicated SQL Server• Exchange Server –

Calendaring, Mail Server, Contact Manager

SharePoint Architecture

The SharePoint platform is a flexible, n-tier service-oriented architecture (SOA). It can be scaled down to operate entirely from one machine, or scaled up to be managed across hundreds of machines.

Small Example

NOTE: This example includes all services, not just search since it’s unlikely you would have a small services only search farm.

Target: 10 Million Items

Query

Crawl

Content Processing

Analytics

Admin

Index

Medium Example

Target: 40 Million Items

Query

Crawl

Content Proc.

Analytics

Admin

Index

Large Example Query

Crawl

Content Processing

Analytics

Admin

Index

Target: 100 Million Items

SharePoint Architecture

Farms - A SharePoint farm is a logical grouping of SharePoint servers that share common resources.

Web applications - Web Applications (WAs) are top-level containers for content in a SharePoint farm, and are typically the interface through which a user interacts with SharePoint.

Site collections - A site collection is used to provide a grouping of 'SharePoint Sites'.

Service applications - Service Applications (SAs) provide granular pieces of SharePoint functionality to other web and service applications in the farm. 

Licensing Internal Users: Users who are the licensee’s or

its affiliates’ employees and on-site agents and contractors.

External Users: Users who are not the licensee’s or its affiliates’ employees or on-site agents or contractors.

Intranet: Website hosting content, information, or software that is accessible inside the firewall to internal users only.

Extranet: Website hosting content, information, or software that is accessible inside the firewall to internal users and named external users only.

Internet: Website hosting content, information, or software that is publicly accessible to all users (internal and external).

Licensing Scenario A : Intranet Server: One SharePoint Server 2013 license per

running instance of the software. Internal Users: One CAL/user.

Licensing Scenario B : Extranet Server: One SharePoint Server 2013 license per running

instance of the software. Internal Users: One CAL/user. External Users: SharePoint CALS are not required; the

server license permits external user access.

Licensing Scenario C : Internet Server: One SharePoint Server 2013 license per running

instance of the software. Internal Users: CALs are not required. External Users: CALs are not required.

End users can manage licenses for apps they purchase through the SharePoint Store

Farm admins can also add themselves as a license manager for an app

Users will be able to see a list of every app they’ve purchased and manage the licenses for it

Farm admins can decide whether to let users purchase apps

They also have a mechanism to approve requests to purchase apps

Managing Licenses

Office 365Communication, Collaboration & Productivity tools for businesses and users

Enterprise-grade cloud services

Comprehensive tools to do your best work

What is Office 365?

• SharePoint Online

• OneDrive• Yammer

• Rich client• Web client• Apps

• Lync Online• Exchange Online

• Archiving• Encryption

EmailReal-time

Communication

CollaborationOffice

• Commercial SW + Services

• Hosted versions of MS Products

• Offered in different plans

• Single sign on with Azure AD

• Business users can subscribe to O365 services

Hosting: Cloud vs. SharePoint

Provider Hosted Apps SharePoint Hosted Apps

Preferred hosting model for almost all types of apps

Good for smaller apps & resource storage

Full power of web – choose your infrastructure & technology

SharePoint-based; no server-side code

May require your own hosting Automatically hosted in SharePoint

May require you own handling of multitenancy & permission management

Inherent multitenancy & isolation

SP App Hosting OptionsSharePoint

The app is hosted in the cloud. Windows Azure and SQL Server Azure components are provisioned automatically when an app is installed. (Available for SharePoint Online only)

Existing sites and services

App web (optional)

Existing sites and services

App web

The app and all resources are hosted in your organization’s SharePoint farm. relies on client side technologies. Your IT organization supports the app.

The app and all resources are hosted by the provider in any environment suitable for the app.

Auto-hosted

SharePointhosted

Existing sites and services

App web (optional)

Windows Azure & SQL Azure

Oauth + REST or client object models

Oauth + REST or client object models

Services that are deployed are named service applications.

A resource that can be shared across sites throughout a farm

Accessed by users through a hosting web application Some services can be shared across farms Individual services can be configured independently Third parties can add services.  Logical layer that makes the back-end infrastructure

available to the farm.

Service applications in SharePoint 2013

Accounts Service Accounts – Needed for a base install of a SP

farm. Everyone has a different way of setting them up How many, How to name, What permissions Level of security : As many as 10 – 15 accounts.

Managed Accounts MSA’s allow you to create an account in Active Directory that is tied to

a specific computer.. That account has its own complex password and is maintained

automatically.  Managed accounts are used for less maintenance and ease of use. AD Domain Policies to automatically reset passwords while meeting

the requirements established by policy.

Service Accounts SQL Server Accounts

SQL Admin SQL Service

SharePoint Server Accounts sp_Install sp_Farm sp_Admin sp_Sites sp_UserProfile sp_UserCode sp_Service sp_Search sp_SearchCrawler sp_Cache (If SharePoint 2013) sp_SuperUser sp_SuperReader

Service Application list : SP 2013 Access Service App Management Service - SP App licenses and permissions Business Data connectivity Service - brings external data into SP

and Office through the cloud and on-premises configurations Excel Services Machine Translation Services Managed Metadata Service - share content types across site

collection &webapp Search Service Secure Store Service – authorization service State Service - store temp data across HTTP requests in a SQL Server

DB User and Health Data Collection Service – troubleshooting SP

issues. User Profile Service - social networking + audiences + site support Visio Graphics Service - share and view Visio diagrams

Workflows Workflow is an automated process that helps people review a

file The person who needs the file reviewed, starts the workflow People are notified automatically to review the file And when everyone’s all done, a web page summarizes the

workflow Types

Approval workflow Collect Feedback workflow Collect Signatures workflow Disposition Approval (Expired content evaluation & deletion) Three-state (Active, Ready, Complete) Group Approval ( request change, approve, reject, or reassign approval

tasks) Translation Management (tracking the assignment of translation tasks)

Workflow Server Manages business processes Manages and monitors the state of activities in a

workflow. Facilitates the flow of information, tasks, and events Functions :

Verification of the current status: Check whether the command is valid

Determine the authority of users: Check if the current user is permitted to execute the task.

Executing condition script:  Evaluates condition script, if true task is executed and if not, triggers rollback.

Authentication Modes

Classic Authentication In classic-mode, SharePoint uses the Windows identity of the

user directly. 

Claims Authentication In claims-mode, SharePoint converts the Windows identity into a

claims-based identity token that it can pass to other services as appropriate.

Authentication Windows Authentication : Uses the Windows

infrastructure, providing support for NTLM, Kerberos, Anonymous, Basic, and Digest authentication.

Forms-Based Authentication: Utilizes a username and password HTML form that queries a membership provider in the backend.

SAML token based : Using an external identity provider that supports SAML and WS-Federation Passive profile.

Path based site collections With path-based site collections, the

differentiation between site collections is their path. http://portal.cybosol.com/sites/sharepointstuff http://portal.cybosol.com/teams/spprojects

Has a couple of limitations - long URLs, users http://portal.cybosol.com/sites/projecttracker http://projecttracker.cybosol.com

Host Header HNSC(Host Named Site Collection) allow you to

have site collections with different hostnames in the same web app

When you create the HNSC, you need to tell SharePoint which web app to put it in with the –HostHeaderWebApplication parameter using powershell

After the HNSC is created, you need to create a DNS record for it, pointing at the same place you point the DNS entries for your SharePoint farm.

Lot of flexibility in your SharePoint farm to scale and provide fancy URLs

Creating webapps Central Administration Control Panel Manage Web Applications New Set the following options – Authentication, IIS,

Application pool, Security, DB name When finished, new web application will be

created in the IIS Note the port number.

Creating site collection Central Administration Control Panel Application Management Create Site collections Change the default Web Application Set Title and Description Specify site address Choose template Set primary and secondary Site collection Admins Specify the Quota Template Review the settings and Finish.

Information Architecture Information architecture is really understanding

what we have now and how to change that. Knowing what and where the information is, along

with who needs access to it. Good IA achieves the following goals.

Sharepoint Governance Set of rules that help facilitate the use,

maintenance and operations of your SharePoint.

Set expectations and guidance for your team as well as the end users.

Should state what Sharepoint environments we will be using with a short description.

What goes in and what it is used for .

Summary

Centralized AdministrationCustomizableCollaborationSite ConsolidationSecurityEase of use

Thank You