SP24: BESTPRACTICES ON UPGRADING SHAREPOINT FROM 2007/2010 TO 2013

Hello guys, if you wasn’t able to watch my session on the biggest online conference SP24, then it’s now available to watch at any time you want.

All you have to do is register at the site if you haven’t done it already.

Check it out here:

https://www.sp24conf.com/2014-1/Conf/SP24S084/ConfPages/SessionRoom.aspx

 

If you have some questions or need some help upgrading or migration SharePoint don’t hesitate to ask me.

My contact details:

Skype: shareptkarm

Twitter: @shareptkarm

Email: knutrelbemoe(at)outlook.com

Phone: (0047) – 98224609

 

Happy SharePointing.

Files from my SPSDubai Session

Link to blogs about same topic:

Upgrading SharePoint 2013 to 2013 SP1

Step by step process on upgrading your wsp files (Visual Studio 2010) to 2012/2013

Step by step process on upgrading your 2010 environment to 2013

Link to my session files: Session Files

 

If you have some questions just write to me:

Email: knutrelbemoe(at)outlook.com

Phone: 0047-98224609

Twitter: SharePtkarm

Skype: SharePtkarm

Files from my SPSBE02 Session SharePoint Upgrade, reel life experience, best practices

Hello everybody. Thanks to everyone who attended my session. If you have questions or want help with your upgrade/migration plan, don’t hesitate to contact me. Sorry for not going to deep into all aspects in my session, just to little time to manage with such a big topic. So If you have problems with you upgrade either from 2007 or 2010 don’t hesitate to contact me.

Here are the files from my session at SPSBE conference. SharePoint Upgrade, reel life experience, best practices

Check also out my other blog post about upgrading SharePoint

Also take a look at this post for tips on setting up your SQL Server

If you have questions also about infrastructure/architecture of SharePoint don’t hesitate to ask, or about how to backup your Office 365 solution, or how to migrate to Office 365. Or how to use Azure as a Failover for your OnPremise environment for instance. This is also topics where I have alot of experience.

Maybe I’ll see someone of you on my speaker session in Dubai on 17th of May, or maybe at the SharePoint Saturday in Oslo in end of may?

Best regards

Knut

Skype: shareptkarm

Email: knutrelbemoe(at)outlook.com

Phone: 004798224609

 

Upgrading SharePoint 2013 To SharePoint 2013 SP1

If you want to upgrade your SharePoint 2013 environment to the lastes Service pack 1 you have 2 alternatives.

1. Upgrade your SharePoint environment to Service Pack 1 then upgrade servers to Windows Server 2012 R2

2. Rebuild all of your servers with new servers installed with Service Pack1 and Windows Server 2012 R2

I will not explain you how you can upgrade your environment because Microsoft for now have pulled back the Service Pack 1 update package. I will describe this in a seperate blog post. But I will instead in this blog post explain to you the steps involved installing service pack 1.

Because with all my experience this is the best way of upgrading the SharePoint servers, because you will reduce the risks of errors while upgrading the servers, and you will also reduce the downtime.

For instance if you had upgraded the servers with the upgrade patch (Service Pack 1) which is pulled, most likely you would either have problems with the Security Token Service (STS) and the Distributed cache.

Bilde16

 

So this is then step by step process on upgrading from SharePoint 2013 to SharePoint 2013 SP1

1. Reinstall all servers with Windows Server 2012 R2 .

2. Install the slipstream version of SharePoint 2013 SP1 on all servers with AutoSPInstaller and AutoSPSourceBuilder.

Check my other blog post on how to install SharePoint SP1 with AutoSPInstaller

Wait with configure SharePoint on all servers with AutoSPInstaller until you have installed the binaries on all servers.

3. Configure the services that should run on the server

Set up the server to run the same services as the farm you should replace inside the input file of AutoSPInstaller. Remember to set all creation of Service Applications to false.

4. Join the servers to the farm with the same server-role as the server you should replace

5. Rebuild the search topology with the new servers, removing the old.

You have to rebuild the search topology with the new servers and removing the old which doesn’t have Service Pack 1 set up. Sometimes Search has to be totally rebuild from beginning during upgrade to Service Pack 1. I’ll write a separate blog article about this in the weekend.

6. Distributed cache.

Add new servers to the distributed cache host with this powershell cmndlet:

Use-CacheCluster
Add-SPDistributedCacheServiceInstance
 

You have to remove the old servers from distributed cache by running the following script on all servers in the distributed cache cluster from powershell:

ds

6. Remove the old server which you just replaced from the farm.

Remove the old servers one by one after you replace them, and you are all done with upgrading to SharePoint 2013 SP1.

If you have some questions about this post, don’t hesitate to contact me

Best regards

Knut

twitter: @sharePTkarm
email: knutrelbemoe(at)outlook.com
skype: knutik.net

Step by step process on upgrading your wsp files from SP2010 to SP2013

This blogpost describes the steps you have to complete to upgrade your Visual Studio 2010 SharePoint 2010 project to a Visual Studio 2012/2013 SharePoint 2013 project.

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

Bilde11

 

It doesn’t matter if it’s Visual Studio 2012 or Visual Studio 2013. Just make sure you update with the latest patches.

2. Upgrade the Visual Studio Project

Open your projects in Visual Studio as an Administrator.
Bilde12
You’ll get a dialog saying “Do you want to upgrade <project name> to a SharePoint 2013 solution? Once the upgrade is complete, the solution can’t be deployed to SharePoint 2010. Do you want to continue?”  Click Yes.
Bilde13

Now Visual Studio will upgrade the solution for us and create a migration report that will tell you how the upgrade went. Hopefully there will be no Errors, only warnings and Messages
Bilde15
Now your code is converted.
3. Check out the assembly references in your project that are pointing to any SharePoint assemblies
Bilde14
As you can see the assemblies have automatically been updated to the correct version of the SharePoint 2013 assembly. Pretty cool if you ask me!
4. Other code updates
Then it’s only one thing left, and that is to change all of the paths in your project, because since SharePoint runs both a 14 hive and a 15 hive, the path to images, layouts and controltemplates are different.
Skjermbilde
That’s it, now you could either deploy your code straight from Visual Studio or you can build a new wsp file.
But for each solution I would seriously consider upgrading the code straight from wsp 2010 to the new App model in SharePoint 2013. I’ll post a blog later about how you should decide to use the app model or to use farm solutions. So drop in on my blog later for that blog post.
Happy upgrading SharePoint.
Don’t hesitate to contact me if you have any questions.
Best regards
Knut
Twitter: @sharePTkarm
Email: knutrelbemoe(at)outlook.com
Mobile: 004798224609
Skype: knutik.net

Step by step process on upgrading to SharePoint 2013 from SharePoint 2010

Hello everyone, this blogpost shows the steps needed to upgrade a SharePoint 2010 web application to a SharePoint 2013 WebApplication. Later I’ll post a blog about the same steps to go from 2007 to 2010.
I assume you have already set up the SharePoint 2013 farm. I’ll later post a blog about how to set up the farm automatically with AutoSPInstaller, and also how to upgrade the different Service Applications. Because if you plan to upgrade those you shouldn’t set this up under installation/configuration of SharePoint, because that would just be waste of time, and you have to delete them afterwords.
1. Add and deploy any required SharePoint 2010 (O14) custom solutions in your SharePoint 2013 farm.
Bilde1
- Adding my SP2010 solution to the farm by running the following cmdlet in Powershell:
Add-SPSolution “C:\demo_sp24\Hello_SP24.wsp”
Bilde2
- Installing the feature with the following cmdlet:
install-spsolution hello_sp24.wsp -gacdeployment -AllWebApplications -force
This completes the first step in the upgrading process and has to be repeted for all wsp files in your solution. If you have any asemblies you need also to install them in the SharePoint 2013 farm.
You can now check the 14 hive and will notice that the visual web part is there:
C:\Program Files\Common Files\microsoft shared\Web Server Extensions\14\TEMPLATE\CONTROLTEMPLATES
If you check the 14 hive you will notice that it’s not there:
C:\Program Files\Common Files\microsoft shared\Web Server Extensions\15\TEMPLATE\CONTROLTEMPLATES
2. Migrate to claims if you didn’t do it in the 2010 environment
If you haven’t done it already you should migrate also the users and the web application to use claims autentication.
Run the following script to migrate the web application to claims. All you just need to do is to open it up and change the name of the webapplication you want to migrate.
Claimsmigration – download the file to the server, rename it to ps1, and run the following cmndlet in powershell:
.\claimsmigration.ps1
Bilde8
Just wait for the script to finish and your webapplication is ready for backup and upgrade to SharePoint 2013
4. Backup and restore the SharePoint 2010 content database to your SQL Server hosting SharePoint 2013 farm.
Next steep is to backup the content database in your old database environment and to restore it in the new.
Bilde3
To backup a database just right click and choose backup database.
5. Run Test-SPContentDatabase cmdlet to identify missing components along with potential errors and related warnings. 
Run the following cmdlet in powershell to test the content database to see if it’s ready to be upgraded:
Test-SPContentDatabase -name SP2010_24_Test_Content_Portal -webapplication http://sharepointdev:86/  > c:\demo_sp24\autid.txt
I choose to put the results of the test into a file, so it’s easier to ready it.
Bilde4
Check the upgrade log and deploy any missing components and re run the cmdlet until no errors returned.
6. Attach the content database to the desired web application using Mount-SPContentDatabase cmdlet.
When the test-SPcontentdatabase runs without any errors you are ready to mount the database to your webapplication. So at this point remember to already have created the web application, created all the managed paths, and remember to use the same URL for the webapplication.
Bilde5
Mount-SPContentDatabase SP2010_24_Test_Content_Portal -DatabaseServer Alias_SPSQL -WebApplication http://sharepointdev:86/ 
This cmndlet attach the database to the webapplication of your desire.
7. After successfully mounting the content database to web application, the site should be accessible in 14 mode.
Bilde6
Now you have successfully attached your old SP2010 solution to SharePoint 2013, you could if you want continue to run it in the 14 hive but then you will not be able to use the new SP2013 features, so I suggestion to upgrade the visual user interface as well.
8. Upgrade the visual user interface
This task you could either let the Site Owners do with the new integrated workflow for testing the new UI. Or you can upgrade all the sitecollection/sites at the same time trough powershell.
I’ll describe in this post the powershell cmndlet and will leave the site owner upgrade for a later update/post. So to upgrade all sites you should run this cmndlet inn powershell:
Run Get-SPSite -contentdatabase SP2010_24_Test_Content_Portal -Limit All | Upgrade-SPSite -VersionUpgrade 
Bilde7
9. Remove old SP2010 code files, and upgrade SP2010 code to SP2013
Now you have to upgrade all of the wsp files in 2010 to SharePoint 2013, and then deploy them to the server.
First i convert my code to SP2013, I will post a separate blog on the steps involved that. So now I just assume that this is done. So then the first step would be to uninstall the 2010 code. I therefor run the following cmndlets:
Bilde9

Uninstall-SPSolution -identity Hello_SP24.wsp -AllWebApplications
Remove-SPSolution -identity Hello_SP24.wsp

Add the new SharePoint 13 (O15) version of the code with the following cmndlets:

Add-SPSolution “C:\demo_sp24\Hello_SP24.wsp”

Bilde1

install-spsolution hello_sp24.wsp -gacdeployment -AllWebApplications -force

Bilde2

Now you can again check the 14 hive for the Visual Web Part, and you will see that the file ((ascx) is gone:

C:\Program Files\Common Files\microsoft shared\Web Server Extensions\14\TEMPLATE\CONTROLTEMPLATES

If you check the 15 hive you will notice that the file is there.

C:\Program Files\Common Files\microsoft shared\Web Server Extensions\15\TEMPLATE\CONTROLTEMPLATES

This means that we have successfully upgraded our code and our web application to SharePoint 2013. Great work everyone! This is so Cool!!

 

Bilde10

If you want I could later put a blog post where I have also included some content types in my 2010 environment. So that you all will see that it’s not any more difficult to upgrade a web application with allot of custom content types then what I just showed you.

Good luck with upgrading, and don’t hesitate to contact me if I could be of any assistance in your upgrade projects.

Best regards

Knut

Twitter: @sharePTkarm

Email: knutrelbemoe(at)outlook.com

Mobile: 004798224609

Skype: knutik.net