There are several options for automating the installation and configuration of SharePoint 2010. In this article I'll give an overview of the basic options available.

Standard approach

The standard, non-automated approach is to install SharePoint as follows (assuming the rest of the environment, including Active Directory and SQL Server, is ready):

1. Install the SharePoint prerequisites
2. Run the SharePoint setup program, which installs application binaries and other files
3. Run the SharePoint Products Configuration Wizard (psconfig), which configures various SharePoint logical architecture elements, and creates content databases.

The SharePoint prerequisites tool can be run silently from the commandline. This tool basically runs the setup for a number of libraries on which SP2010 is dependent, and also ensures that the server is configured as an application server with IIS.

The setup program can be configured to take an xml configuration file as input. The configuration file specifies:

• the packages to install, namely Sharepoint Foundation (called sts) and SharePoint (called spswfe)  
• whether to perform a clean install or an upgrade
• the folders to be used for different purposes
• the activation key (product key, PIDKEY)
• the server role, whether a single server instance or a multiserver environment
• whether to display the user interface
• whether to reboot

Microsoft provide a number of example config.xml files on the SharePoint 2010 DVD in the Files folder.

Once the files are deployed, the next step is to run the SharePoint Products Configuration Wizard. This too can be automated.  The wizard can be run in GUI mode (psconfigui.exe), or through a command line interface (psconfig.exe).

psconfig.exe provides the means to run specific commands. For example, it includes a command to create the configuration database, configdb -create].  Automating psconfig.exe is typically achieved through use of a batch file.

Microsoft have made the same commands available in PowerShell, and automating the install with PowerShell is considered best practice. The standard approach here is to create an xml file with configuration settings, and to write a Powershell script which reads the appropriate settings, and executes the various PowerShell commandlets necessary to get SP2010 configured. Microsoft provides guidance for installing SharePoint using powershell. They include a set of files for use as a starting point (SPModule.zip, available on the previously linked page.).

AutoSPInstaller Codeplex solution

The AutoSPInstaller project, available at http://autospinstaller.codeplex.com, provides a set of scripts for both installing the binary files (by calling setup.exe) and configuring SharePoint 2010. It is implemented as a set of powershell scripts and some xml configuration files.

The AutoSPInstaller solution is quite comprehensive and allows you to create the farm including config and central admin sites, create additional web applications and site collections, configure and start the various SharePoint Service applications, create and configure the my sites web app.

Slipstreaming

Slipstreaming is the practice of copying updated files into the installation source so that they are included as part of the installation. The SharePoint 2010 installation media supports slipstreaming; this is achieved by copying updates into the Updates folder.

Other approaches

Various members of the SharePoint community have produced their own powershell scripts. Other options include use of virtual machine images, and even use of backup and restore tools.