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