I probably wasn't clear enough; Tech B found the root cause (specific update that hosed a DLL)... That's always been my troubleshooting focus. Find the root cause...
*********************** Charlie Kaiser charl...@golden-eagle.org Kingman, AZ *********************** > -----Original Message----- > From: Jacob [mailto:ja...@excaliburfilms.com] > Sent: Thursday, August 27, 2009 10:47 AM > To: NT System Admin Issues > Subject: RE: OT: Our profession has been exposed > > Hmm... Still have to found out the root cause. Why did 12 > machines have the same DLL problem at the same time? Bad > patch? Copying over the DLL is just a quick fix which is > perfectly normal in this situation. Still need to find the > actual problem. > > When I troubleshoot, I like to come up with a temp, quick fix > (what is takes to get the user/system going).. then a > permanent fix which addresses the root cause (which can take > time). Most techs I run into just look at the temp, quick fix > and never look at the root cause. Could be the just do not > know to (training) or no time to look at the root cause (a > whole other issue). ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
