Microsoft has released Security Updates (SUs) for vulnerabilities found in:
Exchange Server 2016
Exchange Server 2019
SUs are available in a self-extracting auto-elevating .exe package, as ...
Updated Jun 13, 2023
Version 1.0
Blog Post
Ok, that's easy then 🙂 You can not turn on "Domain Network" by yourself (just Private and public), but you can use an:
[PS]> Restart-Service NlaSvc -Force
to do an NIC autodetect for the Domain Profile. If DCs/AdDomain can be found by DNS, this will work. You can see the "sensing" in Network Center "Detecting network..." or similar. If this will not work (and it won't sometimes, 1 of 100 times) then disable and re-Enable the NIC for "heavily force/pushing" an autodetect on the Firewall Profiles of the NIC. (Beware of RDP sessions which will break the connection when NIc is disabled, I use the VM Console for this operation, first time I forgot^^). Server reboot would probably also be OK, but sometimes it is not possible or customers try to avoid it because of application dependencies)