SharePoint 2010 Environment Setup - Post Installation Configuration and Tricks-n-Tips
Post- installation Configuration
Change your Site's Authentication provider (not central Admin) from "Classic" authentication to Claims Authentication
It can be done via PowerShell Script
Add-PSSnapin Microsoft.SharePoint.PowerShell $webApp = Get-SPWebApplication "http://sitename/" $webApp.UseClaimsAuthentication = 1 $webApp.Update() $webApp.ProvisionGlobally() $webApp.MigrateUsers($True)
- To create a new secure store target application for ‘Visio Services’ go to Central Administration | Application Management | Manage service applications | Secure Store Service
- Then go to Central Administration | Application Management | Manage service applications | Visio Graphics Service | Global Settings
- Check the Application ID under Unattended Service Account
- You should have entered an application Id here, if not create a Secure Store Target Application of type Group and then enter its Target Application ID for Visio Graphics Account.
Solve “Missing Server Side Dependencies – 8d6034c4-a416-e535-281a-6b714894e1aa” error
- Navigate to SharePoint Central Administration Page
- Click General Application Settings on left hand side Quick Launch bar
- Under Search, click Farm-Wide Search Administration to open farm wide search administration page.
Now, under Search Service Application click Search Service Application
Now restart the server by executing iisreset -noforce command on command prompt.
Add the local Administrators group to the SQL System Administrators
To fix the outstanding problems highlighted by the health analyser, go to the Central Admin site and click on the "Health Analyser" alert bar that appears across the home page, or click the "Review problems and solutions" link on the homepage.
Address Issue 'The server farm accoun should not be used for other services'
For each alert, open it up and work out what the alert is being thrown by, and what to do to fix it. For example:
The Services that are causing the problem are listed in the explanation field, however some of them are a bit Cryptic (Such as SPUserCodeV4 - This is actually the SharePoint Foundation Sandboxed Code Service!)
Under "Security" --> "Configure Service Accounts", the services are listed using "Friendly Names" - most of the time it's pretty easy to work out what the Cryptic name in the Health Analyser Message means for the service… however if you cannot work it out, just go through each one and find the ones with the Farm account selected.
Select the Service(s) in question and change them to something else (such as a common generic Services account)
Address Issue 'Built-in accounts are used as application pool or service identities.'
$tracingService.ProcessIdentity.CurrentIdentityType = "SpecificUser" $tracingService.ProcessIdentity.ManagedAccount = $managedAccount $tracingService.ProcessIdentity.Update()
# This actually changes the "Run As" account of the Windows service.
Then, open up computer management and add the same account to the Performance Log Users group on all servers.
Address Issue 'Databases exist on servers running SharePoint Foundation.'
The "Database Exists on the Same Server" issue will not go away, as we're using SQL Standard on the same server.
Address Issue 'Validate the My Site Host and individual My Sites are on a dedicated Web application and separate URL domain'
My Site host and My Sites will throw the same error if they are located in the same web app; however for a development environment this is acceptable.
Tricks & Tips
- If the developers install Visual Studio 2010 before installing SQL Server 2008 R2, then the express version of the SQL Server 2008 will get installed by VS2010 complete installation.
Therefore, that would be ideal to tick off the SQL Server express edition installation option when installing Visual Studio 2010. Alternatively, install VS2010 and SharePoint SDK in the very end stage of this procedure.
- Installing service pack and cumulative package are most important steps during the installation and setup phase, by which it can save a lot of hassle for further setup later on. Therefore, it’s highly recommended to install patches, and then run the windows updates before kicking off the server configuration.
- Moving SharePoint logs off C drive is just a quick approach to avoid the situation, where it runs out the space from the operating drive.
- The tip here is to use PowerShell, which is neat and quick solution to get this updated:
Set-ItemProperty ‘IIS:\Sites\SharePoint – 80′ -name logFile.directory -value ‘D:\SPLog\SiteLog’ Apart from that, we also can quickly update the SharePoint Diagnostic log files to the new directory by the following Powershell Cmdlet:
Set-SPDiagnosticConfig -LogLocation D:\SPLog\SPDiagnosticLog
- Moving away SharePoint databases from C drive is another pre-caution method to ensure that, the SharePoint application runs out the space along with the huge increate of the database growth.
A quick one I set up is to change the “Database default locations” to D drive or another other drive except for the C drive where your operating system sits. After restarting the server, whatever the new database SharePoint create from this database, it will go to the new directory we define earlier.
- a. http://geekswithblogs.net/manesh/archive/2010/05/28/building-the-ultimate-sharepoint-2010-development-environment.aspx
- b. http://p2p.wrox.com/content/articles/setting-your-sharepoint-2010-development-environment
- c. http://msdn.microsoft.com/en-us/library/ee554869.aspx
- d. http://blah.winsmarts.com/2009-11-SharePoint_2010_Development_Environment_-and-ndash;_Practical_Tips.aspx
- e. http://www.wictorwilen.se/Post/My-SharePoint-2010-development-rigs.spx
- f. http://www.alpesh.nakars.com/blog/powershell-to-change-sharepoint-diagnostic-log-file-location/
- g. http://sptwentyten.wordpress.com/2010/04/13/change-the-iis-log-file-directory-via-powershell/
This blog entry aims to demonstrate that the simple setup steps for building up the SharePoint 2010 environment from ground-up on a fresh development box.
Essentially we would like to install SharePoint 2010 “Server Farm” mode – (not “stand-alone” or “Front-end only” mode) and use the SQL 2008 R2 instance as its target database server.
Install SQL Server 2008 R2
SQL Server 2008 R2 gets installed without any hassle on Windows Server 2008 R2 and all default feature settings are coped with SharePoint 2010 installation.
In our case, we would like to install the default instance with full-text indexing and other shared components except for Reporting Service. (Please refer to the following the screen-shot)
Install KB971831 and SharePoint 2010 Pre-requisites
Before installing SharePoint 2010 Pre-requisites, we need to make sure that WCF Hotifx for Microsoft Windows (KB971831) has been applied on the target machine.
Once it has been done, we could quickly start to install SharePoint 2010 Pre-requisites from the SharePoint 2010 installation media. (Please refer to the following screenshot.)
Install SharePoint 2010
1. Choose the Server Farm as the installation type. DO NOT SELECT Standalone because the standalone version installs a copy of SQL Server Express and should not be used.
2. From the server type, same again. Do not choose standalone edition. We should always choose complete edition with all components.
3. After the installation, it’s highly recommended to run the windows updates and cumulative updates rather than going straight to configuration part. Firstly, patch on http://support.microsoft.com/kb/2459125, then http://support.microsoft.com/kb/2459257)
It’s important to install any service packs and cumulative updates first before continuing with the SharePoint configuration.
Configure SharePoint 2010
1. Create a new server farm
Fire off the configuration wizard, and acknowledge the IIS service re-set during this process. Then create a new server farm and then move on. (Please refer to the screen-shot below.)
2. Configure database
Enter the name of the database server and select a name for the Config database.
3. Enter a farm passphrase
In my case, I would just use my NDE AD password for it.
4. Specify port numbers for SharePoint application Use 3100 for Central Admin, 3500 for Search and 4000 for My sites (Please refer to the screen-shot below.)
5. Choose NTLM for security protocol
6. Review the settings and click Finish to complete the configuration wizard.
Initial Farm Configuration Wizard
1. Run the wizard to provision the components.
2. Create a service account that will become a managed service account for the farm.
3. Check the service applications that will be installed. In my case, I select all of them.
4. After the service application provisioning process has completed, the wizard will prompt me to create a web application and root site collection.
5. After putting title and selecting a template, we are all set for provisioning SharePoint 2010 environment.
Install Visual Studio 2010 and SharePoint 2010 SDK
a. Install Visual Studio 2010
I recommend doing a complete installation along with all shared components, by which there is less hassle for later configuration and patch on.
b. Download and Install the Microsoft SharePoint 2010 SDK
This basically installs the SharePoint 2010 SDK and SharePoint Foundation Server 2010 SDK onto the target machine for development usage.
Download & Install SharePoint 2010 Designer
You could download the designer 64bit from this address http://www.microsoft.com/downloads/en/details.aspx?FamilyID=566d3f55-77a5-4298-bb9c-f55f096b125d&displaylang=en
There are a lot of other ways to set up the SharePoint 2010 farm enviornment, and here I have just quickly gone through the set-up process based upon the latest exercise I have conducted and hopefully, it could benefit anyone who's looking for similar reference from the internet.
In the next article, I would like to show you the post-installation configuration and tips-n-tricks when it comes to SharePoint 2010 farm installation and configuration.
Stay tuned and there are a lot more to come!