This post is all about installing WSS v3 in parallel to WSS v2 on your SBS. Now, the Microsoft provided documentation does a good job of walking you through this, but there a few things they don’t provide solutions to that you need to think about in advance.
First, I’m going to go out on a limb and think that you are probably planning on using the search functionality within WSS v3. The nice thing about v3 is that you do not need full-blown SQL in order to get full-text search. The down side is that if you upgraded your companyweb database to a full SQL backend to get search functionality, this breaks the search in WSS v3. However, we can fix this – but it means that we aren’t going to have search on our WSS v2 sites. If you’re like me where you’re moving everything to v3, this isn’t a big deal. However, if you determine you need to keep full-text search on your v2 sites, or if you’re running SBS Std you can go ahead and skip this post
(Edit: There’s mixed reviews on just what does break search in WSS 3.0 as Susan mentions here. Short story is that we know search works if you’re running SBS Std. We know search breaks if you upgraded your companyweb to full SQL 2000 Std. What we don’t know is if search breaks if you upgraded your companyweb to full SQL 2005 Workgroup. I’m going to try to find a box to sacrifice and test this scenario. Until then – let me know what you’ve seen out there)
So here’s the plan: In order to get full-text search working on WSS v3, we need to effectively downgrade our existing WSS v2 to use WMSDE instead of full SQL. The high-level overview of this process is that we’re going to backup our WSS v2 site(s), remove the intranet component from SBS, uninstall the SHAREPOINT SQL instance, then re-install the intranet component and restore our WSS v2 sites. Simple, right?
Step 1: BACKUP!
I like to be extra safe with this, so I’m suggesting two backups of each site – one with STSADM and one with SMIGRATE. An stsadm backup is great because it keeps all of our security, etc. in tact. An smigrate backup is great because it gives us the flexibility of restoring to any machine running WSS v2, not just the machine the backup was taken from. So, to backup your companyweb create a new directory somewhere on your server, with two sub directories – stsadm and smigrate. (On my server the directory I created was D:\wsstemp)
Open a command prompt and change your working directory to C:\Program Files\Common Files\Microsoft Shared\web server extensions\60\bin
Enter the following command:
stsadm -o backup -url http://companyweb -filename D:\wsstemp\stsadm\companyweb.dat -overwrite
Be sure to replace D:\wsstemp\stsadm with your local path. When that command is finished, you’ll run an smigrate backup from the same working directory:
smigrate -w http://companyweb -f D:\wsstemp\smigrate\backup.fwp -y
Again, be sure to replace D:\wsstemp\smigrate with your local path.
Repeat this for each WSS v2 site you have. You can store multiple stsadm backups to the same directory, as each stsadm backup is contained within a single file, just be sure to use a different file name for each site . However, you will want to save your smigrate backups in a separate folder for each site, as the smigrate backup can be split among multiple files depending on the size of the site being backed up)
Step 2: Remove intranet component.
Now that you have your WSS v2 site(s) backed up, we can remove the intranet component from SBS. To do so, go to Add/Remove Programs and locate Windows Small Business Server 2003, and click Change / Remove.
When the Small Business Server Setup Wizard starts, click Next until you get to the Component Selection screen. On this screen, click the Action column next to Server Tools and select Maintenance. Then, click the Action column next to Intranet and select Remove.
Click Next and finish the SBS Setup wizard.
Step 3: Remove the Sharepoint SQL instance:
Once the SBS Setup wizard completes, you will return to the Add/Remove Programs window. Locate the Microsoft SQL Server 2000 (SHAREPOINT) entry and click Change/Remove. Follow the wizard to completely remove the Sharepoint SQL instance.
Once you have successfully removed the Sharepoint SQL instance, close Add/Remove Programs and reboot your server.
Step 4: Re-install SBS Intranet component.
After your server reboots, you are ready to reinstall the SBS intranet component. This process is virtually identical to the removal process we went through in step 2. The only difference is that when you get to the Component Selection screen, you will select to install the Intranet component, the finish the wizard.
Once the wizard has finished, verify that you can navigate to http://companyweb and that you get a new, stock companyweb site.
Step 5: Restore your existing companyweb site.
At this point, our easiest restore is going to be using our stsadm backup. Open a command prompt and navigate to C:\Program Files\Common Files\Microsoft Shared\web server extensions\60\bin then enter the following command:
stsadm -o restore -url http://companyweb -filename D:\wsstemp\stsadm\companyweb.dat -overwrite
Be sure to replace D:\wsstemp\stsadm\companyweb.dat with your local path and filename of your backup. Once this completes, navigate to http://companyweb and verify that your original site is in-tact.
There you go – you have successfully downgraded your companyweb site from a full SQL backend to a WMSDE backend, which will allow search to function when you get WSS v3 installed.