Using Project Web Access

[Tim]

I've just installed Project Server 2003 as well as PWA and now I'm realizing
that Project Professional may be needed by all my users? I thought just
purchasing Project2003 server alone would do the trick, but then I had to
purchase Project Professional to publish projects. Makes sense to me since
it's not included in the requirements.

So now I have a few projects created, but end user use of even Project Web
Access seems incomplete in features or really weird to look at.
http://office.microsoft.com/en-us/projservadmin/HA011643821033.aspx
states, "You can perform all of the activities that are available to members
of the Team Members security group by using Project Web Access."

Actually no you can't. Project Web Access is really hard to use. There's
so much to it.
1) I can't open a task within a published project. It only displays the
task name, but I can't view the details.
2) I already created an extended SharePoint site for the project server, but
now a message states, "The documents, risks and issues features in Project
Web Access use Windows SharePoint Services. A Windows SharePoint Services
site needs to be created for your project before you can share project
documents or track project risks and issues. Site creation takes a few
minutes, so if the project was just published, wait a few minutes and then
visit the page again. Otherwise, contact your server administrator." whenever
I click on risks, issues, or documents.
3) I can't adjust tasks or anything else or view any details. It's like
everything in PWA is ultra deluxe limited read only.

So does that mean I need a separate SharePoint site for EACH PROJECT???
That's a bit of a pain.

So what can PWA users actually do without Project Professional loaded on
their local system? By comparison it seems like Outlook Web Access can be
used without the Outlook client and do EVERYTHING to manipulate their mailbox.
First I buy Project server, then the CALs, then load SQL desktop edition,
then Sharepoint. Now I have to go back and spend a couple more grand on
Project Professional? Is any of this going to ever be intuitive? I'm the
only IT person in this shop and with other projects, my fear is rolling this
out and it 1) not be useful and 2) spend my entire life answering questions
to such a complicated system.

Recommendations?

 

[Scott m Wagner - EPM Consulting Services]

Tim,

The Microsoft "Enterprise Project Management" EPM Solution can be complex.
It can also be fairly small and easy to maintain. This really depends on the
type of implementation. If you have no history with this solution and you are
not planning on using the available documentation and invest the time to
understand this solution. I would suggest one of two things:

1) Contact a Microsoft EPM Partner in your area who can advise you.
or
2) Try a different solution. This one is not for you.

I am not trying to offend you in any way but as you stated this in not a
simple install and use solution, people in your organization will need to
have input and will need to be trained in how to use this solution. The
application also requires administration. Again, depending on the type of
implementation this can range from a small task for one person and can be
added to their responsibilities or in a large organization this could be the
full time job of two or more people or added to the responsibilities of an
existing organizations helpdesk.

If you are interested in learning more about the solution for yourself,
please read the guides. They are available for download here
http://www.microsoft.com/technet/prodtechnol/office/project/2003/reskit/default.mspx

 

[Dale Howard [MVP]]

Tim --

I'm not sure who told you that you didn't need to use Microsoft Project
Professional 2003 with your Project Server system, but he/she is sadly
mistaken. In addtion to the Project Server software, you must also purchase
Microsoft Project Professional for your each of your Project Server
administrators and each of your project managers as well. You do not need
to purchase this software for anyone else, such as executives and team
members, as they will use the PWA interface. Your Project Server
administrators will use Microsoft Project Professional 2003 to create
enterprise fields and outline codes, and to build the Enterprise Resource
Pool. Your project managers will use this software to create, publish, and
manage enterprise projects.

When a PM creates and saves a new project, the system automatically creates
a WSS subweb that hosts Risks, Issues, and Documents associated with that
project. If you set up the system correctly, site creation is automatic.

Beyond this, if you seriously intend to use Project Server 2003, I would
strongly encourage you to refer to the following FAQ for documentation and
training on the software:

http://www.projectserverexperts.com/Shared Documents/PS2003Documentation.htm

Hope this helps.

 

[Tim]

Microsoft did on the actual box for Project Server 2003. It makes zero
mention that Project Professional is needed. I scoured the outside of the
box. It offers hardware requirements, makes mention of SharePoint and SQL,
and that's it. Even on the back of the media case in fine print it states
and I quote, "* Requires Windows Server tm 2003 running Windows SharePoint
Services." Didn't see Project Professional within the fine print or the
media box. Now of course I can't get a refund on all this licensing I
purchased. Whatever happened to here's your Server license and CALs, here's
a link on how to implement and train users on this, oh and by the way since
you bought the server license, enjoy ALL the features not just some of them.
Sorry....end rant.

The WSS automatic site create doesn't work. Within Admin menu on PWA, I
clicked on manage windows sharepoint services, and go through the 3
validation steps. The first 2 no problem. The third causes a popup to
download to save file MS_ProjectServer_PublicDocuments. Huh? I even went
ahead and created a virtual folder under the IIS site where the "Create a
site under this SharePoint URL" is referencing. It is
http://servername:91/WSS.

Total emotional abuse for one person to take. Now it's like I have so much
time and money invested in it to back out now. Anyone want to buy a
ProjectServer2003 license with 9 CALs?

 

[Nico Oosthuysen]

Tim,

One little thing from my side - why did you buy the software without
trying it first? In my experience Microsoft is more than willing to
assist with trial versions of the software for you... Personally I
always try out software before I buy it - if i am not happy with it
then there is nothing to return!

Anyways, apart from that, this is a good solution for thousands of
companies around the world, so I am sure if you get across the initial
hurdles you will start to see real benefits. As other users in the
group has thusfar suggested, it will also be a very good idea to
enlist (at least some) support from an EPM partner in your region or
country.

Your problem with WSS - Can you tell me if you have an item called
"Sharepoint Central Administration" in your Administrative Tools
folder? And if there is, what happens when you click on it? It
sounds to me as if your SharePoint installation is broken\not there -
we will need to fix this first as SharePoint is responsible for
hosting the websites for the projects.

Thanks,
Nico Oosthuysen

 

[Tim]

The SharePoint Admin is in fact in our Admin tools and the site is extended.
When I click on it, it does in fact bring up the typical menu system for
SharePoint.

I understand that MS offers trials. What this REALLY boils down to is
management saw an ad from a well known reseller for ProjectServer 2003 for
like $600. So we ordered it. We were then "stuck" from that point on
because it was really like $1200 and then had to add CALs. Then we installed
the SQL desktop edition to avoid having to buy a full SQL server license.
Then we realized that NOPE getting Project Server in of itself doesn't give
us a functioning product. We need at least one copy of Project Professional
to manage enterprise resources plus SIMPLY CREATE A PROJECT. Oh brother! So
much easier and cheaper to buy 9 copies of Project Pro, load it on the
laptops and then make sure the data files are on a network share. Then it
really begins when the end user training issue becomes a realization. Then
we realize that you really can't see all the details of say a task within a
Project within PWA as just one example as to why PWA is so awkward. So now
it's no longer a $600 solution when we exam all this, plus add in a
consultant.

May be easier to simply share out a calendar under our Exchange Public
folders. Throw tasks appointments and contacts in there, and be able to use
it within Outlook OR OWA without training issues and have it be fully
functional and collaborative.

 

[Nico Oosthuysen]

Tim,

Did you perform the steps in the installation guide, under the section
"Configure Windows SharePoint Services"? Specifically, the sections
called:

- Run the Windows SharePoint Services Configuration Wizard
- Create a Windows SharePoint Services Administrator

If you have, then please go to your PWA Admin Page, to the Manage
Windows Sharepoint Services section. The top URL should point to your
WSS Administration site, normally something like http://servername:58703.

The second URL should point to the Managed Path that is configured
with the WSSWiz.exe tool to provision Project Workspaces. This is
normally something like http://servername/sites

Then hit save changes - does it validate the connection?

If not, please post your error.

On Project Server in general - it as you say that there are perhaps
simpler ways to do these things. The trick, however, is in added
benefits. The EPM solution has killer added benefits. If you would
like more detail on that, you can find a lot of information on what is
possible at http://office.microsoft.com/en-us/epmsolution/FX101935291033.aspx.
If you would like more information on how to achieve what you need
from EPM (if you in fact do need EPM, sometimes people don't... ),
should have a look at the Partner Directory at http://directory.microsoft.com/mprd/default.aspx
to find a MS partner that specializes in EPM.

Nico