Problem with DHCP server in Active Directory

Question

Active Directory

We have an organization consisting of several branches located in nearby cities, the local networks of which are connected into a common "corporate" through the WAN of a local provider. Since the connection between the branches is quite reliable, the head of the IT department and the network administrator decided (and they cannot be persuaded here) to install AD controllers only in the central branches, and leave the local networks of the sites (branches) without them, while the workstations in the sites are authorized on the controllers AD, located in the central offices. Each of the sites has a server for storing files and a DBMS with which users work. In addition, DHCP (a standard Windows service authorized in AD) is configured on it to automatically distribute IP within the subnet of the site.

Faced withnext problem. In the event of a long network break between the site and branch (due to a line failure), the site server with DHCP enabled refuses to register clients, apparently due to the fact that it cannot find the AD controller. It turns out that the local network of the site is completely out of order. Although, the main tasks should run inside the local area of ​​the site, with the exception of email and some other general processes.

Since DHCP is configured in this way only on those sections for which I am responsible, and on most of the rest - IPs are registered statically on workstations, the administrator and the head of the department insist that I remove DHCP services from my sections and manually drive in addresses for everyone .

I see 3 solutions here:

1) accept and transfer all workstations to static IP (horror in my opinion!);

2) use some third party non-AD DHCP service (sounds more reassuring);

3) solve this problem within the framework of a standard DHCP server so that it does not refuse to work if communication with AD controllers is lost (the best option).

Tell me, is there such an opportunity to solve the problem in the 3rd way? Thanks in advance for all the suggested ideas.

Answer 1

If DHCP is on 2003, then maybe give this server also the role of a secondary controller?

Answer 2

Alternative configuration in the properties of the network connection of the client will not work? Settings can be synchronized with startup scripts.

Answer 3

The right decision is to install a RODC.