I do not believe there is a valid excuse here for detecting my tools as dangerous. To my anger and frustration, my ipscan tool was gone. This evening while configuring a serial-to-wireless ip bridge on a medical device, I needed the ability to scan the scope after configuring the unit as it is using dhcp and there is no other way to determine the IP post configuration.
#Download angry ip scanner install
If that's the case why does it get quarantined automatically? And how does putting Angry IP scanner in the same category as applications that install themselves without asking give me more control? "SR fully understands that the use of these tools is legitimate for network administrators and their purpose is not to decide on behalf of them what tools they want to use in their environment but instead to allow more control on the use of such tools" I'm refusing to let this drop with my account manager and I won't give in until either they remove Angry IP scanner from their definitions or my company is no longer using SAV. It doesn't take much for the department to lose confidence in an application and I still get comments about the memory leak in an earlier release of SAV. If Symantec feel it's ok to block legitimate applications then what's to stop them doing it again and again? There are a few hundred users in my IT department alone, and I don't want them coming to me every week to have another tool unblocked. That's annoying enough on it's own but I feel that that there's a much larger principal at stake here.
#Download angry ip scanner full
Now I can download and use the scanner but whenever a full system scan runs it still gets quarantined, although it does allow me to undo it. It took a few days and just when I'd got the exclusion fixed they recategorized it from hacktool to other and I had to do it again. Configuring the exception wasn't working so I had to work with a Symantec support technician to fix it. I have to say I'm very annoyed about this too.
0 kommentar(er)
