W
wwalkerbout
Greetings,
The last step in a Project Server 2003 implementation of installing
the Project Server (after WSS, DAC, etc...) seems to rely on the
Account IWAM_<ServerName>.
In a secure environment where the name of that Account has been
changed (and the Registry entry to prevent auto-generation of that
Account has be changed), is there a way to make that Project Server
installation program recognize the new Account?
Our installation process seems to work fine until the very last
moment, where it rolls back. A check of a verbose version of the
installation log file suggests (via an error code), that it might be
due to that Account change (although this is not certain).
Any other suggestions on what might cause such a roll-back would be
appreciated.
Cheers,
Wayne
The last step in a Project Server 2003 implementation of installing
the Project Server (after WSS, DAC, etc...) seems to rely on the
Account IWAM_<ServerName>.
In a secure environment where the name of that Account has been
changed (and the Registry entry to prevent auto-generation of that
Account has be changed), is there a way to make that Project Server
installation program recognize the new Account?
Our installation process seems to work fine until the very last
moment, where it rolls back. A check of a verbose version of the
installation log file suggests (via an error code), that it might be
due to that Account change (although this is not certain).
Any other suggestions on what might cause such a roll-back would be
appreciated.
Cheers,
Wayne