ITPro’s taking the SharePoint 2013 Red Pill

Jason Himmelsteinjhimmelstein@sentri.com @sharepointlhorn

A Journey down the rabbit hole

Jason’s contact & vitals• Microsoft vTSP

• virtual Technology Solutions Professional

• SharePoint Foundation Logger • http://spflogger.codeplex.com

• Blog: www.sharepointlonghorn.com • Twitter: @sharepointlhorn • LinkedIn: www.linkedin.com/in/jasonhimmelstein• SlideShare: http://www.slideshare.net/jasonhimmelstein• Email: jase@sharepointlonghorn.com

• Author of Developing Business Intelligence Apps for SharePoint• http://bit.ly/SharePointBI

Agenda

• Hardware Requirements• Software Requirements• Claims First Methodology• Architecture Changes• New & Retiring Service Applications• eDiscovery• Search• Business Intelligence

How do we explain SharePoint?

Communities

Search

Sites

Composites

ContentInsights

Wheels?

Where we are going, we don’t need wheels!

Hardware RequirementsDependencies and Prerequisites

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

Web & Application Servers | Single Server FarmsSharePoint 2010 vs. SharePoint “2013” Comparison:

Component SharePoint 2010 Minimum Requirement SharePoint “2013” Minimum Requirement

Processor 64-bit, four cores 64-bit, four cores

RAM 4 GB for developer or evaluation use

8 GB for production use in a single server or multiple server farm

4 GB for developer or evaluation use

8 GB for production use in a single server or in a multiple server farm

Hard disk 80 GB for system driveMaintain twice as much free space as you have RAM for production environments.

80 GB for system driveMaintain twice as much free space as you have RAM for production environments.

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

Database Servers – Minimum Hardware Requirements

SharePoint 2010 vs. SharePoint “2013” Comparison:Component SharePoint 2010 Minimum Requirement SharePoint “2013” Minimum Requirement

Processor 64-bit, four cores for small deployments

64-bit, eight cores for medium Deployments

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

8 GB for small deployments

16 GB for medium deployments

Hard disk 80 GB for system drive

Hard disk space is dependent on the sizeof your SharePoint content

80 GB for system drive

Hard disk space is dependent on the size of your SharePoint content

Hardware Requirements

Memory Processor DiskSingle Server

(Integrated or Standalone Database)

8 GB x64 1x4 80 GB (OS)

Single Server(Integrated or Standalone

Database)

*Development Environment/Evaluation

24 GB x64 1x4 80 GB (OS)

Web / Application Servers

*Pilot, Production, Servers in a Farm

12 GB x64 1x4 80 GB (OS)

Hardware and software requirements for SharePoint Server 2013 (http://technet.microsoft.com/en-us/library/cc262485(v=office.15).aspx)

Software RequirementsDependencies and 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

Database Servers – Minimum Software Requirements

SharePoint 2010 vs. SharePoint “2013” Comparison:Component SharePoint 2010 Minimum

RequirementsSharePoint “2013” Minimum Requirements

SQL Server The 64-bit edition of Microsoft SQL Server 2005 with Service Pack 3 (SP3).

The 64-bit edition of Microsoft SQL Server 2008 with Service Pack 1 (SP1) and Cumulative Update 2

The 64-bit edition of Microsoft SQL Server 2008 R2

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

Windows Server

The 64-bit edition of Windows Server 2008 with SP2

The 64-bit edition of Windows Server 2008 R2

The 64-bit edition of Windows Server 2008 R2 Service Pack 1 (SP1)

Database Servers – Optional Software

• 64-bit edition of Microsoft SQL Server 2012 RTM (i.e. not Release Candidate 0 / RCO)

• SQL Server 2012 RTM Manageability Tool Kit• SQL Server 2012 RTM Native Client 64-bit• SQL Server 2012 RTM SQL ScriptDom 64-bit• System CLR Types for SQL Server 2012 RTM• SQL Server 2012 RTM Transact-SQL 64-bit• SQL Server 2012 RTM Data-Tier Application

Framework 64-bit

RTM

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:

Enables the creation & consumption of OData services

Provides support for information protectionProvides support for information protection

Provides in memory distributed cachingProvides in memory distributed caching

.NET Framework 4.0.NET Framework 4.5

Provides support for Windows PowerShell 3.0

Provides support for Windows PowerShell 3.0

Software Requirements

PrerequisitesWindows Management Framework 3.0Application Server RoleWeb Server (IIS) RoleMicrosoft .NET Framework 4.5Update for the .NET Framework 4 (KB2468871)Microsoft SQL Server 2008 Service Pack 1 Native ClientWindows Identity Foundation (KB974405)Microsoft Sync Framework Runtime v1.0 (x64)Windows Server AppFabricWindows Identity Foundation v1.1Microsoft Information Protection and Control ClientMicrosoft WCF Data Services

Windows Server 2008 R2 Service Pack 1

Windows Server 2012

Windows Management Framework 3.0

Microsoft .NET Framework 4.5Update for the .NET Framework 4 (KB2468871)

Windows Server AppFabric

Microsoft Information Protection and Control ClientMicrosoft WCF Data Services

Hardware and software requirements for SharePoint Server 2013 (http://technet.microsoft.com/en-us/library/cc262485(v=office.15).aspx)

Software Requirements

64-bit edition of Microsoft SQL Server 2008 R2Service Pack 1

64-bit edition of SQL Server 2012

Hardware and software requirements for SharePoint Server 2013 (http://technet.microsoft.com/en-us/library/cc262485(v=office.15).aspx)

Deployment Scenarios

SharePoint 2013 SharePoint 2010

Workgroup Unsupported Supported

Domain Controller Developer Installation Supported for SBS

Client OS Unsupported Developer Installation

Dynamic Memory in VMs Unsupported Unsupported

Windows Web Server Unsupported Supported

“You take the blue pill, the story ends. You wake up in your bed and believe whatever you want to believe.

You take the red pill, you stay in Wonderland and I show you how deep the rabbit hole goes.

I’m only offering the truth…. Nothing more.”

Versioning Changes

• Shredded Storage• Versioning Scenario

• 1st file = 10m storage requirement• 2nd.. 10th = 1m file increase per version storage requirement

Old versioning model

Shredded Storage versioning model

What does this mean for RBS?

1st = 10m 2nd = 11m 3rd =12m 10th = 19m Total = 145m

1st = 10m 2nd = 1m 3rd =1m 10th = 1m Total = 19m

Claims

Authentication Modes• SharePoint 15 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 Migration• The MigrateUsers method in SharePoint 2010 is no longer

the correct way to migrate accounts – it is now deprecated• A new cmdlet has been created called Convert-

SPWebApplication• A simple example – you have a Windows classic web

application• Run Convert-SPWebApplication -Identity "http://yourWebapp" -To Claims –

RetainPermissions [-Force]

Other Claims Migration Scenarios• You have an existing Windows claims application and you want to

bring over content from a SharePoint 2010 Windows classic web app• Option 1 (the safest):

• Create a web application in o15 that uses Windows classic authentication• Attach the SharePoint 2010 content database to this o15 web app• Attaching it will upgrade it to the o15 database format, so verify that it is working

correctly after attach• Run the Convert-SPWebApplication command on the o15 web app to convert the

users from Windows classic to Windows claims• Detach the content database from the o15 Windows classic web app• Attach the content database to it’s final o15 Windows claims web app

• Option 2 (the quickest):• Attach the content DB to an existing Windows claims web application• Run the Convert-SPWebApplication cmdlet again on the web app

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!

New Claims Features• You can choose the characters for the claim type and there

is no enforcement on the ordering of claim types• Pre-populate the custom claim types and characters across all

farms• Install the claim providers that use those custom claim types in

any order

• You can add multiple token signing certificates to the SharePoint STS• Useful in S2S scenarios• Use the Set-SecurityTokenServiceConfig cmdlet

New Claims Features (continued)• The SharePoint STS now supports a federation metadata

endpoint• SharePoint publishes an endpoint describing it’s configuration

and certificates, and can consume the same• HOWEVER…the format it uses and consumes is JSON, so the

trusting partner must support that (AD FS does not today)• There is a possibility we will publish guidance on how to

develop this for ADFS• That would also support multiple token signing certs

Authentication Logging• There is significantly more logging provided to help

troubleshoot authentication issues. You can see things like:• Adding / removing FedAuth cookies from the cache• Where authentication requests get redirected• Which claims providers were used and which were not• Reason why a FedAuth cookie failed to be used (i.e. expiration,

failure to decrypt, etc.)

Request Management

Sourced from: http://articles.boston.com/2011-12-23/metro/30545715_1_traffic-cops-holiday-shoppers-christmas-shopping

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

RM ComponentsRequest Manager (RM)

Request Throttling and Routing

Throttle if appropriate, or select which WFE’s the request may be sent to

Request Prioritization

Filter WFEs to only ones healthy enough for the request

Request Load Balancing

Select a single WFE to route to, based on weighting schemes like health

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

scores

Static Weight = 1Health Weight = 4

Static Weight = 1Health Weight = 4

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

RM Routing Rules• Routing to a server in a MachinePool is based on matching a routing rule• Routing rules are placed in ExecutionGroups• These are numbered 0 to 2, with 0 the default

• Rules are evaluated in each ExecutionGroup• As soon as a match is found no more ExecutionGroups are

evaluated• All machines from pools that match any routing rules are

union’ed together to determine possible target servers

• This means that you create your most important rules in ExecutionGroup 0

Routing Rules and Execution Groups

Execution Group 0

Routing Rule #1

Routing Rule #2

Routing Rule #3

Machine Pool 1

Machine Pool 2

Machine Pool 3Execution

Group 1

Routing Rule #4

Routing Rule #5

Execution Group 2

Routing Rule #6

Routing Rule #7

Machine Pool 1

Machine Pool 3

Match!

XNo Match

Not Evaluated

RM Routing Rules (cont.)•There are some important caveats to remember about routing rules• If no rules are matched, then the request will be sent to any server that is NOT in any machine pool for any rule• In a one server farm that means nothing will route if no rules match, so the alternative is to create a “catch all” rule that matches everything• Just put it in ExecutionGroup 1 or 2 so it’s the last

match

RM Routing Weights• RM uses static weights and health weights• Static weights are associated with WFEs so certain ones will always

be favored when selecting. • This gives added weight to more powerful WFEs and less to weaker

machines• Health weights are used to even out load and keep “sick” WFEs

going• Health scores run from 0 to 10 where 0 is the healthiest and

therefore will get the most requests; this score is used to derive the health weight• WFEs start with a healthy weight; the Policy Engine health rule

updates health weights dynamically – you cannot change it manually

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

New & Retiring Service Applications

What happened to Office Web Apps?• OWA is now stand alone. It cannot run on a SharePoint Server.• Why?

• Not all documents are in SharePoint• Provide unified platform for other applications as well

• Benefits• 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• Scalability with OWA “Farms”

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

How the New Platform Improves on Analytics• The new Analytics Processing engine aims to solve these issues:• Find relevant information (improve search relevance) – based on views, click

thru, etc.• See what others are looking at (“hot” indicators and usage numbers – i.e.

what’s popular based on # of views as well as # of unique users to view)• Understand how much content is being used (i.e. viewed) and how it compares

to other documents • See discussion thread usage and find the hot topics• Use this popularity info to populate views through the Content by Search (CBS)

WebPart• The model is extensible for 3rd parties to build into the platform

Processing and Storing Analytics Data• Data goes through an analysis and reporting process that is contained

within the search service application• Things like views and counts are combined with click-thru and other

search metrics and pushed into the reporting database• Some data like view counts are also pushed into the index so it can be

included in search results, sorted on (i.e. what’s most viewed), etc.• An analytics processing job examines data for clicks, links, tags, etc., as

well as the usage data to create the data points used for reporting

Analytics System Components• The Analytics system can be considered as five parts:• Event: Each item comes into the system as an event with

certain parameters• Filtering & Normalization: Each event is looked at to see:

• Special Handling: Certain types of events will be directly written to the .usage files

• Filtered Out: Some events like those from robots, should not be counted and allowed to pass

• Normalized: Rewritten so it can be counted along with other hit types. E.g. document reads through the WAC should be counted as reads against the document

• Allowed to Pass: So that normal counting methods can be performed

Analytics System Components (cont.)•Custom Events: You can configure up to 12 custom events in addition to what comes OOB•Calculation: We run calculations to sum or average across events•Reports: A number of default reports are available, including:• Top queries• Most popular documents in a library or site• Historic usage of an item – view counts for last

recent history as well as all time

Access Services

• Good news: the old Access Services 2010 Service App is still here

• Better news: the new Access Services 2013 Service App is here

• The horrifying news: how Access Services 2013 management is done

Access Data Services

Access Client

Web Browser

SharePoint SQL

Access App 3

Access App 2

Access App 1

Access App 5

Access App 4

Access App 8

Access App 7

Access App 6

Access App 10

Access App 9

Manageability

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 Site-level retention policies

Compliance levels extended to sites Policies include:

Retention policy for sites and Team Mailbox associated with site

Project closure and expiration policy

eDiscovery Center Designed for managing discovery

cases and holds Establishes a portal through which

you can access discovery cases to conduct searches, place content on hold, and export content

New Cache Service• 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 Setup• The farm account is used as service account for Cache

Service• Like user profile service in SharePoint 2010, during setup

the service account should have elevated privileges (i.e. local admin)• After setup is complete you should lower the privileges

for the account

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.)• More data will be available after Beta 2

Cache Host

Cache Host

Cache Host

Cache Server Performance• There are hundred(s) of perf counters; there are also

counts exposed via developer’s dashboard• # of reads • # of writes • # of hits• # of misses • time for read • time for write • Total I/O (how much data has been transferred in a given period of time)

Cache Service Health• The following health rules have been created to help you track the

Cache Service (look in the Availability section for most):• One of the cache hosts in the cluster is down (Availability)• Firewall client settings on the cache host are incorrect (Configuration)• Cache host is in throttled state (Availability)• The high availability node for SharePoint distributed cache is not

available (Availability) – happens when there are less than 2 servers running the cache service

• There exists at least one cache host in the cluster, which SP doesn't know about (Configuration) – happens when the cache service is disabled in SharePoint but AppFabricCaching Service is running on the machine

• Cached objects have been evicted (Configuration) – indicates eviction happened across the cache cluster. Not bad in and of itself but may be a clue if it happens frequently and/or there are perf issues

ECM & e-Discovery

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

Central Place to view all Cases

Add, manage and export discovery sets

Site Based Compliance & preservation• Compliance officers create policies,

which define:• The retention policy for the entire site

and the team mailbox, if one is associated with the site.• What causes a project to be closed.• When a project should expire• Can set also site collection as read only

• Policy also available optionally from self site creation• Policies can be replicated from

content type hub cross enterprises

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

Unified Discovery across Exchange, SharePoint and Lync• Find it all in one place (unified console)• Find more (in-place discovery returns the richest data)• Find it without impacting the user (Give legal team discovery, leave IWs alone)

Discovery Center in SharePoint Unified Preserve, Search and Export

Exchange Web Services Connect to Exchange to get mailbox data

Lync Archiving to Exchange Exchange is the compliance store for Lync

Search Infrastructure Exchange and SharePoint use the same search platform

Search

Search• New Search architecture

with one unified search

• Personalized search results based on search history

• Rich contextual previews

Connectors• The following connectors will be available out of the box in SharePoint:

SharePoint HTTP File Share BDC – also includes these other connectors that are built on BDC

framework: Exchange Public Folders Lotus Notes Documentum Connector Taxonomy Connector

Requires the Term Store to be provisioned for crawling, so requires SharePoint Server Requires Secure Store only if you want to create an end-to-end BDC experience,

including per-user authentication, so requires SharePoint Server People Profile Connector

Requires the profile store to be deployed and populated, so requires SharePoint Server

Crawling and Content Sources

There are improvements to the crawling feature itself: For HTTP sites, crawler supports a new type of

authentication - anonymous Crawling also supports certain out of the box web part

content that is rendered asynchronously on the client The crawler gets a “classic” type rendering of pages with the

new asynchronous web parts on them in order to index them

Crawling “Continuously” “Continuous crawling” is a new feature to crawling in SharePoint

2013 – it only applies to SharePoint sources When you crawl continuously every 2013 minutes (by default)

the crawler gets changes from SharePoint sites and pushes them to the content processing component You can change the interval using Set-

SPEnterpriseSearchCrawlContentSource after Beta 1 Refresh Because of changes in how the index is created and stored, a

document can appear in the index within seconds of going through the content processing component – you no longer have to wait for long index merges until it shows in results

It also means you can get latest changes even while a full crawl is starting, so you can see results before full crawl completes

Search UI Configuration

• Result Types• Display Templates

• Search Navigation• Search Refinement• Query Suggestions• Thumbnail Previews• Site Level Search Admin Summary

Search Refinement

• There are two different modes for the refiner web part: search results and faceted navigation• With search results the refinement data works essentially the same as

SharePoint 2010• With faceted navigation it uses a term from the term store to filter what

kind of data should be displayed (explained on next slide)

• Refinement is different with SharePoint 2013 in that you can define display templates to use for rendering different kinds of refinements• In SharePoint 2010 you had to write your own custom refiner

Faceted Navigation with Search Refiners• With Faceted Navigation, it is used in conjunction with term sets

that are used for navigation• With each term you select which managed properties should be

used as refiners with that term• Within the managed property you need to configure it as

“Refinable”• Example:

• You have term store terms Camera and Laptop• You have managed properties Megapixel Count, Color and Manufacturer• For Camera term, you add refiners for Megapixel Count and Manufacturer• For Laptop term you add refiners for Color and Manufacturer

• Another Example:• Department is the term store term, Customers and Projects could be

refiners

Query Suggestions

• Query suggestions take a big leap forward in usability. It improves on the experience in SharePoint 2010 as follows:• Your personal SharePoint activity factors into the query suggestions, i.e. you

have a personal query log• It includes weighting based on sites that you have previously visited• It uses the most frequent queries across all users that “match” the search terms

• The behavior of the query suggestions turns into more of a “browse and find” kind of experience

• You can also add inclusion and exclusion lists for suggestions via the SSA admin pages

Thumbnail Previews The new Office Web Apps is the engine for thumbnail previews in

SharePoint 2013 The BIG WIN HERE – you can now browse through the entire document in

the preview See all pages, see animations, zoom in, scroll through the entire document The point of this is to allow users to find the exact item they’re looking for right

in search results – no more clicking a result, hitting the back button, and on and on until they find the one they’re looking for

It also addresses the two major shortcomings of thumbnails in SharePoint 2010: It could only be used with FAST Search It did NOT work with claims authentication  Since there’s only one search engine in SharePoint 2013 you get document previews

out of the box In a different twist, previews only work with claims authentication – it will

not work with classic Windows authentication

Business Intelligence

Now available as Early Release

http://bit.ly/SharePointBI

Business Intelligence• Excel BI

• Instant analysis through In Memory BI Engine

• Power View Add-in

• Excel Services• Improved data exploration• Field List and Field Well Support• Calculated Measures and Members• Enhanced Timeline Controls

Business Intelligence• PerformancePoint Services

• Filter enhancements and Filter search• Dashboard migration• Support for Analysis Services Effective

User

• Visio Services• Refresh data from external sources –

BCS and Azure SQL• Supports comments on Visio Drawings• Maximum Cache Size service

parameter• Health Analyzer Rules to report on

Maximum Cache Size

Jason’s favorite new feature…

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

Tasks - Architecture

animated

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

Questions & Answers

Handy information• Jason’s info

• http://www.sharepointlonghorn.com • jase@sharepointlonghorn.com• @sharepointlhorn

• This Deck is available now at http://bit.ly/itproredpill

• SharePoint 2013 Presentation: ITPro training• http://www.microsoft.com/en-us/download/details.aspx?id=30361

• Wictor Wilen• Claims Auth: http://www.wictorwilen.se/sharepoint-2013-claims-is-the-new-black

• Spencer Harbar• Request Manager: http://www.harbar.net/articles/sp2013rm1.aspx

• Dan Holme• Shredded Storage: http://bit.ly/dh-shred

• Andrew Connell• Setup Guide for Devs: http://bit.ly/ac-devsetup2013

• Todd Klindt• http://www.toddklindt.com/blog• SPC 2012 shtuff: http://www.toddklindt.com/spc2012 • Weekly Netcast: http://www.stickam.com/toddklindt