Installing WSS 3.0 on SBS 2003 Standard

Installing WSS 3.0 on SBS 2003 Standard

Windows SharePoint Services 3.0 on Small Business Server 2003 Standard:

The Very Basics

Version 5.1, updated June 24, 2008

Note for v.5.1: I have discovered a major potential problem with these instructions. By default, even when you move the WSS 3 database off the C: partition (step 13), you will still end up with a couple of log files in C:\WINDOWS\SYSMSI\SSEE\MSSQL.2005\MSSQL\Data. One of these in particular, the SharePoint_Config log, will grow unchecked unless you take steps to control it. This could potentially eat up all available space on the server operating system partition, with obviously serious consequences.

I hope to add step-by-step instructions for preventing this problem in the future. In the meantime, please see these articles for more information:

This is a step-by-step guideline to installing WSS 3.0 on a single-NIC SBS 2003 Standard as an addition to the built-in Companyweb, which runs on WSS 2.0. By following these steps you will have two separate functional web sites, both of which are accessible via LAN and Internet. The WSS 3.0 site will be at http://intranet on the WAN and https://servername.domain.tld:5555 from the Internet. You may substitute your own desired values for intranet and 5555, and of course servername.domain.tld should be your own — in my case it’s sbs.schrag.net.

If you find any mistakes in these instructions, please report them to david@schrag.net.

This document does NOT cover:

  • Why you would install WSS 3.0
  • Content migration
  • Full-blown SQL installations
  • ISA or the SBS RRAS firewall
  • How to generate or purchase an SSL certificate — it assumes you already have one available.

For a fuller explanation of WSS 3.0 in an SBS 2003 environment, readers are urged to consult the following resources, some of which have been plagiarized in the document you are reading (Steps 1-8 are largely from the Microsoft document and the remaining steps are largely from Chad Gross’s blog, particularly part 4.)

See also the articles tagged as SharePoint in The Schlog. OK, here we go.

  1. Back up your server — just in case.
  2. Configure your hardware firewall to direct traffic on port 5555 to your server’s IP address. (Reminder: these instructions do not apply to dual-NIC server configurations.)
  3. (UPDATED, v5) If you haven’t already, install SP3 for WSS 2.0. This is a prerequisite for upgrading to 3.0, and even though you won’t actually be upgrading your 2.0 site to 3.0, the installation of 3.0 won’t run without WSS 2.0 SP3. The service pack is available through Microsoft Update. No reboot is required.
  4. Download .NET Framework 3.0 from http://go.microsoft.com/fwlink/?LinkId=77799 and save it to disk on your server.
  5. Install .NET Framework 3.0. The install process will involve another 54 MB download. Default installation settings are OK. A reboot may or may not be required.
  6. (NEW, v5) Install SP1 for .NET Framework 2.0 and .NET Framework 3.0 from Microsoft Update. A reboot is required.
  7. (NEW, v5) If you have WSUS 3.x installed on the server, install this hotfix to avoid post-installation configuration errors. For more information, see this Microsoft blog.
  8. (NEW, v5) This step has been reported by a reader, but not verified by me: If you have SQL Server 2005 Express installed (or, I presume, SQL Server 2005 installed), the configuration of SharePoint 3 will fail early on with a “cannot connect to database” error. (This may not happen if you have upgraded the companyweb to SQL Server 2005; I just don’t know).

    To fix this, uninstall and reinstall but when reinstalling you _ABSOLUTELY__MUST_ select “Web front end” on the “Server type” tab and then create a farm. The process is shown pretty well at http://www.cjvandyk.com/blog/Lists/Posts/Post.aspx?ID=87, although that is not SBS-specific. For the Database Server I used {myserver}\SQLEXPRESS but perhaps some other instance would have worked too.

  9. (UPDATED, v5) Download WSS 3.0 SP1 install file and start the installation.
  10. On the Microsoft License Terms page, review the licensing agreement. To continue, you must accept the agreement. Click Yes.
  11. On the Windows SharePoint Services 3.0 Properties page, complete the following:
    1. On the Upgrade tab, select No, do not upgrade at this time. Caution: When you install Windows SharePoint Services 3.0 on your server, do not choose Gradual upgrade or In-place upgrade. If you do, several Windows SBS administration tools will fail, and you might lose data on your Windows SharePoint Services sites. You must choose No, do not upgrade at this time, which results in a side-by-side installation.
    2. On the Server type tab, ensure that Stand-alone is selected.
    3. (NEW, v5) On the Data Location tab, pick a partition with a lot of free space (probably not your C: partition).
    4. Click the Install Now button.
    5. When the wizard finishes, leave the Run the SharePoint Products and Technologies Configuration Wizard now check box selected, and then click Close. Let the wizard do its thing. If you see a dialog box for restarting Internet Information Services (IIS), SharePoint Administration Service, and SharePoint Timer Service if required, click Yes.
    6. If you are prompted to reboot, click Yes. (But you probably won’t be.)
  12. The default Web site (http://ServerName) that is automatically generated during Windows SharePoint Services 3.0 Setup opens in your Internet browser. Close the browser. The default Web site (http://ServerName) and the http://companyweb Web site stop at this point. You cannot use these Web sites until you complete the remaining steps in this document.
  13. (NEW, v5) By default, WSS 3.0 is installed using the Windows Internal Database on the system partition (C:). You will probably want to move the data files to a different location so you don’t fill up the system partition. The steps listed in this section are adapted from two articles, found here and here. These instructions assume you already have SQL 2005 Express installed. If not, see those two articles for more information.
    1. Create a new folder to contain your data. In this example, I’m using F:\WSS3
    2. Launch SharePoint 3.0 Central Administration from Start |Administrative Tools. Click on Application Management, Content Databases. Click on WSS_Content. Change the Database Status from Ready to Offline. Click OK.
    3. Open two command prompt windows. One will be used for SQL commands, the other for Windows Operating system commands. In the OS prompt window, type net stop mssql$microsoft##ssee
    4. Using Windows Explorer or a scripted command, move C:\WINDOWS\SYSMSI\SSEE\MSSQL.2005\MSSQL\Data\WSS_Content.mdf and C:\WINDOWS\SYSMSI\SSEE\MSSQL.2005\MSSQL\Data\WSS_Content_log.ldf to F:\WSS3
    5. At the command prompt, type net start mssql$microsoft##ssee
    6. In the second command prompt window, type sqlcmd -S \\.\pipe\mssql$microsoft##ssee\sql\query -E. Then type three commands within the SQLCMD environment:
        1. EXEC sp_attach_db @dbname = ‘WSS_Content’, @filename1 = ‘F:\WSS3\WSS_Content.mdf’, @filename2 = ‘F:\WSS3\WSS_Content_log.ldf’
        2. go
        3. exit
  14. Open your DNS MMC, expand <servername>, and select Forward Lookup Zones. Select your internal domain name, so that the list of computers in your domain appears in the right pane. Right-click the internal domain name and select New Host (A). Create a new A record for ‘intranet’ that points to the internal IP of your SBS, check the box to create a PTR record, and then click Add Host.
  15. Click Done. Open a command prompt and type ipconfig /flushdns. Ping intranet and verify that you receive replies from the internal IP of your SBS.
  16. Click Start | Administrative Tools | SharePoint 3.0 Central Administration.
  17. Click on the Application Management tab. Click Create or extend Web application. Click Extend an existing Web application. On the page that opens, click on the Web Application field and select Change Web Application. On the page that opens, select your SharePoint Web Application. (It should be listed as “SharePoint – 80” with a URL of http://servername/. Click the name to select it.
  18. In the IIS Web Site section, select the option to create a new web site. Enter a description for the new site (e.g., Intranet). In the Port field, enter 80. In the Host Header field, enter intranet. Verify that the path is set to the default: C:\Inetpub\wwwroot\wss\VirtualDirectories\intranet80. Leave the rest of the fields in their default settings. Click OK.
  19. Open your web browser and verify that http://intranet opens your new Sharepoint site. At this point it should prompt you for credentials, and if you are browsing from your SBS box you should be prompted to add http://intranet to the list of trusted sites. Do so.
  20. Return to the SharePoint 3.0 Central Administration and click on the Application Management tab.
  21. Under the SharePoint Web Application Management section, click on Remove SharePoint from IIS WebSite.
    1. In the Web Application section, verify that the web application is http://servername.
    2. In the Deletion Options section, verify that the IIS Website is set to SharePoint – 80 (Default).
    3. Elect the option to Delete IIS Web sites. Click OK.
  22. Open IIS Manager, expand servername and expand web sites. Select the default web site and click the Start button.
  23. Right-click the Intranet web site and choose Properties.
    1. On the Web Site tab, the TCP port should be 80 and the SSL port should be 5555. Click the Advanced button. The IP address should be Default, the TCP port should be 80, and the Host header value should be intranet. In the lower half of the window, the IP address should be Default and the SSL port should be 5555. Make changes if necessary and click OK.
    2. On the Home Directory tab, verify that Local path is set to C:\Inetpub\wwwroot\wss\VirtualDirectories\intranet80 and that Application pool is set to SharePoint – 80.
    3. On the Directory Security tab, use the Server Certificate button to install or select your desired SSL certificate. The steps involved here will depend on what type of certificate you are using (self-signed or third-party) and whether it is a new or existing certificate. Covering each scenario is beyond the scope of this document.
    4. Click OK.
  24. Go back to SharePoint 3.0 Central Administration and click Application Management. Click Create or extend Web application. Click Extend an existing Web application.
    1. In the Web Application section, select SharePoint – 80. It should show up as http://servername.
    2. In the IIS Web Site section, choose the Create a new IIS web site radio button. In the Description box, type Intranet – SSL. (Do NOT simply type Intranet here or you will get confused later.) Choose 5555 for the port. Edit the end of the path so that it reads C:\Inetpub\wwwroot\wss\VirtualDirectories\intranet80.
    3. In the Security Configuration section, set the Use SSL button to Yes.
    4. In the Load Balanced URL section, change the URL to http://servername.domain.tld:5555.
    5. Click OK.
  25. Go back to IIS Manager, refresh the view, and open the Web Sites folder. You should see both Intranet and Intranet – SSL. Intranet will be stopped. Right-click Intranet – SSL and choose Stop. Then right-click Intranet and choose Start. Right-click Intranet – SSL and choose Delete.
  26. Open a new browser window and confirm that you can still access http://intranet.
  27. (NEW v2) Go back to SharePoint 3.0 Central Administration. On the Operations tab, under Global Configuration, click “Alternate access mappings.”  Click “Edit Public URLs.” Change the Alternate Access Mapping Collection to SharePoint – 80. Verify that the boxes are completed as follows and save changes if necessary:
    1. Default: http://intranet
    2. Intranet: [leave box blank]
    3. Internet: https://servername.domain.tld:5555
    4. Custom: [leave box blank]
    5. Extranet: [leave box blank]
  28. On a machine outside your LAN, open Internet Explorer and browse to https://servername.domain.tld:5555. Depending on the type of certificate chosen and the browser you are using, you may get a security warning. If so, continue through this. You should then be prompted for domain credentials. For now, use the domain admin credentials that you used to install WSS 3.0, because the rest of your domain users are not automatically given rights to the new intranet. If the Team Site comes up, you have successfully completed your task.
  29. (NEW v2) When you are setting up links to your WSS pages — for example, a link from the QuickLaunch page to a document library or list in your WSS site — leave out the http://intranet and https://servername.domain.tld:5555 prefixes and just put in the remainder of the URL. For example, if you create a list called “Employee Birthdays,” enter the link simply as /Lists/Employee%20Birthdays/AllItems.aspx. SharePoint will be able to detect whether a given user is coming in internally or externally and will pass the appropriate prefix to the user’s browser.
  30. (NEW v3) By default, SMTP services are not enabled so e-mail handling will not work. According to the Microsoft guide to installing WSS 3.0 on SBS, “The integration of incoming e-mail with Windows SharePoint Services 3.0 does not work because of a conflict with Exchange.” Not sure exactly what that means yet or what the implications are. So for now skip the incoming e-mail bit. In SharePoint 3.0 Central Administration, from the home page, click task #2, Outgoing e-mail settings. On the next page, click “Configure Outgoing E-mail Settings” again. Complete as follows:
    1. Outbound SMTP server: servername (do not use servername.domain.tld and do NOT use “localhost”)
    2. From address: administrator@domain.tld (or another address of your choosing)
    3. Reply-to address: administrator@domain.tld (or another address of your choosing)
    4. Character set: leave as default
  31. (NEW, v5) Regarding the incoming e-mail issue in the previous step, a reader wrote the following, which I have not yet verified. Note that these instructions include settings for spam filtering, which may or may not be necessary in your environment:

The implication is, wss/sps expects to have its own smtp service, and not have exchange installed on the same os, this allows the true mail server to have an internal dns record and smtp connector setup to pass mail to the dummy smtp receiver on the wss server as documented  here: http://www.combined-knowledge.com/Downloads%202007.htm

This process will allow an incoming email to reach the a sharepoint wss server 3.0 installed in parallel to the wss2.0 on a Sbs 2k3 r1/r2 server (created by Paul Sexstone , Paul@acsnz.biz)

  1. Create a drop directory where all sharepoint destined email can be stored:

    d:\spsserver\email

  2. Setup custom weight list to black list keyword to push all messages with a given tag word “spsletmein” through to the sps server (see imf documentation at http://support.microsoft.com/?kbid=907747 and custom weighting documentation at http://go.microsoft.com/fwlink/?linkid=52072)>

    C:\Program Files\Exchsrvr\bin\MSCFV2\MSExchange.UceContentFilter.xml

    <?xml version=”1.0″ encoding=”UTF-16″?>
    <CustomWeightEntries xmlns=”http://schemas.microsoft.com/2005/CustomWeight“>
    <CustomWeightEntry Type=”BOTH” Change=”MAX” Text=”spsletmein”/>
    </CustomWeightEntries>

  3. Setup script to find and copy tagged emails to drop directory

    spsspam.cmd

    rem tag test is = spsletmein

    for /f  “tokens=*” %%i in (‘findstr /m /c:spsletmein f:\spamdir\*.*’) do copy “%%i” d:\spsserver\email

  4. Setup a scheduled task to run the script above which copies only tagged emails to the dump folder without affecting other imf archived messages
  5. Create a domain user for sharepoint aliases, hidden from exchange address list, the user account is just a placeholder to allow the incomming messages to pass the recipient filter block which is set to block unknown email addresses.
  6. Enable incoming mail and specify drop directory in sharepoint administration operations management, with advanced setting. Specifying the no active directory integration and and email domain name which is used in exchange (external domain name to allow sps mail to be sent from external)

    eg : email server display address = companyname.co.nz

                email drop folder = d:\spsserver\email (as specified above)

  7. Add an email address to the sharepoint user created in active directory
  8. Enable the sharepoint site or list for incoming mail, and specify email address specified in active directory

How to use: send an email to the sharepoint email address created above, and have the message contain “spsletmein” in the subject or message body. The resulting message will reach the sharepoint enabled list or library successfully.

Note: wss incomming email logs are held at

C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\Logs

and allow you to see the processing of the mail from the drop folder, essential in diagnosing misprocessing problems and email not arriving where expected.

[End of instructions]

If it is not working, double-check that the firewall is configured correctly, that the properties of the Intranet site are as shown in step 23, and that the site is running. If it’s still not working, delete any sites named Intranet from IIS Manager and start again on step 16.

Reminder: report any proven errors in this document to david@schrag.net.

As a next step, you might want to try the WSS 3.0 templates. See http://msmvps.com/blogs/bradley/archive/2007/06/26/so-if-you-are-looking-to-install-the-wss-3-0-templates-on-your-wss-3-0-side-by-side.aspx.

See also the video tutorials mentioned in the Diva’s blog.

Note: special thanks to Davin Biggs of BDAV Consulting in Melbourne, Australia, for helping me work this out and for providing a couple steps toward the end. (Because of my lazy editing and renumbering, I forget exactly which steps they were.) Thanks to Eriq Neale for information on the WSUS hotfix. Thanks to Paul Sexstone for instructions on handling incoming e-mail.

Posted in All, SBS, Server 2003, SharePoint, Software, Technology on Jul 11th, 2007, 9:31 am by David Schrag   

18 Responses

  1. July 12th, 2007 | 8:24 pm

    Microsoft Introduces New Tool for Small Business Server Partners…

    Press Release: Microsoft Executives Outline Next-Generation Business Opportunities for Partners with…

  2. briwlls
    September 5th, 2007 | 7:16 am

    Great article David! I emailed this article to our local SBS group, Technology Wizards.

  3. September 5th, 2007 | 7:25 am

    […] David Shrag’s instructions on deploying SharePoint3 http://davidschrag.com/schlog/167/installing-wss-30-on-sbs-2003-standard […]

  4. September 29th, 2007 | 4:49 am

    […] Installing WSS 3.0 on SBS 2003 Standard. […]

  5. June 1st, 2008 | 10:36 am

    […] on SBS instructions updated I have posted a substantial update to my instructions for installing WSS 3.0 on SBS 2003 Standard. If anyone has time to double-check my work and fix any problems, I would greatly appreciate […]

  6. June 24th, 2008 | 11:52 am

    […] caused by an expanding log file created by Windows SharePoint Services 3.0. I’ve updated my WSS-on-SBS instructions to acknowledge the problem and point people toward the fix, but I don’t have step-by-step […]

  7. July 17th, 2008 | 8:03 am

    […] (David Schrag has an excellent post on this and there is also the official white paper on the SBS blog) […]

  8. January 18th, 2009 | 12:22 pm

    […] the site rather than the normal path/port that WSS generates: Using David Schrag’s instructions (http://davidschrag.com/schlog/167/ installing-wss-30-on-sbs-2003-standard) he says to extend a website and the delete the system […]

  9. January 18th, 2009 | 12:41 pm

    […] forum and the following link was mentioned for anyone that needs a step-by-step on how to do that http://davidschrag.com/schlog/167/in…-2003-standard — Costas "Cary Shultz" <cshultz> wrote in message news:e8vPNScWIHA.4896… > […]

  10. roberto
    August 26th, 2009 | 10:31 pm

    Thanks David.

    I just wondered: what happens to the content database that gets turned off in step 13… should one leave offline or set it to ready again. or should one create a new content database?

    thanks

  11. Rick
    September 21st, 2009 | 3:44 pm

    Working on setting up the inbound email to WSS3.0 per instructions above. I’m confused about the spsspam.cmd script where it looks at the “f:\spamdir\*.*” I am assuming that I replace this folder with the path to my spam directory from my Exchange server. However, I’m not sure where that is or how it populates. I’ve checked the bad mail folder but what determins where the CustomWeighted filtered email goes? That is what I’m stuck on. Any ideas? Thank you.

    Rick

  12. Aaron
    February 20th, 2010 | 11:11 am

    Thanks for the instructions – very helpful!
    I’m stuck on steps 17-23. You suggest extending a web application from http://servername for Intranet (http://intranet). Then you suggest deleting IIS site for http://servername. On step 23 you reference http://servername again for setting up a SSL site, but I now only have http://intranet. http://servername is gone. Any ideas? Thanks, Aaron

  13. March 8th, 2010 | 3:54 pm

    David,

    I set my server up based on these instructions some time ago and it has work flawlessly until recently. All of a sudden I can no longer access http:/intranet from within the network, although I can still access from outside the network with the external address with no issues. Any suggestions?

    skids

  14. April 1st, 2010 | 5:25 pm

    […] http://davidschrag.com/schlog/167/installing-wss-30-on-sbs-2003-standard Possibly related posts: (automatically generated)Windows Small Business Server 2008 Best Practices Analyzer availableBlog of the EMEA SBS Team : How to change/reset the status of Migration Tas… […]

  15. March 31st, 2011 | 2:43 pm

    Thank you for these helpful instructions!

  16. April 4th, 2011 | 3:46 pm

    I set my server up based on these instructions some time ago and it has work flawlessly until recently. All of a sudden I can no longer access http:/intranet from within the network, although I can still access from outside the network with the external address with no issues. Any suggestions?

    David
    I seem to be having the same problem as skids.

  17. April 6th, 2011 | 3:44 am

    How do it possible moving the date site in other location?

  18. April 11th, 2011 | 10:45 am

    What a good set of instructions with using these i was able to install wss on my sbs 2003 server. I have been working alot with server 2008 and when it can to doing this wss install on a 2003 sbs server i was drawing a blank. Thanks for the post got me out of a hole

Leave a reply