Installation

Rate this item
(0 votes)

The recommended Windows environment which offers the best performance for SharePoint is to have 64-bit servers. Such an environment provides significantly larger address space than 32-bit one; more room for SharePoint assemblies, CLR/Native APIs, Network Stack, IIS/ASP.NET and other components hosted in their respective tiers.

Windows Server 2008 and SQL Server

Use Windows 2008 with the following roles: Web Server role, Windows Internal Database, and the Microsoft .NET Framework 3.5

Take into account that Windows 2008 Web Edition is not supported for farm roles, except WFE boxes, due to restrictions of non-Web editions of SQL Server on Windows 2008 Web Edition. The release of “SQL Server 2008 Web Edition” extends usage of Windows 2008 Web Edition for SharePoint. Refer to licence regulations and SQL Server 2008 Web Edition info for more details: http://tinyurl.com/b8nype

SharePoint installation supports SQL 2005 and 2008 Servers. A few advantages of SQL 2008 over SQL 2005 are in performance, encryption, clustering, mirroring and etc. Moreover, it provides updated SharePoint Web Parts for Reporting Services and KPI. Detailed information about SQL 2008 and SharePoint can be found in the following post http://tinyurl.com/cdkcyw.

Do not install SharePoint on Domain Controller box in virtualized environment. DC role of Windows 2008 limits performance of hard drive by turning off caching to provide AD consistency. Any installations on virtualized DC might not work properly.

SharePoint installs only on the top of SQL Server; it does not operate with others databases. However, SharePoint can be used with the third party databases, for example Oracle, to store List content and to provide other services such as Authorization or Personalization.

User SQL Aliases

When provisioning a new SharePoint farm, it is highly recommended to use an alias to connect to the Microsoft SQL Server, as this provides for greater flexibility to move the SharePoint databases to a new server. For example, if starting with a smaller, virtual SQL database server and then scaling out to a larger physical cluster in the future, the migration process can be simplified by using an alias during the installation.

Install Microsoft Office 2007

Install Office 2007 on Application Servers with the following applications:

-Word and Excel for documents in Document Library

-PowerPoint for Slides in Document Library

-Access for “Edit in Datasheet” support in Document Library

Install Office SharePoint Designer(SPD), which is necessary for development environment. SPD releases as separate installation.

Install all Windows Updates

Make sure that all servers have the latest service packs and updates for Windows, SQL and Office prior installing SharePoint.

Install SharePoint

Install SharePoint across all servers in farm. Start with WSS/MOSS package with integrated SP1. Using WSS/MOSS installation without SP1 and applying SP1 later is error-prone approach.

Follow the next order of installation:

·Application server where Central Administration site will be hosted

·All front-end Web servers

·The index server (if using a separate server for search queries and indexing)

·The query servers, if separate from the WFE servers

·Other application servers (optional)

Consider using scripts to automate SharePoint installation and configuration for the large farm deployment. SharePoint provides several configuration files and console commands that will do all deployment un-attendant. This will speed up installation and brings consistency of building and rebuilding servers in farm.

There are three commands to automate SharePoint installation:

·SharePoint Setup.exe + Config.xml - to script the setup questions

·PSconfig.exe - to script configuration wizard

·STSADM.exe – to script central admin UI for creating web apps and site collections

Alternative solution is to use already preconfigured Power Shell scripts. “SharePoint Deploy” tool on CodePlex provides the configured scripts for the standard installation, which can be adapted to any environments.

Refer to the following documentation for details about unattended installation http://go.microsoft.com/fwlink/?LinkID=135694&clcid=0x409, and info about installations scripting http://technet.microsoft.com/en-us/library/dd335964.aspx.

 

Take into account that uninstalling of SharePoint is not supported. It does not uninstall correctly and additional steps required to clean remaining files and database (http://nehasinha.wordpress.com/2008/02/01/uninstalling-moss-2007-manually). Therefore, just reinstall everything from the scratch if something went wrong, including Windows Server. In this scenario, using virtualization and snapshots feature save a lot of time.

Detailed information about SharePoint installation guidelines is published on TechNet http://go.microsoft.com/fwlink/?LinkId=106632

Check Office Web Service availability

Sometimes, SSL protocol of Office SharePoint Web Service is broken.To test it, go to IIS Management Console and open SharePoint Office Web Service in browser via https://. If it doesn’t work – don’t process further till fix it. This is very critical stuff, because, SharePoint roles cannot be assigned on other services in farm. (I’ve seen such issues across several clients, when you can't use other boxes in farm and only Application boxes are available for Index and Query roles, because SSL was broken).

No known fix at this moment, except reinstalling SharePoint

Install SharePoint updates

Install all SharePoint updates (Infrastructure Updates and/or Cumulative Patches) after farm is deployed. Check the release notes of the latest cumulative patch if it includes all previous patches and updates. Sometimes you need to install previous updates manually. Cumulative patch releases each 2 months. Follow the official documentation “Deploy software updates for Office SharePoint Server 2007” for the processes of how to deploy infrastructure update (WSS Upgrade needs to be installed first and only then MOSS upgrade)

Be careful with SharePoint hot fixes

There are several hot fixes, for example “Coreserver.msp” package, which are released after Cumulative Patch. However, be careful with these fixes, because they are temporary solution before the next official update, and they are not properly tested. Install hot fixes for specific problems only.

Leave a comment

Make sure you enter the (*) required information where indicated. HTML code is not allowed.