You have just installed the Dynamic Host Configuration Protocol (DHCP) service on a Windows 2000 Server computer that is a domain controller. What must you do before the DHCP service will start handing out leases to clients?

Introduction / Context:
In an Active Directory environment, Windows 2000 and later require additional safeguards to prevent unauthorized servers from distributing IP addresses. After installing the DHCP service on a domain controller or any domain member, an administrator must explicitly authorize the server in Active Directory before it begins leasing addresses. This question tests whether you understand that authorization step and how it relates to DHCP operation in a secure enterprise network.

Given Data / Assumptions:

The server is running Windows 2000 Server and has the DHCP service installed.
The server is also a domain controller in an Active Directory domain.
You want the DHCP service to begin handing out IP address leases to client computers.
You know that some configuration steps, such as scopes or reservations, may be needed later, but the immediate issue is that the service will not start fully until a key requirement is met.
The options include authorizing the DHCP server, configuring scopes, reservations, and DNS integration.

Concept / Approach:
Active Directory-integrated DHCP in Windows 2000 includes an authorization mechanism to prevent rogue DHCP servers on the network. Only DHCP servers that have been explicitly authorized in Active Directory are allowed to start and respond to client requests. This is done using the DHCP console, where an administrator with appropriate rights authorizes the server’s IP address or name. While configuring scopes, reservations, and DNS integration is important for proper DHCP operations, those tasks are not the gating factor preventing the service from starting in an Active Directory environment.

Step-by-Step Solution:
Step 1: Recognize that the question focuses on a prerequisite necessary before DHCP will function on a domain controller. Step 2: Recall that in a Windows 2000 Active Directory domain, DHCP servers must be authorized in Active Directory to prevent unauthorized servers. Step 3: Understand that if a DHCP server is not authorized, it detects this state and does not hand out leases on the network. Step 4: While scopes, superscopes, and multicast scopes control which addresses are available, they do not override the authorization requirement. Step 5: Similarly, reservations and DNS integration are configuration details that can be adjusted later but are not mandatory for the service to start offering basic leases. Step 6: Conclude that authorizing the DHCP server in Active Directory is the essential step to enable the service.

Verification / Alternative check:
In a real environment, if you install DHCP on a domain-joined server and then open the DHCP console, you may see a message that the server is not authorized. After right-clicking the server node and choosing Authorize, the status changes and the server begins serving clients. This practical experience validates that authorization in Active Directory is required.

Why Other Options Are Wrong:
Configure a scope, a superscope, and a multicast scope – Scopes are necessary to define available addresses, but the service will still not function if the server remains unauthorized.

Configure a DHCP address reservation – Reservations are optional and apply to specific clients; they are not a prerequisite for the service to start.

Configure the DHCP server for DNS integration – DNS integration is recommended but not required for DHCP to begin issuing leases. It is a feature that enhances name resolution, not a hard requirement.

Common Pitfalls:
A frequent misunderstanding is assuming that configuring a scope is the only requirement for DHCP to start working. In Active Directory domains, many administrators are surprised to find that DHCP remains inactive until authorization is completed. Another pitfall is confusing authorization with DNS integration; both are important but serve different purposes.

Final Answer:
Before the DHCP service will begin handing out leases, you must authorize the DHCP server in Active Directory.