Home > SharePoint > SharePoint Deployment

SharePoint Deployment

December 30, 2011 10:09 am Leave a comment Go to comments

Before you can deploy Microsoft® SharePoint® Server 2010 or Microsoft® SharePoint® Foundation 2010, you must meet the following requirements:


SharePoint Server 2010 and SharePoint Foundation 2010 are 64-bit applications and can only run on a 64-bit edition of the Windows Server® 2008 operating system. You must have hardware that supports the use of a 64-bit operating system and 64-bit SQL Server.

SharePoint Server 2010 and SharePoint Foundation 2010 must be run on a 64-bit edition of Windows Server 2008 with Service Pack 2 or Windows Server 2008 R2.

For server farm installations of SharePoint Server 2010 and SharePoint Foundation 2010, you must be running 64-bit versions of Microsoft SQL Server® 2005 or Microsoft SQL Server 2008 (each with the appropriate service packs and updates) on your database servers.

Keep your environments synchronized by using the following:·

Profile replication engine – a tool for keeping profile and social data synchronized across farms.

· Content deployment – a method of moving content between authoring, staging, and live environments.

· Mirroring and log shipping – two techniques for keeping content changes synchronized across farms.

Keep your environments clean by using the following best practices:Be sure to reformat your computers before re-using hardware between environments or within an environment. Do not simply uninstall and reinstall. If there are old customizations or configurations, they can affect how that computer works and introduce errors into your environment.

Log shipping allows you to automatically send transaction log backups from a primary database on a primary server instance to one or more secondary databases on separate secondary server instances. The transaction log backups are applied to each of the secondary databases individually. An optional third server instance, known as the monitor server, records the history and status of backup and restore operations and, optionally, raises alerts if these operations fail to occur as scheduled.

Log shipping consists of three operations:

  1. Back up the transaction log at the primary server instance.

  2. Copy the transaction log file to the secondary server instance.

  3. Restore the log backup on the secondary server instance.

The log can be shipped to multiple secondary server instances. In such cases, operations 2 and 3 are duplicated for each secondary server instance.

A log shipping configuration does not automatically fail over from the primary server to the secondary server. If the primary database becomes unavailable, any of the secondary databases can be brought online manually.







The following figure shows a log shipping configuration with the primary server instance, three secondary server instances, and a monitor server instance. The figure illustrates the steps performed by backup, copy, and restore jobs, as follows:

  1. The primary server instance runs the backup job to back up the transaction log on the primary database. This server instance then places the log backup into a primary log-backup file, which it sends to the backup folder. In this figure, the backup folder is on a shared directory—the backup share.

  2. Each of the three secondary server instances runs its own copy job to copy the primary log-backup file to its own local destination folder.

  3. Each secondary server instance runs its own restore job to restore the log backup from the local destination folder onto the local secondary database.

The primary and secondary server instances send their own history and status to the monitor server instance.

Configuration showing backup, copy, & restore jobs

Installation and configuration

There are three phases in the process of installing and configuring your environment:

1. Prepare Servers

In this phase, you get your servers ready to host the product.

2. Install

In this phase, you install the product and assign roles to each server. You also create the configuration database and the SharePoint Central Administration Web site.


Configure settings, services, solutions, and sites

In this phase, you prepare the farm to host your site content by configuring global settings, creating services applications, deploying customizations, and creating and populating the sites.You can use the Farm Configuration Wizard to these configuration steps, or you can perform them by using either the SharePoint Central Administration Web site or Windows PowerShell. Configuration steps are not isolated to a specific tier in the server infrastructure.


Configure incoming email


Configure outgoing


Configure Mobile account


Configure diagnostics and logging



Configure health and diagnostics



Anti virus protection



With SCOM, the level of reporting and alerting is more granular and easily managed than SharePoint’s standard health monitoring.

  • SharePoint 2010 ships a management pack for System Center Ops Manager
  • Improved Knowledge Articles
  • More relevant events and monitors
  • Surfaces SharePoint Health Analyzer (SPHA) rules
  • Integrated with Unified Logging System (ULS)

Configure Quotas


Configure Alternate  Access Mappings


Categories: SharePoint Tags:
  1. No comments yet.
  1. No trackbacks yet.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: