<<Definitely try and call first>> You must have missed some of the messages. This is an old thread.
1. Should call first: We do call first unless, 1. It is an emergency, 2. The user is on a shared computer, no one answers the phone and condition 1 also applies at the time. In this case, it was a developer machine (ergo buggy software) so it had no real data that could be inadvertently viewed (only test data), the user failed to answer the phone (which is not unusual for developers deep in concentration), it was late at night so he was working on something critical to him. 2. The machine was one of three with a buggy POS piece of software that was eating cpu by the second. One ran out of cpu time, the second I was able to stop before it reached 100%, the third I was trying to save. The question was, In an emergency when contacting the user has failed, but someone is using the machine, and when you see a crash about to occur, do you hide and watch it happen, or do you remote in, resolve the issue and the user is normally not inconvenienced at all. The consensus both here and at work both was that I should have just watched it crash. Now that I know that, I can act accordingly, and quote management when they scream about lost work. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Friday, June 06, 2008 9:32 AM To: NT System Admin Issues Subject: Re: General question - Logging onto a user's computer "Steve Kelsay" <[EMAIL PROTECTED]> wrote on 06/05/2008 07:26:44 PM: > I just got reamed for preventing a crash. It irked me, so let me > know what you think, or what your policy is. > > Management simply said "It is not acceptable to log into someone > else's computer without their consent." Period. Exactly. Look at it from their side - you're remoted in; perhaps you might see (inadvertently or not) company information you shouldn't see. Like - you're about to be fired ... and it irks you so much that you do something rash ... > If you see a situation where a crash is about to occur, do you just How do you know that there is a crash about to occur? Are you notified by the computer in question by some monitoring software? > watch because you are trying to identify who is actually using that > workstation at that moment and try to contact them, or do you remote > in, displaying a "Netmgr x has remotely connected to your pc" alert > box, and resolve the issue before they crash and lose a day's work? Definitely try and call first. Especially in light of management's view, which you quote above. ~ Upgrade to Next Generation Antispam/Antivirus with Ninja! ~ ~ <http://www.sunbelt-software.com/SunbeltMessagingNinja.cfm> ~
