Changing Project Server Machine Name

C

Chad Parks

Adrian:



One of our clients has to change their Project Server 2003
machine name. They have a single server configuration (SQL
Server, Analysis Services, Project Server 2003 on one box
running Windows Server 2003).

Before walking the client through the process of changing
the server name, I tried performing the same operation on
a test machine I have set up here (identical
configuration).

These are the steps I have taken:

1) I changed the machine name and restarted the
server.

2) I launched conninfo.exe and specified the new
machine name for the SQL Server.

3) Because both the test machine and the client
machine are using local accounts for COM+, I launched
PSComPlus.exe and specified the new machine name\accounts.

4) I then opened PDS.WSDL in Notepad and corrected
the machine name in the address and saved.

5) I then went to PWA and tried logging in with the
administrator account. I was then prompted with the
following error: "Project Server was unable to log you on
at this time. Please try again later. (5006)". Note: If
I specify an incorrect password for the administrator
account, I receive the standard, "You have entered an
incorrect user name/password combination. (5005)"

If I change the machine name on the server back to the
original and once again go through the steps of launching
conninfo.exe, PSComPlus.exe, and changed the address back
in the PDS.WSDL file, everything works again.



Is there something that we're missing?



Thanks to anyone who can help.
 
G

Gary L. Chefetz

Chad:

I don't think Adrian reads the boards. You'll need to edit the registry to
make the change. It would be helpful if the new Edit Site tool was
available, however it's not. Use the 2002 documentation of the registry
settings and feel your way through the changes made in 2003.

--

Gary Chefetz [MVP]
http://www.msprojectexperts.com
"We wrote the book on Project Server"

*** Remember to look for line breaks in links posted to the news group, use
cut and paste for these.
 
K

Kevin Flanagan

We found that during the installation, there are 140+
files that get hard coded with the domain and machine
name. This makes it a little difficult to change machine
names.

Kevin
 
K

Kevin Lisboa

We had this situation come up within our own company and
we have yet to get a clean solution in place that we can
document. We've even gone so far as getting one of our
certified Microsoft service providers to assemble the
documentation. It has now been 3 months, and they have
yet to complete the task.

Personal recommendation - don't rename the box unless it
is ABSOLUTELY NECESSARY.

--Kevin
 
Top