Information Technology Reference
In-Depth Information
your network to help you better organize and identify your systems, especially in a large enter-
prise network, though from a security standpoint it would probably be advisable to avoid
naming your web servers using a scheme like “WEBSERVER1,” “WEBSERVER2,” and the like.
The instructions we've listed here are based on the assumption that the Windows Server
2003 computer is a member server, not a domain controller. Windows Server 2003
does
permit
you to rename a domain controller using the netdom utility, but the procedure is not quite as
simple as renaming it from My Computer, and even that method should be used with caution
if the domain controller is running other software applications such as Microsoft Exchange.
Of the methods we've included here, the most foolproof is making the change using the
GUI, since a server's computer name is embedded into the Registry in numerous locations.
Renaming a server using the GUI ensures that you haven't missed anything, since the operating
system makes the necessary changes in the background.
See Also
Rename
method of the
Win32_ComputerSystem
class
Microsoft TechNet: “Rename a Domain Controller” (
http://www.microsoft.com/
technet/prodtechnol/windowsserver2003/library/ServerHelp/
aad1169a-f0d2-47d5-b0ea-989081ce62be.mspx
)
Microsoft KB 325354: “How to Use the Netdom.exe Utility to Rename a Computer in
Windows Server 2003”
1-2. Configuring a Static IP Address
Problem
You want to configure a Windows Server 2003 computer with a statically assigned IP address.
Solution
Using a Graphical User Interface
1.
Open the Network Connections applet.
2.
Double-click on the Local Area Connection icon.
3.
Click on Internet Protocol (TCP/IP), and select Properties.
4.
Select the radio button next to Use the Following IP Address.
5.
Fill in the appropriate configuration information in the IP Address, Subnet Mask, and
Default Gateway text boxes.
6.
Click Close when you're finished.
