Professional Documents
Culture Documents
Publisher:
Version:
Date:
Attachments:
PowerShell Scripts
Disclaimer
THIS INFORMATION IS PROVIDED AS IS WITHOUT ANY WARRANTY OF ANY KIND.
All trademarks are property of their respective owners.
Copyright 2012
Table of Contents
1
Overview ....................................................................................................................................5
1.1
1.2
1.3
Preparation ................................................................................................................................7
2.1
2.2
Installation ..........................................................................................................................8
3.2
Updates ...............................................................................................................................8
3.3
Configuration ......................................................................................................................8
3.3.1
3.3.2
3.3.3
3.3.4
Firewall Settings...........................................................................................................8
3.3.5
3.3.6
4.2
4.3
4.4
Accounts ........................................................................................................................... 11
5.2
5.2.1
5.2.2
5.2.3
5.3
6
Resources .......................................................................................................................... 12
6.2
Installation ........................................................................................................................ 13
6.3
Configuration .................................................................................................................... 13
6.3.1
6.3.2
Prerequisites ..................................................................................................................... 14
7.2
Installation ........................................................................................................................ 15
7.3
7.4
7.5
8.1.1
Installation................................................................................................................. 16
8.1.2
8.2
8.2.1
8.2.2
8.2.3
8.3
8.3.1
Installation................................................................................................................. 17
8.3.2
8.4
8.4.1
Prerequisites.............................................................................................................. 18
8.4.2
Installation................................................................................................................. 19
8.4.3
Configuration ............................................................................................................. 20
8.5
8.5.1
Description ................................................................................................................ 21
8.5.2
Declaration ................................................................................................................ 21
8.6
8.6.1
8.6.2
8.6.3
8.6.4
8.6.5
8.6.6
8.6.7
8.6.8
8.6.9
8.6.10
8.6.11
8.6.12
8.6.13
8.6.14
Troubleshooting .......................................................................................................................24
1 Overview
This guide allows you to setup different environments depending on your needs:
Development Environment
SharePoint Server
SQL Server
Active
Directory
Front-end
Web Server
Application Server
SQL Server
Both environments:
We dont deploy a single server with the built-in database. Instead we are using SQL Server 2008 R2
and a Server Farm installation so this deployment can be scaled out to create a 2-tier or 3-tier farm
topology1.
Development environment:
If you decide to create a development environment this guide shows you how to create a closed
environment with an Active Directory on a separate server. You can skip this step if you already have
an Active Directory.
3-tier SharePoint farm:
Regarding the installation itself you will see later that it doesnt matter if a SharePoint Server should
be used as an Application server or a Web Front-end server. The differences are created during
configuration of SharePoint Services or Service Applications and not during installation.
2 Preparation
2.1 Service Pack Slipstream Copy
2.2 Best Practices
3.3 Configuration
Development environment: In order to avoid problems during the installation process later it is
highly recommended to do the following steps.
3-tier SharePoint farm: If you are an administrator usually things like joining a domain are already
done. You should stick with your companys policy and skip applying the steps below.
3.3.1
Computer Settings
1. Join a domain and rename your computer if necessary. Restart your computer.
3.3.2
Network Settings
3.3.3
Remote Desktop
3.3.4
Firewall Settings
3.3.5
3.3.6
5. Proceed to the role services selection and add the features you can see in the picture. If you
are prompted to add required role services and features click yes.
6.
5.1 Accounts
You dont need to assign permissions since they are assigned during installation of SQL Server 2008
R2. The SQL Server service account is used to run SQL Server and should be a domain account.
5.2.2
The setup administrator is used to install SharePoint 2010 and you need to manually assign
permissions.
1. The SharePoint 2010 setup administrator has to be a member of the administrators group on
every server where SharePoint will be installed.
2. This configuration step is done after SQL Server is installed and is documented here for the
purpose of completeness.
The SharePoint setup administrator needs to have the securityadmin and dbcreator role.
The sysadmin role is assigned if you decide during SQL Server installation that your
SharePoint setup administrator should also be the SQL Server Administrator. While I
recommend this in a development environment this isnt done in a production
environment.
5.2.3
5.3 Resources
If you need to know more about other service accounts please read the following advice:
6.2 Installation
6.3 Configuration
6.3.1
Assign Permission
6.3.2
Configure Networking
7 SharePoint 2010
This chapter explains the installation and configuration of SharePoint 2010.
Important: If you are not logged on with the SharePoint setup administrator please logon using the
above created account (setupAdmin).
7.1 Prerequisites
The remaining software requirements can be installed by using the SharePoint Products and
Technologies 2010 Preparation Tool which is part of the SharePoint installer.
Development environment and 3-tier SharePoint farm: Please install the prerequisites on every
server where SharePoint should be installed.
7.2 Installation
7.3 Create a New Server Farm
7.4 Connect to an Existing Server Farm
7.5 Initial Configuration
8 Scripted Installation
8.1 Active Directory
8.1.1
Installation
8.1.2
Account Creation
Join Domain
8.2.2
Assign Permission
8.2.3
The third script allows you to enable the roles and role services2 needed by SharePoint 2010.
Only run this script only on the servers where you want to install SharePoint later:
Write-Host "Installing 'Application Server' role..."
get-windowsfeature|where{$_.name -eq "AS-AppServer-Foundation"}|addwindowsfeature
Please review the script since it also installs features like PowerShell IDE you might not need.
Installation
8.3.2
Assign Permission
Only run the scripts on the server where you want to install SharePoint 2010.
8.4.1
Prerequisites
In this example it requires the SharePoint installation files to be stored in a sub folder called
SharePoint. You can change that if you have the installation media stored somewhere else.
If you get an error message above you might try to turn off the user account control settings.
8.4.2
Installation
The second script starts the installation of a SharePoint server using a configuration file3.
Start-Process "SharePoint\setup.exe" -ArgumentList '/config "..\2. SP2010
- Installation APP.xml"' -WindowStyle Minimized Wait
Please see the reference below to find out more about the parameters and its values.
Note: According to TechNet19 there is no Front-end Web Server (WFE) role anymore. Every server
you install is an application server. Its use is defined while configuring services and service
applications and not during installation.
If an error occurs you may have to restart the server.
You can skip the configuration wizard after the installation has finished.
8.4.3
Configuration
The third script is used to create a SharePoint 2010 farm. You need to modify 4 settings:
$DBServer = 'W2K8R2-03'
$ConfigDB = 'spFarmConfiguration'
$CentralAdminContentDB = 'spCentralAdministration'
$CentralAdminPort = '2010'
$PassPhrase = 'YOURPASS1'
$SecPassPhrase = ConvertTo-SecureString $PassPhrase AsPlaintext Force
$FarmAcc = 'mydomain\spFarmAcc'
$FarmPassword = 'YOURPASS1'
$FarmAccPWD = ConvertTo-SecureString $FarmPassword AsPlaintext Force
$cred_FarmAcc = New-Object System.Management.Automation.PsCredential
$FarmAcc,$FarmAccPWD
The fourth script connects a SharePoint server to an existing SharePoint 2010 farm:
$DBServer = 'W2K8R2-03'
$ConfigDB = 'spFarmConfiguration'
$PassPhrase = 'YOURPASS1'
$SecPassPhrase = ConvertTo-SecureString $PassPhrase AsPlaintext Force
After doing the configuration you should be able to open Central Administration:
8.5.1
Description
Every script contains a description at the beginning of the script explaining the service. Usually you
will find something like this:
If a service is part of a service application please note that any a script for a service application also
starts the service itself.
8.5.2
Declaration
A declaration usually contains the name of the service that should be activated. Dont change the
name of the service since its an internal name.
You need to change the name and amount of machines where the service should be activated.
Managed Accounts
8.6.2
Access Services
8.6.3
8.6.4
8.6.5
8.6.6
8.6.7
Description
The service application enables Enterprise Search in your SharePoint farm.
Requirement
Needs the Usage Service Application first or configures its own where you cant set the database
name.
Configuration
You can change everything except the Service Name which refers to an internal name. The service
can be activated on one or more application servers.
The Service Application name and the Application Pool name can be changed and are used as a title.
The Application Pool account refers to a domain account which was already used to create a
SharePoint 2010 managed account.
The database name is used to name the database where the Service Application data is stored and
can be changed according to your naming conventions.
Special Configuration
The Server Name specifies the name of an application server. All components like crawl and query
are created on one server. If you want to move components to a different server you can use Central
Administration to change the search topology.
The index location includes a path to a location used to store the index.
The Content Access account (and password) is used for crawling content and doesnt have to be a
managed account.
8.6.8
8.6.9
Stuck on Starting: Common Issues with SharePoint Server 2010 User Profile
Synchronization
9 Troubleshooting
If you are getting problems during install this table has a few problems and their solutions listed.
Please note that an error message can have a lot of different reasons.
10 Next Steps
All resources used during this tutorial should have been mentioned where used. If you need
additional information please visit TechNet: Deployment for SharePoint Server 2010.
Next Steps