I was wondering what happens if a machine gets disconnected from the network for a temporary (half second maybe) amount of time. If the user has LF Client open, when this happens, would the users session have a new session ID?
If a machine has a temporary disconnect to the network, with LF Client open, will a new Session ID be created on reconnect?
Each session has a unique session id, so the question boils down to whether a new session is created. For such a short network disruption, I wouldn't expect either end of the connection (client or server) to notice; if there is active communication at the moment of disruption, TCP should handle retransmitting any lost packets. The longer the two ends are unable to communicate, the more likely it becomes that the server will assume the client is gone (and log them out) or the client will discover a problem and try to reconnect.
All that said, why are you interested in session ids?
Yes, entry locks are tied to a session and if you see a new session id in Audit Trail then that suggests that the user was reconnected. You might want to look into the login and logout events for those sessions; that the document was reported as locked suggests that maybe the first session was never really terminated.
Regular write locks are really only necessary while there are unsaved changes in the client. Maybe your users have an unusual use case, but I would expect users would save their changes fairly regularly. If they really need to hold a lock all day you might encourage them to check out the document, since those locks persist over sessions.
Can a column be added "connection ID" in the entry locks node?
The Sessions node in LFAdmin Console lists the username, application and computer for each connection.