We’ve already been introduced to Yaiton Ngo, Quest’s SharePoint administrator. We saw how uses Site Administrator for SharePoint to manage the entire Quest SharePoint environment and make the case for more SharePoint resources. We also saw how he has been able to help content owners see who’s accessing their content and clean up permissions. Our final Inside the SharePoint Admin’s Studioinstallment will revisit Ngo once again as he talks about using Site Administrator for SharePoint for migration planning.
Using Site Administrator for Migration Planning
This whole thing started because Quest Software is in the planning stages for migrating to SharePoint 2010. Ngo is using Site Administrator for SharePoint to help with pre-migration planning, during the migration, and after the migration is complete. Let’s take a look at how he uses this tool in each migration phase.
So Ngo has been using Site Administrator to pull reports around performance, capacity planning, number of site collections, sites and more from the Information Portal. Now he’s using that data to help him prepare for the Quest migration to 2010.
One of the areas of concern is performance. Ngo wants to ensure that the performance issues he is seeing with 2007 are not a concern with 2010. “Site Administrator trend growth reports tell me we’ll soon be out of space if we don’t address capacity before migrating,” said Ngo. “It helps me understand the need for improved hardware to meet this growth. From there I can develop our specifications document.”
“We are trying to avoid some of the mistakes we made in 2003 migration to 2007,” he continues. “We used the Microsoft recommendations but didn’t plan for the growth.” With Information Portal’s trend growth report he can safely predict capacity needs at the current growth rate.
Furthermore, Site Administrator also enables Ngo to accurately scope the migration project. “We have so many sites, over 700 site collections and 2000 sites and workspaces, so we need to get critical reports of permissions, user activity, site and content relevancy and growth trends. 2007 out of the box doesn’t give you any critical reports for scoping a migration project.”
On top of this, Site Administrator helps Ngo to clean up old and unused sites, restructure sites into a more orderly hierarchy and clean up user permissions for a smooth upcoming migration.
Manage As You Migrate
Once the migration is underway, Ngo plans to use Site Administrator to analyze the data that is being migrated. “We can use Site Administrator to make sure that the items in a site are in fact being migrated.”
Using the Site Detail report and Site Collection report in the Information Portal, Ngo can see how many sites have been migrated and how many are left. With the Information Portal, he can easily switch between the SharePoint 2007 farm and the SharePoint 2010 farm reports and compare what has been migrated to what is awaiting migration.
Post Migration Administration
Similar to using Site Administrator during the migration process, using this tool post migration allows Ngo to ensure that no site was left behind. He can review the old farm, look at all the numbers, run a report against the new farm and see if the numbers match.
Because he has already been using Site Administrator for SharePoint with the 2007 farm, he can still use this same tool to manage the 2010 farm. Essentially, there is no learning curve.
The More You Know…
So the moral of this story – Site Administrator for SharePoint is a great tool to have before, during and after the migration process. Site Administrator can help…
- Scope the true size of the migration project
- Plan for future growth
- Restructure content pre-migration to ensure a clean migration
- Review what has already been migrated and what is left to migrate
Spread the word, Site Administrator for SharePoint just made our SharePoint administration that much easier!