I played around with tool and was able to successfuly deploy a multi-instance
install; one production, one demo. The install uses seperate project
databases, seperate sharepoint databases, and uses the same wss admin
database. You can set it up using a seperate w3 site within iis or you can
add it to the existing site. I chose to use the same w3 site.
I first created a new project database, populated it by running setupdb,
which is documented in the install guide under Deploy the Database-> Creating
the project server database manually. Assuming you are wanting to run sp1
for production, make sure to update the demo database as well. I forgot to
do this and had some major issues when trying to add a new project from
project pro.
After getting the database created and updated, make sure to assign
MSProjectServer & MSProjectRole roles to the new databases. Run editsite,
create the site. After the new wss instance is created, go to the project
install, go to Microsoft WSS -> WSS Configuration Wizard and run this against
the new wss intance.
If you are having database issues, verify your MSProjectServerUser and
MSProjectUser passwords. Run the test and also verify those roles have the
proper permissions. Also, I noticed that on my production instance (the one
MS installed), if I would run a test, it would fail. By default, my install
had MSProjectServerUser in the MSProjectMember Role text box under editsite.
I changed this from MSProjectServerUser to MSProjectUser and it passes.
Keith