You need to ensure that all IP address leases are displayed

Your network contains a server named Server1. Server1 has the DHCP server role installed and contains multiple scopes. You restore the DHCP database and discover that the active IP address leases are not displayed. You need to ensure that all IP address leases are displayed. What should you do?

Your network contains a server named Server1. Server1 has the DHCP server role installed and contains multiple scopes. You restore the DHCP database and discover that the active IP address leases are not displayed. You need to ensure that all IP address leases are displayed. What should you do?

A.
Reconcile all of the scopes.

B.
Run jetpack.exe dhcp.mdb temp.mdb.

C.
Restart the DHCP Server service.

D.
Authorize Server1.

Explanation:
Recovery: Restoring from Backup
If the DHCP server database becomes corrupted or is lost, simple recovery is possible by replacing the server database file (Dhcp.mdb), located in the % SystemRoot %\System32\Dhcp folder, with a backup copy of the same file. You can then perform a simple file copy to overwrite the current corrupted database with a backup copy of the same file. If DHCP Manager has been used previously to enable backup, you can obtain the backup copy of the server database file located in the % SystemRoot %\System32\Dhcp\Backup folder. As an option, you can also choose to restore the Dhcp.mdb file from a tape backup or other backup media.
Before restoring the database file from backup, the DHCP service must first be stopped. Once you have copied the backup file to the % SystemRoot %\System32\Dhcp folder from your preferred backup source, you can restart the DHCP service.
To stop the DHCP server service, type the following at a command prompt:
net stop dhcpserver Once the DHCP service has been stopped, the following procedure can be used to safely restore a backup copy of the database from either backup media or the DHCP service backup folder.
First, move the files from your existing DHCP folder to a different folder location, such as \Olddhcp. Be careful to keep the DHCP folder structure intact. For example, type the following set of commands at a command prompt to perform this step:
md c:\Olddhcp move % SystemRoot % \system32\DHCP\*.* C:\Olddhcp Next, remove the corrupted server database file. This can also be done at the command prompt:
del % SystemRoot % \system32\DHCP\Dhcp.mdb
You can then copy the backup database file into the DHCP service folder. The path to be used when performing the actual copy operation varies (as shown in Table 4.15), depending on the specific server version of Windows running on the computer where the DHCP database file is being restored.
http://technet.microsoft.com/en-us/library/cc958954.aspx



Leave a Reply 3

Your email address will not be published. Required fields are marked *


Tech

Tech

Answer is A

From http://support.microsoft.com/kb/173396

Reconciling DHCP Information
After you generate a new database file, you may notice that the scope information is present, but no active leases are displayed. To regain the active leases, you must reconcile the database with the information in the registry using the following steps: 1.From DHCP Manager, click your scope, and then click Active Leases on the Scope menu.
2.In the Active Leases dialog box, click Reconcile.
3.Click OK. Your active leases will appear in the Active Leases dialog box.
NOTE: When you view the properties for a client lease, the computer name will be listed as the IP address of the lease and an arbitrary hexadecimal value will be listed as the client identifier. These will be replaced with the appropriate information as the clients renew their leases.

Repeat the above procedure for each scope for which you must reconcile leases.

netuser258

netuser258

I agree with Tech. The scope must be reconciled after a restore procedure.

neopod

neopod

That technet article applies to windows server 2000 only and has to do with restoring a corrupted database file.

In this scenario the database file is not corrupted, you are using the database file to restore dhcp to another server. The last step in the explanation for this is to restart the service.

answer is C