I have an odd issue. I have a domain environment that needs to be powered down every night.
The environment has 1 domain controller (which is used for both AD and DNS services) and roughly 10-15 Windows 10 PCs.
When I boot the system up in the morning I boot the domain controller first, then after I log into the DC I power on all the Win10 PCs.
The problem I have been facing since the June 2020 Windows Updates is that the Win10 PCs don't want to connect to the DC upon the first boot. Users attempt to log on to the Windows 10 PCs and receive an error message stating "we can't sign you
in with this credential because your domain isn't available." This will happen to anywhere from 1-10 PCs on any given day, and the PCs that this occurs on changes every day. These users have all logged into the domain before. The group policy
is set to cache 5 sets of credentials. So even if the PC cannot connect to the DC initially, the users should still be able to log into the PC but cannot. Also, I'm not sure why the PCs cannot domain authenticate in the first place. The only
way the users can log into one of the affected PCs is to reboot the PC and then log in. Another thing I have noticed is that if a user IS able to log into a PC using a cached credential (prior to rebooting the PC) the network icon in the bottom right
corner doesn't show the domain name. Instead it shows "network #" with the # being any number from 2-10.
NSlookup works on all PCs.
All PCs including the DC have static IPs.
All PCs including the DC point to the static IP of the DC in the DNS settings for IPv4.
I have tried removing a Win10 PC from the domain and rejoining the domain and the issue still occurs.
One troubleshooting step I have tried is to let all Win10 PCs sit for 20 minutes or so before logging in, and they all logged in no problem at that point. (this is not a viable option, as the network and PCs need to be ready to use with no issues within
a few minutes -not 20- of the environment being booted up).
Again, this issue started after the June updates, but I don't see any known issues regarding DNS or AD, or any changes regarding either of those services. Am I missing something?
Any help would be appreciated. Can provide event viewer logs if needed.