Hardware requirement => SharePoint Server 2010

Hardware requirements — Web servers, application servers, and single server installations

The requirements in the following table apply both to installations on a single server with a built-in database and to servers running SharePoint Server 2010 in a multiple server farm installation.

Component Minimum requirement

Processor - 64-bit, four cores

RAM - 4 GB for developer or evaluation use , 8 GB for production use in a single server or multiple server farm

Hard disk - 80 GB for system drive

You must have sufficient space for the base installation and sufficient space for diagnostics such as logging, debugging, creating memory dumps, and so on. For production use, you also need additional free disk space for day-to-day operations. Maintain twice as much free space as you have RAM for production environments. For more information, see Capacity management and sizing for SharePoint Server 2010.

Hardware requirements—Database servers

The requirements in the following table apply to database servers in production environments with multiple servers in the farm.

Component Minimum requirement Processor - 64-bit, four cores for small deployments , 64-bit, eight cores for medium deployments

RAM - 8 GB for small deployments , 16 GB for medium deployments


Note: These values are higher than those recommended as the minimum values for SQL Server because of the distribution of data required for a SharePoint Products 2010 environment

Hard disk - 80 GB for system drive
Hard disk space is dependent on the size of your SharePoint content.

What are the different Types of Upgrade method used in Sharepoint 2010

Before you run any process to upgrade from Microsoft Office SharePoint Server 2007 to Microsoft SharePoint Server 2010, you have to determine which upgrade approach to take.

Use the information in this article to help compare the pros and cons for each approach and to review information about special cases that might influence your approach

Approach	Description	Pros	Cons
In-place upgrade	You can install SharePoint Server 2010 on the same hardware. You can also upgrade the content and settings in the server farm as part of a single process.	Farm-wide settings are preserved and upgraded. Customizations are available in the environment after the upgrade, although manual steps may be required to upgrade or rework them.	Servers and farms are offline while the upgrade is in progress. The upgrade proceeds continuously. Consequently, you must allocate enough time for all content to be upgraded in sequence.
Database attach upgrade	You can upgrade the content for the environment on a separate farm. The result is that you do not upgrade any of the services or farm settings. You can upgrade the databases in any order and upgrade several databases at the same time. While each database is being upgraded, the content in that database is not available to users.	You can upgrade multiple content databases at the same time, which results in faster upgrade times overall than an in-place upgrade. You can use a database attach upgrade to combine multiple farms into one farm.	The server and farm settings are not upgraded. You must manually transfer settings that you want to preserve from the old farm to the new farm. Any customizations must also be transferred to the new farm manually. Any missing customizations may cause unintended losses of functionality or user experience issues. Copying databases over a network takes time and bandwidth. You must plan for that. You need direct access to the database servers.

What is Service Application Framework?

 => Replacement for the Shared Services Provider  in MOSS 2007
=> API provided by backend application servers and consumed by front-end application servers.
=> Used for developing middle-tier applications that are hosted in SharePoint and provide data and   

      resources to other SharePoint features
=> Enables services to be shared between computers on a server farm
=> Load balance and manage services
=> Out of the box - 20 built in services
=> Certain objects automatically backed up and restored
=> Ideal for deploying, managing and discovering WCF service clients and endpoints.
=> Windows Powershell support
=> Timer job infrastructure available at Service-scope
=> Use of SharePoint configuration store and support for storing data in SharePoint managed custom database is available


Load Balancing

=> Use Round robbing load balancing
=> Service application proxy method invocations must be routed thru the front end web server to an
      appropriate app server by using a load balancing tool.
=> Calls between frontend and app servers to require separate external load balancer than the load         
      balancing for front-end web servers
=> SPRoundRobinServiceLoadBalancer can be enhanced or replaced by third party.

Management and Administration

=> Services plug their management UI into SharePoint Service Management page
=> Common admin tools such as upgrade, backup, restore and account management
=> Common UI to manage, start, stop, group, associate, federate and backup SharePoint services.
=> Can define specialized admin roles and can be delegated to users who are not farm admins
=> Security trimmed

Security

•Claims-based identity model  Example - Search service

Benefits

The Service Application Framework allows developers to provide load balanced middle-tier resources that can be managed through SharePoint and leverage the full power of SharePoint 2010.

Installing SharePoint 2010 SP1

****  Key Points to Remember while installing SP1 for Sharepoint ****

=>  The packages may require up to four times their file size in remaining disk space during installation
      So make sure that you have sufficient disk space

=> Restart the computer at the end of the installation.

=> If you are using Office Web Apps in a mixed version environment, where Office Web Apps has SP1-or-later applied while SharePoint Server 2010 remains on the RTM version, you must install the following two updates before you install SP1 for Office Web Apps:

• 2510639  (http://support.microsoft.com/kb/2510639/ )
• 2510648  (http://support.microsoft.com/kb/2510648/ )

Install the service packs in the following order on every server in the farm:

1. Service Pack 1 for SharePoint Foundation 2010
2. Service Pack 1 for SharePoint Foundation 2010 Language Pack (if applicable)
3. Service Pack 1 for SharePoint Server 2010
4. Service Pack 1 for SharePoint Server 2010 Language Pack (if applicable)

After installing Service Pack 1 you must run the SharePoint 2010 Products Configuration Wizard Just incase it fails or there are any issues .

Run the Command : psconfig –cmd upgrade –inplace b2b -wait

One time on every server in the farm. This step updates the farm to the latest version and is required in order to have full SharePoint functionality. If you do not run the wizard, the farm will run with reduced capacity. i.e; Search will not be able to index content

You must restart the User Profile Synchronization service after installing Service Pack 1

http://technet.microsoft.com/en-gb/library/ee721049.aspx#StartUPSSProc

After the SP1 is installed, the Workflow feature is disabled when a new site collection is created. To use the Workflow feature in a new site collection, enable it in the Site Collection Settings page.

After you are done it is strongly recommend that you install the install the June 2011 Cumulative Update refresh package.

The June Cumulative Update includes several important security and bug fixes that are not included Service Pack 1.

2536601  (http://support.microsoft.com/kb/2536601/ ) Description of the SharePoint Foundation 2010 cumulative update package (SharePoint Foundation server-package): June 30, 2011

2536599  (http://support.microsoft.com/kb/2536599/ ) Description of the SharePoint Server 2010 cumulative update package (SharePoint server-package): June 30, 2011

Visual Upgrade in 2010 , On all sites in a web application

Upgrade all the sites in a web application in SharePoint 2010 . You can Use this SharePoint PowerShell code to accomplish

$SPwebApp = Get-SPWebApplication "http://SP2010.com"
 
    foreach ($SPsite in $SPwebApp.Sites)
    {
       foreach($SPweb in $SPsite.AllWebs)
        {
         
           $SPweb.UIVersion = 4
       $SPweb.Update()
    write-host $spweb.url
        }
    }
read-host  #just to pause

Unable to move Content Editor Webpart from one place to other

Issue

While moving the Content Editor web part from one place to another We get the following error message "Error On page" on the Bottom left of the IE.

 Or

 After moving the content Editor web part , when we click Exit edit mode . It gives "Unexpected error has occurred".

Cause

This usually happens whenever we copy the HTML code from one Content Editor web part to another. When we copy the HTML code it also copies the Web part ID and it conflicts.

Resolution

Open the Site in Firefox\Chrome browser as IE will not give you the Drop down to edit the webpart

Modify the Content Editor Web part

Open the Source Code

Remove the following Tag from the code for eg:- "id=WebPartWPXX WebPartID="XXXX-XXXX-XXXX-XXXX-XXXXXXXX"

Click Apply - OK

You can then move the web parts without any issues

Workflow Error: "An error has occurred in Approval"

It’s not a known issue But it’s more of a Setup error

 We have the SharePoint OOB Approval workflow which can be attached to a document library to start whenever a new document gets created and get the required approvers to review and approve the document for publishing.

 It is a very easy task to set-up this workflow

 Steps to setup a workflow :

 For a document library or list , go to Settings->Workflow Settings->Add Workflow

 Choose the Approval workflow from the list, make it start on item creation go to the second workflow page.

 Select the approvers and check "Update the approval status (use this workflow to control content approval) "

 Finish and create a document in the library.

 Although this might seem as an easy straightforward task the workflow might after all still end-up in error:

  Error  System Account  An error has occurred in Approval

 Cause : Because This is an approval workflow

 which should update the approval status of the document Also

 if you missed one step like setting the approval for the document library this simple task will fail at the end.

 The workflow will start and run flawlessly until the end when it will try to update the approval status.

 If this setting is set to not to require content approval it will fail to update it hence throwing the above error.

 So, if you encounter this, just go into the document library settings and go to Versioning Settings Page

 Set "Require content approval for submitted items " to yes and everything should be fine.