Error message while trying to change Private network type to Domain Authenticated

The error message is pretty self-explanatory.  But to reiterate and/or clarify. You don't set a network connection to domain.  You can choose public or private. But domain is selected by the OS when it authenticates to a domain controller. Which means it had to be domain joined, the DC has to be reachable, and the connection has to be secure.  Should these fail  then the connection falls back to public or private.

OK I have network connections that identify themselves as "Public" or "Private" even when they should be "Domain Authenticated" since I am booting up the laptop from a proper Windows shutdown while they are connected to a docking station that is connected to an Ethernet cable and while these laptops are also connected to the company's Wi-Fi network.

That is why I am hoping to be able to change these network types from "Public" or "Private" to "Domain Authenticated." I also don't want to have to log out of, shutdown, or restart my laptops just so that they can re-authenticate to the domain controllers to become "Domain Authenticated."

Do you know any ways of being able to change the domain types to "Domain Authenticated" without having to log off of, restart, or shutdown Windows 10?

In windows 10, the location is per connection.  So a wired dock connection can be domain while a wifi is public, if both are being used simultaneously (not that I'd ever recommend such a configuration.  Gateways and routing gets very tenuous and dual-homed machines.)

The profile is updated whenever it detects a network status change.  So when you aren't docked, the wired NIC is effectively disabled. You dock...that's a network change for that hardwired NIC.  The presence of a DC is checked, and if authentication to the DC is successful, that connection is put in the domain profile.

Wifi...if you connect to your phone as a hotspot, you'd be public or private. If you change (after being logged in) to a corporate WiFi network, and it can reach a DC, *that* connection will be changed to "domain."

So it is per connection and per network status change.  That does not require a log off, restart, or shutdown.  With caveats.

Contacting a DC does require proper DNS.  Again, dual homed machines can get funky here.  If you bounce from a home network on 192.168.0.0/24 and the corporate Wi-Fi is also 192.168.0.0/24, the system may not see a reason to renew a lease, and use your home DHCP settings.  Which, if that happens to be ISP DNS servers and the de-facto standard of 192.168.0.1 for a default gateway...you magically still have internet access, but *don't* have the right settings to see the DC.  Of course an ipconfig /release and ipconfig /renew would fix this, since the issue is just bad lease info...but it makes troubleshooting obnoxious because the problem isn't immediately apparent.

So it really boils down to Networking and TCP.IP basics.  Gotta check those, and gotta make sure your domain-joined computers can actually connect to their DCs and are authenticating when you connect.

-Cliff