Implement
The method of upgrade used in this example is the database attach method (DB Attach). Since so many SharePoint 2007 environments currently run on Windows Server 2003 (and since Windows 2008 is the only OS that SharePoint 2010 can be installed on), many SharePoint administrators will likely opt for this method for upgrade, simply because in many cases the environment doesn’t exist for an in-place upgrade.
Using the DB Attach method of upgrade is also useful for practicing and testing the upgrade, even if ultimately an in-place upgrade is used instead. The DB Attach method can be used as another tool to inventory any customizations on the existing site, because the upgrade log will map out exactly what is missing (usually displaying the GUID of the missing component).
Finally, another benefit of the DB Attach method is that it can keep the existing site up and running while the upgrade is tested and executed, mitigating downtime.
|
Accounts Needed for Setup |
|
Setup User Account |
· Domain user account
· Member of the Administrators group on each server where SharePoint setup is run
· This is the account that runs PSConfig (the SharePoint Configuration wizard)
· SQL Server login on the SQL server
· Member of the following SQL Server roles:
o Securityadmin fixed server role
o Dbcreator fixed server role |
|
Server Farm Account |
· Domain user account
· This account interfaces with SQL
· Dbcreator fixed server role on SQL server
· Securityadmin fixed server role on SQL server
· Db_owner fixed database role for all databases in the server farm |
The account used to run the SharePoint Products &Technologies configuration wizard needs SQL rights to get to the databases, which is why it needs the Securityadmin and Dbcreator roles.
New Wizards in SharePoint 2010
SharePoint Products & Technologies 2010 Preparation Tool – also known as the Prerequisite Installer Wizard. This tool checks the server to make sure all the necessary components are installed before SharePoint 2010 is installed. If an internet connection is available, the Preparation Tool can download and install any missing components, or newer versions of the currently installed components. It can also use installation files provided by an administrator in the \PrerequisiteInstallerFiles directory (a newer version of an installer file can also be downloaded if the tool discovers a newer version is available on the Internet). The Preparation Tool confirms or installs the following components:
· IIS 7.0
· SQL Server Client
· Microsoft Filter Pack 14
· PowerShell 2.0
· Windows Installer 4.5
· .Net Framework 3.5 SP1
· Microsoft Sync Framework Runtime 1.0
· Microsoft “Geneva” Framework
· Microsoft Server Speech Language Pack (English-U.S.) version 6.0
· Microsoft Chart Controls for Microsoft .NET Framework 3.5
· Microsoft Unified Communications Manager API 2.0 Speech
There are several components related to speech that many people may question. These are used in the SharePoint search component for People Search when searching a name phonetically.
Setup Wizard – This is the wizard that walks the administrator through the process of installing SharePoint 2010.
SharePoint Products & Technologies Configuration Wizard (PSConfig.exe) – The wizard that runs after SharePoint 2010 is installed and after any patches or Service Packs are installed. It is very similar to the Configuration Wizard used in SharePoint 2007 with a few differences, most notably the addition of the Passphrase screen. Using a Passphrase to encrypt the farm provides an extra layer of security and stability because the farm account no longer has to control everything. If additional servers are added to the farm, the Passphrase will need to be entered during the Configuration wizard to allow the server into the farm.
Server Farm Configuration Wizard – This wizard in Central Administration walks the administrator through the process of setting up the farm and services for the first time. One of the main components of using the Server Farm Configuration Wizard is that it will automatically provision instances of all the default service applications, including:
· Access Services
· Application Registry Service
· Business Connectivity Services
· Excel Services
· Lotus Notes Connector (this service may not be provisioned by default in later builds)
· Managed Metadata Service
· People Profiles
· Search Service Application
· Secure Store Service
· State Service
· Usage and Health Data Collection
· Visio Graphics
· Web Analytics Web Service
· Word Conversion Service Application
Configuring the Farm
Configuring the Search Service Application
The Search Service Application is one of the more complicated and time-consuming aspects of an upgrade. An in-place upgrade means that search will be upgraded automatically with little configuration necessary, but a DB Attach upgrade will require search to be re-configured, as no search settings are imported from the SharePoint 2007 farm. On the upside, however, having to set up search again will allow for existing search settings to be carefully examined to determine if they are still necessary (crawl rules, for example). In many cases, this may provide a good opportunity to do some Search “house-cleaning.”
Some of the steps that will be necessary for configuring the Search Service Application:
· Configuring farm-wide search dashboard and settings, such as search timeout and ignoring SSL warnings
· Defining the default access account
· Specifying the email contact address
· Defining a proxy server (if necessary)
· Adding crawl rules
· Installing necessary IFilters and adding necessary file types
· Adding additional content sources, creating crawl schedules, defining priority, and adding crawl rules for these sources
· Promoting crawled properties to managed properties
· Creating scopes
· Building a Search Center (and defining proper user permission)
· Setting up search federation, server name mappings, result removal
· Enabling search reporting
· Enabling People Search
· Adding user profiles to the People service application (which includes configuring My Sites and crawling the profile store to enable people search)
Next > Implement, part 2