Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
Publisher:
Version:
Date:
Andreas Glaser
1.1
1/1/2013
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
Installation ..........................................................................................................................7
2.2
Updates ...............................................................................................................................7
2.3
Configuration ......................................................................................................................7
2.3.1
2.3.2
2.3.3
2.3.4
Virtual Memory............................................................................................................8
2.3.5
2.3.6
Firewall Settings...........................................................................................................8
2.3.7
3.2
3.3
3.4
Accounts ........................................................................................................................... 11
4.2
4.2.1
4.2.2
4.2.3
4.3
5
Resources .......................................................................................................................... 12
5.2
Installation ........................................................................................................................ 13
5.3
Configuration .................................................................................................................... 13
5.3.1
5.3.2
6.2
Prerequisites ..................................................................................................................... 15
6.3
Installation ........................................................................................................................ 15
6.4
6.5
6.6
7.1.1
Installation................................................................................................................. 16
7.1.2
7.2
7.2.1
7.2.2
7.2.3
7.3
7.3.1
Installation................................................................................................................. 17
7.3.2
7.4
7.4.1
Prerequisites.............................................................................................................. 18
7.4.2
Installation................................................................................................................. 20
7.4.3
Configuration ............................................................................................................. 21
7.5
7.5.1
Description ................................................................................................................ 22
7.5.2
Declaration ................................................................................................................ 22
7.6
7.6.1
7.6.2
7.6.3
7.6.4
7.6.5
7.6.6
7.6.7
7.6.8
7.6.9
7.6.10
7.6.11
7.6.12
7.6.13
7.6.14
7.6.15
7.6.16
Troubleshooting .......................................................................................................................27
A.2
1 Overview
This guide allows you to setup different environments depending on your needs:
Development Environment
SharePoint Server
SQL Server
Front-end
Web Server
Active
Directory
Application Server
SQL Server
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. With a closed environment you dont
depend on connectivity to your companys AD or on a person managing it (e.g. if you need accounts
or changes).
Important: Dont install SharePoint 2013 on a Domain Controller or Working Group. There will be
loss of functions and unexpected behavior.1 So you need at least two virtual machines.
Running two virtual machines instead of one looks like you need more hardware. Please take a look
at my example development environment later for a useful deployment.
We dont deploy a single server with the built-in database. Instead we are using SQL Server 2012 and
a complete installation so this deployment can be scaled out to create a 2-tier or 3-tier farm
topology2.
SharePoint 2013 Preview : Stand alone server set up : Facts and Fallacies,
http://blogs.msdn.com/b/syedi/archive/2012/07/26/sharepoint-2013-preview-stand-alone-server-set-upfacts-and-fallacies.aspx
2
Install SharePoint 2013,
http://technet.microsoft.com/en-us/library/cc303424(v=office.15).aspx
In addition to the flexibility you can choose which features you really need to install in order to get
your work done.
Evaluation:
For evaluation of the product you can use the single server installation with the built-in database.3
2.3 Configuration
Development environment: In order to avoid problems during the installation process later it is
highly recommended to do the following steps.
N-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.
2.3.1
Computer Settings
1. Join a domain and rename your computer if necessary. Restart your computer.
If you dont have a domain right now I will show you later how to configure an Active
Directory.
2.3.2
2.3.3
Network Settings
2.3.4
Virtual Memory
2.3.5
Remote Desktop
2.3.6
Firewall Settings
2.3.7
3. Select a server from the server pool where you want to install Application Server and Web
Server.
7. Skip the feature selection dialog and proceed to the role services dialog.
8.
You dont need to assign permissions since they are assigned during installation of SQL Server. The
SQL Server service account is used to run SQL Server and should be a domain account.
4.2.2
The setup administrator is used to install SharePoint 2013 and you need to manually assign
permissions.
1. The SharePoint 2013 setup administrator has to be a member of the administrators group on
every server where SharePoint will be installed. Go to Server Manager > Tools > Computer
Management and add the setup administrator.
2. The second 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.
4.2.3
4.3 Resources
5.3 Configuration
5.3.1
Assign Permission
5.3.2
Configure Networking
6 SharePoint 2013
This chapter explains the installation and configuration of SharePoint 2013.
Important: If you are not logged on with the SharePoint setup administrator please logon using the
above created account (spAdmin).
FIX: IIS 7.5 configurations are not updated when you use the Server Manager class to commit
configuration changes
FIX: A hotfix is available for the .NET Framework 4.5 that resolves an ASP.NET race condition
issue in Windows 7, Windows 7 SP1, Windows Server 2008 R2, Windows Server 2008 R2 SP1,
Windows Server 2008 SP2, and Windows Vista SP2
FIX: A hotfix is available for the .NET Framework 4.5 that resolves an ASP.NET race condition
issue in Windows 8, Windows RT, and Windows Server 2012
6.2 Prerequisites
6.3 Installation
6.4 Create a New Server Farm
6.5 Connect to an Existing Server Farm
After the installation and configuration process Central Administration will open:
7 Scripted Installation
7.1 Active Directory
7.1.1
Installation
7.1.2
Account Creation
Join Domain
7.2.2
Assign Permission
7.2.3
The third script allows you to enable the roles and role services5 in Windows Server 2012 and 2008
required by SharePoint 2013.
Only run this script 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
7.3.2
Assign Permission
Important:
Only run the scripts on the server where you want to install SharePoint 2013.
You need to open a PowerShell console with Run as administrator to start the scripts.
Otherwise you have permission problems since the spAdmin is not the built-in server
administrator SERVERNAME\administrator.
7.4.1
Prerequisites
The first script starts the prerequisites installer minimized and in an unattended mode:
Start-Process "SharePoint\PrerequisiteInstaller.exe" -ArgumentList
"/unattended" -WindowStyle Minimized -Wait
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.
Note: Please run the .bat file since this file reads the exit codes of the installer and suggests the next
step based on the code.
The installation of prerequisites requires the server to reboot or exits with an error:
7.4.2
Installation
The second script starts the installation of a SharePoint server using a configuration file.
Start-Process "SharePoint\setup.exe" -ArgumentList '/config "..\2. SP2013
- Installation APP.xml"' -WindowStyle Minimized Wait
You can leave the license key blank if you want to install SharePoint Foundation 2013.
Please see the reference below to find out more about the parameters and its values.
Note: Since SharePoint 2010 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.
7.4.3
Configuration
The third script is used to create a SharePoint 2013 farm. You need to modify 4 settings:
$DBServer = 'W2K8R2-03'
$ConfigDB = 'spFarmConfiguration'
$CentralAdminContentDB = 'spCentralAdministration'
$CentralAdminPort = '2013'
$PassPhrase = 'YOURPASS1'
$SecPassPhrase = ConvertTo-SecureString $PassPhrase AsPlaintext Force
$FarmAcc = 'domain\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 2013 farm:
$DBServer = 'W2K8R2-03'
$ConfigDB = 'spFarmConfiguration'
$PassPhrase = 'YOURPASS1'
$SecPassPhrase = ConvertTo-SecureString $PassPhrase AsPlaintext Force
After doing the configuration you are able to open Central Administration:
7.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.
7.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
7.6.2
7.6.3
7.6.4
7.6.5
7.6.6
7.6.7
7.6.8
7.6.9
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.
Do not configure:
Do configure:
$ServerName: Specifies the name of an application server. All components like crawl and
query are created on one server.
$DatabaseName: 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.
$spAppPoolAcc: Refers to a domain account which was already used to create a SharePoint
managed account.
$spContentAccess: The account and password is used for crawling content and doesnt have
to be a managed account
Requirements
1. The SharePoint Farm account needs to be member of the local Administrators group on the
server where the User Profile Service Application should run.
2. After putting the SharePoint Farm account in the local Administrators Group you need to
restart the server so the security token becomes active.
3. Logon using the SharePoint Farm account.
4. Open a PowerShell console using 'Run as administrator' to run the PowerShell script.
5. The SharePoint Farm account doesnt need Replicating Directory Changes in Active
Directory.
Its the account you use to create a new Synchronization Connection after you have
successfully created the User Profile Service Application.
6. Please wait at least 5 minutes since the start of the User Profile Synchronization Service
needs time:
Do not configure:
Do configure:
$ServerName: Specifies the name of an application server where the User Profile Service
Application and all of its services will run.
$FarmAccount: The User Profile Synchronization Service needs to be configured using the
SharePoint Farm account.
$DatabaseName: The database name is used to name the user profiles, social and sync
database and can be changed according to your naming conventions.
$spAppPoolAcc: Refers to a domain account which was already used to create a SharePoint
managed account.
8 Troubleshooting
If you are getting problems during install this table has a few problems and their solutions listed.
Although they are used with SharePoint 2010 they will work with SharePoint 2013 too since the base
is the same.
9 Next Steps
All resources used during this tutorial should have been mentioned where used. If you need
additional information please visit TechNet: Install and configure SharePoint 2013.
Next Steps