I'm not sure what the circumstances are nor how you made this determination. The whole thing sounds a little weird.
I would say that A) I would never just take over someone's computer if they were working at the same time. If they were out to lunch, and I had some premonition that something was going to happen that was going to impact the company or others, then I might do it. But I'm not sure I remember that ever happening. B) I have remotely connected to hundreds of computers over the years to perform some kind of maintenance or fix without informing anyone. They want me to manage computers, Ill manage them, but I'm not going to ask permission every time I need to do it and I would only logon with my own or other support credentials, not the users. If I was going to use user credentials, I'd do it locally or with them in my cube. HOWEVER, there may be certain higher level execs that you work with that don't want anyone touching their computer and in that case, either do it with them in the room or let it melt. From: Steve Kelsay [mailto:[EMAIL PROTECTED] Sent: Thursday, June 05, 2008 4:27 PM To: NT System Admin Issues Subject: General question - Logging onto a user's computer 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. If you see a situation where a crash is about to occur, do you just 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? ~ Upgrade to Next Generation Antispam/Antivirus with Ninja! ~ ~ <http://www.sunbelt-software.com/SunbeltMessagingNinja.cfm> ~
