Local references to old server name remain after Windows 2003 server rename
- by imagodei
I have a standalone Win 2003 server with Windows Sharepoint Services (WSS3) running on it. I had to rename the server and I had bunch of problems resulting from this. Note that the server is not in AD environment.
Most obvious problems were with Sharepoint, which didn't work. I was somewhat naive to think it will work in the first place, but OK - I've solved this using step 1 & 3 from this site (TNX)
Other curious behavior/problems remain. Most disturbing is that Sharepoint isn't able to send email notifications to participants.
I noticed there are several references to old server name everywhere I look: in Registry, in Windows Internal Database (MICROSOFT##SSEE). I see instances of old server name in the Sharepoint Central Administration - Operations - Servers in farm. There is reference to a servers:
oldname.domain.local
oldname.local
On one of those servers there is also Windows SharePoint Services Outgoing E-Mail Service (Stopped).
Also, when I try to telnet locally to the mail server (Simple Mail Transfer Protocol (SMTP) service), I get a response:
220 oldname.domain.local Microsoft ESMTP MAIL Service, Version: 6.0.3790.4675 ready at Tue, 15 Jun 2010 13:56:19 +0200
IMO these strange naming problems are also the reason why email notifications from within Sharepoint don't work.
Can anyone tell me how to correct/replace those references to oldservername? Why is the email service insisting on old name? Of course I would like to try it without reinstalling the server.
TNX!
