virtual lab - upgrade

8/8/2019 Virtual Lab - Upgrade

1/14

SharePoint RTM - IT PRO - Upgrade


2/14


Table of Contents

SharePoint RTM - IT PRO - Upgrade ....................................................................................... 1

Exercise 1 Verify Upgrade Readiness ............................................................................................................................. 2

Exercise 2 Gain Upgrade System Familiarity.................................................................................................................. 5

Exercise 3 Troubleshoot Upgrade Failures and Resume Upgrade ................................................................................. 7

Exercise 4 Explore Visual Upgrade Features ................................................................................................................ 10


3/14


Page 1 of 12


Objectives After completing this lab, you will be better able to:

Verify existing 2007 farm and content upgrade readiness through the useof the 2007 pre-upgrade checker command

Verify existing 2010 farm readiness to upgrade specific content databasesusing the 2010 Test-SPContentDatabase cmdlet

Initiate upgrade for individual content databases using the 2010 STSADMo addcontentdb command

Review the upgrade session status using the improved CentralAdministration web site Upgrade Status page

Initiate upgrade for multiple individual content databases using multiplePowerShell sessions to trigger parallel upgrade sessions

Troubleshoot an upgrade failure due to missing features, and how torestart upgrade for individual content database

Use Visual Upgrade features to switch sites from the 2007 product lookand feel to the new 2010 product user interface

ScenarioThis lab provides an introduction to the Microsoft SharePoint Server 2010

upgrade infrastructure, and demonstrates some changes and improvements in

the upgrade and patching system.

Learn about the administration experience for upgrading from Microsoft Office

SharePoint Server 2007 (MOSS 2007) to Microsoft SharePoint Server 2010,

including verification of upgrade readiness at the farm and content databaselevel, using command line upgrade actions, and reviewing upgrade status and

logs.

Estimated Time to

Complete This Lab60 Minutes

Computers used in this

Lab demo2010a

The password for the Administrator account on all computers in this lab is:

pass@word1


4/14


Page 2 of 12

Exercise 1

Verify Upgrade Readiness

ScenarioIn this exercise you will review a pre-created pre-upgrade checker report from a MOSS 2007 SP2 farm, and will also

check an existing content database for upgrade readiness from within SharePoint 2010.

Tasks Detailed Steps

Complete the following

tasks on:

demo2010a

1. Review Pre-UpgradeChecker Report

Note: Review a pre-upgrade checker HTML report to gain an understanding of

existing components and server side customizations installed in that farm, and to

identify potential upgrade issues when upgrading content from that farm to this

SharePoint 2010 farm.

a. Open Windows Explorer by clicking Start > Computer > Local Disk (C:).b. Navigate to the following folder:c. C:\ITPro\Upgrade\Exercise 1\Reportsd. Double click on the PreUpgradeCheck.htmfile to open it. Internet Explorer will

open to display the pre-upgrade checker report. (If you receive the Active

content warning from IE, click Yes)

e. Scroll through the sections of the report noting the various items it listed as beingimportant to consider for upgrade readiness including, among other important

items, installed language packs, features, and site definitions. Note: Pay special

attention to any failed upgrade checks as these indicate areas that will require

additional attention before beginning upgrade.

f. Close Internet Explorer.


5/14


Page 3 of 12


2. Create a new WebApplication for

Restore

Note: In order to restore the backups, we need to create a new web application

where the restored sites will reside.

a. Open Central Administration by clicking Start > All Programs > MicrosoftSharePoint 2010 Products > SharePoint 2010 Central Administration.

b. Click Application Management in the quick launch bar on the left.c. In the Web Applications section, click Manage web applications.

d. In the Ribbon, click the New icon at the left. A Create New Web Applicationwindow will open.

e. In the Authentication section: Leave Classic Mode Authentication selectedf. In the IIS Web Site section: Choose Create a new IIS web siteg. Set the port to 80h. Set the Host Header to moss.contoso.comi. In the Application Pool section: Select Create new application pool.j. Select Configurable.k. Choose CONTOSO\sp_demo2010aapppool from the drop down.l. In the Database Name and Authentication section:Set the Database Name to

WSS_Content_MOSS.

m. Scroll to the bottom of the page and click OK. It may take a few minutes to createthe web application.At the Application Created screen click the OK button.

3. Test Existing MOSS2007 Content

Databases

Note: Now you will test several MOSS 2007 SP2 content databases using the Test-

SPContentDatabase cmdlet to verify the readiness of the SharePoint 2010 farm to

upgrade the content databases.

a. Open the SharePoint 2010 Management Shell by clicking Start > All Programs >Microsoft SharePoint 2010 Products > SharePoint 2010 Management Shell .

b. Within the console, run the Test-SPContentDatabase PowerShell cmdlet to checkan existing MOSS 2007 SP2 content database:

Test-SPContentDatabase -Name WSS_Content_1 -WebApplication

http://moss.contoso.com

c. Notice that no errors are reported after the check on WSS_Content_1.d. Repeat the above procedure in steps 2 and 3 for two more content databases

with the following commands:

Test-SPContentDatabase -Name WSS_Content_2 -WebApplication


6/14


Page 4 of 12



Test-SPContentDatabase -Name WSS_Content_EN -WebApplication


Scan through the results noting the various items listed as being important to

consider for upgrade readiness including missing language packs, features, site

definitions, and assemblies.

Note: Many more issues show up in these additional two databases. Later in Exercise

3 you will identify the upgrade issues from the upgrade logs after attempting

upgrade, and will then solve the issues of missing site definitions and missing features

by installing them and resuming upgrade.


7/14


Page 5 of 12

Exercise 2

Gain Upgrade System Familiarity

ScenarioIn this exercise you will attach the existing, previously checked MOSS 2007 content database to the SharePoint

2010 farm to initiate upgrade, and will review upgrade status while the upgrade is occurring. You will also upgrade

two content databases in parallel to demonstrate the new multi-session upgrade ability.



tasks on:

demo2010a

1. Review Previous andCurrent UpgradeStatus

a. IfCentral Administration is not open, click Start > All Programs > MicrosoftSharePoint 2010 Products > SharePoint 2010 Central Administration.

b. If a credential prompt appears, sign in as contoso\administrator with a passwordofpass@word1

c. On the Central Administration home page, click on the Upgrade and Migrationheader.

d. Click on the Check upgrade status link, under the Upgrade and PatchManagement heading.

e. Switch back to the SharePoint 2010 Management Shell.f. Within the console, run the following STSADM command to add an existing

content database:

stsadm -o addcontentdb -url http://moss.contoso.com -

databasename WSS_Content_1

g. Once the database attach command has been issued, return to the UpgradeStatus page and notice that the upgrade event you triggered shows up as a

distinct upgrade session status row with a status of In Progress.

Note: It may take a minute or so for anything to show up on the Upgrade Status

page, as the data refreshes in the background periodically.

h. Review the upgrade session data, paying special attention to the fields for Status,Errors, and Warnings, as these indicate items that may require attention from the

farm administrator.

Note: This upgrade may take approximately 5 to 8 minutes to complete, but you can

continue the lab at this point. The progress of the upgrade is shown in the

Management Shell window.


8/14


Page 6 of 12


2. Upgrade TwoContent Databases at

the Same Time

a. In Windows Explorer, navigate to the folder at the following path:C:\ITPro\Upgrade\Exercise 2\

b. Right-click on the ParallelUpgrade.ps1 file and select Run with PowerShell. Thescript will launch in a new PowerShell command window, and then shortly

thereafter will launch a second command prompt window to perform to content

database upgrade sessions in parallel, one per command window.

Note: The two upgrade sessions are each using differing Visual Upgrade settings to

allow for visual comparison between similar content later in Exercise 4.

c. While the parallel upgrade script is in progress, you can switch to the UpgradeStatus page in the Central Administration web site to watch the progress being

refreshed approximately every minute.

d. Wait for both command windows to close before continuing. Each window willclose automatically. It is normal for one window to close before the other. This

script may take approximately 5 to 8 minutes to complete. Progress can also be

monitored in each of the command windows opened.


9/14


Page 7 of 12

Exercise 3

Troubleshoot Upgrade Failures and Resume Upgrade

ScenarioIn this exercise you will troubleshoot an upgrade issue by reviewing the upgrade log and then installing a missing

solution and restarting upgrade from the command line.



tasks on:

demo2010a

1. Open Failed UpgradeLog

a. On the Check upgrade status page, select the Status text of individual rows in theUpgrade sessions table one at a time until you find the specific upgrade session

for the content database WSS_Content_EN.

Note: You can find out which database the session was for by looking at either the

Starting Object or the Command Line field in the Upgrade Sessions table.

b. Near the bottom of the Selected upgrade session details table, select thecomplete path and filename of the upgrade log file from the Log File row (Hint:

triple clicking on the table cell will select the entire path and filename).

Note: This log file is located the folder C:\Program Files\Common Files\Microsoft

Shared\Web Server Extensions\14\LOGS\

c. With the text of the path selected, right-click and select Copy.Note: This page automatically refreshes every 60 seconds, so you will need to be quick

in selecting the text and copying it before the next page refresh.d. Open the log by clicking the Start button, paste the copied text into the Start

Search text box, and press Enter.

e. Scroll through the upgrade log from top to bottom noting that there are variouswarnings and errors.

Note: Pay special attention to any lines with the [ERROR] status as these indicate

items that failed during upgrade and will require additional attention to complete

upgrade.


10/14


Page 8 of 12


2. Find Errors in theUpgrade Log

Note: Use the Find ability of Notepad to quickly identify error entries in the upgrade

log to determine the cause of the upgrade failures.

a. Click in the text area of Notepad, and press Ctrl + Home go to the top of the file.b. Click on the Edit menu and select Findc. In the Find window, type the following: [ERROR]d. Click the Find Next button to find the first warning if it exists. If any errors are

found you will see their text highlighted. Note the description of the cause of the

errors you are seeing. In this case, the errors indicate missing site templates and

missing features.

e. Normally you would want to repeat the Find Next procedure until you arepresented with a Notepad dialog that indicates Cannot find *ERROR+. You would

then repeat the process looking for [WARNING] status on items on the log.

However, in this case there are many errors and warnings, so you will need to fix

these errors before continuing with later exercises in the lab.

Note: If errors or warnings are found in an upgrade session, you should always start

with the first occurrence of an error and work down through the upgrade log to

determine consequences such as further errors or warnings. In this case, the large

number of upgrade failures was caused by missing Solutions, which you will now

install.

f. Close Notepad.3. Install Missing

Solutions and

Features

Note: Install the missing solution based site definitions and features to allow the

content to be upgraded without the previously identified failures.a. Open the folder C:\ITPro\Upgrade\Exercise 3\F40\b. Right-click on Install.cmd and select Run as administrator.c. The script will launch in a new command window. This script is installing the

Fantastic 40 administrator deployed features onto the SharePoint 2010 farm and

deploying them locally.

d. Wait for the script to finish and then press Space to close the command windowbefore continuing. This script may take approximately 2 - 4 minutes to complete.

You may be prompted for credentials, if so type Administrator for the username


11/14


Page 9 of 12


and pass@word1 for password. You can close the window after supplying the

credentials.

4. Rerun Upgrade forContent Databases

a. Open the following folder: C:\ITPro\Upgrade\Exercise 3\b. Right-click on the ResumeUpgrade.ps1 file and select Run with PowerShell. The

script will launch in a new PowerShell command window.

c. You will be prompted to confirm the upgrades in the PowerShell window. Type Yand press Enter. The first database will successfully upgrade, and you will beprompted to confirm the upgrade for the second database. Type Y and press

Enter again. (You will be prompted to upgrade the WSS_Content_1 again. This

database contained no errors so you can either choose Y or N. Either option will

skip the upgrade)

d. This script will find and attempt to resume upgrade on the two content databasesthat had errors previously. It is using the PowerShell cmdlet Upgrade-

SPContentDatabase to upgrade currently attached databases. This upgrade pass

should be much faster, as only the failed items and their children will need to be

upgraded.

e. Wait for script to finish and the command window to close before continuing .This script should only take a minute or so to complete.

f. Once the upgrade script is complete, return to the Upgrade Status page in theCentral Administration web site to verify that the content has upgraded without

errors or warnings.

g. Close Internet Explorer.


12/14


Page 10 of 12

Exercise 4

Explore Visual Upgrade Features

Scenario

In this exercise you will work with the new Visual Upgrade feature to preview and then change a site over to the2010 user interface.



tasks on:

demo2010a

1. Review an upgradedsite using the 2007

user interface

a. Open the folder C:\ITPro\Upgrade\Exercise 4\b. Double click on theEnglish Sites.htm file to open it. Internet Explorer will open a

page that lists various site collections that you recently upgraded in the previous

exercises. These sites include ones based on the built-in templates, and others

using the Fantastic 40 template and administrator-deployed features.

c. From Internet Explorer, on the left side of the table, right-click on the link forEnglish F40 Templates - MOSS 2007 UI, and then select Open in New Tab.

d. If a credential prompt appears, log in as contoso\administrator and a passwordofpass@word1

e. Look at the page, noting that the user interface is still using the MOSS 2007 lookand feel. The content database that contains this site collection was initiallyattached and upgraded with the -PreserveOldUserExperience option set to true,

which is the default behavior.

f. Click the Business Performance link from the tree view in the quick launch.


13/14


Page 11 of 12


2. Review an upgradedsite using the 2010

user interface

a. Switch to the tab in Internet Explorer displaying the list of sites. Right-click on thelink for English F40 Templates - MSS 2010 UI and select Open Link in New Tab.

b. Look at the page, noting that the user interface is displaying the new MOSS 2010user experience.

c. Select the link to the site Business Performance from the tree view on the lefthand side of the page.

Note: The content database that contains this site collection was initially attached

and upgraded with the -PreserveOldUserExperience option set to false.

d. By switching between the two tabs displaying upgraded sites, note that even afterupgrading to the new user experience, the data remains the same and the web

parts are in the same layout.

Note: It is important to note that some pages may not attain their new userexperience due to several types of customizations including incompatible script or CSS

dependencies.

3. Use the VisualUpgrade Preview

Note: Now, you will use the Visual Upgrade Preview feature to temporarily switch an

upgraded site to the SharePoint 2010 user experience.

a. Switch to the tab displaying the site with the MOSS 2007 user interface. Selectthe Site Actions dropdown, then select the Visual Upgrade item.


14/14


Page 12 of 12


b. At the bottom of the page, select the Preview the updated user interface optionand then click the OK button. Youll be taken back to the page you were

previously on, with an upgraded look and a colored notification on the page

indicating that it is in a preview state.

c. Take some time to explore the visually upgraded Business Performance site.

d. By switching between the two tabs displaying upgraded sites, note that afterupgrading to the new user experience, the look and feel of the sites should be thesame, the data remains the same, and the web parts are in the same layout.

e. Close Internet Explorer.

virtual lab - upgrade

Documents