EMEA (Europe, Middle East and Africa) Premier Field Engineer

at Microsoft Corporation
Technologies: Microsoft SharePoint Products and Windows
PowerShell
Email: david.rosa@microsoft.com
Twitter: @davidaspt
Linkedin: http://www.linkedin.com/in/davidalexandrerosa

System Requirements
Architectural Changes
Development Model
Themes and Look & Feel
Working Sharing and Offline
Enterprise Content Management
Web Content Management

Social and Connected Experiences

Business Intelligence
Demos

Load balanced or routed requests

Web tier

Processor: 64-bit, 4 cores

RAM: Web Front-End or Application
Server on a Three-tier farm 12 GB
Hard disk: 80 GB free for system drive
Maintain 2x free space as available
RAM

Application tier

Database tier

Web servers with

query component

Application servers with:

Central Administration
Search administration
component
Crawl component

Database server with:

Central Administration
configuration and content
databases
Content databases
Search administration database
Crawl database
Property database

Load balanced or routed requests

Web tier

Processor: 64-bit, 4 cores for small

deployments and 8 cores for
medium deployments
RAM: 8 GB for small deployments
and 16 GB for medium deployments
Hard disk: 80 GB free for system drive
SharePoint data storage depends on
several requirements

Application tier

Database tier

Web servers with

query component

Application servers with:

Central Administration
Search administration
component
Crawl component

Database server with:

Central Administration
configuration and content
databases
Content databases
Search administration database
Crawl database
Property database

64-bit edition of Windows Server 2008 R2 Service Pack 1

(SP1) Standard, Enterprise or Data Center
Windows Server 2012 Standard or Datacenter

Web Server (IIS) role

Application Server role(s)

Microsoft .NET Framework 4.5

Microsoft Information Protection &

Control Client (MSIPC)

Windows Identity Foundation 1.0

and WIF Extensions

SQL Native Client 2008 R2 SP1

Sync Framework 1.0 SP1

Windows Server AppFabric (Velocity)

+ CU1 (KB2671763)

WCF Data Services 5.0 (ODataLib

Open Data Library)

Windows PowerShell 3.0

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

1 or Microsoft SQL Server 2012
For Business Intelligence Scenarios SQL Server 2012 SP1 is
required
64-bit edition of Windows Server 2008 R2 Service Pack 1
(SP1) Standard, Enterprise or Datacenter or Windows Server
2012 Standard or Datacenter

For full offline and integrated experience

SharePoint Designer 2010 only works for 2010 mode sites

SharePoint Designer 2013 works for both 2010 and 2013 mode sites

SharePoint Workspace 2010 work for 2010 mode (14 mode) sites
2013 introduces new SkyDrive Pro to replace this product part of Office

installation

Browser

Supported

Internet Explorer 10

Internet Explorer 9

Internet Explorer 8

Not Supported

Internet Explorer 7

Internet Explorer 6

Google Chrome (Latest released version)

Mozilla Firefox (latest released version)

Apple Safari (latest released version)

WCM features in 2013 provide deep level of control over

markup and styling
Designers can target browser compatibility based on
user agents
Includes different mobile devices
IE6 or standards based (IE8+, Firefox 5.x, etc.)
Design Manager for easy markup editing and
modification for different browsers

 SharePoint Preparation Tool

Checks the presence of prerequisites

Installs and configures required packages
Requires Internet Connection to pull down missing
prerequisites otherwise will pinpoint missing
prerequisites
Can be run w/o Internet Connection to check for
missing prerequisites

 Public updates and hotfixes packages

Update Web Front-Ends & Application Servers as

appropriate
Ensure SQL Updates installed
Ensure all SharePoint servers are at the same patch
level

Run on Web and Application servers

Ensure you are logged on as local admin
If running from bits on a file system, locate and run
prerequisiteinstaller.exe from the SharePoint 2013 bits
folder
Otherwise, if you install from bootable image click
Install software prerequisites
May require several server reboot however
preparation tool will continue to run after restart
Click Finish on the Installation Complete page

Verify that you have an accurate list of the required software

and download them
Create a shared folder on a computer that can be accessed by
the servers on which the prerequisites will be installed
Copy the files that you downloaded from the Internet to the
shared folder
Execute PrerequisiteInstaller from command prompt with
appropriate switches
Full list of switches - PrerequisiteInstaller.exe /?

Example - PrerequisiteInstaller.exe /SQLNCli: "\\o15-fi-admin\SP_prereqs\sqlncli.msi" /IDFX: "\\o15-fiadmin\SP_prereqs\Windows6.1-KB974405-x64.msu"

After completing Preparation tool you must also install following KBs:

KB 2554876 - The SharePoint parsing process crashes (for Windows 2008 R2 SP1)
KB 2708075 - FIX: IIS 7.5 configurations are not updated when you use the
ServerManager class to commit configuration changes (for Windows 2008 R2 SP1)
KB 2472264 - You cannot customize some TCP configurations by using the netsh
command (for Windows 2008 R2 SP1)
KB2759112 - Hotfix: ASP.NET race condition in .NET 4.5 RTM (for Windows 2008 R2
SP1)
KB2765317 - Hotfix: ASP.NET race condition in .NET 4.5 RTM (for Windows 2012)

Login as local administrator using specific Setup account

Installation steps similar to SharePoint 2010
Install on all SharePoint WFE & Application servers
Run Configuration Wizard when setup is finished on all servers
Configure diagnostic logging/usage health data/etc.
Configure service applications and other required services
Farm configuration wizard exists like in 2010 for automating this in
developer, test and sandbox environments
PowerShell and manual creation of service applications in production
environments
Create Web apps, site collections/sites, based on requirements

Download language pack from Internet

Login using Setup account which you used for initial
installation of SharePoint
Run setup for language pack
Run SharePoint 2013 Configuration Wizard
Repeat steps on each server of the farm

The goal is to make changes equal to the size of the change, not size of the
file

When a file is updated via Cobalt, only the bits that have changed are sent
over the wire from the client to the SharePoint WFE. However, because
SharePoint lacks the concept of incremental updates to SQL we are forced to:
Pull the entire file to the WFE
Merge the changes into it
Write the entire file back to SQL

We break the file into pieces and store that in SQL

On update we only touch the shredded blobs that correspond to the updated
bits
No more round tripping entire files to the WFE and back

Weve reduced scenarios that might invoke full table scans

There have been lots of improvements around finding docs for link fix-up and
alert handling
Reduced data redundancy for some features
Using advanced indexing features provided by SQL 2008 R2
Changes in architecture to support wide lists, i.e. lists where a single item
spans multiple rows in the database to hold the data

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
SharePoint ONLY supports the version of caching that it ships you cannot
independently upgrade it.

The config DB keeps track of which

machines in the farm are running the
cache service
It is all provisioned by SharePoint setup
A new Windows service the
Distributed Cache service is installed
on each server in the farm when
SharePoint is installed

There are a few new service applications in SharePoint 2013:

App Management Service: allows you to install SharePoint apps from the Office
Marketplace or the App Catalog
SharePoint Translation Services: does simple language translation of Word, PPT,
and XLIFF files into HTML
Work Management Service: provides task aggregation across systems such as
SharePoint, Exchange and Project
Workflow Manager is new and not really a service app but similar; provides an
externalized host using REST and OAuth to run workflows

Office Web Apps is no longer a service application

Web Analytics is no longer a service application

URLs have been cleaned to be human friendly and

understandable!

From this:
http://office/2013/collab/Demo/_layouts/PowerPoint.aspx?PowerPointView=ReadingView&PresentationId=/2013/collab/Demo/Docs/w
ac.pptx&Source=http%3A%2F%2Foffice%2F2013%2Fcollab%2Fdemo%2Fdocs%2FTraining%2520Module%2Fdocsethomepage%2Easp
x%3FID%3D96%26FolderCTID%3D0x0120D52000DC71A13124DA5249ACA958C4DFD092C90037E1F59EB352013B4F940A3806D9B183F
0%26List%3Dc910e954%2D68ca%2D42ae%2Dbb0f%2D1c6908c73e77%26RootFolder%3D%252F2013%252Fcollab%252Fdemo%252F
wac%25202013&DefaultItemOpen=1

To this:
http://office/2013/collab/Demo/Docs/wac.pptx?Web=1

OWA is now a separate server product, not a service

application
You can create an OWA farm that can support multiple
SharePoint farms
You can view files from a number of different data sources,
including:

SharePoint
Exchange
Lync
File servers

This allows you to scale and manage OWA separately

from other Microsoft server products, as well as share
that infrastructure between them
OWA farm version does not need to be in sync with
SharePoint farm
You connect your SharePoint farm to the OWA farm
using PowerShell
NewSPWOPIBinding

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 that
Couldnt promote search results based on an items popularity
(as determined by # of times an item was viewed)
It required a very powerful SQL box and significant storage
and IO
Lists dont have explicit view counts
The architecture had problems scaling to large numbers

Worth highlighting:
User Profile Replication Engine
Profile Sync Changes
My Site Data Store Changes

SharePoint 2013 User Profile Replication Engine (UPRE)

In SharePoint 2013 the UPRE has had ownership given back to the SharePoint
Base team
It has been more like a toolkit deliverable in the past and has suffered some
reliability issues
Bringing it in with core Product Group ownership will ensure it gets the right
developers and testing applied to it
UPRE is available as a separate download on the web

Profile Sync Performance Improvements

Performance improvement goals are to reduce full import time from 2 weeks
down to 60 hours for very large directories (i.e. 200K users, 600K groups)
One piece of anecdotal evidence: 300K users, less than 7 hours for full import;
previously it took nearly three weeks
Some of those improvements included:

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
Cleaning up unused historical data
Move resolution of some objects out of SharePoint and into the sync system

New Profile Synchronization Option

Active Directory Direct Import

Active Directory forest with multiple domains, one connection per domain
Selection of OUs from which to import
Import User and Group objects
Simple text-filters written in LDAP syntax
Full and incremental import
You can switch back between FIM and AD Direct

Stretched farms are no longer supported in SharePoint 2013

Stretched means different data centers with less than 1ms latency
All servers in the farm, including SQL, must be in the same physical building
now
User Profile Service Application across enterprise

For 100% fidelity in 100% of features, we recommend you have only one User Profile
service application (UPA) in your enterprise

Certain social features will have a very slightly degraded experience unless:

There is only one enterprise UPA

All server farms are connected to it by local network consuming UPA over a WAN is not supported

Full Trust Solutions

No real control

Sandbox
Partial control

SP Code
SP Code

More custom
code: aspx, dlls,
web services, GAC

Support is a nightmare

Upgrade is quite a challenge

Securing code to run in hosted environments is effectively impossible

Sandboxed
Custom Code

App Model
Control, Trust, Manage
SP Code

Isolated
App client
side code

Host/language independent

Way too strict for developers

Management and update easily doable per app

Hard to maintain and expand

Emprases reusability

Managed by your self

No server side sandbox, improved CSOM

App code
(client or
server)

2003 What is an Application?

SharePoint was not an Application Platform, except web parts

Investments were in portals and content

Push to embrace SharePoint for LOB applications

Experience was to write custom server side code

SharePoint and Developer Tools come together

Silverlight, CSOM and other new capabilities
Partially trusted code reduces impact and risk to farm

Client side experience via html or iFrame

Leverage CSOM and REST APIs from Azure and other clients
Investments in app discovery and management via SharePoint store

2007 Everything is an Application!

2010 Choose the right Application
2013 Redefine Application as App

Apps can be found in two places the Office Store and App Catalog
The Office Store is just like the market places you know Windows 8 and
Windows Phone
The App Catalog is like an on-premises version of the Store
Its an internal location where you can publish applications purchased or
developed in house
Users install apps from the Store or catalog

App Catalog

Each web application has a catalog, which is stored in a site collection

Since it uses a standard site collection, you can manage it in much the same
way as you would any other site
Scaling
Backup and Restore
Permissions
The catalog site collection uses two document libraries for the catalog features:
Apps for SharePoint and Apps for Office

Apps for SharePoint can use two different host types in an on-premise farm:

Provider Hosted an application that is hosted in Windows Azure or other external

host. It renders as full page or iFrame on a page
SharePoint Hosted an application that is hosted in SharePoint. At installation time a
separate sub-web is created for each app for security reasons
Auto Hosted is a third option only available for o365 sites

Provider-hosted applications have an authorization process they go through to

get access to content in a SharePoint site

An App for SharePoint uses the security of the current site

These apps also use a prefix and App Domain in the Url, which is hosted in a
separate subweb in SharePoint
Configured in central admin one per farm
Requires a DNS wildcard entry, i.e. contosoapps.com
The Url for the app then looks something like this:

https://apps-87e90ada14c175.contosoapps.com/myapp/pages/default.aspx

For most common scenario intranet with multiple web apps, not using SSL it
means you may need an additional web app to listen for SharePoint App
requests

An App for SharePoint uses the security of the current site

These apps also use a prefix and App Domain in the Url, which is hosted in a
separate subweb in SharePoint
Configured in central admin one per farm
Requires a DNS wildcard entry, i.e. contosoapps.com
The Url for the app then looks something like this:

https://apps-87e90ada14c175.contosoapps.com/myapp/pages/default.aspx

For most common scenario intranet with multiple web apps, not using SSL it
means you may need an additional web app to listen for SharePoint App
requests

http://app-bf473b5225nn0f.apps.contoso.com/SharePointAppTitle

Dissecting the App URL:

http://tenant-APPUID.domain.com/APPNAME

APPUID

APPNAME

Unique ID given to each

app installation in tenancy

Name of SPWeb under where app

is installed

Makes each app domain unique

Developers have control

End users will typically find apps by going to Add an App for the site

Team sites include a big button to reach the Add an App

page on the home page by default
All apps can be browsed or searched
New apps automatically percolate to the top
Specific apps can be designated as a featured app by a catalog admin; featured
apps show up at the top of the list

Farm
Full trust solutions
Customizations to file
system of servers
Hosted in same process
as SharePoint
Server side SharePoint
API access
Classic model from 2007

Sandbox

SP Apps

Declarative elements
Partially trusted code
service still included for
limited server side support
Hosted
in isolated
process
Deprecated
in SP2013
Limited server side
SharePoint API access

New Apps model

Deployed from corporate
catalog or SharePoint
store
Manage permission and
licenses specifically
Simple install and
upgrade process
Preferred option

No custom code on the SharePoint server

Easier to upgrade to future versions of SharePoint
Works in hosted environments w/o limitations
Reduces the ramp-up time for those building apps
Dont need to know/be as familiar with SharePoint -isms
Leverage hosting platform features in new apps
Enables taking SharePoint apps to different levels further than what can be
done with farm / sandbox solutions
Isolation private vs. public clouds

Developer Dashboard rebuild for SP2013 to provide more additional information

for its user

Running in separate window to avoid affecting rendering of actual page

Detailed request information per page with Gantt view
Dedicated tab for ULS log entries for particular request
Additional detailed information included for request analyzing
Works by using dedicated WCF service (diagnosticsdata.svc) designed for the purpose of providing
tracing information for developer dashboard

Key investments are in workflow

management

New workflow configuration

New 2013 workflow model with Workflow Manager

Support for example for copy-paste operations in

workflow designing
Design and split view option removed from SPD

Easy and visual workflow designing

directly in SharePoint Designer

 Workflow now treated as a service

Moved to Workflow Manager

Doesnt have to run in the SharePoint farm

Can still runs on SharePoint WFE / App servers
Harnesses the latest workflow technology from Microsoft

SharePoint deployment drives where workflow

runs

On-Prem: Workflow Manager

Hosted: Windows Azure Workflow Service

Improves stability, scalability & transparency

 Introducing Stages

Mitigates SharePoint Designers lack of loop support

Provides functionality of state machine workflows in WF 3.5

Loop # times / with condition / with expression

Declarative workflows have loops

Declarative workflows can call REST/SOAP

services

Theme styling has been dramatically improved:

Everything is now based on XML instead of a proprietary format
PowerPoint is no longer used to create custom themes
We support web fonts, enabling web site designers to build a custom look
without having to worry whether clients have the fonts installed locally
You get much richer themes and common building blocks for customizing
them
A background image, palette and fonts with live preview
The ability to preview how a site theme will look has been streamlined and no
longer requires the publishing feature to work

This is what the theme experience looks like now, along with a sample of a site
based on a customized theme:

Sharing in SharePoint 2013 is designed to address these limitations with the

Sharing feature:
A Sharing dialog for adding users and security groups
Integrated with Office 2013 client applications so items can be shared directly
from them
An email invitation with a message that can be customized when its sent out
A request on behalf of feature, where if you dont have rights to add
someone to the site, you can send a request on someone elses behalf.
A requests management page where admins can view and respond to all
requests
A conversation component to requests, so admins and users can have a
dialog about the request

SkyDrive Pro enables people to synchronize their

work documents from SharePoint to the cloud, and
also take documents offline when they're on the go.
People can access or edit their documents across
devices; files are automatically synchronized with
SkyDrive Pro when connected online.

One of the new features added to in SharePoint 2013 is the ability to drag and
drop files directly to document libraries from the browser. This allows users drag
one or more files from their system drop it onto the browser and files will
uploaded to the document library. This feature works not only in IE but in
Firefox and Google chrome as well

Metadata as enabler for different functionalities

Navigation, term and search driven pages
Numerous new capabilities for term store manager
to enhance term usage models
Multilingual improvements and new capabilities
Dataview editing support included
Taxonomy API exposed via CSOM and REST for
extensibility purposes

Cross site collection term access for private

groups
Pinning terms
User interface for custom property editing
Indication of the term set usage for other
SP2013 functionalities
Additional multilingual support with
automatic translation support
Block users from using keywords outside of
specific term set

Support for OneNote notebooks

Document set icon on search results
Folders supported
Support for easier aggregation
Better development support
Versioning improvements
Search directly in document set

Office Web Applications is no longer a Service Application

You can use it with Microsoft Lync, Microsoft Exchange
and Microsoft SharePoint!
Word, Excel, PowerPoint and OneNote Web Apps can
view files from File Servers
3rd parties can integrate with OWA to provide access to
documents in their data sources, e.g EMC Documentum,
IBM FileNet, OpenText, etc.

Exchange and SharePoint together

Documents are stored in SharePoint
Emails are stored in Exchange
Site mailboxes can receive emails and have their own
email address
Easy access to both from Outlook and SharePoint
Unified compliance policy applies to both

Support the tools and workflows designers use

Variations & Content Translation
Search Engine Optimization
Cross Site Publishing
Video and Embedding
Image Renditions
Clean Urls
Metadata Navigation

Social

Microblogging
Share content, links and media
Follow people, sites, content and conversations
Activity Feeds
Provides a view into recent activity related to
content, links, media and people

Social

Communities

Community sites with self-service

administration and moderation
Modern community features such as
achievements and reputation

Discussions

Modern discussion boards

Client application integration

Categories, comments and moderation

Blogs

Mobile
Classic and contemporary views for
mobile browsers
Automatic mobile browser redirection
Target different designs based on user
agent string
Office Mobile Web Apps
Word
PowerPoint
Excel

Enterprise Search Improvements

New Search Architecture with one

unified search
Personalized search results based on
search history
Rich contextual previews

Excel BI with instant analysis in

memory BI engine with PowerPivot
Excel Services

Improved data exploration

Field list and field well support
Calculated measures and members
Enhanced timeline controls

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 commends on Visio Drawings
Maximum cache size service parameter