Installing SharePoint Services 3.0 in a Sandbox Environment

by Kindler Chase 16. March 2008 12:18

Warning: This is a very long post (as in several megs!). The information provided here will aid you in the installation of Windows SharePoint Services 3.0 (WSS 3.0) in a sandbox environment, aka, Virtual PC. The information will also work as a guideline for installing Microsoft Office SharePoint Server 2007 (MOSS 2007). And with a few minor adjustments, you can easily adapt this for installing WSS in a server environment as most of the concepts remain the same.

Table of Contents


For this walk-through, you will need to prepare your virtual environment with the following:

  • A complete installation of Windows Server 2003 R2 (or similar) with all patches installed.
    • For reference, I have named my virtual server: VirtualWSS (feel free to use VirtualMOSS if you are setting up a MOSS environment)
  • Installation of .NET 2.0 and related service packs.
  • Installation of .NET 3.0 and related service packs.
  • Upgrade Internet Explorer 6 to Internet Explorer 7 and apply all IE 7 patches.

Most, if not all, of the .NET installs/updates and upgrade to IE 7 can be accomplished directly through Windows Update.

Once you have upgraded to IE 7 you should uninstall "Internet Explorer Enhanced Security Configuration":

  • Start > Settings > Control Panel > Add Remove Programs > Add/Remove Windows Components and uninstall the Enhanced Security:

Now would be a good time reboot and save your current machine state and maybe even a copy of the current image if you want to start from scratch again at some point.

SharePoint Service Accounts

As a best practice, there should be several service accounts in a SharePoint environment (WSS and MOSS). The accounts you create do not require any special permissions as SharePoint will provision permissions as needed during the installation and configuration of SharePoint. Personally, I remove all roles for every account as soon as I create them as SharePoint will take care of their roles/permissions. For reference, I am prefacing each service account with "vpc" instead of the standard "svc"; vpc = Virtual PC, svc=Service-Account.

Create the following accounts on your server. Be sure to uncheck "user must change password at next logon" and check "password never expires" (see screen shot below):




  • Global SharePoint Admin
  • Account used to install SharePoint


  • SharePoint Configuration account
  • Account used to connect to the SQL server (as defined during the installation wizard of SharePoint)


  • SharePoint Crawler account
  • Used to crawl content


  • SharePoint Search account
  • Used to perform searches


  • SharePoint Content Pool account
  • Used as the site collection application pool


  • SharePoint Shared Services Pool account
  • Used as the Share Services (SSP) application pool


  • SharePoint Shared Services Acct account
  • The account that runs Shared Services






  • This group is the local machine's Administrators group.
  • The following users should be members:
    • vpcSPAdmin
    • vpcSPConfig

If needed, here is a sample screen shot when creating a user:

Global SharePoint Admin Account (vpcSPAdmin)

For the remainder of this walk-through, you will need to be logged into your server under the vpcSPAdmin account. Remember to have added the vpcSPadmin account as a member of the local machine's Administrators group.

As a best practice, you should never install SharePoint under your personal account. Doing so will forever tie your personal account to the administration of SharePoint. The installation should be done under a service account.

Reboot your server and log in under the vpcSPAdmin account. After the reboot, verify everything runs as expected and then commit your current state to disk.

Application Server Roles

When setting up your application server roles for SharePoint, you could certainly manually configure them. Or, you can take the path of least resistance and use the "Manage Your Server" applet: Start > Administrative Tools > Manage Your Server:

Mail Server

SharePoint has several email features you'll want play with at one point or another. In order for the email features to work, you'll need an email server. Seeing as SharePoint does not require Microsoft Exchange (though you could certainly use it if you wanted); the easiest route to take is to use the built-in Mail Server (POP3, SMTP) on Windows Server 2003:

  1. Start up the Manage Your Server applet
  2. Add or Remove a Roll
  3. Preliminary Steps > Next
  4. Server Role
    1. Select Mail server (POP3, SMTP) > Next
  5. Configure POP3 Service
    1. Authentication Method: Select Local Windows Accounts
    2. E-mail domain name: SharePoint.local (or whatever domain you are using)
    3. Click Next
  6. Summary of Selections
    1. Click Next
  7. When the configuration is complete, you should receive a "This Server is Now a Mail Server" notification.
    1. Click Finish and you are done

There are few things that need to be wrapped up to complete the mail server configuration:

  1. Open the POP3 Service: Start > Administrative Tools > POP 3 Service
  2. Right click your mail server (VIRTUALWSS) > Properties: Make sure Require SPA and Always create an associated user is unchecked:
  3. Expand the local domain (SharePoint.local) and right click the domain: New > Mailbox:
  4. Mailbox Name: vpcSPAdmin (do not create an associated user):
  5. When a new mailbox user is created, you'll get a nice message:
  6. Close down the POP3 Service console.

Application Server

.NET is required for SharePoint and SQL Server 2005. IIS is required for SharePoint. Combined, .NET and IIS is known as the Application Server role which can be installed the same way the Mail Server was installed:

  1. Start up the Manage Your Server applet
  2. Add or Remove a Roll
  3. $Preliminary Steps > Next
  4. Server Role
    1. Select Application server (IIS, ASP.NET) > Next
  5. Application Server Options
    1. Leave both options, FrontPage server extensions and Enable ASP.NET, unchecked
  6. Summary of Selections
    1. Click Next
  7. When the configuration is complete, you should receive a "This Server is Now an Application Server" notification.
    1. Click Finish and you are done

The ASP.NET / IIS Gotcha

If, as in our case, you install ASP.NET prior to installing the Application Server (IIS), then you'll need to manually register ASP.NET with IIS. To determine if ASP.NET is registered with IIS, open up IIS and check the Web Server Extensions list:

  1. Start > Administrative Tools > Computer Management:
    1. Expand Services and Applications
    2. Expand Internet Information Services
    3. Select Web Service Extensions
  2. If ASP.NET is not registered, then you'll likely see a screen that either does not have ASP.NET listed (as in our case) or ASP.NET is listed, but is set as Prohibited:
  3. To register.NET with IIS, open a command prompt and enter the following:
    1. %SYSTEMROOT%\Microsoft.NET\Framework\v2.0.50727\aspnet_regiis -i -enable
  4. After .NET is registered, your command prompt window should look similar to this:
  5. Now return to IIS and verify that .NET has been registered (you'll need to refresh the console to see the changes). And while you're there, change "Active Server Pages" and "Server Side Includes" to an Allowed status:
  6. Close down the Computer Management console.

Application Server Roles Wrap Up

Once you have installed all the application server roles, you may want to visit Windows Update as there are likely a few updates that need to be applied that are related to the application server roles you just installed.

Go ahead and reboot your server; remember to log in under the vpcSPAdmin account. After the reboot, verify everything runs as expected and then commit your current state to disk.

Installing SQL Server 2005

All things SharePoint related are stored in SQL Server 2005. OK, not everything, but most everything. Installing SQL Server 2005 is a fairly straight forward process with a few points of interest:

  • You do not need to create any SQL Server user accounts as long as you have set up your service accounts as described in this outline. Why? SharePoint will take care of all the necessary account permissions.
  • Though not entirely necessary, you should install SQL Server under the global SharePoint service account vpcSPAdmin.
  • Prior to installing SharePoint, make sure you configure SQL Server to create databases on our dedicated SQL Server drive. No worries, I'll walk you through the steps after SQL Server is installed.

SQL Server 2005 Installation

Let's get started with the installation of SQL Server 2005:

  1. Mount the SQL Server 2005 ISO:
    1. From the Virtual PC Menu > CD > Capture ISO Image…
    2. Load up the ISO to begin the installation
      (sorry, but I couldn't figure out a way to get a screen shot with the CD menu open)
  2. On the SQL Server 2005 Start screen select to install "Server components, tools, Books Online, and samples":
  3. Accept the licensing terms.
  4. Installing Prerequisites:
    1. Click Install
    2. Click Next when the prerequisites are installed
  5. Welcome to the Microsoft SQL Server Installation Wizard:
    1. Click Next
  6. System Configuration Check:
    1. If everything is configured properly you'll be presented with a screen full of green "Success" checkmarks. Success!
    2. Click Next
  7. Registration Information:
    1. Enter you registration information and click Next (c'mon, do you really think I'd give you my information?!?)
  8. Components to Install:
    1. SQL Server Database Services
    2. Analysis Services
    3. Reporting Services
    4. Workstation components, BOL and development tools
    5. Click Next
  9. Instance Name:
    1. Leave "Default instance" selected
    2. Click Next
  10. Service Account:
    1. Select "Use the built-in System account"
    2. Select "local system" from the drop down
    3. Click Next
  11. Authentication Mode:
    1. Use "Windows Authentication Mode"
    2. Click Next
  12. Collation Settings:
    1. Leave everything default and click Next
  13. Report Server Installation Options:
    1. Use "Install the default configuration"
    2. Click Next
  14. Error and Usage Report Settings:
    1. Your choice here. Personally, I do not elect to send error reports or usage data.
    2. Click Next
  15. Ready to Install:
    1. Click Next
  16. If everything is installed properly, which will take 20+ minutes, you'll be presented with a screen full of green "Success" checkmarks. Success!
    1. Click Next
  17. Completing Microsoft SQL Server 2005 Setup
    1. Click Finish

SQL Server 2005 is now installed (SQL Server SP2 will be installed later). Reboot your server; remember to log in under the vpcSPAdmin account. After the reboot, verify everything runs as expected and then commit your current state to disk.

SQL Server 2005 Surface Area Configuration

Our typical install of SQL Server was done in a secure mode (default) and we now need to open up how SQL Server communicates.

  1. Start > All Programs > Microsoft SQL Server 2005 > Configuration Tools: SQL Server Surface Area Configuration
  2. Select "Surface Area Configuration for Services and Connections"
  3. In SQL Server 2005 Surface Area Configuration, expand "Database Engine" and select "Remote Connections" and then select "Local and remote connections: Using both TCP/IP and named pipes"
  4. Click Apply and then OK to accept the "Connection Settings Change Alert"
  5. Click OK back on the SQL Server 2005 Surface Area Configuration window.
  6. Close the SQL Server 2005 Server Surface Area tool.

SQL Server 2005 Memory Allocation and Default Database Location

Here we'll provide SQL Server explicit instructions on how much of our virtual memory to use and then change the default location of databases (optional step).

  1. Start > All Programs > Microsoft SQL Server 2005: SQL Server Management Studio
  2. Connect using Windows Authentication under the vpcSPAdmin account
  3. Right click the VIRTUALWSS SQL Server > Properties
  4. Select "Memory" from the left pane and then change the "Server memory options" to have half of the memory allocated to your Virtual PC. In my case, I have allocated 2 GB of memory to my Virtual PC so I'll change the maximum memory to 1000 MB.
  5. Select "Database Settings" from the left pane and change the "Database default locations" for both "Data" and "Log" to our dedicated database HDD. In my case, I created a directory named: D:\MSSQL\Data
  6. Click OK
  7. Close down the SQL Server Management Studio.

SQL Server 2005 is now configured. Reboot your server for the settings to take effect and be sure to log in under the vpcSPAdmin account.

SQL Server 2005 SP2 Installation

Installing SQL Server 205 SP2 is fairly straight forward.

  1. Mount the SQL Server 2005 SP2 ISO:
    1. From the Virtual PC Menu > CD > Capture ISO Image…
    2. Load up the ISO to begin the installation
      (sorry, but I couldn't figure out a way to get a screen shot with the CD menu open)
  2. Once the ISO is loaded up, double click the executable (SQLServer2005SP2-KB921896-x86-ENU.exe) to extract the files
  3. Welcome screen
    1. Click Next
  4. License Terms
    1. Accept the terms and click Next
  5. Feature Selection
    1. Leave everything as default and click Next
  6. Authentication
    1. Leave everything as default and click Next
  7. Error and Usage Reporting Settings
    1. Your choice of what you want to report and then click Next
  8. Running Processes
    1. Wait a minute or so for the process to be found and then click Next
  9. Ready to Install
    1. Click Install
  10. The installation process will take around 20+ minutes or so. Once everything is installed, you'll be presented with a dialogue to reboot your server and a screen full of "Success" checkmarks. Success!
    1. Click OK and then click Next

  11. Installation Complete
    1. View the summary if you want; click Next
  12. Additional Information
    1. Since we are not using Vista, uncheck the Provisioning Tool launcher and then click Finish

SQL Server 2005 SP2 is now configured. Reboot your server for the settings to take effect (un-mount the SP2 ISO from the Virtual PC's CD drive if you want); be sure to log in under the vpcSPAdmin account after the reboot. After the reboot, verify everything runs as expected and then commit your current state to disk.

You may want to save a copy of your current image to use as the foundation for a MOSS install at a later date; I'll have a follow up post that will describe the MOSS installation that will build off what has been done so far.

Installing Windows SharePoint Services 3.0 (WSS 3.0)

Finally! After much preparation we are ready to install WSS.

Windows SharePoint Services 3.0 Installation

  1. Run the SharePoint.exe executable that has SP1 rolled up with the SharePoint install (link was provided in the prerequisites) to extract the files
  2. License Terms
    1. Accept the terms and click Continue
  3. Choose the installation you want
    1. Select Advanced
    2. Server Type: Web Front End (this will allow us to configure the database settings)
    3. Data Location: leave as is
    4. Feedback: Your choice. And then click Install Now
  4. The Installation will begin
    1. Installation Process
    2. When the installation is complete, check "Run the SharePoint Products and Technologies Configuration Wizard now." And then click Close

SharePoint Products and Technologies Configuration Wizard

We'll now configure our base install of WSS 3.0 using the Configuration Wizard for items such as database and authentication configuration.

  1. You should now be in the "Welcome to SharePoint Products and Technologies" wizard which opens up automatically after the last step above.
    1. Click Next
    2. Click Yes to accept the services to be stopped when prompted
  2. Connect to a server farm
    1. Select No, I want to create a new server farm
    2. Click Next
  3. Specify Configuration Database Settings
    1. Database server: VIRTUALWSS (or whatever you named your server)
    2. Database name: WSS_Config (or use the default of SharePoint_Config or come up with a name you like)
    3. Specify Database Access Account: Use the vpcSPConfig account we set up earlier
    4. Click Next
  4. Configure SharePoint Central Administration Web Applications
    1. Specify port number: 9999 (or leave as the default or come up with your own port number)
    2. Configure Security Settings: select NTLM
    3. Click Next
  5. Completing the SharePoint Products and Technologies Configuration Wizard
    1. Review your settings and make corrections if needed
    2. Leave the Advanced Settings alone
    3. Click Next
  6. Configuring SharePoint Products and Technologies
    1. SharePoint will go through a series of base configuration tasks which may take 5+ minutes
  7. Configuration Successful
    1. When SharePoint is done configuring everything, you'll get a nice congratulatory screen telling you so
    2. Click Finish

Finally, when the SharePoint configuration window is closed, Central Administration should open right up and we can begin configuring the SharePoint environment:

At this point, I like to click into Operations and then Application Management just to be sure everything is looking good. Don't do any configuration, yet; but, poke around and see what's out there.

Miscellaneous Configuration

Adding the http://virtualwss site to our list of trusted sites on the local intranet will alleviate the annoying username/password prompt when attempting to access a site on WSS. And some minor modifications to the browser's settings doesn't hurt either.

  1. Open IE 7 > Tools > Internet Options
  2. Select the Security tab
    1. Click the "Trusted Sites" icon
    2. Click the "Sites" button
  3. In the Trusted sites window
    1. Uncheck the box for "Require server verification (https:) for all sites in this zone
    2. Add http://virtualwss to the trusted websites list
    3. Click Close
  4. Back in the Internet Options > Security: Trusted sites window
    1. Click "Custom level…" in the "Security level for this zone" area
  5. In the Security Settings window
    1. Select "Low" in the Reset custom settings area and then click "Reset…"
    2. Accept the prompt to say Yes you want to change the settings for this zone
    3. Scroll down to the bottom of the Security Settings window and verify that "User Authentication > Logon: Automatic logon with current user name and password" is selected and the click OK
  6. Click OK to close out of the Internet Options window.

WSS 3.0 is now installed with a base configuration. Reboot your server; be sure to log in under the vpcSPAdmin account after the reboot. After the reboot, verify everything runs as expected and then commit your current state to disk.

Configuring Windows SharePoint Services 3.0

There are many different methods to configure WSS; some are just plain bad, while others fall in the category of over-the-top best practice. The approach I've taken falls somewhere in the middle.

For reference, to open Central Administration you can either hand enter the URL (http://virtualwss:9999) or open it from within windows:

  • Start > Administrative Tools > SharePoint 3.0 Central Administration

Configure Farm Administrators

By default, the vpcSPAdmin and vpcSPConfig accounts should have been provisioned to the Farm Administrators group. Verify that they have been added:

  1. Open Central Admin > Operations > Update farm administrator's group (under the Security Configuration heading)
  2. Verify that vpcSPAdmin and vpcSPConfig are listed as a Farm Administrator
  3. If the accounts are not listed, then you may not have followed the steps outlined in this guide. You can enter the accounts manually, but who knows if everything was installed properly?

Configure Outgoing E-Mail

Earlier, we set up the SMTP server. Now it's time to configure SharePoint to use our SMTP server so it can send out email notifications/alerts.

  1. Open Central Administration > Operations > Outgoing e-mail settings (under the Topology and Services heading)
  2. In the Outgoing E-Mail Settings page:
    1. Outbound SMTP Server: VIRTUALWSS (or whatever name you provided earlier)
    2. From/Reply to address: vpcSPAdmin@SharePoint.local
    3. Click OK

Configure Services

If we were installing MOSS, there would be several services that need to be started and/or configured:

  • Document Conversion Launcher Service
  • Document Conversions Load Balancer Service
  • Excel Calculation Services
  • Office SharePoint Sever Search
  • Windows SharePoint Services Search
  • Windows SharePoint Services Web Application

However, since we are only installing WSS, the only service we need to configure is the Windows SharePoint Services Search"

  1. Open Central Administration > Operations > Services on Server (under the Topology and Services heading)
    1. Click the service "Windows SharePoint Services Search"
  2. Configure Windows SharePoint Services Search Service Settings:
    1. Service Account: VirtualWSS\vpcSPSearch
    2. Content Access Account: VirtualWSS\vpcSPCrawler
    3. Database Server: VIRTUALWSS
    4. Database Name: WSS_Search (or leave as default or come up with your own name)
    5. Database Authentication: Windows authentication
    6. Index Schedule: Leave as default for now
    7. Click OK (if an error is thrown when the service is being configured, reboot your server and start the configuration again; I've seen an error thrown but haven't been able to track down why. Rebooting the server seems to clear up the error for some reason.)
    8. When the configuration is complete, you should see the service started on the Services on Server page. Note that the " Windows SharePoint Services Search" label has changed to "Windows SharePoint Services Help Search":

Configure Diagnostic Logging

We'll only make one quick change in the diagnostic logging: change the log folder to our data directory. Why? The log folder can become quite large and we have a dedicated data drive so we may as well use it :)

  1. Open Central Administration > Operations > Diagnostic Logging (under the Logging and Reporting heading)
  2. Trace Log Path: D:\SharePoint\Logs (don't forget to create the directory!)
  3. Click OK
  4. If you want, move all the old files from C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\LOGS\ to the new directory.

A built-in log viewer is noticeably absent in SharePoint. You'll need to write your own… aack! Or you can use the Log File Viewer that Scot Hillier wrote and has kindly shared with the SharePoint community over at CodePlex under the project name SharePoint 2007 Features. Thanks Scot!

Creating the First Site Collection

Prior to creating a Site Collection, we need to configure a Web Application which will serve our Site Collection.

Create a Web Application

  1. Open Central Administration > Application Management > Create or extend Web Application (under the SharePoint Web Application Management heading)
    1. Click the "Create a new Web application" link
  2. Create New Web Application:
    1. IIS Web Site: Use an existing IIS web site > Default web site
    2. Leave everything else default under the IIS Web Site section
    3. Security Configuration: Authentication Provider > NTLM
    4. Leave everything else default under the Security Configuration and Load Balanced URL sections
    5. Application Pool: Create a new application pool
      1. Application pool name: Pool_CollaborationPortal
      2. Configurable user name/password: VirtualWSS\vpcSPContentPool (and your password)
    6. Reset Internet Information Services: Restart IIS Automatically
    7. Database Name and Authentication
      1. Database Server: VIRTUALWSS
      2. Database Name: CollaborationPortal_Content
      3. Database Authentication: Windows Authentication
    8. Search Server > VIRTUALWSS
    9. Click OK
  3. When the configuration is complete, you should see the Application Created Page.
    1. Click the "Create Site Collection" link to create the Site Collection.

Create a Site Collection

Now that the web application has been created, we can now create a site collection.

  1. You should be on the Create Site Collection Page from the previous step.
    1. Web Application: Make sure the http://virtualwss application is selected
    2. Title: Collaboration Portal
    3. Description: Add whatever you want.
    4. Web Site Address: Maker sure the selection uses the single forward slash which will create the site at the root.
    5. Template selection: Leave as the default "Team Site"
    6. Primary Site Collection Administrator: vpcSPAdmin (verify the user is found by clicking the check names icon or use the keyboard shortcut ctrl+k )
    7. Secondary Site Collection Administrator: leave blank
    8. Quota Template: leave as default
    9. Click OK
    10. When the configuration is complete, you should see the Top-Level Site Successfully Created page. Click OK to return to Central Administration.

The Site Collection is created! Go ahead and navigate to http://virtualwss and check it out. Reboot your server; be sure to log in under the vpcSPAdmin account after the reboot. After the reboot, verify everything runs as expected and then commit your current state to disk.

Miscellaneous Tasks

To complete the virtual WSS environment, you should install the remaining software from the prerequisites:

  • Office 2007
  • SharePoint Designer 2007
  • Visual Studio 2005

Once you have installed the remaining software, rebooted as needed and saved your state to disk, you can move on to the final tasks of optimizing the virtual image. Though optimizing the virtual image is beyond the scope of this post, here are several items you can do to reduce the size of the virtual disk and reduce the amount of memory being used by the server.

  • Disable all unnecessary services
  • remove any desktop background images
  • turn off the screen saver
  • turn off hardware acceleration (right click the desktop > Properties > Settings > Advanced > Troubleshoot)
  • change performance options to adjust for best performance (system properties > advanced > performance settings)
  • Defrag the disk
  • Compact the virtual hard disk (you'll need to use the Virtual Disk Precompactor.iso included with Virtual PC)
  • Finally, save a copy of the image to refer to for future builds and/or use the Virtual PC's differencing disk option to run multiple versions of your WSS environment from a single base image.

I've probably missed a few optimizations, so feel free to post your comments on other optimization techniques.



5/23/2008 3:32:19 PM #

Nice job - I was tasked with creating one of these and you just saved me a ton of work~

bob e United States

5/23/2008 5:06:21 PM #

Saving a ton of work is always good to hear! Smile

Kindler Chase United States

8/14/2008 8:06:02 AM #

Hi, Need Request to INSTALL WSS 3.0

Your messages is nice for a Desktop Machine or Laptop. but I want to Install in Remote Desktop Connection, where Database and Active Directory are another Remote Desktop Connection. I Install .Frameworks 2.0, 3.0 and Security Updates but the Username and datbase configuration is Failed durring SharePoint Products and Technologies.


Ramu India

8/19/2008 9:57:51 AM #

Great piece of documentation Kindler.

I have just one question regarding the SharePoint service accounts.  In a production environment, would they normally be domain accounts or would they remain local accounts - what would be best practice?

LeRoo United Kingdom

8/19/2008 10:46:39 AM #

Hi LeRoo,

In production, the service accounts will be domain accounts. The Admin and Config accounts (vpcSPAdmin, vpcSPConfig)need to be placed into the local machine's administrator's group.


Kindler Chase United States

11/20/2008 2:58:59 PM #

Thank you SO much for the great detailed steps for installing WSS 3.0 to a virtual server.  We spent almost a month trying to troubleshoot why the alerts were not working for WSS.  After a call to Microsoft they suggested that we try a new image on the virtual server and install WSS.  I found your website and we followed the steps you listed that pertained to our configuration and the alerts worked correctly right away when we installed to the new vm server.  We truly appreciate you taking the time to document the steps involved.


Deb K United States

11/20/2008 4:08:08 PM #

Hi Deb,

Glad to hear that your install/alerts are working now Smile  Thanks for the great feedback, too!


Kindler Chase United States

1/15/2009 9:10:12 AM #

Thank you so much for this detailed installation and configuration.  I have a few questions though (please don't laugh as I'm a near-novice on this one):

1.  How/Where does this installation differ from installing MOSS itself (I'm still not that clear on the difference between MOSS and WSS other than that MOSS works on WSS 3.0 platform and has server capabilities, hence is an extension of sorts of WSS 3.0)

2.  I want to set up a virtual training environment for MOSS than I can package and deploy on several laptops for training; is this possible with the configuration/installation you've highlighted?

3.  If I use the trial version of MOSS in this virtual environment, will it expire?

I'd appreciate your detailed response as soon as possible.  Thanks so much again for a detailed article!



1/29/2009 8:01:39 AM #

Hello, any thoughts on my questions above?

Someone please respond.



1/29/2009 8:47:50 AM #

Hi Jonas,

I think you may get a better response on the MS SharePoint forums. However, here's some things to get you going in the right direction:

1. MOSS vs. WSS:

2. Yes, the configuration I presented here is set up precisely for deployment on a development VM machine (laptop, desktop, server, whatever).

3. IIRC, the MOSS trial will expire after x days; including in a VM environment.



Kindler Chase

4/7/2009 9:52:46 AM #

Great guide to installing SharePoint, However when installing MOSS, whatever you do DO NOT choose WFE.  

If you do this then the indexer will NOT be installed and you will not be able to set up a Shared Services Provider.

In a MOSS environment, make sure you select the Complete install (not single box), otherwise you are looking at an uninstall and reinstall.


Mark Stokes United Kingdom

6/4/2009 12:45:04 AM #

Thanks Mate,

looking forward and waiting for the latest 2007 version deployment with the following technology:

Windows Server 2008 SP 2 Std x64
SQL Server 2008 SP1 Std x64
WSS 3.0 SP2 (another problematical installation)
MO SharePoint Server 2007 SP2 (probably the hardest one to install without error)

because I'm currently doing it now and I got stuck to the point that I had to rollback to all SP1 :-( and yet still faced some error.


Albert Widjaja Australia

6/9/2009 8:59:22 AM #

I just wanted to say thanks for the great post, I had an internship where my task was to build and evaluate a WSS site for the company on avirtual machine.  Everyone was suprised when i had it finished so fast, because I have never worked with SharePoint before.  I have to say though that your site is right on point.  i have also used it to install on a server 2008 machine with SQL 2008, and the basic install went the same.  There were some differences, but you had enough detail, that when it was not the exact same, I was able to find it with no problem.

James Claiborne United States

6/9/2009 4:22:00 PM #

Hey James,

Thanks for the compliment. And good to hear that you were able to get your project off the ground so fast Smile


Kindler Chase United States

7/7/2009 1:42:19 PM #


Congratulations, excellent tutorial for installing sharepoint server, usually with the installation of sql we must be careful


Eddier Galeano Colombia

Kindler Chase

Kindler Chase
This is SharePoint's world. I'm only living in it.

Your host, on the right, with my better half, Sadi.