Installing SharePoint 2013Alan Richards

1 Introductions

2 Security Accounts

3 Installing SharePoint

4 Installing Office Web Apps

5 Installing Workflow Manager

6 Q & A

• Senior Consultant• SharePoint MVP• 18 years experience in IT• Worked with SharePoint since team

services

uk.linkedin.com/in/richardsalan

@arichards_Saruk

www.edutechnow.com

alan.richards@foundation-sp.com

+44(0) 782 483 1088

Security Accounts

• Least privilege at all times• Setup accounts to use with SharePoint

• Setup user• Domain Users & Local Administrator• DB – Security Admin & Database Creator

• Farm service account (Database access account)• Domain Users• DB – Setup will set permissions

• Application pool account• Domain Users• DB – Setup will set permissions

• Active Directory• Add accounts to Active Directory

• SP-Setup• SP-FarmAd• SP-AppPool

http://technet.microsoft.com/en-us/library/cc678863.aspx

Installing SharePoint 2013

Login as SharePoint Setup

http://craiglussier.com

$passphrase = ConvertTo-SecureString -asPlainText –Force Set-SPPassPhrase -PassPhrase $passphrase –Confirm

Creating a SharePoint Site

A managed account allows SharePoint 2013 to control aspects of the account and synchronise password changes with Active Directory if necessary

• Name for the new website – Make it something recognisable

• Port for the website – The default is 80, you can use something different if you need to

• Do you require anonymous access – Is it going to be a public site

• Secure Sockets Layer – If you require the web application to use SSL then all servers will require valid certificates

• Authentication method – NTLM or Kerberos• URL of the website – The URL that users will use to

access the site (FQDN if using SSL) • Application pool name – Make it something

recognisable• Security account – Use the Application Pool

Account (you should have created a managed account using the instructions above)

• Database server – The name of the database server storing the SharePoint 2013 databases

• Database name – The name given to the database for this web application

• Authentication – The default is Windows and this is the recommended way of accessing the database server

• Name for the new website – Make it something recognisable

• Port for the website – The default is 80, you can use something different if you need to

• Do you require anonymous access – Is it going to be a public site

• Secure Sockets Layer – If you require the web application to use SSL then all servers will require valid certificates

• Authentication method – NTLM or Kerberos• URL of the website – The URL that users will use to

access the site (FQDN if using SSL) • Application pool name – Make it something

recognisable• Security account – Use the Application Pool

Account (you should have created a managed account using the instructions above)

• Database server – The name of the database server storing the SharePoint 2013 databases

• Database name – The name given to the database for this web application

• Authentication – The default is Windows and this is the recommended way of accessing the database server

• Name for the new website – Make it something recognisable

• Port for the website – The default is 80, you can use something different if you need to

• Do you require anonymous access – Is it going to be a public site

• Secure Sockets Layer – If you require the web application to use SSL then all servers will require valid certificates

• Authentication method – NTLM or Kerberos• URL of the website – The URL that users will use to

access the site (FQDN if using SSL) • Application pool name – Make it something

recognisable• Security account – Use the Application Pool

Account (you should have created a managed account using the instructions above)

• Database server – The name of the database server storing the SharePoint 2013 databases

• Database name – The name given to the database for this web application

• Authentication – The default is Windows and this is the recommended way of accessing the database server

• Name for the new website – Make it something recognisable

• Port for the website – The default is 80, you can use something different if you need to

• Do you require anonymous access – Is it going to be a public site

• Secure Sockets Layer – If you require the web application to use SSL then all servers will require valid certificates

• Authentication method – NTLM or Kerberos• URL of the website – The URL that users will use to

access the site (FQDN if using SSL) • Application pool name – Make it something

recognisable• Security account – Use the Application Pool

Account (you should have created a managed account using the instructions above)

• Database server – The name of the database server storing the SharePoint 2013 databases

• Database name – The name given to the database for this web application

• Authentication – The default is Windows and this is the recommended way of accessing the database server

• Name for the new website – Make it something recognisable

• Port for the website – The default is 80, you can use something different if you need to

• Do you require anonymous access – Is it going to be a public site

• Secure Sockets Layer – If you require the web application to use SSL then all servers will require valid certificates

• Authentication method – NTLM or Kerberos• URL of the website – The URL that users will use to

access the site (FQDN if using SSL) • Application pool name – Make it something

recognisable• Security account – Use the Application Pool

Account (you should have created a managed account using the instructions above)

• Database server – The name of the database server storing the SharePoint 2013 databases

• Database name – The name given to the database for this web application

• Authentication – The default is Windows and this is the recommended way of accessing the database server

Installing Office Web Apps

http://www.microsoft.com/en-us/download/details.aspx?id=35489

Certificates• Recommended for production• Trusted source• Required for external sites

Configuration• PowerShell to configure Web Apps

New-OfficeWebAppsFarm -InternalUrl https://yourserver.local -ExternalUrl https://webapp.yourdomain.com –CertificateName "OfficeWebApps Certificate" –EditingEnabled

Verify• Browse to a web page to verify Web Apps is working• https://yourserver.local/hosting/discovery• Returns a screen of xml

Claims

• For SharePoint 2013 to access Office Web Apps the web application must use claims based authentication• Convert-SPWebApplication -Identity "http://yourwebapplication:port" -

To Claims –RetainPermissions

Licensing

• To enable users to edit documents using Office Web Apps they need to be assigned licenses to edit.

Get-SPUserLicense$x = New-SPUserLicenseMapping -SecurityGroup <ADsecuritygroup> –License OfficeWebAppsEdit$x | Add-SPUserLicenseMappingEnable-SPUserLicensing

Binding• Bind SharePoint 2013 to the Office Web Apps server

New-SPWOPIBinding -ServerName <WebAppServerName>

Installing Workflow Manager

Workflow Manager• Install of SharePoint 2013 – Provides 2010 workflows• Standalone or co-located• The installation of Workflow Manager uses the Web Platform Installer

from Microsoft and can be downloaded from http://go.microsoft.com/fwlink/?LinkID=252092

• You can use default settings• Configure connection to SQL• Service account• Use http or https• Certificates

Connecting to SharePoint• Logon to each SharePoint 2013 web front end and install the Workflow

Manager Client, this can be downloaded from http://go.microsoft.com/fwlink/p/?LinkID=268376• Register workflow server

Register-SPWorkflowService –SPSite "http://myserver/mysitecollection" –WorkflowHostUri “http://workflow.example.com:12290”

Test Configuration• Download SharePoint Designer

2013 from the Microsoft website, this link will access the download site http://www.microsoft.com/en-us/download/details.aspx?id=35491

Q & A