• SharePoint Online – Features and Restrictions
• Disaster Recovery
• Search

John can be reached on twitter at: twitter.com/ferringer.

• The impact on infrastructure in 2010
• The impact the underlying OS has on 2010 behavior
• How SP 2010 can be used in global deployments
• Performance Point
• Service Applications
• Claims Based Authentication

Recap of the upgrade steps:

In the previous post I took you through as far as Migrating the Content DB where we attached Joel’s 2007 content database to a newly built SharePoint 2010 Foundation Server (note the new naming conventions).

Apply new Look and Feel

So at this point everyone is excited to open a browser and take a look at the new site.  The only problem is that once the browser opens and renders the site – there isn’t any change to how the site looks…what’s up with that? 

In this new version of SharePoint, Microsoft has shipped all of the CSS and Masterpages from 2007 to help ease the transition of sites in 2007 to 2010.  In fact what they have also done is increased the delineation of SharePoint responsibilities from the IT Pro and the rest of the SharePoint user base.  The beauty of this is that at this point my role as the System Admin is complete – Joel’s blog is now running on 2010 – mission accomplished.  It would be at this point that I would had the site over to Joel and his designer to decided when they wanted to apply the 2010 look and feel.

Being that it is my role to help Joel with these things as well (and it helps me with more info for blog posts), I went ahead and completed the process.  You see inside: Site Actions > Site Settings under “Title, Description, and appearance” there are these radio-button choices at the bottom of the screen:

• Keep the previous SharePoint user experience.
• Preview the new SharePoint user experience, but let me return to the previous user experience.
• Use the new SharePoint user experience, and don’t ask me again.

Note: If you are tracking along w/ your own DB and following my steps, you may find that you can’t log into your site collection… why you ask?  Because if you have built your new farm in a new domain – you have just restored content from an old domain with old domain users.  Go add yourself to the Site Collection Administrators in Central Admin.

Apply Joel’s Theme

Once you select “Use the new SharePoint Experience…” you will see an immediate change as your are dropped back in Central Admin – you have the new admin features and layout available!  As you go back to your home page, you will see the new theme applied as well.

Now Joel’s page has the new look and feel but all of his styling is gone.  This is because the default.master is being fed from the “uncustomized” version of the page which is located on the WFE.  To get Joel’s styling back, all we have to do is open SharePoint designer and re-apply the page created by Heather Waterman.

Once that’s done, you are good to go:

So there you have it: Migrating a SharePoint blog from 2007 to 2010.  In future posts I’ll dig a little deeper into each of these areas – this post was meant to give you the “big picture” of the process.

Please feel free to comment below with any questions about the process or reach out to via email or lastly – view some of my SharePoint information over at my employer’s site: Rackspace!

First of all, let’s understand the outline of what needed to be accomplished:

• Acquire another server
• Install SharePoint 2010
• Perform a “preupgradecheck” on the old server
• Install any prerequisites on the new server
• Migrate the Content DB
• Apply the new look and feel
• Apply Joel’s theme

Sure seems simple enough, right?  In the end it wasn’t all that hard – but there were a few “gotchas” along the way.

Acquire Another Server

Why did we need another server?  There were 2 reasons: Because we wanted both the 2007 and 2010 site to show up simultaneously and because the old hardware was running on 32-bit architecture.  As you may remember – SharePoint 2010 requires a 64-bit OS to run.

Install SharePoint 2010

This part was simple enough and to be honest, was another reason why we needed a second server.  For this demo, we had already in stalled the bits for 2010 and we couldn’t make this site live before Monday as the NDA from Microsoft was still in place.

Perform an “stsadm –o preupgradecheck”

I can’t stress enough the importance of doing this on your 2007 SP2 (or later) site.  This goes through your current site and checks all dependencies to ensure you are ready to go.  Here is a screen-capture from Joel’s:

Install any Prerequisites on the Server

This means that any packages (WSP’s, Features…)  that are installed on the source server need to be installed on the target server.  In Joel’s case, this included the Community Kit for SharePoint.

Confession: I forget to do this the 1st time I attempted the migration and the upgrade on the content DB failed.  Good thing I had another copy of the source content DB (you should too!)

So off to codeplex I went and downloaded the install files.  It is certainly nice when a package comes with an INSTALL.BAT but guess what? Any and all of those install files out there have to updated if they drop any files in

c:\program files\common files\microsoft shared\web server extensions\12\*

Know why???  Because in SharePoint 2010 the install directory changes to:

c:\program files\common files\microsoft shared\web server extensions\14\*

After updating their install.bat, all worked well.

Migrate the Content DB

Part of this step does including creating a new site collection.  It doesn’t much matter what template you use, as you will be detaching and deleting it’s database.  Once you have it created, go into central admin and delete the content DB from the WEB app.

Now, when I made a copy of Joel’s production DB, I just made a SQL Backup of the content.  I could have copied the MDF and LDF files and moved them to the new server.  But being lazy and only wanting to move one file, I opted for the “backup” method.

So now over on the 2010 server I opened SQL Studio and performed a “restore” of Joel’s content db.  Note: you may need to either kill SQL connection or just restart the SQL service. 

Now that I had a copy of the Content DB on the new SQL server, it is was time to connect it to SharePoint 2010.  To do this, you have to use the command line as the GUI interface can not handle the upgrade.  Open a CMD interface and navigate to the BIN directory:

c:\program files\common files\microsoft shared\web server extensions\14\bin

and perform the following:

stsadm –o addcontentdb –url enter your url –databasename enter your db name

The system will churn a bit, give you a little progress info… and hopefully you’ll see a 100%.  Now it’s time to navigate to your site and enjoy the goodness of the migrated site.  The reality is, you will not see any change!  This is actually a good thing – you see SharePoint 2010 does an amazing job of enhancing the line between the IT Pro and the Designer/Developer role.   We will talk more about this in the next blog post! 

On to: Part II

Now, one day from boarding the jet that will take me to Las Vegas my schedule is packed:
Sunday
- Travel
- 4:00 “Tech Check” for my portion of the Joel Oleson preso on Monday
- Welcome reception

Monday
- Morning Key Note address. I’ll be live-blogging from the event!
- Present in Joel Oleson’s session on SharePoint 2010. Come see what we are up to in there!
- Exhibit Hall
- Partner Party

Tues Day
- Exhibit Hall
- Morning Sessions
- Lunch
- AvePoint Session – this one is a must for anyone involved in System Administration of SharePoint. AvePoint and Rackspace will be announcing a new partnership as well as some innovative SharePoint integration technologies
- Exhibit Hall
- Customer Dinner

Wednesday
- More of everything! I’ll finish the rest of these details as they firm-up!