SharePoint Upgrade, reel life experience, best practices #SPSBE02Knut Relbe-MoeApril 26th, 2014

Thanks to our sponsors!

Gold

Silver

Knut Relbe-MoeSenior Solution ArchitectTechnical Lead SharePointSteria ASOsloNorwayContact

@sharePTkarmEmail: knutrelbemoe@outlook.comBlog: www.sharepointblog.noSkype: shareptkarmMobile: 0047-98224609

My Experience: SharePoint evangelist, mentor, speaker Old developer, turned Architect / ITPro Have worked with SharePoint since the 2003 version. Worked with several clients upgrading their solution from

2007/2010 to 2013. Worked with several clients upgrading from 2013 to 2013

SP1 Works as a Lead Architect and advisor creating

SharePoint Farm architecture/infrastructure on many projects. With up to 25.000 users.

Worked with automating the installation and configuration of SharePoint.

I’m proud to work for:

Technet guide What can be upgraded? What about upgrade from 2007? Upgrade process – different options Step by step process on upgrading to SharePoint 2013 How to upgrade your custom solutions from 2010 to 2013. How to upgrade from 2013 to 2013 SP1

About this session

Some facts: SharePoint doesn’t support upgrading

straight from MOSS 2007 to SharePoint 2013. You first have to go trough SharePoint 2010.

SharePoint 2013 doesn’t support «In-Place upgrade». Which is a good thing!

SharePoint 2013 supports «database attach» which arrived with SharePoint 2010

SharePoint 2013 supports upgrade of some of the Service Applications

Upgrade?

Or

Migrate?

Technet

01.06.2013

So what about technet?

Technet doesn’t tell you what to do when it doesn’t go like planed…

Only one problem

What can be upgraded?

SharePoint Web applications/content

Custom Code

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

What can be upgraded?

What about upgrade from 2007?

I have SharePoint 2007… Should I skip 2010? You can’t skip 2010, because SharePoint doesn’t support

upgrading straight from MOSS 2007 to SharePoint 2010

Upgrade path

MOSS 2007 SharePoint 2010

SharePoint 2013

Another option If you don’t want to go trough SharePoint 2010, it’s plenty migration tools that support

migration from all the way back to 2003/2007. Under i Have linked some options (it’s many more), you need to look at the differences,

and choose the one which is right for you. This can change from project to project and the task you have in front of you.

Upgrade process – different options

Upgrade process – farm solutions

Setup 2013 farm

Deploy 2010

solutions

Copy databases

from SP 2010

Attach database to

SQL

Test database on

SP 2013

Mount database on

SP 2013

Uninstall 2010

solutions

Deploy upgraded

2013 solutions

Upgrade Site

Collections to 2013

Misc config scripts

Analyze todays environment

Clean up the 2010

environment

Migrate to claims if not

already done

Upgrade process – moving to the cloud – best practice

Could your 2010 code be replaced by

standard functionality

Yes

No

Great, use standard

functionality

Can you do it with the app

model

Yes Rewrite the code to app

model

NoThink how you can move it to the app model

anyways

Rewrite the code to 2013

solution

Color DescriptionBlue Supporting items for your decision

OrangeSolution is not cloud ready and can't be used with Office 365. So it has to be farm solution.

YellowYellow: Can't be used with Office 365 multitenant. Could work with Office 365 dedicated (please verify it with Microsoft before starting to build it).

Green Solution is cloud ready and can be used with Office 365

The decision chart is based on the idea, that you separate each use case and you do an evaluation for each of them. It could be that your solution is a mix of apps, sandbox solutions and a client application used to deploy and configure it.

Adrian Fiechter@adrianfiechter  http://tinyurl.com/oq87nnd

Iterative upgrade process

Tobias ZimmergrenEntrepreneur / Microsoft MVP / Technology Evangelist@zimmergrenwww.zimmergren.net

You can also take a look at Tobias Zimmergrens iterative upgrade process wheel.For more info about this go to his site:http://t.co/LMdhQh4wnD

Step by step process on upgrading to SharePoint 2013

Prepare and gather info Clean up the 2010 environment (Remove faulty features, solutions that should not be

used anymore) Build servers / install 2013 SharePoint Backup and upgrade of service application database Upgrade your SP 2010 code to SP 2013 Backup and upgrade of content databases Deploy 2010 WSP files to the 14 – hive in SP 2013 Test-SPContentDatabase – Correct any mistakes that occurs Mount-SPContentDatabase – Probably fails Migrate to claims Upgrade site collection – Upgrade SPSite http://server/sitecollection Deploy of SP2013 WSP-Files

Step by step process on upgrading to SharePoint 2013

Add and deploy any required O14 custom solutions in your SharePoint 2013 farm

Step by step process on upgrading to SharePoint 2013

Backup and restore the SharePoint 2010 content database to your SQL Server hosting SharePoint 2013 farm.

Step by step process on upgrading to SharePoint 2013

Run Test-SPContentDatabase cmdlet to identify missing components along with potential errors and related warnings.

Check the upgrade log and deploy any missing components and re run the cmdlet until no errors returned

Step by step process on upgrading to SharePoint 2013

Attach the content database to the desired web application using Mount-SPContentDatabase cmdlet.

Step by step process on upgrading to SharePoint 2013

After successfully mounting the content database to web application, the site should be accessible in 14 mode.

Step by step process on upgrading to SharePoint 2013

Run Get-SPSite -contentdatabase SP2010_24_Test_Content_Portal -Limit All | Upgrade-SPSite -VersionUpgrade. To perform visual upgrade.

Step by step process on upgrading to SharePoint 2013

Migrate to claims if you didn’t do it in the 2010 environment

Step by step process on upgrading to SharePoint 2013

Upgrade SP2010 code to SP2013

Deploy of SP2013 WSP-Files

Step by step process on upgrading to SharePoint 2013

Your site collection should now be accessible in the 15 mode along with all new capabilities enabled in the farm and for the hosting web application such as Social and Office Web Apps.

Step by step process on upgrading to SharePoint 2013

Upgrade your Custom Solutions

Get the latest version of visual studio developer tools with Web Platform Installer

Open your projects in Visual Studio

You’ll get a dialog saying “Do you want to upgrade <project name> to a SharePoint 2013 solution? Klick Yes.

Once the upgrade is complete, the solution can’t be deployed to SharePoint 2010. Do you want to continue?”

The migration report tells you how the upgrade went.

Hopefully there will be no Errors, only warnings and Messages

Check out the assembly references in your project that are pointing to any SharePoint assemblies

Note that the assemblies have automatically been updated to the correct version of the SharePoint 2013 assembly.

Replace all the paths in your project Path to the images folder Path to the layouts folder Path to the controltemplate

folder

Other code updates //images folder

//layouts folder

//controltemplates folder

Demo time: Content upgrade and code upgrade

Demo – summary Create web application in 2013 farm Set Source DB-To Read Only (in 2010 farm) Backup existing content DB. (in 2010 farm) Restore content db to new SQL Server Test upgrade process using:

Test-SPContentDatabase -name ContentDBName -webapplication http:/mydemo > c:\autid.txt

Review log files for errors/upgrade blockers Run Mount-SPContentDatabase command to upgrade DB (DB is updated but not

site collections) To upgrade the visual experience to 2013 on all site collections run the following

command: Get-SPSite -contentdatabase ContentDBName -Limit All | Upgrade-SPSite

–VersionUpgrade I have now shown you how to upgrade your custom solutions to 2013. But for each solution you have to consider, shall I just convert the code, or shall I

rewrite the code completely so it would also work with the new SharePoint App Model

Typical errorsLegacyUIDetectedMissingFeatureMissingSetupFileMissingAssemblyConfiguration

Look for UpgradeBlocking: FalseGreat!

Upgrading SharePoint 2013To: SharePoint 2013 SP1

1. Install SharePoint 2013 service-pack 1 on all servers.

2. Install SharePoint 2013 Language pack service pack 1 on all servers

3. Complete the upgrade with psconfig/config-wizard to complete on all servers

4. Install Windows 2012 R2 on all servers

Alternative 1:

Upgrade to 2013 Service Pack 11. Patch SharePoint 2013 Farm to SP1 –Microsoft just republished the SP1 Patch. Until then you have to reinstall the server

2. Install SharePoint 2013 service-pack 1 on all servers if not already done. Without SP1 we can’t run Windows 2012 R2 with SharePoint 2013 (and be supported at least).

3. Next, complete the upgrade with psconfig/config-wizard to complete the upgrade process. If a server hasn’t been fully patched done yet you’ll see a warning about software version mismatches.

Windows 2012 is perfectly capable of mounting local ISO files as a virtual disc. Click the ISO, then run setup when the ISO is mounted.

Prepare Windows 2012 R2 ISO

44

Run setup, accept the UAC elevation and begin the install. Get the updates

45

46

Make sure you install the GUI Windows only. SharePoint doesn’t support server core.

Make sure you select “upgrade” as it’s pretty much the entire point of this article/process.

Windows Upgrade Compatibility Check The compatibility check will point out the Hyper-V device drivers might not work after the

upgrade. We don’t mind. If you need to restart for any reason, setup will insist you do that 1st too here.

47

If your server has 4 million apps installed, these may cause problems with the upgrade. As this is my “production” environment, there is just SharePoint + prerequisites so this is what I see:

Running Setup & Upgrading Windows 2012 to R2 Once passed the compatibility checks, Windows setup should basically

keep itself busy for the rest of the process without any interruption needed

48

Setup will restart a couple of times.

Verify SharePoint Functionality & Fixing Errors As mentioned earlier, the upgrade to

Windows 2012 R2 can leave SharePoint rather broken by default.

Specifically the Security Token Service can break because of a problem with then SharePoint farm certificate.

Click on “view these issues” and you might see something like this:

How to fix it! STS is likely broken and the cache-cluster probably needs a reboot to get it

working again.

Fix the cache cluster by removing and then re-adding each cache server in turn

For STS errors, a simple psconfig upgrade command per failing server (psconfig -cmd upgrade -inplace b2b) should fix that problem up.

If not run the following commands to rebuild your environmentpsconfig -cmd services installpsconfig -cmd installfeaturespsconfig -cmd secureresources

Alternative 2:My recommendation.1. Reinstall the Servers.2. Install Windows 2012 R2 on all

servers3. Install SharePoint 2013 service-

pack 1 on all servers. 4. Install SharePoint 2013

Language pack service pack 1 on all servers

5. Join the SP1 servers to the farm6. Complete the upgrade with

psconfig/config-wizard to complete on all servers

7. Remove the old 2013 servers from the farm

Service Pack 1 Re-released

Upgrade to 2013 Service Pack 1 update Microsoft has just as promised re-released Service Pack 1 for SharePoint 2013.

If you have already installed SP1 install this update on top of SP1

Then run Config Wizard like you always should do after a patch/upgrade.

Link to the download of SP1 update SharePoint Foundation – KB – Download SharePoint Server – KB – Download Project Server – KB – Download Office Web Apps – KB – Download

Another note – Best practice on install

Scripted install of cumulative updates/Service Pack 1To save a lot of time during installation of cumulative updates / service pack, take a look at Russ Maxwell powershell script to script the installation. This will save you a lot of time.http://blogs.msdn.com/b/russmax/archive/2013/04/01/why-sharepoint-2013-cumulative-update-takes-5-hours-to-install.aspxThis script reduces the patch time from 5 hours to approximately 30 minutes

Another note – Best practice on install

About the script1. Disable the IISAdmin and SPTimerV4 service2. Shut down IIS Admin and Timer Services if they are running     3. Give you the option to Pause the Search Service Application (see search notes below)       4. Stop Search Services (see search notes below)  5. Install the patch in passive mode (No user interaction required but will witness the patch install in the UI)Note:  Power Shell should remain open in the background while patch is running6. Upon completion of the patch, the Power Shell script, services in step 1 are set to Automatic       7. Starts up IIS Admin and Timer Services                    8. Starts up Search services        9. Resume the Search Service Application if it was paused                                                                                                                       10. Finally, the script will display the Start Time and End Time for patch install

Drop the SharePoint cumulative/sp1 update in the same folder as the script. For instance C:\scripts 

How to run the scriptImportant:  Only one update should be placed here and the file extension should be .exe.

Finally, run the script from c:\scripts using SharePoint Management Shell.  

Example Screenshot during patching it looks like:

Example Screenshot – Patching is complete!

How to succeed upgrading SharePoint

How to succeed upgrading SharePointTest upgrade of all contentsTest, test and test againInvolve the business owners to early identify if the upgrade was

a successCreate a log of activities and prioritize the error handlingsRepeat the process with upgrading until end result is

acceptable.Expect that mistakes will happen, upgrade is never straight

forward. Make sure to have a plan to resolve the problems. Or consider not upgrading at all, recreate the site instead

How to succeed upgrading SharePointPlan the upgrade.Analyze todays solution up against new solutionHave any functionality written in 2010 been replaced with

standard 2013 functionality.Upgrade the code to work in SharePoint 2013, or rewrite the

code to use the App Model.Prepare for the future – move to Cloud / hybrid solutions.Use scripts to minimize the upgrade timeReinstall the servers instead of upgrading to minimize

downtime.

Another option: Don’t upgrade! Migrate the data instead of upgrading them

Microsoft doesn’t have any tools to support this, but it exists many 3trd party tools.

Tools can migrate everything from single files, libraries, site, site collections. You can also get the metadata with you.

They support migration to SharePoint Online.My experience is that they work best when you migrate simple content

like document libraries, files and so on.More complex migrations, also work, but requires a lot of testing, and

planning, and some will simply not work.

Different migration tools

And many others.

Summary

Summary I have now shared with you my best practices on how to upgrade your

SharePoint environment and solutions. Also I have shown you the best practices on how to script the installation

of cumulative updates and service packs. And last but not least I have shown you that to reduce downtime, the best

way of upgrading to SP2013 SP1 is to rebuild all the servers, and add the new servers to the farm, and remove the old.

To succeed involve business as soon as possible. Maybe it’s better to start from scratch and use the current solution as prototype.

Always consider different options before upgrade. If you have any other questions ask in the chat or drop me a

email or twitter message. Good luck with your upgrade projects!

Thanks toTobias ZimmergrenDan HolmeRuss MaxwellAnd many others.

My contact details:Twitter: @sharePTkarmEmail: knutrelbemoe@outlook.co

m / kirm@steria.noBlogg: http://www.sharepointblog.no Skype shareptkarm

Mobile: 0047-98224609Linkedin:

http://no.linkedin.com/pub/knut-relbe-moe/2/70b/6a/

Thank you!