Upgrading from SPS 2003 to MOSS 2007 Beta2 TR using the gradual approach

EDIT – Updated to RTM http://msmvps.com/blogs/shane/archive/2007/04/15/upgrading-from-sps-2003-to-moss-2007-using-the-gradual-approach.aspx

Warning – I have been very hesitant to post these directions. Why? Because they make it seem very simple to upgrade from 2003 to 2007. While at the core it can be an easy process in reality there is a lot of planning and decision making you need to do before you ever sit down with this guide. In class it is taking me hours of lecture just to present all of the options and reasoning to the students. How much time have you spent planning to this point? Here is a quick list of some of the topics we cover.

  • Which method are you going to use? Gradual, In place, or database migration?
  • Do you have a communication plan in place? For who? Your content managers? Users?
  • If gradual do you have a new URL planned and setup?
  • Is your hardware strong enough? The hardware specs have gone way up from v2.
  • What type of farm do you have now? Are you upgrading to the same farm type?
  • Do you have any custom site definitions? Have you created mapping files for them?
  • Do you have unghosted pages? Do you know what you are going to do with them?
  • Are you using 3rd party web parts? Will they work with v3? What about custom web parts you wrote?

Anyway, you get my drift. This process is way tougher than just getting your portal upgraded. And I am not trying to scare you I just would feel responsible if I didn’t let you know some of the other challenges you will have. Ok. A couple of my quick points and then the directions begin.

This step by step guide will hopefully help you to go from a SharePoint Portal Server 2003 with Service Pack 2 to Microsoft Office SharePoint Server 2007 Beta 2 Technical Refresh. The environment that I am using to create these instructions is as follows.

  • Windows Server 2003 Standard i386 running Active Directory and DNS
  • SharePoint Portal Server 2003 with SP2
  • SQL Server 2000 SP4

I am also using SNAGIT 8 from TechSmith for screen captures

The concepts, environment, and my learning curve have all come thanks to SharePoint Solutions. I am part of the team that has created and is delivering their Upgrading From SharePoint 2003 to SharePoint 2007 course.

For more information on beta 2 TR check out my previous post.

If you would like to download these instructions in PDF form you can get them from here.  I really just wanted to try out the Word add in for creating PDFs.

For Microsoft instructions on upgrading from 2003 to 2007 check out Installing Microsoft Office SharePoint Server 2007 for Beta 2 Technical Refresh from Microsoft.

  1. Download Microsoft .NET Framework Version 2.0 Redistributable Package (x86)
  2. Install .NET 2.0 by running dotnetfx.exe that you just downloaded.
    1. At the welcome screen click Next
    2. At the EULA screen click I accept and Install
    3. The install will now run for several minutes and will give you a message when it finishes
  3. Download the Windows Workflow Foundation Runtime Components Beta 2_2(EN) for x86.exe
  4. Install Windows Workflow Foundation Runtime Components Beta 2_2(EN) for x86.exe that you just downloaded
    1. Click Yes at the warning message as long as you don’t have a previous copy of Windows Workflow installed. Odds are you do not. If you are unsure you can check for it in Add Remove Programs and if you do then click No and uninstall it before continuing.
    2. At the License Agreement screen click Yes
    3. After a minute or so you will get a message about viewing the license. Click OK and the WWF 2.2 install is complete
  5. Now you need to download Beta2 for Office SharePoint Server. To do this you must register.
  6. Once you have beta 2 expand the files to your hard drive. In my example I create a folder c:\moss and extracted all of beta 2 to this folder.
  7. Download SharePoint Server 2007 Beta 2 Technical Refresh
  8. Now you need to extract this patch into the c:\moss\updates folder by running
    1. officeserver2007b2tr-kb000000-x86-fullfile-en-us.exe /extract:C:\MOSS\Updates
    2. accept the license message and click continue
  9. Download Windows SharePoint Services 3.0 Beta 2 Technical Refresh
  10. Now you need to extract this patch into the c:\moss\updates folder by running
    1. WSSv3b2tr-kb000000-x86-fullfile-en-us.exe /extract:C:\MOSS\Updates
    2. accept the license message and click continue
  11. If you have done everything correctly you should have a folder that looks like this

  12. Now you are ready to install MOSS
    1. Navigate to c:\moss and double click setup.exe
    2. Enter your product key and click continue
    3. At License Terms screen check I accept and click Continue
    4. SLOW DOWN! At this screen it is very easy to make a mistake that will cause you a lot of grief so be careful.
    5. First thing to do is to choose your upgrade approach. In my testing (a couple hundred upgrades to this point) I have found that gradual is the best approach to use. It provides maximum flexibility since it will let you run v2 and v3 sites from the same machine side by side. For these instructions we will assume you want to do a gradual upgrade. For more information on the options available check out Joel Oleson’s post.
    6. To do a gradual upgrade choose Yes, perform a Gradual Upgrade DO NOT PRESS UPGRADE

    7. Now go to the Server Type tab and choose Complete and now it is safe to click Upgrade

    8. Now prepare to wait a few minutes while the bits are actually installed. When it gets to the Applying Updates screen you may feel like the process is hung due to this screen running for several minutes. This is normal behavior. What is going on behind the scenes is Beta2 was fully installed in its normal process. Now setup is automatically installing the technical refresh for you. So you aren’t seeing the screens for that but they are being applied automagically at this time. Just be patient.
    9. Finally you get the completion screen. Make sure the box is unchecked to Run the config wizard and click close.
    10. Odds are you will get a screen that says you must Reboot to complete setup. If you do click Yes.
    11. If you rebooted log back in when it finishes.
  13. If the configuration wizard is open close it now. You will come back to it after a few more steps.
  14. Now we need to make a couple of small registry changes. For our example follow step A below for gradual upgrade and then proceed to step 15. If you chose another method choose the step most appropriate for you.
    1. Gradual Upgrade
      1. Open regedit
      2. Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\12.0\WSS\
      3. Find the key SetupType and modify its value to V2V_GRADUAL_UPGRADE
      4. Find the key SetupTypeBackup and modify its value to V2V_GRADUAL_UPGRADE

      5. Close the registry editor
      6. Go to step 15
    2. Automated in-place upgrade for a typical installation (using MSDE not SQL Server)
      1. Open regedit
      2. Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\12.0\WSS\
      3. Find the key SetupType and modify its value to V2V_INPLACE_UPGRADE
      4. Find the key SetupTypeBackup and modify its value to V2V_INPLACE_UPGRADE
      5. Add the following registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\12.0\WSS\WmsdeToWyukonUpgrade type DWORD, and set its value to 1
      6. Close the registry editor
      7. Go to step 15
    3. Automated in-place upgrade for Single Server with SQL Server or any farm configuration
      1. Open regedit
      2. Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\12.0\WSS\
      3. Find the key SetupType and modify its value to V2V_INPLACE_UPGRADE
      4. Find the key SetupTypeBackup and modify its value to V2V_INPLACE_UPGRADE
      5. Close the registry editor
      6. Go to step 15
  15. Open a command prompt
  16. Navigate to C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN and run Prescan.exe /c preupgradescanconfig.xml /all
    1. You can review the output here to find unghosted pages and what definitions your sites are using.
  17. Close the command prompt
  18. Now you need to uninstall the WWF that you installed in step 4
    1. Navigate to Control Panel > Add/Remove Programs
    2. Find Windows Workflow Foundation near the bottom of the list and click Remove.
    3. Are you sure? Click Yes.
    4. Once you are taken back to the Add or Remove Programs screen the uninstall is complete. (This happens very quickly.)
    5. Close add/remove
  19. Download Microsoft Pre-Release Software Microsoft .NET Framework 3.0 – Release Candidate
  20. Install .NET 3.0 Framework
    1. Double click dotnetfx3.exe
    2. Read the license agreement and click I have read and Accept
    3. Click install
    4. You will notice that the installer minimize to the tray. You need to wait until it finishes and you get message as such.

    5. Once you click the message it will send some anonymous information back to the mother ship. Give it a second to finish.
  21. Now we can run SharePoint Products and Technologies Configuration Wizard by going to Start> Microsoft Office Server > and clicking the link.
  22. On the Welcome screen click Next
  23. On the pop up about warning click Yes
  24. On the language pack screen click OK. If you have any language packs to install now would be the time to do it. I can’t find a link to any to provide. Sorry.
  25. On the connect to a server farm screen you need to choose No, I want to create a new server farm and click Next

  26. Now you need to specify the name of the SQL server and the account password that SharePoint will use. In our example we are SQL is installed on the local server so we will enter the server name and the password.

  27. Now you can take the defaults here and click Next. If you wanted to specify the port that Central Administration will use you may do so now. You also have the option to choose Kerberos authentication instead of NTLM. If you are familiar with how to make Kerberos work it is the preferred method. If you have no idea what that is then NTLM will work fine and you don’t lose anything.
  28. At the Completing screen make sure things look good and click Next.
  29. Now sit back and relax. This will take several minutes to process the 11 steps necessary. Once it finishes you will get a Configuration Successful screen where you can click Finish.
  30. You will not be automatically taken to SharePoint Central Administration. Here we need to get your farm back to fully functional. The first step is to click on the Operation tab
  31. Now click on Services on server under Topology and Services
  32. If you look in the server role section will see several options. You need to choose Single Server in our example.
    1. Now for the options at the bottom we need to get all of them Started. To the right of each one that you need to start you will set Start
    2. Click start for Document Conversions Load Balancer Service
    3. Click start for Document Conversions Launcher Service
      1. For the load balancer select your server name and click ok
    4. Click start for Excel Calculation Services
    5. Click start for Windows SharePoint Services Search
      1. Fill out your service accounts in the form domain\username and the enter password
      2. Accept the other defaults and click Start
    6. If everything looks like below you are ready to continue
  33. Now click on the Home tab

You are now ready to go on performing a gradual upgrade. I will save this process and explanation for another day. I am sure if you have gotten to this point you are as tired as I am. This was not a hard process just long and tedious.

If you want to continue on then here is a brief outline of your next steps

  • Go back to the operations tab and click on site content upgrade status
  • Find your portal and click Begin upgrade
  • Once you fill out that screen you will be able to start upgrading sites
  • When you go to upgrade your sites remember you always have to upgrade the root site first
    • Sometimes after you upgrade the root site you need an iisreset before you can upgrade another site

One more thing before I let you go. Did you read the warning above? You should go back and read that. There is still a lot to do, you just finished the easy part.

Have fun!

Shane – SharePoint Help

EDIT – Updated to RTM http://msmvps.com/blogs/shane/archive/2007/04/15/upgrading-from-sps-2003-to-moss-2007-using-the-gradual-approach.aspx

33 thoughts on “Upgrading from SPS 2003 to MOSS 2007 Beta2 TR using the gradual approach”

  1. Yes it works, great!
    In upgraded a SharePoint 2003 portal to 2007 with this guide.
    My test evironment contains only 2 sites, one english teamsite and one
    meeting site in Dutch language.

    After migrating only the english teamsite is working, the dutch meeting site
    doesnt work.
    Wil this upgrade only work voor ID1033 sites?

    Thanks in advance,

  2. Shane, I followed your graduate upgrade instructions (I thought) perfectly. After step 23, it simply started upgrading (no language pack options, no server farm connect options). Of course, the upgrade failed and I can no longer access the old portal.

    Any thoughts what might have happended?

  3. Edward – I have found that people see this type of behavior when on step 12-6 they click upgrade before choosing gradual as an option. So far I haven’t tried to figure out how to undo things at this point. Sorry. If you do find a solution please let me know. Also, check your upgrade log to see if you can find why the upgrade is failing.

  4. Shane,
    Best written instructions I have found so far, however, they do not address the Medium Farm(2-1-1) with Windows Load balancing and SSL type of Setup? Do you have any suggestions or directions for this type setup? TIA, Norm

  5. Hello,

    The upgrade from SPS to MOSS works perfectly (test SPS) for me as well. I got one question however. I want to upgrade the existing SPS to MOSS, but not on the same server. We have purchased new servers for this, so now I would like to move the Portal.
    So far, the only possibility I see, is backing up the SPS and restoring on the new servers and there do the gradual upgrade. Is that the only possibility? Or are there tools which can help me do this automatically?

    Thanks in advance

  6. Great Post but you stopped right where I desperately need help. Can anyone help here.

    Situation: Upgrading a medium Farm with a 2-1-1 set up using Shared Services, Windows Load Balancing, and no SSL. Current Farm is Running SPS2003 SP2, SQL2000 SP3+. Trying to do a SharePoint 2003 direct to SharePoint 2007 Beta2 TR Gradual Migration.

    1. Do I have to do anything with Windows Load Balancing during the installation/Setup/Gradual Migration? Disable one server? Undo Load Balancing during the Migration? And if so, at what point in the process do I need to do this?
    2. Do I have to create all the new IIS Web Applications ahead of time, since I see no way in the Admin screens I have seen to enter unique IP addresses? If so, is there a procedure for this?
    3. This is a question about what seems to be a grey area in all the documentation I can find.
    Using the procedures for a gradual migration using Shared Services, I get to the point where I run the SharePoint Products and Technologies Configuration wizard on all 3 servers. Then I configure and start the required services on the servers appropriately (services required are Office SharePoint Server Search, Excel Calculation, and Windows SharePoint Services Search).
    So at this point, is the next step
    a. to Create Shared Services Provider (This yielded an error that says “An unhandled exception occurred in the user interface.Exception Information: Unable to connect to the remote server”
    And if so, is this SSP run on a Load Balanced URL or on a single server seperate URL?
    b. to Begin Upgrade on my current Parent Portal (Shared Services Provider) (This yielded an error that says “No connection could be made because the target machine actively refused it.”
    And again I run into the problem of unique IP addresses vs Host names.
    c. I have totally missed something and should be doing ????????

  7. I do not have the Portal Server running on my machine, only WSS 2.0. Are the steps the same? I have the MOSS 2007 Beta slipstreamed to do the TR updates. But when I run the install I get no “Upgrade” option. Should I continue with the installation? Are there steps to upgrade to WSS 3.0? I haven’t even found the beta install files for that, only MOSS 2007. Please help, and thanks for your great work.

  8. I also get this error.

    The Execute method of job definition Microsoft.Office.Server.Administration.ConfigurationCheckerJob (ID 01efe81d-d226-42ba-b598-98bed58850e4) threw an exception. More information is included below.

    Object reference not set to an instance of an object.

    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

  9. I have to do a migration from SPS 2003 to MOSS 2007, no Betas, my question is: Can help me this guide to do this or what can I do?

  10. Great article, Helped me a lot !!!

    but i am steel waiting for the second part of the explanation.
    have you posted it already ?
    if anyone have the next steps for this explanation, i would be greatful if you can help me.


  11. I have a single site that run’s on SP 2003 with SQL 2000 . I also have a full fledged Site collection running MOSS with SQL 2005. I need to know if there is a way to export this single site with all data to MOSS.



  12. I have two web servers. One is for load balancing–when one server is busy with request it sends it to the second web server. How would I install SharePoint 07 on the load balancing server? It has SharePoint 2003 installed on it right now. During the install–Would I choose COMPLETE or WEB FRONT END for the server type!? Thank you.

  13. One of the problems I have encountered with the gradual (and other) upgrade with a site definition upgrade file is that the actual pages do not seem to be upgraded, and neither do the forms (/doclib/AllItems.aspx). I have been testing several of our sites – things migrate fine when i provision a new site on a definition in wss 2.0, but for existing sites, after the upgrade, i still get some of the old look and feel of wss 2.0.

    One thing that I notice is that default.aspx on each of these sites is that they appear to be unghosted. When resetting to site definition after the upgrade (for the page), it just copies the file, and leaves another unghosted file in its place.

  14. I’m not very techy as I am on the management side already and it has been awhile (years actually) since the last time I did actual programming. I’m looking at doing the following for our SharePoint migration project –

    (1) On environment 1 (current development server – where the SharePoint 2003 app is hosted), run the gradual upgrade and then do a backup.

    (2) On environment 2 (new production server – where MOSS 2007 is installed), do a backup restore.

    Will this work? Please advise.


Leave a Reply

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