Tutorial: Creating A MOSS Development Environment Part IV – Configuring MOSS

Ok, this is the last entry in this series of tutorials for setting up a MOSS development environment.  In the prior posts, we installed SQL Server, installed MOSS, installed VS.NET and some other supporting products, and in this post, we’ll configure MOSS.  The plan for this configuration is to go through the basic farm configuration with assigning roles to our server and setting up a web application.  As an additional task, we’ll extend the web application that we create and configure it for secure (https) access.  I’ve discovered that in most deployments, clients are looking for secure websites, so it makes sense to develop on one whenever possible.

Here are the links to the prior posts in this series:

Tutorial: Creating A MOSS Development Environment Part I – SQL Server Installation
Tutorial: Creating A MOSS Development Environment Part II – MOSS Installation
Tutorial: Creating A MOSS Development Environment Part III – VS.NET Installation


There are a few things that we’ll need to do as prework for completing this tutorial.  Create the following accounts:

WssSearchService (we’ll use this account for all of SharePoint’s search functionality)
SpsContentAccess (used for the content access account for indexing)
MainAppPool (we’ll use this for the app pool account)
(will be used for the SSP application pool)
MossWebApp01 (will be used for the main web application)

Configuring MOSS

Starting in MOSS Central Administration (Start > All Programs > Microsoft Office Server > SharePoint 3.0 Central Administration), click on the Operations tab on the top of the page.  Notice that on the left side of the window, it says Server Farm Configuration Not Complete in red.  Under the Topology and Services header, click on Services on server.

cfg01 cfg02

On this page you’ll notice that there are several services available to start, though many if not all of them will need further configuration.  We’ll start at the bottom of the list and work our way up.  Begin by clicking on the Start link next to the Windows SharePoint Services Search service.  On the next page, fill in the account information that we will be using for Search, the accounts that we created in the Prework section of this post.  In the Service Account area, use the WssSearchService account and for the Content Access Account area, use the SpsContentAccess account.  The rest of the settings can be left as the defaults.  In a production deployment, you would want to name your databases something more meaningful, but for the sake of our dev environment, the default database names will suffice.  At the bottom of this form, click on Start.

cfg03 cfg04

After clicking start, you should see the operation in progress screen.  Get used to it. 😉


We should arrive back at the services on server screen.  Note that the Windows SharePoint Services Help Search service in now showing a status of Started.  Next we’ll click Start next to the Office SharePoint Server Search service, and fill in the details on the following page to start that service.  Check both checkboxes for Use this server for indexing content, and Use this server for serving search queries.  Fill in a contact email address, since this is a dev environment, this address can be arbitrary.  Use the WssSearchService account, leave the other settings at their defaults and click Start.

cfg05 cfg06

We’ll return back to the Services on server page, with the Office SharePoint Server Search service showing a status of Started, and we’ll move right up the line to the Excel Calculation Services Start link.  After clicking that link, you should be returned to the same page with the service now running.

cfg07 cfg08

Next we’ll click the start button for the Document Conversions Load Balancer Service. Again, you should be returned to the same screen with the service started.  And finally, click the Start link for the Document Conversions Launcher Service.  On the following page, make sure to select your Load Balancer as shown in the image below, before clicking OK.  You should be returned to the services screen with all services started.  If you run into errors, they are typically from entering account information incorrectly.  Remember the format <domain><username>.

cfg09 cfg10

cfg11 cfg12

Moving right along, we’ll now click on the Operations tab on the top of the page, or the Operations breadcrumb located below that.  Back on the Operations page, under the topology and services section again, we’ll now click on Outgoing e-mail settings.  If you ever have difficulty finding a link on the admin pages, remember, CTRL-F for Find can save you time if you know what you’re looking for.  On the Outgoing E-Mail Settings page, fill in your SMTP server information, a ‘From’ address and a ‘Reply-to’ address.  I typically use something like donotreply@domain.org.  If you do not have an SMTP server, you can download and configure PostCast Server (google it) and utilize that.  It’s a free product or there is at least a free version. :)  After clicking OK you should be returned to the operations page again.

cfg13 cfg14

We will now configure the Shared Services Provider for the MOSS environment. Begin by clicking the link on the left titled Shared Services Administration.  On the next page click on the link for New SSP.

cfg15 cfg16

On the New Shared Services Provider page, click on the Create New Web Application link. On the Create New Web Application page, fill in the details necessary for your web application, or use the settings that I reference:

  • Create New IIS Website – selected
  • Description: sspDev.dev.local
  • Port: 80
  • Host Header: sspDev.dev.local
  • Path: <leave as default>
  • Authentication Provider: <leave as default> NTLM
  • Allow Anonymous: <default> No
  • Use Secure Socket Layers (SSL): <default> No
  • URL: http://sspdev.dev.local
  • Create New Application Pool: selected
  • Application Pool Name: sspdev.dev.local
  • Select a security account for this application pool : Configurable selected
  • User Name: <domain>mossSspAccount
  • Password: <password that you created>
  • Database Server: <default>
  • Database Name: WSS_Content_SSPDEV_01
  • Database Authentication: <default> Windows Authentication.

Click OK. And you’ll receive the operation in progress screen again, and will then be returned to the New Shared Services Provider page.

cfg16 cfg17

cfg18 opProg

Back at the New Shared Services Provider page, fill in the details as listed below:

SSP Name

– SSP Name: sspdev.dev.local

– Web Application: sspdev.dev.local

My Site Location Section:

– Web Application: sspdev.dev.local

– Relative URL: /MySites/

SSP Credentials:

– User Name: MossSspAccount

– Password: <your password>

SSP Database:

– Database Server: <your server name – default>

– Database Name: WSS_SSPDEV_DB_01

– Database Authentication: Windows Authentication

Search Database:

– Database Server: <your server name – default>

– Database Name: WSS_SSPDEV_SEARCHDB_01

– Database Authentication: Windows Authentication

Index Server: (leave all defaults)

SSL for Web Services: (leave default).

Click OK.  If you get a window warning you that the My Sites and SSP are on the same web application, click OK again.  After the operation in progress window appears and runs for a short time, the SSP should be created, which will finally remove the red warning on the side "Server Farm Configuration Not Complete".

cfg20 cfg21


Now we’ll create our web application that will host our development portal.  Click on the Application Management link on the top of the page.  Click on Create or extend Web Application under the SharePoint Web Application Management section.


On the Create or Extend Web Application page, click on Create a new Web Application.


On the Create New Web Application page, fill in the form as follows:

IIS Web Site:

– Create a new web site: selected

– – Description: dev01.dev.local

– Port: 80

– Host Header: dev01.dev.local

– Path: <leave as default path>

Security Configuration:

– Authentication Provider: <default> NTLM

– Allow Anonymous: <default> No

– Use Secure Socket Layers (SSL): <default> No

Load Balanced URL:

– URL: dev01.dev.local

Application Pool:

– Create new application pool: Selected

– – Application Pool Name: dev01.dev.local

– Select a security account for this application pool:

– – Configurable:

– – – User Name:  <domain>MossWebApp01

– – – Password:  <your password>

Reset Internet Information Services: Leave as defaults

Database Name and Authentication:

– Database Server Name: <default>

– Database Name: WSS_Content_DEV01_01

– Database Authentication:

– – Windows Authentication: Selected

Click OK.  After the Operation In Progress screens finishes, you’ll get the Application Created screen.  Click on the Create Site Collection link.


Confirm that your web application is correctly selected as: dev01.dev.local and fill out the form as follows:

Title and Description:

– Title: Development Portal 01

– Description: Development Portal Description

Web Site Address:

– URL: <default> /

Template Selection

– Collaboration Tab: Team Site. (You can create based on any template you want.)

Primary Site Collection Administrator:

– User name: <domain>administrator

Secondary Site Collection Administrator

– User name: <leave blank unless you have an account that you want to use>

Quota Template: <leave default>

Click OK.  After the operation in progress window completes its cycles, you should arrive at the Top-Level Site Successfully Created page.


Before doing anything else, open a run box either by using (window-key + R, or Start > Run).  In the run dialog box, type the following command: notepad.exe c:WindowsSystem32DriversEtcHosts.  Edit the Hosts file adding the following lines to the bottom:       sspdev.dev.local       dev01.dev.local

The space between the IP address and the name is a TAB.  This allows for the server to override dns lookups for the above domains and points them back to the local server via the loopback adapter (  If you have questions, please post them in comments and I’ll answer them as best I can.

cfg27 cfg28

After saving the Hosts file, you should be able to route to your new MOSS site by typing in dev01.dev.local into your address bar.

cfg29 cfg30

Well I hope you’ve learned something through these articles.  If not, thanks for reading them anyway, if so… :).  If there was anything that was unclear, please let me know and I’ll try to explain it better.  I have to admit that by the time this was all said and done, I was tired and trying to move through it quickly.



2 thoughts on “Tutorial: Creating A MOSS Development Environment Part IV – Configuring MOSS”

  1. thanx again!

    problem in the last moment, after the problemshooting i get the same result
    I have a DNS service running on my other server belong the AD., have assign the static ip address to the sharepoint server 50.6.
    the last attempt i have follows your suggestion even the names and database and the application.

    i get :

    You are not authorized to view this page
    You do not have permission to view this directory or page using the credentials that you supplied.

    Please try the following:

    •Contact the Web site administrator if you believe you should be able to view this directory or page.
    •Click the Refresh button to try again with different credentials.
    HTTP Error 401.1 – Unauthorized: Access is denied due to invalid credentials.
    Internet Information Services (IIS)

    what do i do wrong here? is i am loged in as Administrator.

  2. I apologize for my poor English, had a bit in a hurry and neglected to check the spelling. Ok, I’ve read a bit about HTTP Error 401.1, it is perhaps a authontication bug or something. I have followed your instructions and have double-checked almost everything, but without any result. I have tried to access the site through my host, and Ochs from my AD server with same results. I can access the central admin page.

    is there something I missed that check? please Help!

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s