How To Recover Your SharePoint 2007 Product ID by Bert Johnson

On my post about the SP2 bug, I had a comment by Bert Johnson about a post of his explaining how to recover the SharePoint 2007 Product ID from your system. This is indeed very handy if you do not happen to have it or find it anymore and do not want to bother your customer for it loosing face (again [:D])

Bert wrote a vbs script that decodes the Product ID from the registry key blob data where it resides.

Thanks Bert for sharing this information, which will probably help a lot of us out there.

Subscribe to Bert’s blog with this Feed:{071A5AE9-9B1F-44E7-8AF7-C0BC07CF531D}

The original post can be found at .

Here is the script :

' Extract MOSS 2007 Product ID
' Written by Bert Johnson (PointBridge)

Const HKEY_LOCAL_MACHINE = &H80000002
Set reg=GetObject("winmgmts:{impersonationLevel=impersonate}!\\.\root\default:StdRegProv")

wscript.echo GetKey("SOFTWARE\Microsoft\Office\12.0\Registration\{90120000-110D-0000-0000-0000000FF1CE}", "DigitalProductId")

Public Function GetKey(path, key)
    Dim chars(24), prodid
    Dim productkey(14)

    reg.GetBinaryValue HKEY_LOCAL_MACHINE, path, key, prodid
    For ib = 52 To 66
        productkey(ib - 52) = prodid(ib)

    'Possible characters in the Product ID:
    chars(0) = Asc("B")
    chars(1) = Asc("C")
    chars(2) = Asc("D")
    chars(3) = Asc("F")
    chars(4) = Asc("G")
    chars(5) = Asc("H")
    chars(6) = Asc("J")
    chars(7) = Asc("K")
    chars(8) = Asc("M")
    chars(9) = Asc("P")
    chars(10) = Asc("Q")
    chars(11) = Asc("R")
    chars(12) = Asc("T")
    chars(13) = Asc("V")
    chars(14) = Asc("W")
    chars(15) = Asc("X")
    chars(16) = Asc("Y")
    chars(17) = Asc("2")
    chars(18) = Asc("3")
    chars(19) = Asc("4")
    chars(20) = Asc("6")
    chars(21) = Asc("7")
    chars(22) = Asc("8")
    chars(23) = Asc("9")

    For ib = 24 To 0 Step -1
        n = 0

        For ikb = 14 To 0 Step -1
            n = n * 256 Xor productkey(ikb)
            productkey(ikb) = Int(n / 24)
            n = n Mod 24

        sCDKey = Chr(chars(n)) & sCDKey
        If ib Mod 5 = 0 And ib <> 0 Then sCDKey = "-" & sCDKey

    GetKey = sCDKey
End Function
Simply save that to a file named “ExtractMOSS2007ProductID.vbs” and run it to recover your key.  Once recovered, re-apply your Product ID through Central Admin, as outlined in KB971620.

How to upgrade to SharePoint 2007 SP2 – Step by Step by Chris Givens

I was reading trhough my blogroll today and noticed a very complete blog post for deploying SP2 in a large MOSS environment. It describes optimized steps for installing SP2 with lesser downtime as you would have by just installing it. Chris Givens is a SharePoint trainer. His Advanced SharePoint 2007 Operations course looks very interesting. Just a pitty that you have to go all the way to Seattle for it…. For us European trash guys, it is hard to defend that to our manager, right? 

So please, read through this post as it may help you with your upgrade of your farm if you have large databases.

This is the original content of Chris’s Post that can be found at

 built this lab for the latest update to my Advanced SharePoint Operations course.  But I felt like it would benefit the entire community…so here you go!  Good luck!

Module #25: Updating The Farm Lab #01


Course:                SharePoint 2007 Operations

Estimated Time to Complete:  45 minutes


·         Upgrade to SP2

Operating Notes:  

·         You will need sharepoint2007 and svr-sp2 images

·         Assumes that you are using SQL Server 2000/2005/2008 for your database server (Not Internal DB engine)


·         None


Overview:         Learn the steps of preparing your farm for upgrade and then performing the upgrade.

Exercise 1 – Prep the Farm

Purpose:         There are a series of recommend steps that will speed up the upgrade of your SharePoint Farm.  Following these somewhat simple suggestions will get you through the process much faster!  Rebuilding indexes will ensure that the upgrade process will modify the database schemas and records as quick as possible.  Truncating the log files will ensure that your backup and restores will run quickly.  Detaching

A farm ready for upgrade

Task 1 – Clean up the databases (rebuild indexes)

  1. Open SQL Server Management Studio
  2. Connect to your sharepoint database server
  3. Click “New Query”
  4. Run (press Atl-X) the following command on each SharePoint database (set the dropdown for each):
    • WSS_Content*
    • SharePoint_Config*

SELECT  object_id, index_id, avg_fragmentation_in_percent, page_count
FROM sys.dm_db_index_physical_stats(DB_ID(), NULL, NULL, NULL , NULL)
order by avg_fragmentation_in_percent desc

    DECLARE @objectid int
    DECLARE @indexid int
    DECLARE @command varchar(8000)
    DECLARE @baseCommand varchar(8000)
    DECLARE @schemaname sysname
    DECLARE @objectname sysname
    DECLARE @indexname sysname
    DECLARE @currentDdbId int

    SELECT @currentDdbId = DB_ID()

    PRINT CONVERT(nvarchar, GETDATE(), 126) + ': Starting'


       sys.indexes AS i
        sys.objects AS o
        i.object_id = o.object_id
        i.index_id > 0 AND
        o.type = 'U'

    OPEN indexesToDefrag
    -- Loop through the partitions.

        -- Lookup the name of the index
            @schemaname =
            sys.objects AS o
            sys.schemas AS s
            s.schema_id = o.schema_id
            o.object_id = @objectid

        PRINT CONVERT(nvarchar, GETDATE(), 126) + ': ' + @schemaname + '.' + @indexname + ' is now being rebuilt.'

        -- Fragmentation is bad enough that it will be more efficient to rebuild the index

        SELECT @baseCommand =
            ' ALTER INDEX ' +
                @indexname +
            ' ON ' +
                @schemaname + '.' + object_name(@objectid) +
            ' REBUILD WITH (FILLFACTOR = 80, ONLINE = '

        -- Use dynamic sql so this compiles in SQL 2000
        SELECT @command =
            ' BEGIN TRY ' +
               @baseCommand + 'ON) ' +
            ' END TRY ' +
            ' BEGIN CATCH ' +
               -- Indices with image-like columns can't be rebuild online, so go offline

               @baseCommand + 'OFF) ' +
            ' END CATCH '

        PRINT CONVERT(nvarchar, GETDATE(), 126) + ': Rebuilding'
        EXEC (@command)
        PRINT CONVERT(nvarchar, GETDATE(), 126) + ': Done'

        FETCH NEXT FROM indexesToDefrag INTO @objectid, @indexid, @indexname

    CLOSE indexesToDefrag
    DEALLOCATE indexesToDefrag

SELECT  object_id, index_id, avg_fragmentation_in_percent, page_count
FROM sys.dm_db_index_physical_stats(DB_ID(), NULL, NULL, NULL , NULL)
order by avg_fragmentation_in_percent desc



Task 2 – Check disk space on web and database servers

  1. On each web front end, open Explorer to “My Computer”, record your disk space.  Make sure you have at least 300MB free for install of files
  2. On each database server, open Explorer to “My Computer”, record your disk space.  Make sure that you have enough space to make a copy of your largest content database.
    • Example:  if you have three databases of size 10GB, 20GB and 30 GB.  Make sure you have at least 30GB of free space on your DB server.

Task 3 – Backup the databases (truncate and backup)

  1. Create a folder called “D:\Backups”, ensure that you have enough disk space to save all your backups to this location (add the size of each database to determine how much you will need)
  2. Run the following commands TWICE for each database (this will shrink, backup and truncate your database and log files):
    • WSS_Content*
    • WSS_Search*
    • SharePoint_Config
    • SharedServices*

use WSS_Content

dbcc shrinkfile ('WSS_Content')
dbcc shrinkfile ('WSS_Content_log')

backup database WSS_Content to disk = 'D:\backups\wss_content.bak'
backup log WSS_Content to disk = 'D:\backups\wss_content.bak'

dbcc shrinkfile ('WSS_Content')
dbcc shrinkfile ('WSS_Content_log')

Task 3 – Evaluate Database Size

  1. If you designed your farm wrong, it is possible that you have a single web application with a single content database that contains all your content.  This type of setup normally means you have a database that is going to get large very quickly and backup and restore operations, as well as future upgrades could take a considerable amount of time.  It is suggested that you create more content databases and partition your site collections across multiple databases.
  2. You have two options to do this:
    • Create another content database in the web application
    • Create another web application with a new content database
  3. Create a new site collection in your port 100 site
    • Open “Central Administration”
    • Click “Application management”
    • Click “Create Site collection”, ensure that you are on port 100 web application
    • For Title, type “SC2”
    • For URL, select “/sites/”, and type “SC2”
    • For owner, type “administrator”
    • Click “Ok”
  4. You will now have two site collections in your content database, you can use the following commands to backup a site collection, delete it and restore to a different web application (and hence a new content database):

stsadm -o backup -url http://sharepoint2007:100/sites/Sc2 -filename c:\backup.dat –overwrite

stsadm –o deletesite -url http://sharepoint2007:100/sites/Sc2

stsadm -o restore -url http://sharepoint2007:777/sites/sc2 -filename c:\backup.dat

  1. You can continue this process to load balance your site collections across multiple content databases and in essence distribute your database sizes so that upgrading will not be so painful.
    • NOTE: you can only use a url once in a web application

Task 4 – Detach the content databases

  1. Open the “Central Administration” site
  2. Click “Application Management”
  3. For each web application in your web application list (EXCEPT central administration), do the following steps. NOTE: Click “Web Application List” to see them all:

    • Click “Content Databases”

    • You will see a list of content databases for the web application
    • Click the database name

    • Click the “Remove content database” check box
    • Click “Ok”
    • Click “Ok”

    • Click “Ok”
    • You should now see that the web application has no content databases:

  1. Again, do this for every web application EXCEPT the Central administration web application!
    • NOTE: you may have several content databases…this may be a tedious task so you should likely follow step 5
  2. You can also create a command line utility to do this:
    • Open Visual Studio
    • Click “File->New Project”
    • Select “Console Application”
    • For name, type “ContentDetachAttachScript”
    • Copy the following into the program.cs file:

using System;
using System.IO;
using System.Collections.Generic;
using System.Text;

using Microsoft.SharePoint;
using Microsoft.SharePoint.Administration;

namespace ConsoleApplication1
    class Program
        static void Main(string[] args)
            TextWriter tw = File.CreateText("C:/detachall.bat");
            TextWriter tw2 = File.CreateText("C:/attachall.bat");

            SPFarm farm = SPFarm.Local;
            SPAlternateUrlCollectionManager mgr = farm.AlternateUrlCollections;                                             

            foreach (SPAlternateUrlCollection altColl in mgr )
                foreach (SPAlternateUrl url in altColl)
                    if (url.UrlZone == SPUrlZone.Default)
                            SPSite site = new SPSite(url.IncomingUrl);


                            SPWeb root = site.RootWeb;
                            if (root.WebTemplate != "CENTRALADMIN")
                                //get the web application for the site collection
                                SPWebApplication webApp = site.WebApplication;

                                foreach (SPContentDatabase cd in webApp.ContentDatabases)
                                    tw.WriteLine("stsadm -o deletecontentdb -url " + url.IncomingUrl + " -databasename " + cd.Name + " -databaseserver " + cd.Server);

                                    tw2.WriteLine("stsadm -o addcontentdb -url " + url.IncomingUrl + " -databasename " + cd.Name + " -databaseserver " + cd.Server);

                                    //Console.WriteLine("Content Database [" + cd.Name + "] was detached");


                        catch (Exception ex)


            Console.WriteLine("Press enter to close");


    • Compile the program, press F6
    • Copy the executable to your SharePoint Farm
    • Run the executable
    • Open the C:\detachall.bat file , this file will contain all the stsadm commands that will detach all your content databases
    • Open the C:\attachall.bat file, this contains all the stsadm commands to reattach your databases (NOTE: you should attach one at a time in the later steps).

Task 5 – Backup important files

  1. If running in a virtual environment, backup your front end webservers main image file.  After doing this, you may skip the rest of these steps and head straight for upgrade!!!
  2. Web.config files for all web applications (located in WSS directory of wwwroot)
  3. Core Site definitions that were modified  ( located in 12 hive template/sitetemplates directory)
  4. Any customizations including:
    • Changes made to core.css
    • Changes made to javascript files
    • Pretty much anything you changed in the 12 hive…

Task 6 – Upgrade the servers (WSS)

  1. Stop IIS
    • Open a command prompt, run “iisreset /stop”
  2. Run “d:\lab files\25_Lab01\ wssv3sp2-kb953338-x86-fullfile-en-us.exe”
  3. Click “Click here to accept…” check box
  4. Click “Continue”
  5. The service pack should start…:

  1. When the WSS update finishes, the Configuration Wizard will start:

  1. Click “Next”

  1. Click “Yes”

  1. Click “Next”

  1. Click “Ok” at the information popup, the farm will start to configure itself.  This includes:
    • Updating DLLs (gac)
    • Creating/Updating registry keys
    • Creating/Updating 12 hive information
    • Updating web.config files
    • Installing new features
  2. The install should finish:

  1. Repeat the above steps for the svr-sp2 image

Task 7 – Upgrade the servers (MOSS)

  1. Stop IIS
    • Open a command prompt, run “iisreset /stop”
  2. Run “d:\lab files\25_Lab01\ officeserver2007sp2-kb953334-x86-fullfile-en-us.exe”

  1. Click “Click here to accept…” check box
  2. Click “Continue”
  3. The service pack should start…:

  1. When the MOSS update finishes, the Configuration Wizard will start:

  1. Click “Next”

  1. Click “Yes”

  1. Click “Next”

  1. Click “Ok” at the information popup, the farm will start to configure itself.  This includes:
    • Updating DLLs (gac)
    • Creating/Updating registry keys
    • Creating/Updating 12 hive information
    • Updating web.config files
    • Installing new features
  2. The install should finish:

  1. Repeat the above steps for the svr-sp2 image

Task 8 – Reattach the content databases

  1. Open the C:\attachall.bat file, run the attach command for each content database that you detached
  2. SharePoint will upgrade the database as it attaches it.

Task 9 – Verify Install

1.       Open the upgrade.log file (in 12 hive LOGS directory)

o    Look for “Finished upgrading SPFarm Name=<Name of Configuration Database>”

o    Look for “In-place upgrade session finishes. Root object = SPFarm=<Name of Configuration Database>, recursive = True. 0 errors and 0 warnings encountered.”

2.       If the above entries DO NOT exist, look for all instances of

o    “fail”

o    “error”

3.       Check version number on:

o    Owssvr.dll (in 12 hive isapi directory) should be “12.0.6421.1000”



o    Registry “HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\12.0”


o    Central administration

4.       Check version of the sharepoint databases:

o    Run the following sql command on each database:

select * from versions
order by timestamp desc


o    You should get “”


5.       On Central Administration, click “Operations”

o    Click “Servers In Farm”

o    The version for the farm and servers should be “”


Task 10 – Check for SharePoint 2010 readiness

1.       Run the following command:

stsadm –o preupgradecheck


2.       Review the PreUpgradeCheck-*.htm file in the 12 hive logs directory (it should open in a browser window

3.       You should watch out for the following items:

o    The above command should be run on all Web Front end servers to ensure they are identical

o    You should review the Site Definition information for any non “Internal” site definitions, these will need to have an upgrade definition file.  Your developers will need to build this file for SP 2010

o    If you have language packs installed, you will need to install the latest version when SP 2010 comes out

o    Look for any referenced and missing features.  Either install them or delete the references to them

o    Depending on the type of upgrade to SP 2010 you do, you many need to plan for URL changes in your sites

o    Review the Lists that have more than the recommends number of items.  These could slow the migration process to SP 2010.  Consider removing the list or deleting items to shrink the list size

o    Review any Custom Field types that have been added to your Farm.  CAML is not used in SP2010 and each of them will need to be re-developed with XSLT in mind.

o    If you are running on 32 bit OS and Server 2003, you will need to start planning for migration to a 64bit server 2008 environment to run SP 2010

Bug in SP2 – product expiration date is improperly activated.

I saw this note on a linkedin post this morning and I immediately checked my calendar to see if it was April 1st today. Guess what, it isn’t….This bug will make SharePoint expire as though it was a trial installation 180 days after SP2 is deployed. Please check the original post on the msdn blogs here

To work around this issue you will need to re-enter their Product ID numbers (PID) on the Convert License Type page in Central Administration.  Please see this KB article for detailed steps. 

lessons learned in my last sps to moss migration project using gradual approach

I have been doing a fun project for a customer, which asked to have his SharePoint Portal Server 2003 farms upgraded to MOSS 2007 using the gradual upgrade approach. I wanted to share some tips and things to consider when you are facing such a project.

1. remove unused and/or previous versions of webparts fom the SharePoint configuration.

There can still be web parts registered in SharePoint that have been physically or manually removed from the virtual server. Check stsam -o enumwppacks for any webpart packages installed that are no longer registered in the web.config files and so on. Know that when you start the upgrade of the web application, MOSS will try to upgrade all registered webpart packages and that if it cannot find it anymore, the process will fail and you zill not be able to upgrade the web application until you have fixed this. 

2. check if your IIS sites have not been renamed

Another one of those things to keep in mind is the fact that when the farm is created in SPS, it writes down the name of the IIS web site in the configuration database. The MOSS upgrade will use this information to find out which IIS site corresponds to the SPS sites. If these sites have been renamed in the meantime and you want to upgrade a SPS web application, then you can get a message indicating that there is nothing to upgrade or you will also not be able to find your SPS virtual servers in the MOSS upgrade pages in Central Administration v3. If for some reason you are in a farm scenario and your IIS site name has been changed on another front end server and not on the one you are performing the upgrade, then you will not get this warning, but the MOSS upgrade will not update the IIS site with the alternat url or port that you configure and you will therefore need to make the changes manually.

3. consider adding an additional frontend server to be used as the server that performs the upgrades

When you are ready to start upgrading sites, you need to do this on a server running the Central Administration role and the Web Application role. Do not think you can get away by using your index server to do your upgrades. The moss upgrade pages go through your IIS configuration to find the web applications that can be upgraded. If you are going through the upgrade pages on a central admin site hosted on your index server and net having the web application role, you will not find any web applications and/or site collections for which you can start the upgrade. Of course having installed MOSS on top of your existing front end servers, already bring an additional load to those systems and your users will probably start complaining with performance issues. That is why I would advise havin an additional frontend server installed in your SPS farm and use this one for performing the upgrades.

4. beware of the side effects of prescan

Another thing that surprised me in the project is prescan. This required tool suppoedly does not change anything to your sites. However it does. You know when you are viewing a list of all yous Document libraries and lists in your site, that it mentions next to each list when the last modification was done in that library or list (e.g. 6 days ago). Well running prescan will reset that information. So while it does not actually change any documents or lists, it does change the last modified date of the list or library itself. Knowing this may help you when you get your users on the phone complaining that all the document libraries have been changed all of a sudden (after you have run prescan)

5. there is no stsadm command to lock/unlock a site in SPS

damn, this is a bugger. Planning to script the upgrade of each site I found out that you cannot lock a site in SPS using the commandline stsadm tool. Apparently this was only introduced in MOSS. I found the solution in SPSiteManager (see my post about it)

6. Plan your content databases in MOSS

part of my project I was asked to have tha large databases in SPS, split up in multiple databases in MOSS. I did this by using the stsadm -o mergecontentdbs operation right after the site has been upgraded. Unfortunately you cannot choose wher the upgrade porcess needs to put the upgraded site collection. Part of the preparations to your upgrade is the fact that you need to configure a 1 to 1 relation of your existing SPS content databases to your MOSS databases, meaning that if a site is located in a specific content database, that its upgraded version will end up in the configured MOSS database and nowhere else (even if there is a parameter in the stsadm -o upgrade command that allows you to specify the targetdatabasename)

A piece of good advise: If you are planning to have more content databases in a specific web application in MOSS than you have in the corresponding virtual server in SPS, create additional empty databases in SPS to match the number of content databases in MOSS. It will save you a lot of trouble if you need to revert an upgraded site and reupgrade it again.

7. Check your upgrade.log file

Every action that MOSS does which regards upgrades of web applications, upgrades of site collections and even reverts of sites is logged in the upgrade.log file. If you have chnaged the default logging location in Central Administration v3 – Operations – Diagnostics Logging, then do not expect the upgrade.log file to be there as well. This log file does not leave the nest. You need to find it in the 12-hive Logs folder. A good practice would be to clear this file before starting the upgrade of any site.

8. Know how to rollback a failed upgrade of your SPS virtual server.

I had this issue that I was finally ready to start the upgrade of the web application and that during this upgrade process the well-known “unknown error occured” appeared. When I went back to the upgrade page, I was not able to rollback this operation or redo the upgrade. So what do you do next? the answer is very simple: delete the newly created web application in MOSS and every change made to the IIS sites (URL redirection) will automatically be undone as well.

I am sure that I can add some otherpoints to this list, but nothing comes to my mind on this sunny sunday afternoon. If something does come up I will gladly add it to this post and share it with you guys.

Steve Riley: employment ended with Microsoft!

What a shock when I found out about Steve Riley being kicked out of Microsoft as part of a restructuring. If you ever attended Tech Ed conferences, then you must have seen Steve in action. His sessions were and still are legendary. The session I enjoyed most was: Defending Layer 8

I am sorry to hear you go, Steve, but I am sure you will be around soon.

Read all about Steve on his blog soon to disappear I gues:

Good news: His new blog can be found at