Discussion Locked

importance of logging out of network??

0 helpful
17 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
We have discovered that many users in our company do not log out of the network at night for not wanting to wait with the time necessary to login in the morning. Aside from not being able to get the latest updates of software the firm rolls out, what are some of the other negative implications of not logging out of a network each night on the user end?

17 replies

by vramji

In network environment, Everybody must logout the systems.

1. files may be corrupted
2. Misuse or mishandling problems are occured

by gigelul

You can implement a policy for use a custom screen saver from resource kit WinNT.
WinExit is like any other screen saver. It can be configured and tested using the Desktop applett in the Control Panel. When activated WinExit will beep, to indicate that logoff process is about to begin, and displays the logoff dialog box. If no action is taken and the countdown timer reaches zero, the system will initiate logoff procedure. At any given time before the countdown timer reaches zero you can abort the process by either moving the mouse pointer over the dialog box or pressing any key on the keyboard.
But the maximum timer can be 999s(winexit)+99min(windows).
Or you must set in User Manager\Policies\Account Policy - Forcibly disconnect remote users from server when logon hours expire. With this setting in place I don't have any problems when users don't log off.

by pschuvie

The biggest reason - Security -

If that is the attitude and some one needs to be convinced it is a problem why do they lock the door at night? or maybe you dont.

While I like Florinel's solution, I really think that if you don't get this tightened up, with the full support of management, then all that solution does is encourage everyone to disregard any system activity or policy that is inconvenient.

by ann777

1) HDDs have a MTBF (mean time between failues) rating, and if a HDD is left activated 24/7, then there may be more hardware failures than desirable.

2) Power issues (especially if you have janitors who don't care if their vaccuum eats a power cord). Surges or brownouts cannot affect a powered off computer.

3) Security issues... what other people may be able to see if they can access a persons computer contents.

4) Backup issues if users have network data files open files on their workstations.

Depending on the OS and applications used, it's probably a good idea to reboot/shutdown at least once a day and clear memory leaks.

by bitsybug20

A major problem I find, being at a remote location and using a vpn client to get into the company network, is that if the electricity goes out or the network goes down at night while a computer is logged into it, the settings for the DNS configuration are incorrect the next day and have to be reconfigured or it won't loggin to the network at all. Also, as the others have stated, SECURITY is the biggest issue. Hackers are everywhere, and some have nothing better to do than to mess with peoplescomputers. They will find that if they logout, in the longrun, the time will not be as bad as if someone wipes out their drive or steals their email address book and attacks the whole company with viruses! Then they really would have some down time!

by dlafrombois

Everyone is correct. The fundamental issue here is security. Two points need to be addressed.

1) In some cases someone could come behind the valid user, who did not log off correctly, and capture their old session. Although most system will run a process to clean these cached session, someone to access these old session before the house keeping.

2) If the session is not shut down correctly, file can be corrupt and user may loose data. If the use shutdown correctly or log off it ensure that all files and data is closed correctly.

Hope this helps.

by joseph moore

Just to add to your level of paranoia:
If your users do not log out at night, and if their systems are not locked (with a screen saver password on Windows systems, for example) then what is to stop a member of the nightly cleaning crew from accidentally hitting the mouse and (somehow) deleting that document the VP was working on.
If the VP had logged out of his workstation before he/she left, then this could not have happened.
Accidents (and deliberate accidents) can and do happen all the time. Every single workstation on the network is a potentially vulnerable point to anyone who can gain physical access to your office. If workstations are left on and logged in, then all kinds of damage can be performed. And all without "hacking".Start up a new IT policy that everyone needs to log out when they leave at night. To add to that, you can implement Logon times, so their account is logged out automatically at a certain time (but this method will cause problems; trust me!)
Password-protected screen savers are the minimum you should implement if you can't get the logout policy.
Lastly, perhaps you need more domain controllers to speed up the morning login times, if that is the root cause of people not wanting to log out.

hope this helps

by jereg

All of the answers are good, I'd only add that depending on the backup software you're using, any PC that's on at night may be holding files open on the server, and these files won't get backed up. Even with an open file manager running, some files still resiste backups.

This discussion is closed to new replies.