viestinnän seminaari 8.11.2012 / sharepoint


Introduction to SharePoint 2013Arto RothTechnology ConsultantSalcom Learning Center


SharePoint 2013 Architecture In general model has stayed

same as in previous version Numerous platform level

improvements and new capabilities Shredded Storage SQL Improvements Cache Service Request Management Themes Sharing


Service applications in SharePoint 2013 New service applications available

and improvements on existing ones

Office Web Apps is no longer a service application

Web Analytics is no longer service application, it’s part of search


Enterprise Content Management eDiscovery capablities

Support for searching and exporting content from file shares

Export discovered content from Exchange and SharePoint

Team folders Seemless integration of

Exchange and SharePoint to provide best of both world and end user flexibility


Web Content Management Support the tools and

workflows designers use Variations & Content

Translation Search Engine

Optimization Cross Site Publishing Video & Embedding Image renditions Clean Urls Metadata navigation


Search New Search

architecture with one unified search

Personalized search results based on search history

Rich contextual previews


Mobile Classic and Contemporary

views for mobile browsers Automatic Mobile Browser

Redirection Target different designs

based on user agent string Office Mobile Web Apps

Excel PowerPoint Word

Push notifications


SP2013 System Requirements


Minimum Hardware Requirements

Processor: 64-bit, 4 cores RAM:

8 GB for production use 4 GB for developer or evaluation use

Hard disk: 80 GB free for system drive Maintain 2x free space as available RAM

Web tier

Application tier

Database tier

Web & Application Servers | Single Server Farms

Web servers with query component

Application server with:• Central Administration• Search administration

component• Crawl component

Database server with:• Central Administration

configuration and contentdatabases

• Farm content database• Search administration database• Crawl database• Property database

Load balanced or routed requests


Processor: 64-bit, 4 cores for “small” deployments 64-bit, 8 cores for “medium” deployments

RAM: 8 GB for “small” deployments 16 GB for “medium” deployments

Hard disk: 80 GB free for system drive SP Data Storage dependent on corpus

size, performance requirements, etc.

Web tier

Application tier

Database tier

Database Servers

Web servers with query component

Application server with:• Central Administration• Search administration

component• Crawl component

Database server with:• Central Administration

configuration and contentdatabases

• Farm content database• Search administration database• Crawl database• Property database

Load balanced or routed requests


Web & Application Servers Minimum Software Requirements 64-bit edition of Windows Server

2008 R2 Service Pack 1 (SP1) Standard, Enterprise, Data Center, or Web Server

Web Server (IIS) roleApplication Server role(s)

.NET 4 DGR Update KB 2468871

Information Protection & Control Client (MSIPC)

Windows Identity Foundation (WIF 1.0 and 1.1)

SQL Server 2008 R2 Native Client

Sync Framework Runtime v1.0 (x64)

.Net Framework version 4.0 Open Data Library (ODataLib)

Windows PowerShell 3.0

Preparation tool installs the following prerequisites:


Database ServersMinimum Software Requirements

64-bit edition of Microsoft SQL Server 2008 R2 Service Pack 1

64-bit edition of Windows Server 2008 R2 Service Pack 1 (SP1) Standard, Enterprise, Data Center, or Web Server


Plan Browser SupportCompatibility and Support Considerations


Browser Support MatrixBrowser Supported in 2013 Supported with limitations Not testedInternet Explorer 9 (32-bit)

X

Internet Explorer 8 (32-bit)

X


X


X

Internet Explorer 7 (both)

X

Mozilla Firefox (Latest version in-market)

X

Google Chrome (Latest version in-market)

X

Safari (Latest version in-market)

X


Setup ConsiderationsInstallation & Setup


Install The Bits – Follow the Basic Steps 1. Plan and Prepare; Verify hardware and software

requirements2. Install the required software updates on all farm servers 3. Install the SharePoint 2013 prerequisites on servers in

the application and Web tiers4. Install SharePoint 2013 on the application server and the

Web server5. Create and configure the SharePoint farm6. Provision service applications as needed7. Complete post-deployment tasks as required


Request Management


Request Management (RM) The purpose of the Request Management feature

is to give SharePoint knowledge of and more control over incoming requests

Having knowledge over the nature of incoming requests – for example, the user agent, requested URL, or source IP – allows SharePoint to customize the response to each request

RM is applied per web app, just like throttling is done in SharePoint 2010


RM – Goals RM can route to WFEs with better health, keeping

low-health WFEs alive RM can identify harmful requests and deny them

immediately RM can prioritize requests by throttling lower-

priority ones (bots) to serve higher-priority ones (end-users)

RM can send all requests of specific type, like search for example, to specific machines

Isolated traffic can help troubleshoot errors on one machine

RM can send heavy requests to more powerful WFEs


Machine Pool “Ignite”

RM Routing and Pools Routing rules route requests and are associated with

MachinePools MachinePools contain servers Servers use weights for routing – static weights and

health weights Static weights are constant for WFEs; health weights

change dynamically based on health scoresStatic Weight = 1Health Weight = 4

Static Weight = 1Health Weight = 4

Routing Rule #1Routing Rule #2…Routing Rule #n


RM Scenario – Health Based Routing A series of requests come in; one WFE is in poor

health, while two others are in good health. RM evaluates the following: Health information: { [WFE1, sick], [WFE2, healthy], [WFE3,

healthy] } Based on this RM routes most of the requests

among WFE2 and WFE3 It is still random routing, but greater weight is given to healthier

machines Alternatively the admin could remove WFE1 from

the routing pool, allow it to complete its requests then return it back to the pool


Analytics in SharePoint 2013


New Replacement for Web Analytics Service The Analytics Platform replaces the Web Analytics

service application Some of the reasons for that included:

There was no concept of item-to-item recommendations based on user behavior, i.e. people who viewed this also viewed foo

Couldn’t promote search results based on an item’s popularity (as determined by # of times an item was viewed)

It required a very powerful SQL box and significant storage and IO

Lists don’t have explicit view counts The architecture could have problems scaling to large

numbers


Shredded Storage


Distributed Cache Service


New Cache Service There is a new distributed cache service in SharePoint

2013, based on Windows Server AppFabric Distributed Caching

It is used in features like authentication token caching and My Site social feeds

SharePoint 2013 uses caching features that cloud-based cache (Windows Azure Cache) does not support at this time, so only local cache hosts can be used; may change in the future

SharePoint ONLY supports the version of caching that it ships – you cannot independently upgrade it.


New Cache Service (cont.) A new Windows service – the AppFabric

Caching Service – is installed on each server in the farm when SharePoint is installed

It is managed via the Services on Server page in central admin as the Distributed Cache service

The config DB keeps track of which machines in the farm are running the cache service


Cache Architecture For caching in farm, scale points have not

been determined yet How many servers are needed, what resources

should be built out (CPU, memory, etc.)

Cache Host

Cache HostCache Host


Self-Service Site Creation


Self Service Site Creation Self-service site creation (SSSC) has been revamped

You can specify a custom form that should be used to create a new site

That form can be in the same web app or an entirely different web app

You can specify whether to create a new Site Collection or new Web

You can specify the inclusion under which new sites should be created

NOTE: Remember if you use the farm creation wizard, SSSC is turned On for the web app it creates

You can also define policies in a content type hub and require or ask that each new site uses one of those policies


Creating New Site Collections You still need “Use Self-Service Site Creation”

rights You will have a “Start a new site” link in your

personal menu Clicking it brings up the new site form:

NOTE: You do NOT get to pick a site template; you must create a custom creation form to do that (all are team sites)


Themes


Themes The themes engine has been completely reworked Everything is now based on HTML instead of proprietary

format – including support for HTML5 PowerPoint is no longer used to create custom themes

You get much richer themes and common building blocks for customizing them A background image, palette and fonts with live preview

You can “try it out” to see how it looks


Theme Gallery This is what the new theme gallery looks like, along with

a sample of an HTML 5 based theme:


Theme Selection and Configuration


Sharing


Sharing – Problems Sharing in SharePoint 2013 is designed to solve

these common problems from previous versions of SharePoint:

Granting access to a site can be a bit convoluted Users don’t understand what permission level to grant to other

users Users generally don't know who all has permissions on a site Users can’t see the invitations that have been sent out to

external users. Users don’t understand what rights they are giving people when

they add them to a SharePoint group Users can’t see the level of access they have


Sharing - Solutions Sharing in SharePoint 2013 is designed to address these

limitations with the Sharing feature: A Sharing dialog for adding users, distribution groups, and

security groups An email invitation with a message that can be customized

when it’s sent out A “request on behalf of” feature, where if you don’t have rights

to add someone to the site, you can send a request on someone else’s behalf.

A requests management page where admins can view and respond to all requests

A Personal Permissions page where users can request more permissions than they currently have

A conversation component to requests, so admins and users can have a dialog about the request


Sharing Process Users can share a site from the Site Actions menu Users request access via the access denied page,

like before If a user has the Grant Permissions right, they can

share themselves Otherwise the requests must be handled by an

admin NOTE: You MUST have configured the outgoing

SMTP server for a web application or the “Share this site” menu option will not appear for anyone but site collection admins


Introduction to Office Web Applications


Office Web Apps in SP2010 and other Wave 14 apps

animated


3rd party apps

Office Web Apps in Wave 2013

animated


Why to dedicated Office Web Apps functionality? Not all documents are in SharePoint

Provide unified platform for other applications as well Large customers had numerous farms to manage in 2010

time frame Consolidation of services to single Office Web Apps farm which

provides services for multiple applications Manage scale and performance of Office Web Apps independent

of the SharePoint environment Easier upgrade and maintenance for Office Web Apps

functionality Easier consuming of Office Web Apps functionalities

without complex SharePoint federation Easier to setup also without SharePoint – if only used for

example with Exchange


Office Web App Urls in Wave 2013 URLs have been cleaned to be

human friendly and understandableFrom this:http://office/15/collab/Demo/_layouts/PowerPoint.aspx?PowerPointView=ReadingView&PresentationId=/15/collab/Demo/Docs/wac.pptx&Source=http%3A%2F%2Foffice%2F15%2Fcollab%2Fdemo%2Fdocs%2FTraining%2520Module%2Fdocsethomepage%2Easpx%3FID%3D96%26FolderCTID%3D0x0120D52000DC71A13124DA5249ACA958C4DFD092C90037E1F59EB3515B4F940A3806D9B183F0%26List%3Dc910e954%2D68ca%2D42ae%2Dbb0f%2D1c6908c73e77%26RootFolder%3D%252F15%252Fcollab%252Fdemo%252Fwac%252015&DefaultItemOpen=1To this:http://office/15/collab/Demo/Docs/wac.pptx?Web=1


Office Web Apps Deployment


Office Web Apps Server Requirements Windows Server 2008 R2 x64 (+higher version)

All servers must be domain joined Active Directory to manage server identity

.NET 4.0 IIS 7.0 (role needs to be turned on through the Web Server (IIS)

role) PowerShell 3.0 Load balancer for multi-machine farms SCOM for monitoring Dedicated server(s) with no other applications installed (that are

using ports 80 or 443)


Performance and scale Requires dedicated servers

Can be also virtualized The whole thing can run on a

single server depending on requirements

Add servers to meet demand Never any reason to have

separate farms Except security


Connecting Office Web Apps to SharePoint

Set once for the whole SharePoint farm PowerShell only You can customize which Office Web Apps are registered Nothing is installed on SharePoint Removing is just as easy

Discovery Request

Discovery Response

animated

>>New-SPWopiBinding –Server <serverUrl>


Managing Office Web Apps


Patched Office Web Apps farm

Office Web Apps Farm

Farm availability during upgrade – minimal downtime

WOPI server request

animated


Service Applications in SharePoint 2013


SP2013 - Same services model as introduced in 2010 Services can be

individually consumed from anyWeb Application

Allows for a very rich (and complex) farm structure if required

Provide flexibility to utilize services based on application needs


Service Databases Service Applications with their own DBs:

App Management Service Business Data Connectivity Managed Metadata Service Search Secure Store Service SharePoint Translation Services State Service Usage and Health Data Collection User Profile Word Automation Service Access Services App databases


Cross farm services in SharePoint 2013 Remote farms don’t need perms to

parent farm DBs

Any farm can publish SAs One web application can use both

local and remote SAs

Enables centralized “enterprise” SAs Support only in specific service

applications Business Data Connectivity Managed Metadata Service Search Secure Store Service SharePoint Translation Services User Profile


Apps service application


Introduction to Apps Service Application Is responsible for storing and providing information

concerning SP App licenses and permissions

All licenses for apps downloaded from Marketplace will be stored in Apps service application

Accessed each time app is requested or used in SharePoint to verify validity of the request

©2012 Microsoft Corporation. All rights reserved. Content based on SharePoint 15 Technical Preview and published July 2012. animated

SP App general usage and communication flow


Sharepoint 2013 Apps


User Profile Service


Profile Synchronization Goals for SharePoint 2013 Performance

Large organizations should be able to perform a full sync of AD and SharePoint data over a weekend.

Reliability IT pros should be able to monitor the performance and stability

of profile sync and have access to the information that they need to take corrective action when problems occur.

Compatibility Common Directory Service configurations should be supported,

including Forefront Identity Manager and generic LDAP providers.


SharePoint Sync Performance Changes Performance improvement goals are to reduce full import

time from up to 2 weeks down to 60 hours for extremely large directories – for example, 200K users and 600K groups

Numerous optimizations Adding indexes to certain user properties that eliminated full

table scans Importing data from BDC in batches rather than one by one Removing unused provisioning steps History clean-up Moving resolution of some objects out of SharePoint and onto

the sync system


Active Directory Direct Import – What’s Supported Designed to let you get profile import going as quickly as

possible in a very common scenario – direct AD forest import

Key capabilities Forests with multiple domains, but one connection per domain Select import OUs, import users and groups, use LDAP filters,

full or incremental imports, and switch between FIM and AD Direct

Other things supported Windows, FBA and Trusted provider claims account mapping,

just like SharePoint 2010


Machine Translation Service


Introduction to translation service application Provides built-in machine translation capabilities on the

SharePoint platform Cloud-based translation services Based on WAS architecture Can translate documents, pages and sites Extensible

Full trust solutions and SP Apps supported REST API or CSOM available APIs for batch and immediate translations


ENFI

Variations and Translation Service

ENXLIFFExport

Online TranslationEngineTranslation Vendors

Translation Service Application

ParsersParsersParsers

APIJob Queue and DB

HTML Segments

Target variation

Source variation

Import

animated


Work Management Service


Introduction Business challenge

It is challenging for information workers to get a comprehensive view of their tasks or to have a central point for managing their work.

Tasks are stored across applications and systems, and even in the case where all tasks are stored within a single system, information can still be scattered.

Work management Service applications provides functionality to aggregate tasks to central place Users can go to view and track their work and to-dos Tasks cached to person’s my site


Technical background and configuration Service application doesn’t have any configuration

options in Central Administration Accessed and used directly programmatically by out of the box

functionalities

Out of the box task aggregation with Microsoft SharePoint Products, Microsoft Exchange Server, and Microsoft Project Server Example, users can edit tasks from Exchange Server on a

mobile phone, and the Work Management Service aggregates tasks to the My tasks SharePoint list.

Implementation is based on provider model, so that additional systems maybe integrated to same architecture in future


User Interface for My Sites tasks


Word Automation Service


Overview Word Automation Services is all about file conversions

Three main pain points in SharePoint 2010 Solutions must wait until timer job executes for file generation Can only handle files in SharePoint No easy way to know when conversion has been completed

Feedback I want to convert Word document ”right now” I want to use Word Automation but don’t want to put files to

SharePoint I want to convert document and perform operation to file

immediately when it’s available


Key changes in SharePoint 2013 for Word Automation New ”Immediate” based request (no waiting)

New option to execute conversion immediately, not necessarily from timer job

Operate on one file at the time per request Configuration options from CA for simultaneous request amount

Notify or update items in SharePoint after completion Word Automation Services can perform file conversions and can update files

(ex. update table of contents or fields)


Enterprise Search – Architecture and Topology


Logical Architecture


Crawling the Content• The crawl role is responsible for crawling

content sources. It delivers crawled items – both the actual content as well as their associated metadata – to the content processing component• Invokes connectors or protocol handlers to

content sources to retrieve data• Does not do any document parsing (Content

Processing Component does that)• Information about content sources, schedules,

etc. are synchronized to the registry on crawl role servers from the search admin database

• The Crawl Database is used by the crawl component to store information about crawled items and to track crawl history• Holds information such as the last crawl time, the

last crawl ID and the type of update during the last craw.


Content Processing Content Processing Component

Processes crawled items and feeds these items to the index component

Document Parsing happens through Format Handlers iFilter is supported through a Generic iFilter format handler iFilters are still the extensibility platform for SharePoint 2013

Heart of the indexing process: transforms crawled items into artifacts that can be included in the search index by carrying out operations such as document parsing and property mapping

Performs linguistic processing at index time (e.g. language detection and entity extraction)

Writes information about links and URLs to the Link Database directly

Generates phonetic name variations for people search


Analytics Processing Component Search Analytics analyzes crawled items and how

users interact with search results. Usage analytics analyzes usage events e.g. like

views from the event store When an user does an action (e.g. view a page) the

event is collected in usage files on the WFE’s and regularly pushed to event store where they are stored until processed

Results are then returned to the Content Processing Component to be included in the search index

You can add write code to add custom events Analytics Processing Component supports scaling

out: Add more APC roles to have analysis

complete faster Adding more Link databases to increase

capacity for links and search clicks, and potentially speed up the DB extraction

Adding more reporting databases to store more reports as well as improving SQL throughtput in retrieveing reports


Index Component Used in both feeding and query processes:

Feeding: receives processed items from the content processing component and writes those items to index files

Query: receives queries from the query processing component and provides results sets in return

It also physically moves around indexed content when the index architecture is changed by the Search Administration Component


Query Processing Component

Performs linguistic processing at query time: Word breaking, stemming, query spellchecking, thesaurus

Analyzes and processes search queries and results. When the component receives a query from the search front-end, it analyzes and

processes the query to attempt to optimize precision, recall and relevancy. The processed query is then submitted to the index component(s). As part of this it also decides which query rules are applicable, which index to send the query to, and

whether to do any pre- or post-processing of the query The index component returns a result set based on the processed query back to the

query processing component, which in turn processes that result set before sending it back to the search front-end.


Search Administration Search Admin Component

Runs number of system processes required for search

Is responsible for search provisioning and topology changes

Coordinates search components – Content Processing, Query Processing, Analytics, and Indexing.

Search Admin DB Stores search configuration data:

Topology Crawl rules Query rules Managed property mappings Content sources Crawl schedules

Stores Analytics settings Does not store ACLs anymore


Social features in SharePoint 2013Introduction


Introduction Social gets a big boost in SharePoint 2013

Enriches the functionalities introduced in 2010 Adds new features that improve and facilitate the enterprise

social activities within the organization: Follow people as well as content (documents, sites, tags) Share personal documents easily and keep track of access Keep up-to-date with activities of interest Company Feeds

Across PC, Phone and Browser Content can be accessed from everywhere Offline capabilities integrated with Office Products and Windows Full integration with Windows Phone 8


My Site Host - The Landing Page Newsfeed: shows you updates on

social activities for items and people you are following: People posts People profile changes Changes on followed documents Items tagged with followed tags Mentions Activities: all my activities Likes Company Feeds


About Me – What Other People See


Enterprise Content Management


SharePoint 2013 ECM - Big Bets

Internet Business

•Major WCM Investment•Search Driven Sites•Intranet and Internet applicability

eDiscovery

•In place preservation in SP & Exchange•Integrated, enterprise wide case management

Team Folders

•Work on mail and documents together•SharePoint, Outlook, OWA

•Retention/compliance across stores


The Team Folders – Exchange and SP together

Documents are stored in SharePoint

Emails are stored in Exchange

Team Folders can receive emails and have their own email address

Easy access to both from Outlook and SharePoint

Unified compliance policy applies to both


WCM in SharePoint 2013


Build Great Sites Support the

tools and workflows designers use

Target different designs based on user agent string


Easy content Authoring and Management Variations &

Content Translation

Search Engine Optimization

Cross Site Publishing

RTE Usability Video &

Embedding


Enable Intelligent Experiences Metadata

navigation Topic Pages Clean URLs Content by

Search Recommendatio

ns(item-to-item, popularity)Events Analytics

EngineMined

Recommendations

Search Engine


Enable Commerce on Your Site

Item Catalog Easy Catalog

import/sync


SEO improvements Numerous SEO improvements in site and page level

Features SharePoint 2010 SharePoint 2013Clean URLs http://www.c.com/Pages/cars.asp

xhttp://www.c.com/cars

Home Page Redirects HTTP 302 for http://www.c.com to redirect to /pages/default.aspx

Home page served from address www.c.com – no redirect for browser

Country code top-level domains (ccTLDs)

http://www.c.com/en-us/Pages/cars.aspxhttp://www.c.com/es-mx/Pages/coches.aspx

http://www.c.com/cars http://www.c.mx/coches

XML Sitemaps None Automatically generated and referenced in robots.txt

SEO Properties(e.g. Meta Description)

<title> and <h1> must be identical

Browser titleMeta descriptionMeta keywords

Webmaster Tools integration

None Assists with ownership verification

http://www.c.com/Pages/cars.aspx

http://www.c.com/Pages/cars.aspx

http://www.c.com/cars

http://www.c.com/

http://www.c.com/

http://www.c.com/en-us/Pages/cars.aspx




http://www.c.com/cars

http://www.c.mx/coches


Image renditions Image transformation dynamically in

SharePoint Thumbnails are actual thumbnails

Images Consistency sized images

Resizing will resize actual image, not only it's presentation

Optimizes page payload Cropping for targeting

areas of pictures


Video improvements Enable easy enterprise podcast

scenarios Video support improvements

Embedding to any content page Thumbnail generation Renditions also for videos External video support to store Multiple encodings for single video

Video player as HTML 5 implementation Fallback to Silverlight


Development in SharePoint 2013


Development environment setup considerations Client OS installations are not anymore

supported Windows 8 OS supports also 64 bit clients in

Hyper-V Similar hosting options as for SP2010 for

virtualized environments Cloud based hosting of also development

environments for easy and fast availability and scale for your team

Windows Azure Workflow service can be installed on same server as SharePoint

Office Web Applications has to be installed on separate server


Authentication and Authorization - Claims


Authentication Modes SharePoint 2013 continues to offer support for both

claims and classic authentication modes However claims authentication is THE default

authentication option now Classic authentication mode is still there, but can only be

managed in PowerShell – it’s gone from the UI Support for classic mode is deprecated and will go away

in a future release, so we recommend moving to Claims There also a new process to migrate accounts

from Windows classic to Windows claims


Authentication Infrastructure One of the big improvements is that SharePoint

tracks FedAuth cookies in the new Distributed Cache Service In SharePoint 2010 each WFE had its own copy That meant that if you got redirected to a different

WFE, you would need to re-authenticate This means that sticky sessions are no longer required

when using SAML claims!


Technologies & Approaches

Database Protection


Supported Database Servers & Operating Servers Windows Server 2008 R2 with Service Pack 1 Windows 2012 Server RTM SQL Server 2008 R2 with Service Pack 1 SQL Server 2012


Native Backup/Restore No Significant Surfaced Changes Full/Differential Only

Does Not Backup the Transaction Log Does Not Use Backup Compression

Knits Together SQL Backups & Hierarchal Storage Backups


Failover Clustering No Stored Data Loss Mature Technology Well Understood Recovery Model Complex Configuration & Operation Shared Storage (Practical) Requirement Perceived Hardware Under Usage Very Low RPO/RTO

Still not technically zero! There will be service interruption while the failover occurs!


Database Mirroring No Stored Data Loss “Failover Clustering, only Simpler” Less Perceived Hardware Under Usage Redundant I/O Path Database-Level Protection Direct, Deep Support In The Product “Minimally Available” Very Low RPO/RTO


Log Shipping “Backup, Restore, Repeat” Read-Only Secondary Copies

Product Patches May Require Read/Write @ Secondary Multiple Targets Moderate RPO/RTO Achievable


Log Shipping


Availability Groups Not technically related to Database Mirroring or Log

Shipping Ground-up re-architecture, at the SQL OS and Storage

subsystem levels Requires Windows Failover Clustering


Availability Groups Requires SQL Server 2012 Enterprise Edition Requires Windows Server 2008 Enterprise Edition Requires Hotfixes

KB976097 – Adds support for asymmetric storage KB2494036 – Adds support for node quorum vote configuration


Learn UpgradeUpgrade Requirements


Server Prerequisites 2010 or earlier SharePoint products must not be installed To use existing 2010 SharePoint Farm hardware:

Backup your farm using SharePoint backup tool Ensure your backup of farm and databases

Ensure SharePoint 2010 or earlier is not installed Either uninstall old products

This includes dependent products like Project Server and language packs Or pave the operating system


Client Minimum Software Requirements Office 2010 or Office 2013

For full offline and integrated experience SharePoint Designer 2010 only works for 14 mode sites SharePoint Designer 2013 works for both 14 and 15 mode sites SharePoint Workspace 2010 and 2013 work for both 14 and 15

mode sites Web Browser

Internet Explorer 7 or higher


Upgrade Methods Database Attach Upgrade

Only available method for version to version (V2V) upgrades Works for both version to version (V2V) and build to build (B2B)

upgrades Works for content and services databases

In-Place Farm Upgrade Only available for build to build (B2B) upgrades


Databases Supporting Database Attach Upgrade Content databases Project databases

Note: Four 2010 merged to one during upgrade Search admin database Profile database Social database Managed Metadata database Secure Store database

Note: Passphrase required to retain passwords in store Access databases

Note: Supported for B2B upgrades only


Databases Not Supporting Database Attach Upgrade Configuration database

Unsupported for both V2V and B2B upgrades Has never been supported in prior versions

Search index databases Unsupported for V2V upgrades only

Sync database Unsupported for V2V upgrades only


System Status Bar Notification Examples


Choosing Migration vs. Upgrade When

When upgrade is not possible due to bad prior choices Database modifications Unsupported site definitions

When downtime is not tolerable Why

Cost of downtime is higher than negative impact from migration Massive redesign is required to site/data structures

How Migrate using 3rd party tools only, no Microsoft supplied solution


Environment CleanupIt’s a dirty job…

…but someone has to do it


Spring Cleaning For A Healthy Farm Cleanup existing 2010 farm

before upgrade Delete stale SPSites and

SPWebs stsadm -o DeleteSite [-force]

[-gradualdelete] stsadm -o DeleteWeb [-force]

Remove extraneous document versions Primarily user driven, OM

operations or tools help

Cleanup templates, features, & web parts Primarily user driven, OM

operations or tools help Finish Visual Upgrades to

14 Repair data issues

stsadm -o DatabaseRepair [-deletecorruption]

stsadm -o ForceDeleteList stsadm -o

VariationsFixupTool


© 2011-2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows 7 and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted

to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

viestinnän seminaari 8.11.2012 / sharepoint

Technology

introduction2012

configuration2012

2012 microsoft

web amp

content based

internet explorer

published

rights reserved