SharePoint 2013 : What’s new upgrade and Migration

Leave a comment

This article is intended to briefly highlight what’s new in the upgrade/migration process with SharePoint 2013. It’s not a fully detailed migration plan.

Supported migration method

In order to upgrade from SharePoint 2010 to SharePoint 2013 you have to use the database attach method or 3rd party tools. The in-place upgrade method is not supported for a version upgrade (Ex: from 2010 to 2013). The in-place upgrade method is only supported for a B2B scenario (patch, service pack).

Quick steps to use the database attach method you need to:

  • Collect information and settings about your existing environment (http://technet.microsoft.com/en-us/library/ff645391.aspx or http://spsfarmreport.codeplex.com/ can help)
  • Create and configure a SharePoint 2013 farm and configure the new Farm
  • Backup the content database and service application databases from the SharePoint 2010 farm
  • Restore the content database and service application databases on the SharePoint 2013 farm
  • Attach and upgrade the database to a SharePoint 2013 farm
  • Upgrade the site collections
  • Verify that the upgrade process worked as expected
  • Apply customizations

Note: Claims-based authentication is now the default option for SharePoint 2013 Preview, you must use Windows PowerShell to create a web application that uses Windows Classic authentication or change the authentication method before backup/restore you database.

Not all the service application databases can be upgraded with the database attach upgrade method. For the SharePoint 2013 Preview, you can use the database attach upgrade method to upgrade the following service application databases:

  • Business Data Connectivity
  • Managed Metadata
  • PerformancePoint
  • Secure Store
  • User Profile (Profile, Social, and Sync databases)
  • Search administration

Note: Because of the changes in the SharePoint 2013 architecture, you should disable the Web Analytics (The presence of SharePoint Server 2010 Web Analytics information in your content databases could cause an error during upgrade) and PowerPoint Broadcasts sites (PowerPoint Broadcast sites cannot be upgraded to SharePoint Server 2013 Preview) before backing up your content databases.

My site upgrade

“For My Sites, make sure that you upgrade the My Site Host site collection before you allow users to upgrade their individual My Sites. This makes sure that the server software and database changes are complete so that users can start the upgrade of their individual My Sites successfully. Upgrade of a single My Site occurs the first time that a user browses to his or her individual My Site.” Source: http://technet.microsoft.com/en-us/library/jj219650(v=office.15).aspx

Deferred site collection upgrade

When you attach a SharePoint 2010 content database to a SharePoint 2013 Web Application, the database is upgraded but the site collection is not automatically updated. The site will run in SharePoint 2010 mode.

A status bar will be shown on the top of the ribbon to notify the site collection owner/administration that the site in ready to be upgraded. The site collection administrator/owner can upgrade the site now or choose to be reminded later.

With the use of PowerShell, Farm administrators can prevent the site collection administrators to start the upgrade process. The Farm administrator would then be responsible for the upgrade process and have more control.

Farm administrators can also control whether new site collection can be created only in SharePoint 15 mode (2013 for the moment), or SharePoint 2010 mode.

In SharePoint 2013 you can run site collection in SharePoint 2010 mode or in SharePoint 2013 mode on the same server. You get a true preview because the 14 and 15 hives are both installed on the server.

Upgrade evaluation site collection

In SharePoint 2010 it was possible to use the « Visual upgrade » to see what the upgraded 2007 site would look like in SharePoint 2010. The concept is similar with the “Upgrade evaluation site collection” where a site collection administrator can request a preview of the migrated site collection. After the request, a timer job is scheduled to run once a day in order to create a complete copy the requested site collection and upgrade the copy to SharePoint 2013.

Since it is a true copy, changes made to the copy do not affect the original site. The “preview site” will have its own separate url. The “preview site” has a 30 days lifetime by default. After the 30 days the “preview site” is deleted.

“Farm administrators can choose to prevent users from creating upgrade evaluation sites by setting the SPSite.AllowSelfServiceUpgradeEvaluation property for a site collection.”

Source: http://technet.microsoft.com/en-us/library/ff191199(v=office.15)

Site collection health checks

Like any upgrade/migration you should make sure that your customizations can be upgraded. SharePoint 2013 includes the “site collection health check” to help you make some verification to your site prior to upgrading.

The site collection health check includes a set of rules that could be run against a site collection to verify possible issues before the migration. This can be performed by the site collection administrator from the “site settings” or by the Farm administrator with PowerShell.

You should not rely only on this check before you upgrade your site. You should always test the upgrade process in a test environment before doing your real upgrade.

Site collection health check rules

Rule name

Description

Customized Files
This rule checks for any files that were customized (or unghosted) in the site collection or subsites. When run in repair mode, it can reset the page to the default (reghost the file).
Missing Galleries
This rule checks for all default galleries and reports if any are missing from the site collection or subsites.
Missing Site Templates
This rule checks to make sure that the template the site is based on is available and reports if any elements are missing.
Unsupported Language Pack References
This rule checks to make sure that the language packs that are used by the site collection exist and are referenced correctly by the site collection.
Unsupported MUI References
This rule checks to make sure that the multi-user interface elements that are used by the site collection exist and are referenced correctly by the site collection.

Source: http://technet.microsoft.com/en-us/library/jj219720(v=office.15)

Throttles for site collection upgrade

“To make sure that site collection upgrades do not cause an outage on your farm, there are throttles built in at the web application, database, and content level. This means that even if 100 site collection owners decide to upgrade their site collections at the same time, only some are run at the same time, and the rest are put into a queue to run later.” Source: http://technet.microsoft.com/en-us/library/ff191199(v=office.15).aspx

Upgrade from 2007 to 2013

At the moment of writing this article you can do a database attach only from 2010 to 2013. This means that if you have a Microsoft SharePoint Server 2007 farm you would need to upgrade your databases to 2010 then attach them to a SharePoint 2013 server.

Links on upgrade to SharePoint 2013

Find below a list of links for articles that were published on the Microsoft to help you to go further in you preparation to upgrade to SharePoint 2013.

Get started with upgrades to SharePoint 2013 Preview

What’s new in SharePoint 2013 upgrade

Plan for upgrade to SharePoint 2013 Preview

Attach databases and upgrade to SharePoint 2013 Preview

Services upgrade overview for SharePoint Server 2013 Preview

Plan for site collection upgrades in SharePoint 2013 Preview

Manage site collection upgrades to SharePoint 2013 Preview

Upgrade a site collection to SharePoint 2013

Run site collection health checks in SharePoint 2013 Preview

Upgrade and migrate to SharePoint 2013 (IT pros)

Troubleshoot site collection upgrade issues in SharePoint 2013 Preview

SharePoint 2013 : What’s new on Installation

Leave a comment

The installation process has not changed much from SharePoint 2010 to SharePoint 2013. The bigger change is in the Prerequisite software. But the Prerequisite installer takes good care of this part.

In this article you will find quick steps to install SharePoint Server 2013 Preview and allow you to test drive this new version of SharePoint.  These steps are a good starting point to work with the Preview version, but I would add more steps before installing a production environment. You will find the hardware and software requirements for the SharePoint Servers and Database Servers.

Installation quick Steps:

  1. Download SharePoint Server 2013 Preview from: http://technet.microsoft.com/en-US/evalcenter/hh973397.aspx?wt.mc_id=TEC_121_1_33
  2. Install the 64-bit edition of Windows Server 2008 R2 Service Pack 1 (SP1) Standard, Enterprise, or Datacenter or the 64-bit edition of Windows Server 2012 Release Candidate Standard, Enterprise, or Datacenter on the SharePoint Server with the minimum Software and Hardware (see below)
  3. Join SharePoint Server to the domain
  4. Install the 64-bit edition of Windows Server 2008 R2 Service Pack 1 (SP1) Standard, Enterprise, or Datacenter or the 64-bit edition of Windows Server 2012 Release Candidate Standard, Enterprise, or Datacenter on the SQL Server with at least the minimum software and hardware requirements (See below)
  5. Join the SQL Server to the domain
  6. Install The 64-bit edition of SQL Server 2008 R2 Service Pack 1 (Minimum requirement you can install SQL Server 2012)
  7. Create an account for installation and make this account Local administrator on the SharePoint Server
  8. Give the installation account the dbcreator and securityadmin Role on the SQL Server instance.
  9. Log on the SharePoint Server with the installation account created previously and install the SharePoint Server 2013 prerequisite either from the set-up page or the command (see below).
  10. Create a domain account for the SharePoint farm administration.
  11. From the set-up page Install SharePoint Server 2013 Preview on the SharePoint Server
  12. Once the SharePoint Server 2013 preview installation is completed you need to run the SharePoint Configuration Wizard to create a new farm. You have two options Complete or Standalone ( I recommend Complete)
  13. You will need the name of the SQL Server, the name of the farm configuration database, the username and password of the farm service account and a Passphrase.
  14. Once the SharePoint configuration Wizard completes you could run the Farm configuration Wizard to configure the services. I prefer configuring the services using PowerShell scripts or manually. I don’t like the Wizards.

If everything goes well the SharePoint Central Administration site will open up in your browser and you will be able to configure your farm and create Web applications to test SharePoint Server 2013 Preview.

Note: Using the following link you can download a Deployment guide for SharePoint Server 2013 preview where you will find additional steps to install and configure your SharePoint 2013 preview farm. Ex: How to create a SQL Alias, and how to configure SQL Server to be more secure.

Important:
SharePoint 2013 Preview does not support single label domain names. For more information, see Information about configuring Windows for domains with single-label DNS names.

Hardware and software requirement SharePoint Server:

Installation Scenario

Deployment type and scale

RAM

Processor

Hard disk space

Single server with a built-in database or single server that uses SQL Server Development or evaluation installation of SharePoint Foundation 2013 Preview 8 GB 64-bit, 4 cores 80 GB for system drive
Single server with a built-in database or single server that uses SQL Server Development or evaluation installation of SharePoint Server 2013 Preview 24 GB 64-bit, 4 cores 80 GB for system drive
Web server or application server in a three-tier farm Pilot, user acceptance test, or production deployment of SharePoint Server 2013 Preview 12 GB 64-bit, 4 cores 80 GB for system drive

Minimum software requirements for front-end web servers and application servers in a farm:

  • The 64-bit edition of Windows Server 2008 R2 Service Pack 1 (SP1) Standard, Enterprise, or Datacenter or the 64-bit edition of Windows Server 2012 Release Candidate Standard, Enterprise, or Datacenter.
  • KB 2554876 (http://support.microsoft.com/kb/2554876)
  • Windows KB -IIS Configuration Changes KB 2708075 (http://support.microsoft.com/kb/2708075)
  • The Microsoft SharePoint Products Preparation Tool installs the following prerequisites for front-end web servers and application servers in a farm:
    • Web Server (IIS) role
    • Application Server role
    • Microsoft .NET Framework version 4.5 Release Candidate (RC)
    • SQL Server 2008 R2 SP1 Native Client
    • Microsoft WCF Data Services 5.0
    • Microsoft Information Protection and Control Client (MSIPC)
    • Microsoft Sync Framework Runtime v1.0 SP1 (x64)
    • Windows Management Framework 3.0 Release Candidate (RC) which includes Windows PowerShell 3.0
    • Windows Identity Foundation (WIF) 1.0 and Microsoft Identity Extensions (previously named WIF 1.1)
    • Windows Server AppFabric
    • Cumulative Update Package 1 for Microsoft AppFabric 1.1 for Windows Server (KB 2671763)

The SharePoint 2013 Preview prerequisite installer (prerequisiteinstaller.exe) will install the prerequisite. It can be run from the set-up page or from a command line.


When you run it from the set-up page you will need internet connectivity on your server to download the packages. When you run it from the command line, you can download all the packages and tell the installer to install from the downloaded packages.

NOTE: The prerequisite installer creates log files at %TEMP%\prerequisiteinstaller.<date>.<time>.log. You can check these log files for specific details about all changes the installer makes to the target computer.

Hardware and Software requirement Database Server:

Component

Minimum requirement

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

For large deployments, see the “Estimate memory requirements” section in Storage and SQL Server capacity planning and configuration (SharePoint Server 2010).

These values are larger than those recommended as the minimum values for SQL Server because of the distribution of data that is required for a SharePoint 2013 Preview environment. For more information about SQL Server system requirements, see Hardware and Software Requirements for Installing SQL Server 2008 R2.

Hard disk 80 GB for system drive
Hard disk space depends on how much content that you have in your deployment. For information about how to estimate the amount of content and other databases for your deployment, see Storage and SQL Server capacity planning and configuration (SharePoint Server 2010).

Minimum requirements for a database server in a farm:

Source:
http://technet.microsoft.com/en-us/library/cc262485(office.15).aspx

What’s new in SharePoint 2013 Series

Leave a comment

In the next weeks I will be working on a serie of articles to describe new features in SharePoint 2013.  This post will will updated regurlarly with the links for the different articles.  Here are the subject that I am planning to cover:

SharePoint 2013: What’s new on Installation

SharePoint 2013: What’s new on Upgrade and Migration

SharePoint 2013:: What’s new in the Architecture

SharePoint 2013: What’s new for the end user

SharePoint 2013: What’s new in ECM

SharePoint 2013: What’s new in WCM

SharePoint 2013: What’s new in BI

SharePoint 2013: What’s new in Social

SharePoint 2013: What’s new in Branding

SharePoint 2013: What’s new in Developpement

SharePoint 2013 Technical Preview available

2 Comments

Today Microsoft has announced SharePoint and Office 2013 Technical preview.

There are already a lot of documents and visio diagram to help understand what is coming up in the next wersion of SharPoint.  Here is a list of the links that were available at the moment of this post.  There will be a lot more documentation coming up this week.  I will also make sure to write a few articles about my experience with the product.  Meanwhile you can read these documents:

Newly published documents about SharePoint

Leave a comment

Here is a list of newly published or updated documents about SharePoint

How to configure Claim to Windows Token Services in SharePoint 2010 with Kerberos Authentication

http://support.microsoft.com/kb/2722087

How to configure Visio Graphics Services in SharePoint Server 2010 for Kerberos authentication

http://support.microsoft.com/kb/2723977

Change in behavior of SharePoint Server 2010 Output Cache after April 2012 CU

http://support.microsoft.com/kb/2714963

Unable to customize form for published content types

http://support.microsoft.com/kb/2717706

Serge

End of support for MOSS and WSS 3.0

1 Comment

If you are still using MOSS 2007 or WSS 3.0 be aware that the Mainstream support for these products will end on October 9th 2012.

3. What is the difference between Mainstream Support, Extended Support, and online self-help support?

From this site:http://support.microsoft.com/gp/lifepolicy

Support provided

Mainstream Support phase

Extended Support phase

Paid support   (per-incident, per hour, and others)

X

X

Security update support

X

X

Non-security hotfix support

X

Requires   extended hotfix agreement, purchased within 90 days of mainstream support   ending.

No-charge incident support

X

Warranty claims

X

Design   changes and feature requests

X

Product-specific   information that is available by using the online Microsoft Knowledge Base

X

X

Product-specific   information that is available by using the Support site at Microsoft Help and   Support to find answers to technical questions

X

X

Note A hotfix is a modification to the commercially available Microsoft product software code to address specific critical problems.

You can also view this article: http://blogs.technet.com/b/stefan_gossner/archive/2012/06/21/are-you-still-using-wss-3-0-or-moss-2007.aspx

Serge

SharePoint Saturday Toronto

3 Comments

Just coming back from SharePoint Saturday in Toronto.  It was a great day.  My presentation on configuring BCS and Search will be available shortly on the SharePoint Saturday Web site.

http://www.sharepointsaturday.org/toronto/default.aspx

Serge