Reconcile dhcp scope windows 2008

Resources for IT Professionals. Sign in. United States English. Ask a question. Quick access. Search related threads. Remove From My Forums. Answered by:. Archived Forums. Hi, Thanks for the post. This issue could be caused by corrupt system files. Hope this helps. Monday, January 11, AM. Hi Sorry for not replying sooner, got some what side tracked onto something else.

I've tried both the fixes suggested and I still have this problem. Any other suggestions? Monday, April 5, PM. Wednesday, April 7, PM. I am currently experiencing this issue as well. Wednesday, June 2, PM. I can see the DNS event logs though.

Thursday, June 3, PM. I had the same problem but only with one scope. I had to delete the affected scope and recreate it. As time passes, you may experience what we call DHCP drift, which means the contents of your DHCP database no longer reflect accurately what's on your network.

When you reconcile a scope, the DHCP server will cross-check the database contents with the contents of the Registry, reporting and fixing any inconsistencies it finds. You can also reconcile scopes to recover from a corrupt DHCP database. You first remove the database files, then reconcile the server's scopes. Feedback will be sent to Microsoft: By pressing the submit button, your feedback will be used to improve Microsoft products and services.

Privacy policy. Thank you. Specify the ReportOnly parameter to view the inconsistent records without repairs. This command gets inconsistent DHCP client records for the scope The command specifies the ReportOnly parameter. Unlike the previous example, this command makes no changes to inconsistent records.

Runs the cmdlet as a background job.