amset.info
from Sembee Ltd.
UK MS Exchange Consultants

Exchange - Net Admin - Outlook
Windows Mobile - Windows

Contact - Director's Blog

AddThis Social Bookmark Button


Network Admin Home

Branding "System Properties"
with Your Own Information
... Win XP, 2000 and older
... Vista

Changing ISPs Plan

Changing Internal
IP Addresses Plan

Custom Text on the
"Workstation Locked" Screen

Downloading a Complete
Internet Explorer Installation

Group Policy Admin

Login Scripts

Limiting the Number of Logins a User Can Make

NETBIOS Alias

Recovery Console

Reset Administrator Password

Run As

Subnet Masks

Uptime Statistics

Using NetMeeting for
Remote Control

Viewing Printers in a
Web Browser

Network Administration
Page Last Reviewed: 08/12/2009

NETBIOS Alias

Make a new server respond to the name of an old server.

If you have replaced a server with one of different name, but fear that applications or users may still be using the old NETBIOS name, then you can configure a NETBIOS alias. This will mean the new server will also respond to the old name.

A good examples of when this could be useful would be when a replacement Exchange server as been deployed, but there is a script used for the automatic configuration of Outlook.

To configure a NETBIOS Alias, you need to make a change to the registry.

IMPORTANT

Ensure that you have removed all references to the old server before continuing. If this is Exchange for example, the old server needs to have been removed correctly, otherwise you will have a confused Exchange organisation which may try and replicate traffic to itself! The old machine needs to have been removed from the domain and either had its name changed, or wiped, so that another machine cannot come up with the same name.

Registry Key

The key is at this location.

HKEY_Local_Machine\System\CurrentControlSet\Services\LanmanServer\Parameters

Add a new REG_SZ value with the name of "OptionalNames". For the string and the name of the server name that you want this machine to respond to : "OLD-SERVER". No domain information - so not example.local etc.

If you need to have multiple names, for example after a server consolidation, then use the type REG_MULTI_SZ instead.

After making the change, reboot the machine.

Don't forget DNS!

You should also make an entry in your Active Directory DNS for this name, so that the FQDN resolves to the replacement server.
That would be a new A record (if static IP address) or CNAME (if dynamic).

For an A record it would be OLD-SERVER and would have the IP address of the new replacement server.

For a CNAME, it would be called OLD-SERVER and would have the fully qualified name of the new server (new-server.example.local).

Last Page Update:
08/12/2009
More Content from Sembee Ltd.
 
Resources on amset.info Other Sites Sembee Ltd.
Microsoft Exchange Command Prompt Getting Started Guide Microsoft Exchange Consultancy
Microsoft Outlook Login Scripts Director's Blog
Network Administration MS Exchange Resources  
Internet Explorer Knowledge Base search  
Microsoft Windows Recovery of MS Office content from Temp Files  
Microsoft Windows Mobile Troubleshoot the Automatic Updates Client  
Amazon Store    

© Sembee Ltd. 1998 - 2010.

Reproduction of any content on this web site is prohibited without express written consent. Use of this web site is subject to our terms and conditions. All trademarks and registered trademarks are property of their respective owners. This site is not endorsed or recommended by any company or organisation mentioned on this site. This site is to provide guidance only and as such we cannot be held responsible for any consequences of following the advice given.