At last! Here is Part 3 of 3 of my How to Upgrade SharePoint 2007 to SharePoint 2010 series as promised (or at least Part 3A of 3 – I realized there was still a LOT of information to cover, so I decided to ‘Harry Potter’ it and break the last final installment into two posts).
I know most of you have had your SharePoint environments hanging in limbo while you patiently awaited this third and final blog. Let’s finally roll up our sleeves and get these environments back up and running on SharePoint 2010!
To pick up where we left off… the first blog of this upgrade series was essentially just a high level overview of the upgrade process as I just touched on each method. The second blog was more of an introduction to both the In Place Upgrade and Database Attach Upgrade methods. In this third blog, I would like to expand on each method in hopes that you can use this blog as a step-by-step guide to upgrade your environments.
In Place Upgrade
If you’ve retained anything from my previous two posts, I would bet it can be summarized in one word: BACKUP. This is very important in any upgrade method, but is extremely important if you choose to perform an In Place Upgrade. How many of you get extremely annoyed at how many times Microsoft asks you “Are you sure” when overwriting a file? I know I am, but if you think about it, is it really that bad? They know it’s a very important decision that cannot be undone (unless you have what? Yes, a backup!). This isn’t your average Word document. We are talking about your entire SharePoint environment. Just like insurance, you pay on it every month in hopes that you never have to use it. Backups are the same way. It is well worth the additional cost and storage and should be worked in to every company’s budget.
Now that we have a backup of our environment, we can continue with the upgrade. Based on my previous two blogs in the series, I am going to assume the following has already been completed:
- Current environment resides on SharePoint 2010 required hardware.
- Current SharePoint 2007 environment has been patched with Service Pack 2 or later.
- Successfully ran PreUpgradeCheck (stsadm –o preupgradecheck).
- Entire environment has been backed up.
- Ran the prerequisite installer on each web server in the farm.
Once all the tasks above have been completed successfully, we can now begin installing SharePoint 2010. Now is the time to run setup.exe on all SharePoint servers in the farm. If you only have a one server farm, you may immediately run the SharePoint Products Configuration Wizard upon setup completion. If you have a multi-server farm, you need to first run the Configuration Wizard on the server that will be running Central Administration. Once the Configuration Wizard is complete on the Central Administration server, you may continue running it on the other SharePoint servers and join them to the farm.
Now that SharePoint is installed on all required servers, this does not necessarily mean that the upgrade to 2010 is complete. Once the SharePoint setup is complete, it then begins to upgrade the environment. Using Central Administration, you may view the progress of the upgrade by browsing to Central Administration > Upgrade and Patch Management > Check Upgrade Status. Alternatively, you may also check the status by using the localupgradestatus stsadm.exe cmdlet.
Once the upgrade has completed successfully, you are finished! It the upgrade fails, you can easily refer to the specified log files for details.
Next, we will dive in to my favorite method, the Database Attach.
To be continued…
(Please stay tuned next week for the final post in Joe’s blog series on How to Upgrade SharePoint 2007 to SharePoint 2010.)