manual

10 www.microsoft.com/sharepoint
is ready to be upgraded. He does discover some issues where he is not following
SharePoint best practices around large lists, and is able to examine the list and find
solutions. Because preupgradecheck is a read-only tool, it is safe for him to run it often,
confirming his progress as he works to mitigate the issues that have been raised.
Now that Randy has his databases in good shape, he begins building SharePoint Server
2010 on his new hardware. After he has established this farm, configured all necessary
service applications, and provisioned his required Web applications, he can begin the
process of testing upgrade. Because he has chosen the database attach method, he
performs a backup of his database from production and restores it to his new computer
running SQL Server. On this SQL Server, he takes advantage of the Windows PowerShell
cmdlet Test-SPContentDatabase to report any potential issues with attaching the
content database to his newly provisioned Web application. From the output of this
command he finds he has not installed all of the necessary Features on his new server.
He is now able to install the necessary Features avoiding a failed upgrade.
With all of the necessary pieces now in place, Randy performs his first upgrade by using
the Windows PowerShell cmdlet Upgrade-SPContentDatabase. After the upgrade
concludes, he reviews the errors-only upgrade log and then the full upgrade log, which
gives him both a focused picture of any issues that occurred and the line-by-line story
that he can review to get a better understanding of what happened during the upgrade
process.
With the upgrade cmdlet successfully completed , he now can open the site and review
his content. The first thing he notices is that his site looks exactly as it did in the Office
SharePoint Server 2007 farm, thanks to the Visual Upgrade features. To see what his site
will look like with the SharePoint Server 2010 look and feel, he goes into Site Settings
and selects the preview option. This gives Randy the opportunity to confirm that
everything looks appropriate with the new visuals applied. If he is happy with the results,
he can make the change permanent; if he feels he will need to make adjustments to the
site, he can turn preview off and return to the Office SharePoint Server 2007 interface.
The feature is set at the individual site level, allowing Randy to make very granular
choices. He can also use Windows PowerShell to script the changing of the visuals.
After Randy finishes working with the various business content owners to validate the
upgrade process and works through any issues, he is ready to plan his production
upgrade schedule. His plan is to notify his users and then take his Office SharePoint