.jpg)
Migrating SPS 2003 to MOSS 2007 can be tricky to begin with. Now throw in Project Server 2003, PWA Sites, and templates that don't exist in your MOSS 2007 environment. All is not lost and it's actually easier than you might think. In this scenario we again will be using the database upgrade method. (This entire scenario is based upon the assumption that you do not and probably will not have Project Server 2007 installed with your MOSS 2007 deployment.)
Here's what I did:
So let me set up the scenario. You have;
SPS2003 with Project Server 2003 and a mix of default templates and PWA templates
MOSS 2007 with NO Project Server and the same mix of default templates and PWA templates that need to be migrated into MOSS 2007
What you will need; (for a database migration)
SPS 2003
SQL 2000/2005
Winrar, Winzip, etc...(compressing backed up databases before you move them decreases the risk of corrupting your databases)
Project Server 2007 (Trial or Licensed...A trial version will work on a server with other trial licenses. You can not mix and match trial versions with licensed versions.)
MOSS 2007
On to the fix;
BEFORE YOU PERFORM ANY OF THESE STEPS MAKE SURE YOU HAVE CLEAN BACKUPS OF EVERYTHING SHAREPOINT!!!
Install Project Server on a Development Server or VM with MOSS 2007 installed
Run PSConfig
This Reconfigures the Farm to work with Project Server 2007
Installs Templates, Files, Data
It will install key files to;/config/upgrade/pwsupgrade.xml
/template/1033/xml/webtemppwa.xml
/template/site templates/PWA and PWS
/template/features/PWA, PWAProposals, PWS, PWSCommitments, PWSCTypes, PWSocLibs, PWSFields, PWSIssues, PWSRisks
Copy Installed Files
Uninstall Project Server 2007
(You can leave it installed if you wish, but if you want to uninstall it continue to the next step)
(Uninstalling Project Server 2007 kills the SharePoint Farm…nothing in IIS, no CA, nothing…all you have left is DB’s in SQL)
***IMPORTANT***
At this point SharePoint is no more, you won't be able to access sites or CA
***DON'T WORRY***
IISReset
Move copied files to correct locations on your Production Server…/upgrade, /xml, /site templates
Re-run PSConfig (THIS WILL BRING YOUR SHAREPOINT ENVIRONMENT BACK)
Connect to existing Farm
Reattach SQL Server
Reattach Config_DB
Run through PSConfig Steps 1-9
IISReset
ReDeploy Solutions (the Uninstall will retract all deployments)
Restore Migrated DB to Development
Attach Migraged DB to Development
At this point in time you should now be able to browse to your SPS 2003 PWA Sites in your Development MOSS 2007 environment
If everything seems fine in Development restore and attach to Production
-Brian Grabowski
Subscribe to:
Post Comments (Atom)
Posts
3 comments:
Excellent post, Brian! thank you!
How are these sites going to work on the Production environment? I would think that the files for PWA site and list templates would be missing...?
This is a great walk through and has helped me tremendously.
Just a few qualifiers I would like to add from my own experience (and these may seem obvious to some; but as a newbie it took some time to figure out the detail):
1. Before running PSCONFIG, make sure the Site Administrator for EACH SITE has dbcreator and dbsysadmin and or setupadmin on your target SQL server (this will avoid ACCESSDENIED error messages)
2. On your SQL server, grant NT AUTHROITY\LOCAL SERVICE dbcreator, setupadmin / dbsysadmin rights for the same reason as point 1
(I'm not a DBA, so I've probably overkilled on the rights)
3. For a standalone environment run PSCONFIG -CMD SETUP
I would like to thank Tyler Holmes and his blog article "Deploying WSS/Moss 2007 to an Existing Install of Project Server 2007" for pointing me in the right direction on troubleshooting the ACCESSDEINIED issue.
available here http://blog.tylerholmes.com/2008/04/deploying-wssmoss-2007-to-existing.html for the information on ACCESSDENIED errors
Nathan.
Post a Comment