I have a Windows Server 2012 R2 box with the Hyper-V role installed which is also Domain Controller. The server is in a DMZ area of the network, and the only other Windows box is a Server 2012 R2 virtual machine on the same server. The server also hosts a Web Proxy VM which is the network gateway.
The issue I have is that every time the server is booted, because the Web Proxy VM is not yet started, the server can't find the gateway IP and doesn't identify it's own network adapter as 'Domain', it is instead labelled as 'Public'. Disabling and re-enabling the NIC corrects this issue, but can't be done remotely as RDP ports are not open for 'Public' networks, necessitating a trip to the server room.
What is the best way to get the server to re-evaluate the network it is connected to such that it identifies it as 'Domain' and applies the correct firewall rules, within a reasonable time after boot but such that the Web Proxy VM has had time to boot also?