Production and Farm Deployments
- Deployment section on TechNet
- Deployment model – Visio or PDF or XPS – TechNet
- Administrative service accounts required for initial deployment – TechNet
Make sure farm account is in local admins group
- Configuring servers and services for a 3-tier farm – TechNet, step by step guidelines
- Installing SharePoint 2010 on Win2008 R2 and SQL step-by-step – Andreas Glaser (very good)
- Life on the farm part 1: Installing and Configuring – guest post on Joel Oleson’s blog (Sept 2010)
- Consider using a warm-up script to avoid first user logins experiencing slow loading pages. An example is available on CodePlex – SPBestWarmUp (don’t know if it’s the best, but rated by others). Works with 2010 and 2013
Development Environments (i.e. may not be a supported config)
- Setting up a development environment for SharePoint 2010 – MSDN (updated post RTM, May 2010)
- Installing SharePoint 2010 on a single machine – UK MCS blog
- Installing SharePoint Foundation 2010 on Windows 7 (Powershell command to skip the need for AD)
- Installing SharePoint with SQL Server but without AD – Neil Hodgkinson, Powershell commands
- Installing SharePoint complete without AD – Soren Nielson, how to fix Search after
- Installing SharePoint standalone on a DC:
- SQL express is not supported on a DC, default set-up will fail
- Run from command line: setup.exe /config FILES\SETUP\config.xml
SharePoint and Small Business Server 2011
- Expect to have ‘fun’: Recreate your SharePoint Foundation 2010 application and content database, TechNet Mar 2011
- Don’t run the Config Wizard straight away. Check you’ve installed everything you need first. e.g. if installing Enterprise Edition, install OWA as well before running the config wizard.
- If using Powershell New-SPConfigurationDatabase (to install without AD), when prompted to supply user credentials, use format Servername\Username and use a unique account (i.e. spadmin)
- For demo VMs, to turn off IE enhanced security – go to Server Manager, click on Root, scroll down and click on ‘Configure IE ESC’
Service Pack 1
- So what’s the fuss – Spencer Harbar
- 10 best practices and recommendations – Joel Oleson
- Own demo machine: ran SP1 for Foundation, then SP1 for Office Server, then Config Wizard.
Security and Permissions
- Remember SharePoint groups cannot be nested. Windows Security groups can.
- Enabling anonymous access:
- In Central Admin, select Manage Web Apps,
- Select the Web App to be granted anonymous access and click Authentication Providers in the ribbon
- Click on Default zone and check box to enable anonymous access
- Click on Anonymous Policy in ribbon and set policy for anonymous access (e.g. deny write)
- In Site Collection, go to Site Permissions and click on Anonymous access in ribbon
- Kerberos issues. Need to configure Kerberos Delegation if multiple servers in farm and using Kerberos as server authentication. Details: http://www.windowsecurity.com/articles/Troubleshooting-Kerberos-SharePoint-environment-Part3.html
- Correct setting to force ignore proxy when adding to CONFIG files (incl miisetup.exe.config for FIM and web.config). Difference compared to most online sources is addition of ‘useDefaultCredentials’
<proxy usesystemdefault = “false” proxyaddress=”yourproxyserver” bypassonlocal=”true” />
- Basic proxy settings for web.config
<system.net> <defaultProxy> <proxy autoDetect="true" proxyaddress="thisiswhereyourproxyshouldbe" bypassonlocal="true" /> </defaultProxy> </system.net>
Easy way to map site collections to content databases within Central Admin (suitable for a small number):
- Central Admin – Application Management – Manage Content Databases
- Create the content databases you require
- Stop them all (take offline). Note: Doesn’t actually take the databases offline, people can still access SharePoint and create sites, lists and libraries. You just can’t create site collections when the database is offline in Central Admin
- Start the one you want to create a site collection for. Create the site collection. Then stop the database again
- Rinse and repeat for each site collection.
Moving databases to a different server
Best avoided if possible but sometimes the need can arise…
- Moving SharePoint to a different server Iwth aliasing note) – Todd Klindt, Feb 2011
- Move SharePoint Database by Stuart Roberts, Sept 2011
- How to transfer logins and passwords between instances of SQL Server – MS support
- Concise version with scripts – Marcello Tonarelli, June 2010
See also under SharePoint 2013 handbook. Official MS guide has been updated for 2013.
Alternate Access Mapping
Each web application must have either a dedicated IP, Host Header or Port number. The first two options require TCP/IP and DNS to be configured prior to create each web application.
- Creating a SharePoint 2010 site structure using Powershell – Falchion Consulting, Dec 09
General Powershell tips
- Windows Powershell manual – TechNet
- Ten tips for better PowerShell functions – James O’Neill, Apr 11
- Making Twitter word clouds using Powershell – James O’Neill, Nov 09
Problems running Powershell scripts? Don’t forget to change the execution policy if you haven’t signed them. To check what policy is currenlty in use, type ‘Get-ExecutionPolicy. To lower the security level, type ‘Set-ExecutionPolicy RemoteSigned’ (or Unrestricted).
Use iisreset /noforce to help prevent data lose in case IIS services cannot be stopped within one minute time-out period.
Restore-SPSite -Identity <Site collection URL> -Path <Backup file> [-DatabaseServer <Database server name>] [-DatabaseName <Content database name>] [-HostHeader <Host header>] [-Force] [-GradualDelete] [-Verbose]
Backup the entire farm:
Backup-SPFarm -Directory c:\backuppath -BackupMethod Full