Windows 10: PC on Domain network locking automatically when using

Hi team ,


We have a SCADA system at one of our client's which comprises of around 11 operating workstations with OS - Windows 10 LTSC and servers with OS-windows Server 2016 . It is observed that some of the operating workstations are getting locked out randomly while under operation under the user "Operator-1" with all software and service running in the background . User has to further to put the password to sign in again. This is disturbing the plant operation.


1. This is happening only for 3 or 4 workstations in a random manner and frequency is 2 or 3 times per month. Domain settings are default domain controller settings only .


2. It was observed that the user "Operator-1" was logged in to the domain from more than 8 workstation along with active sessions of other user accounts also.


Now we had created users in active directory and segregated them to the different workstations, so that a single user is not logged in to the domain from more than 4 workstation. But we would like to know the actual root cause of this lock out issue , which has to prevent similar future incidents.


***Original title: Windows 10 workstation gets locked out automatically while working.***

:)

 

Domain Account Locked Daily


Hello,
I have similar problem. My domain account locks from time to time. I just upgraded from W8.1 to W10.
I tried many steps to solve this but none is working.
I found out some interesting things. Using a tool "Account Lockout Status" I found that Last Bad Pwd value is changed when I enter credentials after computer automatic or manaul screen lock out.
I can work normally if I do not get a message about "Windows needs your current credentials":



If I get this message and do nothing - account very quickly locks out.
If I do quick screen lock and unlock it will go ok for some time.
Very strange. I replicate the problem of Last Bad Pwd value using another PC with W10. Some other users in domain are ok some same as mine.
Something wrong with specific users and Windows 10 combination..




Regards,
Gediminas

 

Network Location Changing on Domained and undomained machines randomly


Ok, I dug further and found my own answer. The issue is in a service called Network Location Awareness. What can happen on login or config change of a connection is that NLA will check and reset the location to public if it unsure what kind of network it is connected to. Public network location setting will cut off Network discovery, fileshare and locks down the firewall. Anyways what can happen is upon login if your domain controller or another server is slow to respond to the location inquiry from NLA it will automatically go into a Public location and lock down everything making you either reset the location with powershell or unjoin and rejoin the domain. ANNOYING!
HOW TO FIX
Push windows key + r
type services.msc press enter
scroll down to Network Location Awareness in the list on the right hand side and double click
In the dialogue box you should see a drop down menu set to Automatic
Click that drop down and set it to Automatic Delayed or Manual and click apply then exit out of services.

 

PC Build Steps

Ok just because I like steps i am going to create some steps. Please give me the stamp of approval/disapproval

• Install system in case
  • Remember to connect SSD and optical to same SATA ports on motherboard
• Turn on PC
• setup HDD
• run blend test in prime95 for 30-60 min
  • run realtemp at the same time

• While in Prime95 test
  • if CPU goes above 70c in RealTemp, I have a leaky CPU
  • if my system locks up or blue screens, there is an instability in the system somewhere
  • if my system does not lock up or blue screen, my CPU is not damaged and I am in the clear!

What do you guys think??