All computers and other devices on your TCP/IP network must have an IP address in order for the network to function properly. IP addresses can be configured manually at each computer, or you can deploy a DHCP server that automatically assigns IP address leases to all DHCP clients on the network.

Most client operating systems seek an IP address lease by default, so no configuration on the client computer is necessary to implement a DHCP enabled network; the first step is to deploy a DHCP server.

Before your DHCP server can provide IP address leases to clients, however, a range of IP addresses must be defined at the DHCP server. This range, known as a scope, defines a single physical subnet on your network to which DHCP services are offered. So, for example, if you have two subnets, your DHCP server must be connected to each subnet and you must define a scope for each subnet. Scopes also provide the primary way for the server to manage distribution and assignment of IP addresses and any related configuration parameters to clients on the network.

When you deploy DHCP as a MADCAP server, the DHCP server can dynamically assign multicast IP addresses to clients that want to join the group of clients that receive the information sent in the multicast messages.

Multicasting is useful for the point-to-multipoint delivery of information, such as audio or video information, on an internetwork. Multicasting allows one point, such as a media server, to send the information in a single packet to many recipients by using a multicast address.

The advantages of this method are the use of a single packet and no overhead for keeping lists of recipients. Unlike broadcast packets, multicast traffic does not disturb those nodes who are not listening for it. Routers can be multicast-capable and forward the multicast packet to all networks where there is at least one node listening.

You can type the Netsh commands for DHCP in a command prompt window at the netsh dhcp> command prompt, or you can run the Netsh commands for DHCP in batch files and other scripts. All of the functionality that is available in the DHCP console is available at the netsh dhcp> command prompt. This can be useful in the following situations:

• When managing DHCP servers in wide area networks (WANs), commands can be used in interactive mode at the netsh> command prompt to better manage across slow-speed network links.
  
  
• When managing a large number of DHCP servers, commands can be used in batch mode to help script and automate recurring administrative tasks that need to be performed for all DHCP servers.
  
  

The DHCP console is added to the Administrative Tools folder in Control Panel when you install the DHCP server role. The DHCP console appears as a Microsoft Management Console (MMC) snap-in.

The DHCP console also contains enhancements that were suggested by network managers. These include enhanced server performance monitoring, more predefined DHCP option types, dynamic update support for clients running earlier versions of Windows, and the detection of unauthorized DHCP servers on your network.

After you install a DHCP server, you can use the DHCP console or the Netsh commands for DHCP to perform these basic administrative server tasks:

1. Create scopes.
   
   
2. Add and configure superscopes and multicast scopes.
   
   
3. View and modify properties for scopes, such as setting additional exclusion ranges.
   
   
4. Activate scopes, multicast scopes, or superscopes.
   
   
5. Monitor scope leasing activity by reviewing the active leases for each scope.
   
   
6. Create reservations in scopes as needed for DHCP clients that require a permanent IP address for leased use.
   
   

In addition, you can also use the DHCP console or the Netsh commands for DHCP to perform the following optional or advanced setup tasks:

• Add new custom default option types.
  
  
• Add and configure any user or vendor-defined option classes.
  
  
• Further configure other server properties, such as audit logging or boot protocol (BOOTP) tables.
  
  

	Note
	Superscopes are supported only in IPv4. The DHCPv6 server does not support superscopes.