Windows Server Network Identification. How to do it manually/deferred?

Question

Network administration

As you know, after turning on the server, it identifies the network connection. If there is a valid domain controller on the network, the network location is set to domain.name and the firewall rules for the domain network start working. My problem is that the domain controller is initialized later than the normal servers and for them the network location remains as an "unidentified network" with the corresponding access problems to various services. Can I somehow manually / scheduler restart the identification procedure? Now only switching off/on the interface helps, which involves physical access to the server and running around the entire enterprise after each blackout. Or is it better to make a backup CD on fast hardware?

Answer 1

CD must always be raised 1m