Since there doesn't seems to be a way to report feedback for Windows Server like there is for Windows 10, I'm creating a post here. (If anyone knows how to report feedback for Server 2016, please share).
Anyway, after upgrading a Windows Server 2012 R2 Server Core machine configured as a AD DC.
Before upgrading, the NetLogon service is set to Automatic, after an in-place upgrade, the service has it's startup type changed to Manual.
After changing it back to Automatic, things work like they should.
I haven't tested on a full UI server, so not sure if this is a Server Core issue, or a general upgrade issue.
So if anyone else experience issues after an upgrade, this might be the reason.
Seems to be a bug of Windows 2016 upgrade?
Here's a similar recent post : https://social.technet.microsoft.com/Forums/windowsserver/en-US/74c54d71-c04f-421d-abaf-0d5bf35ec3b6/server-2016-inplace-upgrade-from-2012-r2-various-issues-netlogon?forum=winservergen
He says to set it back to Automatic and restart server after.
MCSE Server and Desktop Infrastructures
MCSE Messaging, Collaboration, Productivity, Mobility, Cloud Platform and Infrastructure
Thank you for posting this GurliGebis!
I've just wasted two hours chasing my tail on my DC's NLA profile continually defaulting to "Private" instead of "Domain". I could get temporary success from restarting the NLA and/or the AD DS services, however a system reboot would make the network profile revert back to "Private".
Many thanks - I will be passing this info on to fellow system admins to save them the headache.