Quantcast
Channel: Directory Services forum
Viewing all articles
Browse latest Browse all 31638

Logon issues when pending reboot/shutdown on domain controllers

$
0
0

Is it safe to stop the Netlogon service before shutdown on domain controllers? We are experiencing logon issues with some applications (mostly BizTalk) when automatically patching our DCs using Windows Update.

Event 6913 can be seen in the BizTalk Server log.

An attempt to connect to "BizTalkMgmtDb" SQL Server database on server "BIZTALKDBSERVER" failed.
 Error: "Login failed. The login is from an untrusted domain and cannot be used with Windows authentication."


I’ve read about others experiencing the same issues here:
 
https://blogs.msdn.microsoft.com/biztalknotes/2013/08/22/biztalk-hosts-fail-when-domain-controllers-are-rebooted/
https://support.microsoft.com/de-de/help/2683606/domain-members-fail-authentication-when-domain-controller-is-shut-down

https://blogs.msdn.microsoft.com/biztalkcpr/2009/02/11/do-you-see-the-following-errors-on-your-biztalk-server-every-time-you-reboot-your-domain-controller/
 
Also, from what I can find on the matter, it has long been a problem that domain controllers stop dealing with authentication requests before reboot/shutdown. Shouldn’t this be fixed from Microsoft? Of course we can all set up scheduled tasks via GPOs, however that is no real solution to the actual problem.
 
Thank you.


Edit:

Maybe I should add some info about our environment in case anyone would actually work on this:

DCs running 2016 server

BizTalk 2013 R2 on 2012 R2 server

SQL 2014 on a 2012 R2 server


Viewing all articles
Browse latest Browse all 31638

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>