0

I am bringing up a new site and installing dual homed Windows 2019 RAS/Web servers. The interfaces on the DMZ must have a default gateway defined or they simply don't work. The "internal" interfaces do not have a default gateway defined and this is fine once systems are attached to a domain controller

But while these systems are stand-alone, rebooting reverts the internal NICs profile to "public". I, of course, change it back with Set-NetConnectionProfile. But next reboot and we are back where we started.

It is pretty darn annoying since I can no longer RDP to them! I am wondering if anyone has found a simple solution to this behavior.

Not interested in anything convoluted; no registry hacks or the like. As I say, once my domain controllers are up, this will take care of itself. But I deal with this incredibly moronic behavior (hope you are listening, Microsoft) every time I bring up a Windows site.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.