No Logon Servers Available to Service Request (after Windows Updates)

Hi Everyone, 

Thanks for taking the time to read/answer my problem.  I am an admin and some of my users have been experiencing this issue recently.  It seems to have happened after Windows Updates.  Our systems are Dell 7250/7450's about 2 years old (give or take).  They are running Windows 8.1 and mostly standard programs (office, Kaspersky Anti-virus) but, they are also running Dell Data Protection|Encryption (Enterprise Edition).  

My first case was a user in the airport heading to Japan and couldn't get logged in.  That was bad.  Now, I have lots of users who cannot login to their computers unless they're on the local network.  I'm interested in finding out how I can fix this.  I've seen lots of posts that say I need to remove/readd to the domain but, I'd like to avoid that if possible and actually understand what's causing the problem.  

Here's the sequence of events that seems to have led up to the problems.  

1. Users reported having to reboot after windows updates
2. Users received BIOS message that there are no available windows installations and that SecureBoot has caused a problem.  This was directly related to the Recent Windows Update (MS16-100 aka KB3172729).  This patch caused Dell Encryption to Encrypt the EFI folder (per Dell web article:  https://www.dell.com/support/article/us/en/19/SLN302901).
3. I fixed this using the startup repair on the installation media and users were once again able to get into their systems.
4. HOWEVER, now some of these users are not able to cache their creds.  They leave the local network and get the message "no logon servers available...blah blah blah"
   
   

Log Name:      Security
Source:        Microsoft-Windows-Security-Auditing
Date:          8/19/2016 2:14:59 PM
Event ID:      4625
Task Category: Logon
Level:         Information
Keywords:      Audit Failure
User:          N/A
Computer:      <<REDACTED>>
Description:
An account failed to log on.

Subject:
Security ID: SYSTEM
Account Name:<<REDACTED>>$
Account Domain:ECM
Logon ID: 0x3E7

Logon Type:7

Account For Which Logon Failed:
Security ID: NULL SID
Account Name:<<REDACTED>>
Account Domain:<<REDACTED>>

Failure Information:
Failure Reason:An Error occured during Logon.
Status: 0xC000005E
Sub Status: 0x0

Process Information:
Caller Process ID:0x268
Caller Process Name:C:\Windows\System32\winlogon.exe

Network Information:
Workstation Name:<<REDACTED>>
Source Network Address:127.0.0.1
Source Port: 0

Detailed Authentication Information:
Logon Process:User32 
Authentication Package:Negotiate
Transited Services:-
Package Name (NTLM only):-
Key Length: 0

This event is generated when a logon request fails. It is generated on the computer where access was attempted.

The Subject fields indicate the account on the local system which requested the logon. This is most commonly a service such as the Server service, or a local process such as Winlogon.exe or Services.exe.

The Logon Type field indicates the kind of logon that was requested. The most common types are 2 (interactive) and 3 (network).

The Process Information fields indicate which account and process on the system requested the logon.

The Network Information fields indicate where a remote logon request originated. Workstation name is not always available and may be left blank in some cases.

The authentication information fields provide detailed information about this specific logon request.
- Transited services indicate which intermediate services have participated in this logon request.
- Package name indicates which sub-protocol was used among the NTLM protocols.
- Key length indicates the length of the generated session key. This will be 0 if no session key was requested.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-Security-Auditing" Guid="{54849625-5478-4994-A5BA-3E3B0328C30D}" />
    <EventID>4625</EventID>
    <Version>0</Version>
    <Level>0</Level>
    <Task>12544</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8010000000000000</Keywords>
    <TimeCreated SystemTime="2016-08-19T19:14:59.114149300Z" />
    <EventRecordID>29482</EventRecordID>
    <Correlation />
    <Execution ProcessID="576" ThreadID="1892" />
    <Channel>Security</Channel>
    <Computer><<REDACTED>></Computer>
    <Security />
  </System>
  <EventData>
    <Data Name="SubjectUserSid">S-1-5-18</Data>
    <Data Name="SubjectUserName"><<REDACTED>></Data>
    <Data Name="SubjectDomainName"><<REDACTED>></Data>
    <Data Name="SubjectLogonId">0x3e7</Data>
    <Data Name="TargetUserSid">S-1-0-0</Data>
    <Data Name="TargetUserName"><<REDACTED>></Data>
    <Data Name="TargetDomainName"><<REDACTED>></Data>
    <Data Name="Status">0xc000005e</Data>
    <Data Name="FailureReason">%%2304</Data>
    <Data Name="SubStatus">0x0</Data>
    <Data Name="LogonType">7</Data>
    <Data Name="LogonProcessName">User32 </Data>
    <Data Name="AuthenticationPackageName">Negotiate</Data>
    <Data Name="WorkstationName"><<REDACTED>></Data>
    <Data Name="TransmittedServices">-</Data>
    <Data Name="LmPackageName">-</Data>
    <Data Name="KeyLength">0</Data>
    <Data Name="ProcessId">0x268</Data>
    <Data Name="ProcessName">C:\Windows\System32\winlogon.exe</Data>
    <Data Name="IpAddress">127.0.0.1</Data>
    <Data Name="IpPort">0</Data>
  </EventData>
</Event>

I'm not directly blaming DDPE or the Windows update that fixed SecureBoot BUT, they are related somehow.  I have Dell looking from their end but, I want to cover my bases by looking at this from a Microsoft perspective as well.  

Please let me know if there's any further information you would like.