I am real interested in how he knew. From the sound of his email "resolve the issue before they crash and lose a day's work?" it sounds like he was predicting a software crash that was in some way preventable.
----- Original Message ---- From: David Mazzaccaro <[EMAIL PROTECTED]> To: NT System Admin Issues <[email protected]> Sent: Thursday, June 5, 2008 8:39:19 PM Subject: RE: General question - Logging onto a user's computer That is interesting... S.M.A.R.T Hard drive monitoring? Maybe SNMP traps? He must have a slick setup....hopefully we'll find out soon! :) ________________________________ From: mck1012 [mailto:[EMAIL PROTECTED] Sent: Thursday, June 05, 2008 8:30 PM To: NT System Admin Issues Subject: Re: General question - Logging onto a user's computer I think if it is a written policy you should not log in to the computers. The computers are not the property of the users but they are also not your property so you need to follow policy. And to know when a computer is going to crash, I dont know about that one. You are either trying to hide something or you did something that was going to cause the computer to crash. I dont think we got the whole story here. ----- Original Message ---- From: Sean Martin <[EMAIL PROTECTED]> To: NT System Admin Issues <[email protected]> Sent: Thursday, June 5, 2008 7:56:08 PM Subject: Re: General question - Logging onto a user's computer I'm also curious as to how you knew the PC was about to crash. Our indication of an individual PC crashing is when the user calls to report it. We've got some 1200+ PCs to manage though. I'm kind of on the fence on the whole policy issue though. We have the same policy stating admins are not to remotely administer any "users" PC without their prior knowledge. The policy is there for confidentiallity purposes (user may be working on something we're not supposed to see). However, preventing potential loss of data should be greeted with thanks, not an a$$ chewing. - Sean On 6/5/08, Troy Meyer <[EMAIL PROTECTED]> wrote: Steve if you can see crashes before they occur remotely you need to be making more money. Perhaps Qwest will hire you, we have had some outages on our circuit this quarter and it has been a big PITA. Seriously though, not knowing the entire situation and what is going on, this sounds like an education issue for the boss and the users. Does the boss want to except the loss of productivity, if so, you have to let it go (or find another place to work). Most cases we aren't management and policy setters for privacy type concerns and so if you cant follow what is documented before you, find a place where it isn't an issue (from someone who has left because of bad management policies) BTW Why are they working on stuff all day that can disappear with one crash? Please tell me they save intermittently -troy 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> ~
