What about policies that don't get applied except at boot time, managed software installs, changes that are made by login scripts. We have many staff who just step away from their PCs at the end of the day. I have the machines lock after 15 minutes of idle time. All the time I'll get a ticket stating that an icon on their desktop isn't working anymore or that they don't have a certain software, and I will ask them when the last time they logged in was. Most will say that morning but I tell them to restart their PC and low and behold their issue is resolved.
James ----- Original Message ----- From: Mike Gill To: NT System Admin Issues Sent: Thursday, October 22, 2009 4:45 PM Subject: RE: User who doesn't like logging off / shutting down Locking the workstation doesn't address software updates or deployments being missed, among other things. Andrew should look into why it takes the computer so long to log in that someone would complain. My 3+ year old Dell desktop takes 5 seconds or a little more to be at a useable desktop in Vista. He could also tell her she at least needs to log out on the weekends, or restart the computer as she leaves on Friday. Find some middle ground. -- Mike Gill From: Richard Stovall [mailto:[email protected]] Sent: Thursday, October 22, 2009 1:33 PM To: NT System Admin Issues Subject: RE: User who doesn't like logging off / shutting down Can they hit the Windows key and L at the same time? If not, you can do it for them using Group Policy. From: Andrew Levicki [mailto:[email protected]] Sent: Thursday, October 22, 2009 4:30 PM To: NT System Admin Issues Subject: User who doesn't like logging off / shutting down Hi, I've got a user who doesn't want to log off let alone shut down their computer. They claim that it takes too long and they haven't got time to wait to log on again or start up. They're important enough that I can't force them to do so, but I'm worried about possible problems. The only detrimental effects that I can think of are added power consumption and ticket expiration. Can anybody else think of any other pitfalls or even have any experience of this and how did you deal with it? Thanks, Andrew ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
