Even if you are not migrating from Project server 2003 the Virtual Migration Environment (VME) has something for you! One key point for migration (migration usually refers to 2003 to 2010) or upgrade (2007 to 2010) is that “Script 9” should always be run and acted upon. This script identifies some known conditions in your 2007 system and this is just as applicable if you have come through the VME, or are just starting from 2007 and looking to upgrade to 2010. These are the conditions it identifies:
- Office Project Server 2007 is updated to Service Pack 2 and the October 2009 Cumulative Update
- Projects not saved and published since the installation to Office Project Server 2007 of both Service Pack 2 and the October 2009 Cumulative Update
- Lookup tables that are using names that are reserved in Project Server 2010
- Custom field names that are reserved in Project Server 2010
- Office Web Components (OWC) views in Office Project Server 2007 that need to be migrated to Excel Services for use in Project Server 2010
- User accounts with forms-authenticated login names
- Team names that have no associated lookup table or a value
- Office Project Web Access Portfolio Analyzer OWC views in Project Server 2003 that may need to be migrated to Office Project Server 2007
Even though the title of the TechNet page for the scripts at http://technet.microsoft.com/en-us/library/ff700189.aspx does say “optional” – treat this as being optional in the same way as paying taxes. The penalties for not doing it can be quite hard. This also goes for your 2007 to 2010 upgrade even if you did not start in 2003, nor use the VME.
Another tip for the VME is that you could use this as a practice ground for your 2007 to 2010 upgrade, even if you are not starting from 2003. It is after all just a pre-configured Project Server 2007 system. You could add your own Project Server and SharePoint databases, provision a PWA site and test out the upgrade to 2010 – rather than having to build up your own test environment. Give it a try!