Problem on Initial login after Install

T

Terry Montgomery

Greetings,

I need help. I have just installed a fresh copy of Project Server on a new
server box. I was careful to document my steps and set up SQL Server and
Sharepoint Services as instructed before the final step of installing Project
Server. Everything seemed to work fine. I then went into the server and fired
off the "configuration" link to Project Server on the server box. It opens a
browser and prompts me for my user name and password. I am a local
administrator for this server and the administrator for Project Server. I am
using my Windows authentication for my username and password. The same as I
use to log into the network. I plug in these parameters and Project Server
does not recognize me as a user.
What gives?

Terry Montgomery
Fort Worth, Texas
 
D

Dale Howard [MVP]

Terry --

When you install Project Server, the system creates only one account, which
is the built-in Administrator account. To log into PWA initially, you must
enter "Administrator" as the user name (without the quotation marks) and
enter the password you selected during the installation process. If you did
not write down the Administrator password as instructed, refer to the
following link for the steps to reset the password:

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

Refer to the following link for the steps needed to create an Administrator
login account in Microsoft Project Professional:

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

Given your inexperience with Project Server 2003 and your desire to master
this application, refer to the following link for information about Project
Server 2003 documentation and training:

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

Hope this helps.
 
T

Terry Montgomery

Dale,

First of all, thanks for the help. Your answer worked as you stated. You
have saved me from another day of banging my head on the desk. However, my
frustration is still with me. True it is my first experience in installing
Project Server, however, I have been customizing and running it on a test box
for several months. This install is for the production version. The test box
was already installed by the time I arrived with this company. The people who
originally installed it did not write anything down and basically couldn't
remember how they did it.
My frustration is with Microsoft. I did read the installation instructions
from the documentation you refered to and followed it to the letter. The
problem is Microsoft does not follow its own architecture when it comes to
Project Server. As I stated I am set up via Windows 2003 as a local
adminstrator for this server box. Our environment follows active directory
and windows authentication. Therefore when installing an application on this
server, any Microsoft application that is, should recognize me as the
administrator. Since it asks me for my password as the last step before
installing I naturally use my network password due to windows authentication
being the default. Therefore, Microsoft should not establish a generic
"administrator" as a user name and attach it to my password! Why bother with
windows authentication at all? Is it not the purpose of windows
authentication to reduce the labor or establishing users repeatedly every
time you add a new service or application? If I am the administrator in
Windows 2003 server then the application should set my windows username and
password for that application. Not some generic. Come on Microsoft. Be
consistent!

Thanks for the help Dale.

TM
--
Terry Montgomery
Fort Worth, Tx


Dale Howard said:
Terry --

When you install Project Server, the system creates only one account, which
is the built-in Administrator account. To log into PWA initially, you must
enter "Administrator" as the user name (without the quotation marks) and
enter the password you selected during the installation process. If you did
not write down the Administrator password as instructed, refer to the
following link for the steps to reset the password:

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

Refer to the following link for the steps needed to create an Administrator
login account in Microsoft Project Professional:

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

Given your inexperience with Project Server 2003 and your desire to master
this application, refer to the following link for information about Project
Server 2003 documentation and training:

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

Hope this helps.
Click to expand...
 
D

Dale Howard [MVP]

TM --

I did two good things for you:

1. Gave you an answer that saved you frustration
2. Gave you a chance to "vent" about Project Server

Hang in there, my friend. You have much to learn, but you are well on the
way toward mastering this application. Good luck!




Terry Montgomery said:
Dale,

First of all, thanks for the help. Your answer worked as you stated. You
have saved me from another day of banging my head on the desk. However, my
frustration is still with me. True it is my first experience in installing
Project Server, however, I have been customizing and running it on a test
box
for several months. This install is for the production version. The test
box
was already installed by the time I arrived with this company. The people
who
originally installed it did not write anything down and basically couldn't
remember how they did it.
My frustration is with Microsoft. I did read the installation instructions
from the documentation you refered to and followed it to the letter. The
problem is Microsoft does not follow its own architecture when it comes to
Project Server. As I stated I am set up via Windows 2003 as a local
adminstrator for this server box. Our environment follows active directory
and windows authentication. Therefore when installing an application on
this
server, any Microsoft application that is, should recognize me as the
administrator. Since it asks me for my password as the last step before
installing I naturally use my network password due to windows
authentication
being the default. Therefore, Microsoft should not establish a generic
"administrator" as a user name and attach it to my password! Why bother
with
windows authentication at all? Is it not the purpose of windows
authentication to reduce the labor or establishing users repeatedly every
time you add a new service or application? If I am the administrator in
Windows 2003 server then the application should set my windows username
and
password for that application. Not some generic. Come on Microsoft. Be
consistent!

Thanks for the help Dale.

TM
Click to expand...
 
G

Gary L. Chefetz [MVP]

Terry:

You misunderstood what the application was asking for when it asked you to
enter the administrator password. It was, in fact, asking you to assign a
password for the built-in administrator account in Project Server. I, for
one, can't think of any good reason for the system to have any pre-installed
recognition of any account other than the single built-in administrator
account.




Terry Montgomery said:
Dale,

First of all, thanks for the help. Your answer worked as you stated. You
have saved me from another day of banging my head on the desk. However, my
frustration is still with me. True it is my first experience in installing
Project Server, however, I have been customizing and running it on a test
box
for several months. This install is for the production version. The test
box
was already installed by the time I arrived with this company. The people
who
originally installed it did not write anything down and basically couldn't
remember how they did it.
My frustration is with Microsoft. I did read the installation instructions
from the documentation you refered to and followed it to the letter. The
problem is Microsoft does not follow its own architecture when it comes to
Project Server. As I stated I am set up via Windows 2003 as a local
adminstrator for this server box. Our environment follows active directory
and windows authentication. Therefore when installing an application on
this
server, any Microsoft application that is, should recognize me as the
administrator. Since it asks me for my password as the last step before
installing I naturally use my network password due to windows
authentication
being the default. Therefore, Microsoft should not establish a generic
"administrator" as a user name and attach it to my password! Why bother
with
windows authentication at all? Is it not the purpose of windows
authentication to reduce the labor or establishing users repeatedly every
time you add a new service or application? If I am the administrator in
Windows 2003 server then the application should set my windows username
and
password for that application. Not some generic. Come on Microsoft. Be
consistent!

Thanks for the help Dale.

TM
Click to expand...
 
T

Terry Montgomery

Gary & Dale,

Thank you again for your assistance and veteran wisdom. It is true I have
much to learn. I just think it would be nice if Microsoft would assist in
that education. But that's my complaint about most software companies. They
are poor at documentation. I do think Microsoft gets higher marks than most.
The good reason for not having a generic administrator user is again windows
authentication. Look at SQL Server. Once you are designated as a local
administrator on the box its easy to get rights to the database with single
sign on. If Microsoft is going to assign a generic administrator they just
need to state that clearly. The other confusing part is the sub menu item on
the log in page that states "Log on using your Microsoft Windows user
account". You can't do that without windows authentication being in place.
Thanks for the "rant". I just hope someone at Microsoft is reading these
posts. Believe me, I think this discussion board is a blessing. All this
blabbing is just me. I work with technology in healthcare where small errors
can have dire results on patients. I am just really really picky about
documentation.

Thanks again,
 
G

Gary L. Chefetz [MVP]

Terry:

The documentation is way better this time than last! - The generic
administrator is not a windows account. It does not convey any rights to
anything outside the application. It also provides a fail-safe for
application recovery because once you set Project Server to Windows Auth
Only, you can paint yourself out of the application.
 
Top