Add core features to an existing local area network (LAN)

Updated: October 6, 2010

Applies To: Windows Server 2008, Windows Server 2008 R2

You can use the goals below to add core services to an existing network.

• Add name resolution services to the network with Domain Name System (DNS)

• Add name resolution services to the network with Windows Internet Name Service (WINS)

• Add automatic IP address assignment to the network

Add name resolution services to the network with Domain Name System (DNS)

If you’re currently using lmhosts files or WINS and prefer to switch to DNS, or if you want to add a DNS server to an existing DNS deployment, you can use this goal. To accomplish this goal, you must deploy a DNS server. For more information, see Adding a DNS server at https://go.microsoft.com/fwlink/?LinkId=193981.

Additional tasks for DNS:

• Checklist: Store Data in an AD DS Application Partition at https://go.microsoft.com/fwlink/?LinkId=202967.

• Checklist: Use Forwarders at https://go.microsoft.com/fwlink/?LinkId=202968.

• Checklist: Automatically Remove Stale Resource Records at https://go.microsoft.com/fwlink/?LinkId=202969.

• Checklist: Create an Alias (CNAME) Record at https://go.microsoft.com/fwlink/?LinkId=202970.

• Checklist: Use Resource Records at https://go.microsoft.com/fwlink/?LinkId=202973.

• Checklist: Secure Your DNS Server at https://go.microsoft.com/fwlink/?LinkId=202974.

• Checklist: Configure DNS Client Settings at https://go.microsoft.com/fwlink/?LinkId=202975.

• Checklist: Migrate a DNS Server at https://go.microsoft.com/fwlink/?LinkId=202976.

• Checklist: Create a Reverse Lookup Zone at https://go.microsoft.com/fwlink/?LinkId=202977.

Add name resolution services to the network with Windows Internet Name Service (WINS)

If you’re currently using lmhosts files and prefer to switch to WINS for automatic name resolution services, or if you want to add a WINS server to an existing WINS deployment, you can use this goal. To accomplish this goal, you must deploy a WINS server. For more information, see Deploying WINS at https://go.microsoft.com/fwlink/?LinkId=193983.

Additional tasks for WINS:

• Modify server properties at https://go.microsoft.com/fwlink/?LinkId=202978.

• Manage WINS console data at https://go.microsoft.com/fwlink/?LinkId=202979.

• Manage WINS clients at https://go.microsoft.com/fwlink/?LinkId=202980.

• View WINS records at https://go.microsoft.com/fwlink/?LinkId=202981.

• Manage the WINS database at https://go.microsoft.com/fwlink/?LinkId=202982.

• Configure replication at https://go.microsoft.com/fwlink/?LinkId=202983.

• Manage replication at https://go.microsoft.com/fwlink/?LinkId=202984.

• Use persistent connections at https://go.microsoft.com/fwlink/?LinkId=202985.

• Manage static mappings at https://go.microsoft.com/fwlink/?LinkId=202986.

Add automatic IP address assignment to the network

If you are currently configuring network connections manually with static IP addresses and would prefer to use Dynamic Host Configuration Protocol (DHCP) to automatically assign IP addresses to computers, or if you want to add a DHCP server to an existing DHCP deployment, you can use this goal. To accomplish this goal, you must deploy a DHCP server. For more information, see Checklist: Deploying DHCP Server at https://go.microsoft.com/fwlink/?LinkId=193980.

Additional tasks for DHCP:

• Increase fault tolerance by splitting DHCP scopes at https://go.microsoft.com/fwlink/?LinkId=202987.

• Eliminate manual updates of DNS records by configuring dynamic update and secure dynamic update at https://go.microsoft.com/fwlink/?LinkId=202988.

• Allow remote administration of DHCP servers by configuring Windows Firewall ports at https://go.microsoft.com/fwlink/?LinkId=202989.

• Prevent rogue DHCP servers on your network by authorizing DHCP servers in AD DS at https://go.microsoft.com/fwlink/?LinkId=202990.

• Enforce network access policies for client health by configuring DHCP with Network Access Protection at https://go.microsoft.com/fwlink/?LinkId=202991.

• Automate management of devices that have static IP addresses by creating DHCP reservations at https://go.microsoft.com/fwlink/?LinkId=202992.

• Support multiple subnets with one DHCP server by configuring DHCP relay agents at https://go.microsoft.com/fwlink/?LinkId=202993.

• Avoid reconfiguring DHCP on a new server by migrating an existing DHCP infrastructure at https://go.microsoft.com/fwlink/?LinkId=202994.

• Balance the load on your DHCP servers by using the 80/20 rule for scopes at https://go.microsoft.com/fwlink/?LinkId=202995.

• Centralize management of two or more DHCP servers as a single system by clustering DHCP servers at https://go.microsoft.com/fwlink/?LinkId=202996.