When upgrading to SharePoint 2010 from SharePoint 2007, there are lots of things you can before upgrading to resolve issues itself prior to upgrading. And there are things you can do after upgrade to verify upgrade went okay as well. Obviously, there needs to be involvement from the end users to check the sites and verify that things upgraded well.
As an administrator, you have things available to you after the upgrade such as the upgrade logs and the upgrade status page in Central Administration.
There is one additional method that a lot of people don’t know about and it’s the stsadm command localupgradestatus.
Things to know:
- It’s going to dump out a lot of info, so it’s smart to make sure you output it into a txt file
- It doesn’t take any parameters
- It needs to be run on each server on the farm
To Run The Command:
stsadm –o localupgradestatus >upgradestatus_output.txt
<object> <name>demo2010a</name> <type>Microsoft.SharePoint.Administration.SPServer</type> <level>1</level> <status>OK</status> </object>
So what we have listed are all of the objects for upgrade (example above), as well as the summary.
- Name: the name of the object
- Type: the type of object
- Level: the upgrade priority of the object
- Status: the upgrade status. OK means it’s upgraded. Needs Upgrade, obviously means that it’s not.
The summary will detail the content dbs and their status, site collections and their status, and a object count over all.
 content database(s) encountered.
 content database(s) still need upgrade or cannot be upgraded.
 site collection(s) are contained in the content databases.
 site collection(s) still need upgrade.
 other objects encountered,  of them still need upgrade or cannot be upgraded.