The other way it far more difficult than the process what Manmeet mentioned.
I renamed one of my box few months back due to company policies. Everything
(Project/SQL/WSS/IIS) was on the same box. It took me a lot of time to fix
those issues. But now the server is running with new name without any issue.
I noted few steps in random at that time. I wish I could have saved all the
steps. Will try to replicate the scenario sometime later & will post the
document.
For now here are some random steps (you might get different errors as per
your configuration/environment):
- Backup your DBs. If possible make an image of the system (with Norton
Ghost) or something similar. That way you can always revert back to original
state.
- Note down (or make screen shots) all the configurations on the system
like. DB names, ports used, admin login, IPs, etc..
- After changing name you might get ... Project DB can't be accessed (5001)
or similar error message when you try to access PWA site.
- WSS site might give ....'Can not connect to Config DB' or simiar error.
- In SQL Enterprise Manager go to WSS DB > Tables. Check tables SERVERS &
SERVICES. Make corrections
- Use EDITSite.exe tool to update ODBC connection & update site changes.
- If using OLAP, then create OLAP Admin login in SQL > Security & assign it
to Analysis DB.
- Open Analysis Services Manager > Right clikc Server name & select Edit
Repository Connection String. Make sure string shows the new server name.
- If you have Portfolio Analyzer views, then go to PWA > Admin > Manage
Views. Modify each Portfoliio Analyzer view & correct the name of Analysis
Server in each view.
- I remember I also changed / removed references of old name in registry.
- For error messages always check Event Viewer.
In my case the server was renamed within the same domain.
Let us know about your endeavour.
--
FaisalM
http://www.FaisalMasood.com/
My Project Blog
http://www.faisalmasood.com/blog/msproject
My Sharepoint Blog
http://www.faisalmasood.com/blog/sharepoint