Installing PS 2007 to existing WSS 3.0 (not MOSS) Farm

[jremmc]

Our WSS "farm" is two-tier (1 front-end WSS, 1 back-end SQL 2000 SP4).
http://servername is our Intranet home site, and http://servername/sites/
path is for team sites. I want to install PS 2007 without disturbing existing
WSS structure, so that PS 2007 is at http://servername/pwa path.

I cannot find/no one including MS has written an article on how to install
PS 2007 to an existing WSS 3.0 farm that is has existing, actively used WSS
sites. There's info on PS 2007 after MOSS, and MOSS after PS 2007, but no PS
2007 into WSS 3.0 only. Even the PS 2003 to PS 2007 gradual migration
scenario articles don't clarify the PS 2007 onto WSS 3.0 steps (what to
choose in Config Wizard and Central Admin, particularly in order to ensure
not affecting existing WSS sites/structure.)

I think I understand most of the install procedure, but I've lost it at the
Central Admin steps. After installing PS 2007 binaries and running Config
Wizard (join existing farm, select existing SQL, choose Complete to get
web/application services on same server), in Central Admin do I:

1. create new web application? Or do I use existing WSS web application?
2. use existing web site? (which is WSS, which is using port 80.)
3. create new application pool? Or do I use existing WSS application pool?

Thanks,
jremmc

 

[Paul Conroy]

I've never done it, but it should go something like this:-

Install PS2007 Binaries onto existing WSS server.
Ensure you install WSS/PS service pack 1.

Create new Web Application for SSP (do not extend/create site collection)
Create new Admin Pool for SSP Web App.
Create new SSP using website created above.
Under SSP admin, create new instance of PS using existing web app.

HTH

Paul

 

[jremmc]

Thanks, Paul, that helps. I'll give it a go.

I've never done it, but it should go something like this:-

Install PS2007 Binaries onto existing WSS server.
Ensure you install WSS/PS service pack 1.

Create new Web Application for SSP (do not extend/create site collection)
Create new Admin Pool for SSP Web App.
Create new SSP using website created above.
Under SSP admin, create new instance of PS using existing web app.

HTH

Paul

 

[jremmc]

ack, sorry, need a bit more clarification.

I understand from your reply that for the SSP, I create a new web site when
creating a new Web Application to host the SSP. But, when creating the web
application to host the *PWA site*, do I choose Use an Existing IIS Web Site?
My immediate reaction would be yes, because I want to use the existing WSS
web site on port 80, don't I?

If I go into Central Admin on my WSS deployment now, and pretend to create a
new web application, here's my choices:

If I choose Use an Existing Web Site, only "Default Web Site" is available
under Existing; there's no choice "SharePoint - 80". (If I look in IIS
Manager, Default Web Site is stopped and SharePoint - 80 is running. So,
Default Web Site as choice is confusing.)

If I choose Create New Web Site, I get http://servername:randomport# (not
80), which leads me to believe I would end up with
http://servername:randomeport#/pwa, not the http://servername/pwa that I
want.

If I do select Create New Web Site and change the randomport# to 80,
wouldn't that then overwrite the existing http://servername content (our WSS
Intranet home site)?

Finally, assuming that dilemna is resolved, when creating the site
collection for PWA, I need to first Define New Managed Path /pwa, yes?

Thanks,
jremmc




Thanks,
jremmc

 

[jremmc]

Paul, hope you see this.

ok, I got it now, and got PS 2007 installed into existing WSS 3.0 on my
(hobbled-together) test network. Not without hiccups. For benefit of others:

Note: First (which I did last week thanks to the blogs), I removed and
deleted the MS WSS 3.0 template Project Workspace solution that I had
installed along with the other "Fabulous 40" templates.

Using Technet PS 2007 Library docs, primarily "Deploy Project Server 2007 to
a server farm environment":

Preliminary steps: Having created the WSS accounts (and the SQL Service
account) needed when I installed WSS 3.0, I only had to create the SSP
Application Pool and SSP Service accounts. I chose to create two separate
accounts. The Technet PS 2007 Library doc "Plan for administrative and
service accounts" indicated the install procedure would set the proper
permissions on the accounts (and apparently it did).

Installing Binaries: Ran fine. I entered product key (used Technet
evaluation), accepted agreement, then Install skipped "Choose the
installation" page (where advanced or custom would have been selected) and
went right to Server Type page, with Complete as choice defaulted to
(stand-alone was not an option as WSS is farm), then I clicked Install Now,
and Install ran and finished fine.

Running Configuration Wizard: Got the Welcome page, got the Warning about
stopping services, Install skipped "Connect to a server farm" page and went
right to Specify Configuration Database Settings, with the DB server (we only
have one) and DB name already filled in (and the Advanced button was grayed
out). Clicking Next started the configuration process, so that means the
Specify Database Access Account page was skipped, the Configure SharePoint
Central Admin page was skipped, and the Completing Wizard/verify settings
page was skipped.

Configuration Wizard then failed at Step 8 of 9. The Log that Event Viewer
pointed to was not very helpful; just said failed on B2B ugrade timer job.
Googled and apparently that is a generic error (?), but I found one user
whose issue was that the account under which the WSS Timer Service runs did
not have admin rights on front and back end servers, so I added the account
to administrators group on both servers because improper permissions is a
common cause of failure. Then I also found out about the "other" log file
(Upgrade.log) which the Event Viewer error message did not reference (and
which MS says is in the BIN folder but was in the Logs folder). That log
indicated the upgrade failed when trying to upgrade the individual sites and
also indicated (instinct told me) the issue was caused by the GroupBoard
Workspace subsites (created from the MS template freebie). 3 of my 4 test
sites had a GB subsite and from what I could interpret of the log, the
upgrade succeeded on the one that did not have a GB subsite. So, I deleted
all the GB Workspace subsites, reran Configuration Wizard and the Wizard
completed successfully.

Note: since I added WSS Timer Service account to admin group *and* deleted
GB Workspaces at same time, the configuration wizard failure could have been
a combination of both.

Central Admin configuration part:

Central Admin opened fine and presented me with message: ! Server Farm
Configuration Not Complete ! -- and with 3 new Administrative Tasks: Initial
Deployment: Add Servers to Farm, Initial Deployment: Assign Services to
Server, and Configure Server Farm's Shared Services. I read the Tasks,
determined I should simply finish walking thru Technet document first (which
did not mention these would appear) and so I did.

Configure Farm Services: went fine.

Create the Web application to host the Project Web Access site: I skipped
this entire step and went straight to Create the Web Application for the SSP.
(This entire step is the part of the Technet document that confused me, but I
had an epiphemy after my second (ack!) post that this step was for a clean
install and as I already had WSS, the entire step had already been done when
I installed WSS.)

Create the Web Application to host the Shared Services Provider: went fine.
I changed the suggested IIS web site name to a more meaningful one
(SharePoint-SSP) and port # to easier to remember one, chose NTLM as that is
how WSS is set up, took the suggested application pool name, entered the user
account/password I had created for purpose, changed DB name to more
meaningful one, and chose the WSS server as Search server.

I got a message about needing to do an IIS Reset /noforce before accessing
the new site, but since the document didn't say to do this, I didn't.

Create the Shared Services Provider: went fine. Kept defaults.

Provision the Project Server 2007 Site on the farm: went fine. I changed PWA
to pwa for path (not sure was case sensitive and I prefer small letters). The
Administrator Account info was already filled in with the WSS admin account.
Had to fill in SQL server name in Primary Database section.

Provisioning took a while (after few minutes of looking at "waiting..." I
went away for a while to help a user and when I got back provisioning had
completed.)

At this point, I did a Reset IIS /noforce.

I was able to log into pwa URL with account I used to install PS 2007 with
(as per documents). I was also able to get to my WSS sites fine.

And so there you have how it went for me to set up PS 2007 in a two-tier WSS
3.0 farm.

Thanks,
jremmc

 

[Jouledoc]

hello jremmc,

i think i have same problem with you.

i have existing installation of WSS3.0 and i download trial version of
project server 2007. we are trying to use project server.

but it seems the instalation so hard...

if you don;t mind could you make a screen capture of instalation WSS 3.0 and
PS 2007

thx

 

[jremmc]

I don't have a screen capture, and I don't know what you may have installed
in your environment, e.g. SP1 (I have not yet installed SP1; that is my next
step). But if you note what I did, that should help.