Why logging off is important




















Also, this article only applies to secure versions of Windows. Windows 7. You should see Shut down , but don't click on that. There is a tiny arrow just to the right of that. Click that—it's a little difficult, because you have to click only on the tiny arrow, and not on the much larger button it's attached to. When you click the arrow, a new menu will pop up. Click Log off. Windows Vista. Look for the tiny arrow just to the right of the lock icon. Click that—it's difficult, because you have to click only on the tiny arrow, and not the lock button next to it.

Click Log Off. Windows XP. Click then Log Off. Windows Click then Shut Down. A box will appear with a selection list. Choose Log off and click OK. Windows NT 4. Select Close all programs and log on as a different user and click OK. Windows NT 3. Alternatively, you can double-click the control box of Program Manager, select Log off in the selection list that appears, then click OK.

If so, you just need one extra keypress. Before you log off, make sure you know how to log on again. You need to know both your user name and password. Misuse or mishandling problems are occured. 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. With this setting in place I don't have any problems when users don't log off. 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?

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. I'm not going to add any reasons, just agree that it's a security issue. If you cannot get your boss to work with them or their boss, or everyone's boss if need be then maybe that's not such a great place to work, since there's obviously no respect for IT.

To be honest, a lot of the reasons you used to have to have people log out shouldn't really be an issue anymore i. Computers need to be rebooted 'every so often' for two reasons:. To combat this our updates are set to keep annoying people until they restart.

As far as the computers tending to go crazy, I just ask people if they've rebooted in a while if they have a strange problem. We're talking about one problem every few weeks, so nothing getting worked up about. As far as every night, I can't think of a sound technical reason to require it.

While people should have their work saved and closed out before they leave, it is extremely rare for an unwarranted server reboot to actually cause a problem. I used to be common long ago, not so much today.

If there's no good reason for the policy then change the policy. If you have elements a policy that aren't important and everyone knows it then it makes it harder to enforce the parts that really are important. Nobody said anything about shutting them off. You sure don't leave a user account logged into the server when you're not actively using it though. Servers run just dandy with zero accounts logged into the desktop.

You can set services and applications to "run as" a user. Doesn't always have to be an interactive user account either. It's not about physical access, so just a locking screensaver doesn't work. The thing you have to defend against is having an actively authenticated session with a live network token sitting on the box, waiting for someone to remotely poach it.

We, as a group when I worked for a larger company, used to grab unattended and unlocked computers, and send emails as the logged in user. I would send them to their Boss, letting him, the manager , know. The first email would be the heads up that another email was coming, the second was generally a letter of resignation.

You should see the look on the end users face when they get a reply to a message that came from, sent to their boss, stating that, I am sorry that you have decided to leave the company, I have accepted your resignation.

It does not happen more than once, I can guarantee that. Your boss should really be in your corner over issues like this. Many times I've had users come to me saying they cannot use network resources when logged in. It usually boils down to that their password had expired and because they never logged out they were never being warned.

I have never tried this before, but maybe you could use logon times in AD to force the two problem users to log off automatically after their work hours. Seems that lots of people can't distinguish between logged off, screen locked and shutdown. A lot of people seem to have confused 'shutting down' with 'logging off' in this thread. This post is just one example of many.

To continue this discussion, please ask a new question. Get answers from your peers along with millions of IT pros who visit Spiceworks. A frequently used computer that needs to be shut down regularly should only be powered off, at most, once per day. Doing so frequently throughout the day can decrease the lifespan of the PC. If you have accidentally restarted any computer part, then it may cause damage to your RAM due to excessive heat. Sometimes your memory module may have a fault that slipped through quality control.

These errors can get worse over time.



0コメント

  • 1000 / 1000