Roux Visser’s SharePoint Blog

Summary

The following post outlines the data gathering requirements and installation procedure for the a SharePoint 2007 environment. It aims to achieve the following:

• List and group all required server hardware details
  
• Provide a central point of reference for server account configuration
  
• List all required databases and settings
  
• Specify and provide a checklist of software required on each server instance
  
• Request final information types (port number preferences, load balancing details etc.)
  

Solution Overview

Our example solution consists of two logical SharePoint farms configured over 7 physical servers. The farms can be summarised as follows:

MOSS Farm 1 – Production

Consists of two servers;

• one web and application server
  
• one database server
  

It will be used by users to access content internally (through the LAN).

MOSS Farm 2 – DMZ

Consists of three servers;

• one web and application server
  
• one database server
  

It will be used by users to access content externally (through the DMZ)

Server Details

Notes for table completion:

• Server name should be the machine name of the server, not the DNS name (although they may be the same)
  
• Administrator account should include the domain the account is a member of, i.e. mydomain\joe.bloggs
  
• Please include name, email and telephone of the alternate contact should administrator access to the servers be forbidden
  

 

Service Accounts

Notes for table completion:

• Account names should include the domain the account is a member of, i.e. mydomain\joe.bloggs
  
• If recording of passwords here is not acceptable for security reasons then please provide details of the password retrieval and reset procedure
  

Note: Policies for all service accounts should be set up to prevent logging on locally – further service accounts may be required for additional functionality, refer to previous posts.

Database Details

Notes for table completion:

• This table is for client reference. Netstore will require administrator access to the database in order to create and properly configure each database.
  

 

Server Software Checklist

Server roles

• File Server
  
• Application Server
  

Software pre-requisites

• .Net 3.5 (Confirmed as being installed)
  

SharePoint Software

The install order of the SharePoint packages MUST follow the order below.

Production

1. Perform base install (Say no to running configuration wizard)
   
2. Perform SP1 install (Say no to running configuration wizard)
   
3. Perform Infrastructure update (Say no to running configuration wizard)
   
4. Run SharePoint Products and Technologies configuration wizard
   

DMZ

1. Perform base install (Say no to running configuration wizard)
    
   
2. Perform SP1 install (Say no to running configuration wizard)
   
3. Perform Infrastructure update (Say no to running configuration wizard)
   

Run SharePoint Products and Technologies configuration wizard

 

Further Required Details
 

1. What type and version of email server is in use?
   
2. How is outbound email handled?
   
3. Outbound SharePoint email requires an SMTP server (same SMTP server across 3 farms). Please provide the URL of the SMTP server:
   
4. Can we define the port numbers for other SharePoint sites (Central Admin, extended sites etc)?
   
5. If the answer to question 6 is NO, please define the port numbers for the Central Administration and MySites websites:
   
6. Does the client prefer the use of host headers or port numbers?
   
7. How is load balancing being handled on the Intranet and Extranet Web Front End servers?
   
8. Specify the load balanced URL for the Intranet and Extranet server farms:
   

    

Install Guidelines

All of the databases required by Office SharePoint Server 2007 use the Latin1_General_CI_AS_KS_WS collation. All of the databases require that the Setup user account be assigned to them as the database owner (dbo, or db_owner).

Add a environment path in for the 12 hive on all the servers

Production

• Install Office SharePoint Server 2007 enterprise edition on sge-tukcw-sps01. Do not run the “SharePoint Products and Technologies Configuration Wizard”.
  
• Install WSS 3.0 SP1 on the SharePoint Server. Do not run the “SharePoint Products and Technologies Configuration Wizard”
  
• Install MOSS 2007 SP1 on the SharePoint Server. Do not run the “SharePoint Products and Technologies Configuration Wizard”
  
• Install WSS 3.0 Infrastructure update on the SharePoint Server. Do not run the “SharePoint Products and Technologies Configuration Wizard”
  
• Install MOSS 2007 Infrastructure update on the SharePoint Server. Do not run the “SharePoint Products and Technologies Configuration Wizard”
  
• Run the following command on the SharePoint Server. This command creates the configuration database for the farm.
  

PSCONFIG -cmd configdb -create -server <<domain\sqlinstance>> -database Config_Prod -user domain\spfarmsvc -password <<password>> -admincontentdatabase Content_ProdConfigAdmin

• Run the “SharePoint Products and Technologies Configuration Wizard” on the SharePoint Server.
  
• Run the following command on the SharePoint Server. This command starts the WSS 3.0 search service.
  

STSADM -o spsearch -action start -farmserviceaccount domain\spfarmsvc -farmservicepassword <<password>> -farmcontentaccessaccount domain\spcontacc -farmcontentaccesspassword <<password>> -databaseserver <<databaseserver\sqlinstance>> -databasename Search_ProdWSS

• Run the following command on the SharePoint Server. This command started the MOSS 2007 search service in dual role mode.
  

STSADM -o osearch -action start -role Index -farmcontactemail <<FarmContactEmail>> -farmserviceaccount domain\spfarmsvc -farmservicepassword <<password>>

• Run the following command on the SharePoint Server. This command creates the web application for the Production My Sites web application.
  

STSADM -o extendvs -url http://mysites -sethostheader -donotcreatesite -exclusivelyusentlm -databaseserver <<databaseserver\sqlinstance>> -databasename Content_ProdMySites -apidtype configurableid -description “SharePoint - MySites” -apidname SharePointMySitesAppPool -apidlogin domain\spsspsvc -apidpwd <<password>>

• Run the following command on the SharePoint Server. This command creates the web application for the Production SSP administration web application.
  

STSADM -o extendvs -url http://sspadmin -sethostheader -donotcreatesite -exclusivelyusentlm -databaseserver <<databaseserver\sqlinstance >> -databasename Content_ProdSSPAdmin -apidtype configurableid -description “SharePoint - SSPAdmin” -apidname SharePointSSPAdminAppPool -apidlogin moss\spsspsvc -apidpwd <<password>>

• Run the following command on the SharePoint Server. This command creates the web application for the Production Portal web application.
  

STSADM -o extendvs -url http://sharepoint -sethostheader -donotcreatesite -exclusivelyusentlm -databaseserver <<databaseserver\sqlinstance>> -databasename Content_ProdPortal -apidtype configurableid -description “SharePoint - Portal” -apidname SharepointPortalAppPool -apidlogin moss\spprtappsvc -apidpwd <<password>>

• Run the following command on the SharePoint Server. This command creates the SSP for the PCT environment.
  

stsadm -o createssp -title “PCT SSP” -url http://pctsspadmin/ssp/admin -mysiteurl http://pctmysites -ssplogin <UserName> -ssppassword <password> -indexserver <<SERVER>> -indexlocation <IndexFilePath> -sspdatabaseserver <DatabaseServer> -sspdatabasename Content_SSPAdmin_PCT -searchdatabaseserver <DatabaseServer> -searchdatabasename SSPSearch_PCT

After you have deployed the SharePoint Server, there are some other additional settings which you need to configure. You should perform these tasks to take full advantage of the SharePoint 2007 administrative Features: 

• Email Settings:
  • Incoming:
    

Configuring server for incoming emails will enable you to get advantage of the following SPS 2007 features:

• SharePoint sites can accept and archive incoming e-mail.
  
• SharePoint sites can archive e-mail discussions as they happen, save e-mailed documents, and show e-mailed meetings on site calendars.
  
• In addition, configure the SharePoint Directory Management Service for e-mail distribution list creation and management.
  
• Outgoing
  

Configure Outgoing SMTP Email server to enable SPS 2007 for sending Notifications and alerts to the site users and administrators. You can configure “From” and “Reply to” email addresses for outgoing emails.

• Create SharePoint sites: Create more SharePoint sites and Web applications if your site design requires multiple sites or multiple Web applications.
  
• Diagnostic logging settingsTo get yourself helped in troubleshooting, configure various logging and diagnostics settings including trace logs, event messages, user-mode error messages, and Customer Experience Improvement Program events.
  
• Configure antivirus protection settingsConfigure Antivirus Settings for Server to enable the virus scanning for document upload and downloads, also configure virus scanning timeout and execution threads on the server for antivirus. A SharePoint Server 2007 compatible Antivirus program is required for this.
  
• You can use the following procedure to configure optional administrative settings using SharePoint Central Administration.
  

Configure administrative settings using SharePoint Central Administration

• Click Start, point to All Programs, point to Administrative Tools, and then click SharePoint 3.0 Central Administration.
  
• On the SharePoint Central Administration home page, under Administrative Tasks, click the administrative task you want to perform.
  
• On the Administrative Tasks page, next to Action, click the task.
  

If you installed and configured Office SharePoint Server 2007 on a single front-end server, and a user browses to your server, the server will render the content that is in your Web application. However, if you added subsequent front-end servers to your server farm, the newly-added servers will not have alternate access mappings configured to your Web application. To map newly-added front-end servers to your existing Web application, you need to configure alternate access mappings.

Before you configure alternate access mappings, install and configure Office SharePoint Server 2007 on all of the front-end servers that you want to add to your server farm, and make sure that the servers are joined to your server farm. See “Run Windows SharePoint Services Setup” and “Run the SharePoint Products and Technologies Configuration Wizard” for information about installing and configuring Office SharePoint Server 2007. 

To configure alternate access mappings

1. On the SharePoint Central Administration home page, click the Operations tab.
   
2. On the Operations page, in the Global Configuration section, click Alternate access mappings.
   
3. In Alternate Access Mapping Collection, click Change Alternate Access Mapping Collection.
   
4. In the Select an Alternate Access Mapping Collection dialog box, click the Web application that you want to modify. If you have created only one Web application, and you specified port 80 for the Web application, the Web application should be listed as SharePoint (80).
   
5. Click Edit Outbound URLs, and verify that your Web application is listed in the Default zone for outbound URLs. The outbound URL is the URL that you want users to use to access your Web application.
   

Note: If you have a load-balanced configuration with a host name, add the host name to the Outbound URL for the Default zone.

1. Click Save.
   

• Click Add Incoming URLs.
  
• On the Add Incoming URLs page, in New default zone URL protocol, host and port type the URL for the server that you want to map to your Web application. Typically, this is http://servername:portnumber.
  Note: If you have a load-balanced configuration, you should add the server name of each of your front-end Web servers to the list of internal URLs. This will allow each of your Web servers to reach the content in your common Web application. Also, make sure the zone you selected for the incoming URL matches the zone of the outbound URL for the load balancer. You can have multiple incoming URLs associated with a single outbound URL.
  

1. In Zone, make sure that Default is selected.
   

• Click Save.
  

To take full advantage of the business intelligence capabilities of Office SharePoint Server 2007 you need to start and configure Excel Calculation Services. Instructions for doing this are provided below.

Note: Excel Services is only available if you use a product key that activates the Enterprise version of Office SharePoint Server 2007. 

Start and configure Excel Calculation Services

1. On the SharePoint Central Administration home page, click Administrative Tasks.
   
2. On the Administrative Tasks page, click Add Excel Services Trusted Locations.
   
3. On the Add Excel Services Trusted Locations page, in Action, click Add Excel Services Trusted Locations.
   
4. On the Excel Services Trusted File Locations page, click Add Trusted File Location.
   
5. In the Location section, in Address, type the address of the trusted file location. It is recommended that the trusted file location be an Office SharePoint Server 2007 site, but you can also specify universal naming convention (UNC) paths or HTTP Web sites.
   
6. In Location Type, click Windows SharePoint Services if you specified an Office SharePoint Server 2007 site, click UNC if you specified a UNC path, or click HTTP if you specified an HTTP Web site.
   
7. In the External Data section, in Allow External Data, select the trust level for external data sources that you want to enable by doing one of the following:
   

• Click None to prevent Excel Calculation Services from processing connections to any external data connection.
  
• Click Trusted data connection libraries only to prevent Excel Calculation Services from processing connections to external data sources that are embedded within workbooks. This setting permits Excel Calculation Services to process links to trusted data connection libraries.
  
• Click Trusted data connection libraries and embedded to permit Excel Calculation Services to process direct connections to external data sources that are embedded within workbooks. This setting also permits Excel Calculation Services to process links to trusted data connection libraries.
  

To configure Single-Sing On follow these steps:

• Create a new domain service account for running SSO service.
  
• Change SSO service’s Identity to the new service account form Services
  console.
  
• Add SSO service account as a farm administrator by using “Update farm
  administrator’s group” link from share point central admin.
  
• Right click internet explorer shortcut select “Run As” provide the credentials for the service account to run it. Open share point central admin using this IE window.
  
• Setup SSO using this IE window.
  
• Remove SSO service account from farm administrator group.
  

Common Issues:

You cannot configure single sign-on settings for a server in your server farm deployment of Microsoft Office SharePoint Portal Server 2003. You specify single sign-on settings for the server on the Manage Server Settings for Single Sign-On page of SharePoint Portal Server Central Administration. After you do this, when you click OK, you receive the following error message:

You do not have the rights to perform this operation.

To resolve this issue, make sure that the user account that you configure the Microsoft Single Sign-On Service to log on as meets the following requirements:

•	The user account is the same account that is configured as the single sign-on administrator account, or the user account is a member of the group account that is the single sign-on administrator account.
•	The user account is a member of the STS_WPG local group on all servers that are running SharePoint Portal Server 2003 in the server farm.
•	The user account is a member of the SPS_WPG local group on all servers that are running SharePoint Portal Server 2003 in the server farm.
•	The user account is a member of the public database role on the configuration database.
•	The user account is a member of the serveradmin fixed server role in the instance of Microsoft SQL Server where the single sign-on database is located.

Note In a single-server deployment of SharePoint Portal Server 2003, if the Microsoft Single Sign-On Service runs under an account that is a member of the local Administrators group, the user account does not have to be a member of either of the following roles:

•	The public database role
•	The serveradmin fixed server role

However, we recommend that you do not configure the Microsoft Single Sign-On Service to run as a member of the local Administrators group.

Note Other Issues include

• ISS Service Account Settings to be configured manually in ISS.
  

  • Bug Error resulting in the need for Microsoft Registry Hack (due to Windows Installer 3.1. being installed)

1. On the Create Site Collection page, in the Title and Description section, in Title, enter a title for the new site.
   
2. In Description, enter a description of the site collection.
   
3. In the Web Site Address section, click Create site at this URL, and in URL path click (root).
   It is most common to create a site collection at the root; however, you can create a site collection at a specific URL path.
   

4. In the Primary Site Collection Administrator section, in User name, type the user name of the site collection administrator. This can be the same user account that you specified as the Office SharePoint Server 2007 service account, but you should follow the principle of least privilege and use a user account that does not have administrative privileges or rights on your front-end or back-end servers.
   

• In the Quota Template section, select a predefined quota template to limit resources used for this site collection.
  Note: You can also select No Quota, thereby allowing this site collection to use any available resources.
  

1. In the Template Selection section, click the Publishing tab, and then click Corporate Intranet Site.
   

• Click OK to create the site collection with the attributes you specified.  Upon successful completion, a Top-Level Site Successfully Created page appears.
  
• Click OK to return to the SharePoint Central Administration home page, or click the http://ComputerName link to go to your new SharePoint site home page.
  

Create a Web application for your SharePoint site

On the SharePoint Central Administration home page, click the Application Management tab on the top navigation bar.

1. In the SharePoint Web Application Management section, click Create or extend Web application.
   
2. On the Create or Extend Web Application page, click Create a new Web Application.
   
3. On the Create New Web Application page, in the IIS Web Site section, click Create a new IIS web site, and change the port setting to port 80. This will allow you to access your site by typing http://ServerName. If you use a nonstandard port number you will have to include the port number in the URL to access your site (for example, http://ServerName:port).
   
4. In the Security Configuration section, under Authentication provider, select the appropriate option for your environment, and do not modify any other settings in this section.
   

Note: By default, the authentication provider is set to NTLM.

1. In the Load Balanced URL section, do not modify the default settings.
   
2. In the Application Pool section, select Create new application pool, and use the default settings for the application pool name.
   
3. Click Configurable, and in User name and Password, type the user name and password for the user account under which you want the application pool to run. The user account does not have to be a member of any particular security group. It is recommended that you use the principle of least privilege and select a unique user account that does not have administrative rights on your front-end servers or on your back-end database servers. You can use the user account that you specified as the Office SharePoint Server 2007 service account; however, if that user account is a member of a security group that has administrative rights on your front-end servers or your back-end database servers, you will not be following the principle of least privilege. The user name must be in the format DOMAIN\username.
   
4. In the Database Name and Authentication section, verify the database information and ensure Windows Authentication (recommended)is selected.
   
5. In the Search Server section, do not modify the default settings.
   
6. Click OK.
   
7. On the Application Created page, which appears after successful creation of the Web application, click Create a new Windows SharePoint Services site collection.
   

Create and configure a site

After you configure services in your server farm, you can create a Web application and a site collection. You should create the Web application on the first server on which you installed Office SharePoint Server 2007 (in other words, the same server that is running the SharePoint Central Administration service).  

 

All installation files will be in C:\Build\Packages\MOSS

1. Create C:\Build\Packages\MOSS folder structure

  

2. Copy Microsoft SharePoint Server 2007 installation files in C:\Build\Packages\MOSS\Server12

  

3. Copy SQL Server files to C:\Build\Packages\MOSS\SQLExpress

  

4. Create C:\Build\Packages\MOSS\Scripts

  

5. Copy Config.xml from C:\Build\Packages\MOSS\Server12\Files\SetupSilent\ to C:\Build\Packages\MOSS\Server12\

  

6. Edit this config.xml and replace with your MOSS product key. Leave the rest as is. 

 Then run C:\Build\Packages\MOSS\Server12\setup.exe /config “C:\Build\Packages\MOSS\Server12\config.xml” 

This post was expanded on from the following source; alpesh.nakars.com/blog/script-to-install-moss-with-sql-express/  

Once SharePoint has been installed it is time to configure the services and settings for your SharePoint farm, the following post will outline Microsoft Best Practices for doing so.

 Notes

• If you are prompted for your user name and password, you might need to add the SharePoint Central Administration site to the list of trusted sites and configure user authentication settings in Internet Explorer. Instructions for configuring these settings are provided in the next set of steps.
  
• If you see a proxy server error message, you might need to configure your proxy server settings so that local addresses bypass the proxy server. Instructions for configuring this setting are provided later in this section.
  

Add the SharePoint Central Administration site to the list of trusted sites

1. In Internet Explorer, on the Tools menu, click Internet Options.
   
2. On the Security tab, in the Select a Web content zone to specify its security settings box, click Trusted Sites, and then click Sites.
   
3. Clear the Require server verification (https:) for all sites in this zone check box.
   
4. In the Add this Web site to the zone box, type the URL for the SharePoint Central Administration site, and then click Add.
   
5. Select the Require server verification (https:) for all sites in this zone check box.
   
6. Click Close to close the Trusted Sites dialog box.
   
7. Click OK to close the Internet Options dialog box.
   

Configure user authentication settings for trusted sites

1. In Internet Explorer, on the Tools menu, click Internet Options.
   
2. On the Security tab, in the Select a Web content zone to specify its security settings box, click Trusted sites, and then click Custom Level.
   
3. In the Settings list box, under User Authentication, click Automatic logon with current username and password.
   
4. Click OK twice.
   

Note: If you do not want to add the SharePoint Central Administration site to the list of trusted sites, but you do not want to be prompted for your user name and password every time you access the SharePoint Central Administration site, you can instead add the SharePoint Central Administration site to the Local intranet zone. If you do this, you must enable the Automatic logon only in Intranet zone user authentication setting instead of the Automatic logon with current username and password user authentication setting. 

Configure 2007 Office SharePoint Server services

After you have installed and configured Office SharePoint Server 2007 on all of your front-end servers, you must configure Office SharePoint Server 2007 services. The services you need to configure depends on your server topology and the server roles you deploy. Use the following guidelines to determine which services you need to configure in your server farm.

• Search and indexing servers You must start and configure the Office SharePoint Server Search service on at least one of your front-end servers. This service provides search and indexing services. You can start and configure this service on any type of server, including a server that is acting as an application server and provides only Office SharePoint Server 2007 services, a server that is acting as both an application server and a Web server and provides both Office SharePoint Server 2007 services and Web services, or a server that is acting as a Web server and provides only Web services.
  
• Web servers The Web server role is implemented by IIS and the Windows SharePoint Services Web Application service. The Windows SharePoint Services Web Application service must be running on any server that acts as a Web server and renders Web content. This service is started by default on servers that you set up using the Web Front End option during Setup. If you set up a server using the Complete option during Setup, and you want that server to act as a Web server and render Web content, then you must start the Windows SharePoint Services Web Application service on that server.
  

In addition to configuring services on your front-end servers, you must create the Shared Services Provider (SSP). The SSP makes it possible to share the Office SharePoint Server 2007 services across your server farm. You must create the SSP before you can use it in a farm environment; Office SharePoint Server 2007 does not create the SSP by default in a farm environment.

The following procedures step you through the process of configuring Office SharePoint Server 2007 services, creating a Web application for the SSP, creating the SSP, and configuring indexing settings.

 Start and configure the Search service

1. On the SharePoint Central Administration home page, click the Operations tab on the top navigation bar.
   
2. On the Operations page, in Topology and Services, click Servers in farm.
   
3. On the Servers in Farm page, click the server on which you want to configure the search service.
   
4. Click Start next to Office SharePoint Server Search.
   
5. On the Office SharePoint Server Search Settings page, in the Query and Indexing section, make sure that the Use this server for indexing content and Use this server for serving search queries check boxes are selected.
   
6. In the Default Catalog Location section, type a path to a physical folder to store the index files, or use the default location that is specified.
   
7. In the Contact E-Mail Address section, specify a valid e-mail address.
   
8. In the Service Account section, click Configurable, and in User name and Password, type the user name and password for the user account under which you want the Search service to run. The user account must be a member of the Administrators group on the computer that is running the Search service. If you want to use the principle of least privilege and select a unique user account that does not have administrative rights on your front-end servers or on your back-end database servers, see the Known Issues/Readme for Office SharePoint Server 2007 Beta 2. The user name must be in the format DOMAIN\username.
   
9. In the Web Front End And Crawling section, do one of the following:
   

• If you are configuring the search service on a server that provides Web services and renders Web content, click No dedicated Web front-end computer for crawling
  
• If you are configuring the search service on a server that is a standalone search server that does not provide Web services and render Web content, click Use a dedicated web front end computer for crawling, and then, in Select a web front end computer, click the computer you want to use for crawling.
  

1. Click Start.
   

Start the Windows SharePoint Services Web Application service

You must start the Windows SharePoint Services Web Application service on every computer that you want to act as a Web server and was set up using the Complete option during Setup. This service is started by default on servers that were set up using the Web Front End option. To enhance security, you can leave this service turned off on application servers that do not provide Web content to client computers. Also, you do not need to turn this service on to use SharePoint Central Administration on a server.

1. On the SharePoint Central Administration home page, click the Operations tab on the top navigation bar.
   
2. On the Operations page, in Topology and Services, click Servers in farm.
   
3. On the Servers in Farm page, click the server on which you want to start the Windows SharePoint Services Web Application service.
   
4. Click Start next to Window SharePoint Services Web Application.
   

Create the Shared Services Provider

1. On the SharePoint Central Administration home page, click the Application Management tab on the top navigation bar.
   
2. On the Application Management page, in the Office SharePoint Server Shared Services section, click Create or configure this farm’s shared services.
   
3. On the Manage this Farm’s Shared Services page, click New SSP.
   

Important: If you have not created a Web application for the SSP administration site, you need to create one before you create the SSP. If you have already created a Web application for the SSP administration site, skip to step 14.

On the New Shared Services Provider page, click Create a new Web application.

• On the Create New Web Application page, in the IIS Web Site section, click Create a new IIS web site, and do not modify the default settings in this section.
  
• In the Security Configuration section, under Authentication provider, select the appropriate option for your environment, and do not modify the default settings in the remainder of this section.
  
• In the Load Balanced URL section, do not modify the default settings.
  
• In the Application Pool section, click Create new application pool.
  
• In Application pool name, enter the name of your application pool or use the default name.
  
• Click Configurable, and in User name and Password, type the user name and password for the user account under which you want the application pool to run. The user account does not have to be a member of any particular security group. It is recommended that you use the principle of least privilege and select a unique user account that does not have administrative rights on your front-end servers or on your back-end database servers. You can use the user account that you specified as the Office SharePoint Server 2007 service account; however, if that user account is a member of a security group that has administrative rights on your front-end servers or your back-end database servers, you will not be following the principle of least privilege. The user name must be in the format DOMAIN\username.
  
• In the Database Name and Authentication section, verify the database information and make sure that Windows Authentication (recommended)is selected.
  
• In the Search Server section, do not modify the default settings.
  

Click OK. Upon successful creation of the Web application, the New Shared Services Provider page appears.
NOTE: If the SharedServices Provider created successfully but can not be displayed in your web browser then follow these steps to correct this issue:

This issue happens when creating all your sites in the same web application which means they use the same port, these sites are:

• Shared Service Provider Administration Site (Recommended to be called ‘SSPAdmin’)
  
• My Site Host (Recommended to be called ‘MySite’)
  
• The Main Intranet (or ‘Portal’) Site (Recommended to be called ‘Intranet’)
  

It is much simpler if all of these sites are on port 80 in IIS; this means that you do not have to remember to enter the ports all of the time. However having all three sites on port 80 means that each needs their own Host Header (required by IIS to differentiate between sites on the same port). The simplest way to do this is to create new ‘Host (A)’ records in DNS for each of your three sites. These should point to the IP address of your server; to do this follows these steps:

• Open the DNS Management tool from Administration Tools on your domain controller
  
• Navigate to your DNS zone
  
• Create new ‘Host (A)’ record
  
• Enter the Host header (i.e. ‘SSPAdmin’, ‘MySite’ or ‘Intranet’) for the site and the IP address of your server
  
• Click ‘Add Host’ and repeat for each of the three sites
  

Now the DNS entries are configured, we can continue.

• In the SSP Name section, in Web Application, select the Web application that you created for the SSP, and do not modify any of the default settings in this section.
  
• In the My Site Location section, do not modify any of the default settings.
  
• In the SSP Service Credentials section, in User name and Password, type the user name and password for the user account under which you want the SSP to run. The user account does not have to be a member of any particular security group. It is recommended that you use the principle of least privilege and select a unique user account that does not have administrative rights on your front-end servers or on your back-end database servers. You can use the user account that you specified as the Office SharePoint Server 2007 service account; however, if that user account is a member of a security group that has administrative rights on your front-end servers or your back-end database servers, you will not be following the principle of least privilege. The user name must be in the format DOMAIN\username.
  
• In the SSP Database section, you can either accept the default settings (recommended), or specify your own settings for the database server, the database name, or the SQL authentication credentials.
  
• In the Search Database section, you can either accept the default settings (recommended), or specify your own settings for the search database server, the database name, or the SQL Server authentication credentials.
  
• In the Index Server section, in Index Server, click the server on which you configured the Search service.
  

  
  Note: If there is no index server listed in the Index Server section, then no server in your farm has been assigned the index server role. To assign the index server role to a server in your farm, follow the instructions in the “Configure the Search service” section earlier in this topic.
  

1. In the SSL for Web Services section, click No.
   

• Click OK. Upon successful creation of the SSP, the Success page appears.
  
• On the Success page, click OK to return to the Manage this Farm’s Core Services page.
  

Configure indexing settings

1. On the SharePoint Central Administration home page, click the Application Management tab on the navigation bar.
   
2. On the Application Management page, in the Office SharePoint Server Shared Services section, click Create or configure this farm’s shared services.
   
3. On the Manage this Farm’s Shared Services page, click SharedServices1.
   
4. On the Shared Services Administration page, in Search, click Search Settings.
   
5. On the Configure Search Settings page, in the Crawl Settings section, click Default content access account.
   
6. In the Default content access account section, in Account, Password, and Confirm Password, type the user name and password for the user account that you want to use to crawl content on your sites. This account must be a domain user account. It is recommended that you use the principle of least privilege and select a unique user account that cannot modify content and does not have administrative rights on your front-end servers or on your back-end database servers. You can use the user account that you specified as the Office SharePoint Server 2007 service account; however, if that user account is a member of a security group that has administrative rights on your front-end servers or your back-end database servers, you will not be following the principle of least privilege. The user account that you specify will be added to the Web application Full Read policy for your farm. The user name must be in the format DOMAIN\username.
   
7. Click OK.
   
8. In the Crawl Settings section, click Content sources.
   
9. On the Manage Content Sources page, click Local Office SharePoint Server sites.
   
10. On the Edit Content Source page, in the Crawl Schedules section, under Full Crawl, click Create schedule.
    
11. In the Manage Schedules dialog box, configure schedule settings for full crawls of your content, and then click OK.
    
12. In the Crawl Schedules section, under Incremental Crawl, click Create schedule.
    
13. In the Manage Schedules dialog box, configure schedule settings for incremental crawls of your content, and then click OK.
    
14. In the Start Full Crawl section, select the Start full crawl of this content source check box, and then click OK.
    

This section outlines the steps taken to install SharePoint 2007 on a pre-prepared Windows 2003 Server.     

Run the Officeserver.exe

• Run Officeserver.exe, on one of your Web server computers.
  
• On the Enter your Product Key page, enter your product key and click Continue.
  

1. On the Choose the installation you want page, click Advanced.
   

1. On the Server Type tab, do one of the following:
   

If you are setting up a computer that will act as an application server, or a Web server and an application server, click Complete, and then click Install Now.  

If you are setting up a computer that will act as a Web server only, click Web Front End, and then click Install Now.

1. When Setup finishes, a dialog box appears telling you that you must complete the configuration of your server. Make sure that the Run the SharePoint Products and Technologies Configuration Wizard now check box is selected.
   
2. Click Close to start the configuration wizard. Instructions for completing the wizard are provided in the next set of steps.
   

SharePoint Products and Technologies Configuration

After Setup finishes, you can use the SharePoint Products and Technologies Configuration Wizard to configure Office SharePoint Server 2007. The SharePoint Products and Technologies Configuration Wizard automates several configuration tasks, including: installing and configuring the configuration database, installing Office SharePoint Server 2007 services, and installing SharePoint Central Administration. Use the following instructions to run the SharePoint Products and Technologies Configuration Wizard.

1. On the Welcome to SharePoint Products and Technologies page, click Next.
   

1. Click Yes in the warning dialog box that appears notifying you that some services might need to be restarted during configuration.
   
2. On the Connect to a server farm page, do one of the following:
   

If this is the first front-end server that you are configuring in your server farm, click No, I want to create a new server farm, and then click Next.

 If you have already configured your first server in your server farm, click Yes, I want to connect to an existing server farm, and then click Next.

 

1. On the Specify Configuration Database Settings dialog box, in Database server, type the name of the computer that is running SQL Server.
   
2. Do one of the following:
   

If this is the first server that you are configuring in your server farm, type a name for your configuration database in Database name, or use the default database name.  

If you have already configured the first server in your server farm, click Retrieve Database Names, and in Database name click the database name that you created when you configured the first server in your server farm. The default name is SharePoint_Config.

1. In User name , type the user name of the account used to connect to the computer running SQL Server (be sure to type the user name in the format DOMAIN\username).
   

   Important: This account is the Office SharePoint Server 2007 service account under which several Office SharePoint Server 2007 services run. The user account that you specify as the Office SharePoint Server 2007 service account must be a domain user account, but it does not need to be a member of any specific security group on your front-end servers or your back-end database servers. However, the user account that you specify must be a member of the following two SQL Server security roles on your back-end database servers: Database Creator and Security Administrator. It is recommended that you follow the principle of least privilege and specify a user account that is not a member of the Administrators group as your Office SharePoint Server 2007 service account.
   

2. In Password, type the user’s password, and click Next.
   

• Skip the next step if you have already configured first server in your server farm.
  
• On the Configure SharePoint Central Administration Web Application page, select the Specify port number check box and type a port number if you want the SharePoint Central Administration Web application to use a specific port, or leave the Specify port number check box unchecked if you do not care which port number the SharePoint Central Administration Web App users.
  

1. On the Configure SharePoint Central Administration Web Application dialog box, select NTLM authentication (the default) or Kerberos (depending on the client’s requirements), click Next.
   
2. On the Completing the SharePoint Products and Technologies Wizard page, click Next.
   
3. On the Configuration Successful page, click Finish.