Export (0) Print
Expand All

Rename a stand-alone server (Windows SharePoint Services)

Office 2007

Updated: February 7, 2008

Applies To: Windows SharePoint Services 3.0

 

Topic Last Modified: 2008-02-05

Use this procedure to rename a stand-alone installation of Windows SharePoint Services 3.0 after it has already been renamed in Windows Server 2003 or Windows Server 2008. This topic does not provide information about renaming the actual computer. For more information about renaming the computer, see the Windows Server 2003 documentation.

NoteNote:
You must restart the server after you have renamed it in Windows Server 2003 or Windows Server 2008 and before you rename it in SharePoint Products and Technologies by using the procedure in this article.

This procedure renames the server and stores the new name in the configuration database. Depending upon how you configured your server — for example, using alternate access mapping and customizations — you might need to perform additional steps to make all your sites accessible to users. Those additional steps are described later in this article.

ImportantImportant:
You must be a member of the Administrators group on the local computer to perform this procedure.

You can use this operation before or after a server is renamed in the domain to avoid having to rebuild the server. You must run this operation to rename the server even if the server is not in a domain.

Rename the server by using the Stsadm command-line tool
  1. On the drive where SharePoint Products and Technologies is installed, change to the following directory: %COMMONPROGRAMFILES%\Microsoft shared\Web server extensions\12\Bin.

  2. Type the following command, and then press ENTER:

    stsadm -o renameserver -oldservername <current name of the server> -newservername <new name for the server>

For more information about the Stsadm Renameserver operation, see Renameserver: Stsadm operation (Windows SharePoint Services).

ImportantImportant:
After running the operation, you must run iisreset /noforce to ensure that the rename operation completes.

You should review the access mapping settings for each Web application — including the Central Administration Web application — that is hosted on the server to verify that both the public URLs and internal URLs are appropriate for your server's new name. If there are public URLs or internal URLs that use the old server name, you must update those URLs to use the new server name instead. If you do not change the URLs, user requests for content on the server may not be directed to the server and users will receive a "404" error or some similar error. You can use the SharePoint Central Administration Web site to change the internal URL.

If you are using reverse proxies or load balancers that depend upon those URLs, ensure that the reverse proxies and load balancers are also updated.

For more information about reverse proxies and load balancers, see Plan alternate access mappings (Windows SharePoint Services).

The URL for Central Administration might be affected by renaming the server, and the site might become unavailable after the Rename operation. To fix the URL you must use the Stsadm command-line tool. Because you cannot delete the last public URL for a Web application, use the following procedure to first add the new mapping by using the Addalternatedomain operation and then delete the old mapping by using the Deletealternatedomain operation.

Change mappings by using the Stsadm command-line tool
  1. On the drive where SharePoint Products and Technologies is installed, change to the following directory: %COMMONPROGRAMFILES%\Microsoft shared\Web server extensions\12\Bin.

  2. Type the following command, and then press ENTER:

    stsadm -o addalternatedomain -url <valid URL> -incomingurl <http://incoming url> -urlzone {Default | Internet | Extranet | Custom} -resourcename <non-Web application resource name>

  3. Type the following command, and then press ENTER:

    stsadm -o deletealternatedomain -url <valid URL> -incomingurl <http://incoming url>

For more information, see the following resources:

After you have ensured that the mapping for Central Administration is working, you can use Central Administration to change other mappings.

To edit an internal URL by using Central Administration
  1. In Central Administration, on the Operations page, in the Global Configuration section, click Alternate access mappings.

  2. On the Alternate Access Mappings page, click the internal URL that you want to edit.

  3. In the Edit internal URL section, in the URL protocol, host and port box, change the host name to the new server name.

  4. Click OK to save your changes.

For more information about alternate access mappings, see the following resources:

Some items in a Web page might also need to be changed, including:

  • File paths   Some images in Web pages might use file paths or URLs that may no longer work after you rename the server. Typically, these will be image files, sound files, or other resources used in Web pages.

  • Alerts   If you have configured alerts on any Web applications that use public URLs, verify these alerts and change the public URLs to match the new public URLs.

Was this page helpful?
(1500 characters remaining)
Thank you for your feedback
Show:
© 2014 Microsoft