MicroSoft Project Server seeking Lessons Learned...

P

Paul G

I am seeking feedback on what went well and not so well during a Microsoft
Project Server implementation. The same would like to be understood once the
product has been implemented. The goal is to understand lessons learned and
utilize what worked well and what one would change having gone through an
implementation.
 
M

Marc Soester [MVP]

Hi Paul,

Well, I thought I may be able to give you some feedback in regards to
installation and usage of Project Server since we roll out EPM solutions to
organisations.

Installation:
Generally, you can follow the Microsoft installation guide. You will find,
when you install it the first time, the different service accounts and
databases you need to create may be confusing. It took me 2-3 installs until
I understood each step of an installation. It therefore may makes sense to
"practice" once or twice before installing project Server. Make sure that the
service accounts have the right security, otherwise you will run into
problems. I also produce screenshots on every installation ( more for
documentation purposes). This will allow you to go back, just in case if you
need to check some settings after installation.

The biggest hurdle, I found was setting up Analysis Services ( OLAP Cubes )
since you need to work with an extra MDB file. Don’t be frustrated if it
doesn’t work the first time :)

Also in regards to the Desktop compatibility, you will need to make some
changes like:
All client machines that wish to access the data analysis ( Web based pivot
table ) require the SQL Server 2005 Analysis Services 9.0 OLE DB PROVIDER.
Please note, in order to install this provider you will need to install an
upgrade of the xml schema called MS XML 6

These packages can be downloaded under
http://www.microsoft.com/downloads/...94-8453-4998-8226-fa42ec403d17&DisplayLang=en
( Feature Pack for Microsoft SQL 2005 – February 2007)

The file names are
o SQLServer2005_Analysis Services 9.0 OLE DB Provider_ASOLED89.msi
o Msxml6_x86.msi

Look, experience installing the solution will allow you to streamline the
installation process. I hope that this post has helped you with the
installation.

If you have more questions, please let me know
thanks
 
G

GirlGeek

Hi Paul,

Well, I thought I may be able to give you some feedback in regards to
installation and usage of Project Server since we roll out EPM solutions to
organisations.

Installation:
Generally, you can follow the Microsoft installation guide. You will find,
when you install it the first time, the different service accounts and
databases you need to create may be confusing. It took me 2-3 installs until
I understood each step of an installation. It therefore may makes sense to
"practice" once or twice before installing project Server. Make sure that the
service accounts have the right security, otherwise you will run into
problems. I also produce screenshots on every installation ( more for
documentation purposes). This will allow you to go back, just in case if you
need to check some settings after installation.

The biggest hurdle, I found was setting up Analysis Services ( OLAP Cubes )
since you need to work with an extra MDB file. Don't be frustrated if it
doesn't work the first time :)

Also in regards to the Desktop compatibility, you will need to make some
changes like:
All client machines that wish to access the data analysis ( Web based pivot
table ) require the SQL Server 2005 Analysis Services 9.0 OLE DB PROVIDER.
Please note, in order to install this provider you will need to install an
upgrade of the xml schema called MS XML 6

These packages can be downloaded underhttp://www.microsoft.com/downloads/details.aspx?FamilyId=50b97994-845...
( Feature Pack for Microsoft SQL 2005 - February 2007)

The file names are
o SQLServer2005_Analysis Services 9.0 OLE DB Provider_ASOLED89.msi
o Msxml6_x86.msi

Look, experience installing the solution will allow you to streamline the
installation process. I hope that this post has helped you with the
installation.

If you have more questions, please let me know
thanks
--
Marc Soester [MVP]
State Manager: EPMhttp://marcsoester.blogspot.com





- Show quoted text -
Click to expand...

Having worked with several large companies on MS Project Server
implementations, one of the main 'Lessons Learned' is this:

It's about Accountability and Visibility. While that's part of
Microsoft's marketing message, it's the same 2 words which keep people
from using it. If managers don't want their original plan / baseline
Visible, so that they don't have to be Accountable to management for
explanations on slippages and poor planning, they will find a million
excuses not to use it. Some of those excuses will be blamed on
technical support, Microsoft, management sponsorship, lack of
training, etc etc - but behind a lot of it is the major culture change
of Un-Accountability to Accountability.

How will you address, manage and handle the Accountability Culture
Change? The Fear of Visibility?
 
M

Marc Soester [MVP]

AS GirlGeek mentioned Paul, the idea of an EPM solution every company likes,
but the commitment to EPM and therefore change is the biggest issue that you
will face.

I would suggest including and EPM Partner, that actually has done this many
times. You will be able to profit from their experience in handleing an EPM
rollout. Your investment may be more to start with, but it is an investment
that will ensure a successful rollout.

Not sure where you are located, but check out the mircrosoft site which will
tell you where an EPM Partner is near you.

--
Marc Soester [MVP]
State Manager: EPM
http://marcsoester.blogspot.com
 
P

Paul G

Thank you both for your feedback this has been very helpful and it will used
in our evaluation and vendor questioning. Following this post I will send you
both an e-mail where we are seeking input on a MS premire vendor
 
P

Paul G

Marc just tried e-mailing you at your hotmail account noted on you blog site
and the message bounced... could you update the e-mail addrests. Thx.
 
Top