My upgrade experience to SharePoint Foundation 2010

I thought I’d share with you guys what I had experienced during the upgrade from my WSS 3.0 server to SharePoint Foundation 2010 beta.

First of all, my WSS 3.0 is quite small. There’s only One site collection in there of any significance en some other site collections for testing purposes. So with this in mind I thought this would be a piece of cake.

After having made a stsadm backup of every site collection and a backup of all my SharePoint databases, I was ready to start. After having read though the deployment docs, I found out that if you are running SQL 2008, that it needs to be at least SP1. I was already running that build so I was good to go for that. I must admit that the prerequisite installer runs smoothly. It does detect your missing prerquisite software and goes out to the interent to download the missing bits. The installation of SharePoint Foundation went flawlessly. I was quickly able to start up the Products and Configuration wizard.

The upgrade wizard quickly failed, telling me that I need to install the Dutch Language Pack as it is also installed for WSS 3.0. A quick look on the web showed me that there isn’t one yet available. Hmm.. problem number 1. I had to uninstall the Dutch language Pack before I could continue. Since all my site collections are also created in Dutch, I needed to convert them to an Englich version, so I decided to do some unsupported stuff and change the  language of my site using the following SQL command on my content database:

UPDATE dbo.webs set language = 1033

Sure enough, my sites are now back in English. I ran the uninstall for the dutch WSS Language Pack and again I was good to go.

My next attempt for running teh upgrade failed as well, complaining about an incorrect SQL version. What the h***? Hadn’t I checked that already before? As it turns out you do not only need SQL 2008 SP1, but it also needs the Cumulative Update 2 for SP1 installed. So I got to download those bits, install them and voila, we are back in business.

The final attempt for the upgrade succeeded. The upgrade process ran successfully, giving no errors and I was soon presented  with the new Central Admin site.I quickly checked the look of my sites, which was as expected still the same, although if you go through to Site Settings, you immediately notice that something has changed. It isn’t quite the old version anymore.

 So all I needed to do is play aroud  with the Visual Upgrade Preview and fin out how my sites will look in their SharePoint 2010 version.

so that’s it for my first upgrade experience.

Well actually it isn’t, because after all my sites had been upgraded I decided to take a backup of my new site collections using stsadm and remove everything. I uninstalled SharePoint Foundation 2010, WSS 3.0, deleted all my SQL databases and started a clean install of SharePoint Foundation 2010. After that I restored the site collections and there I was again: up and running. I don’t like running some hybrid versions with both WSS and Foundation installed and prefer a clean install [:D]

 

7 thoughts on “My upgrade experience to SharePoint Foundation 2010

  1. Hi dirk,

    I made a mistake by upgrading my wss3 to sp2010foundation and I urgently need to go back. I didn’t know that they were using my server productively!

    They only added some lists and some dokuments. Is there a way to do it? Any help would be appreciated.

    [email protected]

  2. Hi Patrick,

    The only way I see it is either doing one of the following:
    – leave it in SharePoint 2010 and set the look back to WSS 3.0, but I am not sure if this is even possible. I will try to check this out
    – Restore WSS from backup. For this you will need either
    o a backup of the sharepoint content database with your user’s sites
    o a stsadm backup of each site collection
    Just uninstall the SharePoint foundation 2010, and create a new farm using the WSS 3.0 SharePoint Products and Configuration wizard. Configure your farm and then recreate a new web application and either:
     attach the restored content database
     restore the site collections from your stsadm backup files

    best regards,

    Dirk van den Berghe

  3. Hi Dirk,

    Im running WSS on 32bit server. DO you have any idea how to upgrade to Sharpeoint Foundation which needs 64 bit?
    Which one is the correct step?
    1. Using export from 32bit server & import to 64bit server?
    2. Install WSS 3.0 64 bit on new server and connect to existing server?

    Thank you so much

  4. Hi Neil,

    My personal approach was:
    1. stsadm -o backup operation on all site collections

    2. reinstall server to 64-bit or install new server in 64-bit

    3. Install WSS 3.0 64bit on new server

    4. create the web application(s) again without creating site collection and install missing solutions if any

    5. stsadm -o restore operation to restore the site collection

    6. Upgrade to SharePoint Foundation

    That’s it.

    In my case it wasn’t it. I continued by stsadm /backup of upgraded site collection. uninstall WSS 3.0 and Foundation. Reinstall fresh Foundation and restore the upgraded site collection again. I don’t like having the WSS 3.0 bits still lingering around in the system…

    Best regards,

    Dirk

  5. Hi Dirk,

    From few websites I read, I found a way that no need to install & reinstall WSS. These are the steps :
    1. Install Foundation 2010 [at 64 bit new server]
    2. Create web + site collection [at 64 bit new server]
    3. Remove content db [at 64 bit new server]
    3. Backup WSS_Content [at 32 bit old server]
    4. Restore WSS_Content [at 64 bit new server]
    5. Add content db [at 64 bit new server]

    Is it the same?

  6. Hi Dirk,

    I just found out that there is another way..
    1. Install foundation at new server
    Create Web App
    Create Site Collection
    2. Backup WSS_Content from old server
    3. Remove contentdb from newserver
    4. Restore WSS_Content
    5. Add contentdb to new server

    is it the same with your way?

Leave a Reply

Your email address will not be published. Required fields are marked *