Endpoint Protection

Hi mates ;

     well I have been messing up with teefer2 for quite a long time now, and still havent found a safe way to remove it.
I delete all registries related to teefer from HKLM\system, I delete teefer 2 service and driver files and reboot my machine to find NIC broken (ipconfig shows nothing) .
    There are lots of discussions on teefer  on forums but no reaching to solution.

     For windows guys, does anybody know how to remove a network adapter without breaking NIC?  

Help

Have you tried using the "removeteefer.exe" tool? You will need to open a case with support to get this tool.

Thomas

From my practical experience, the best way to remove the Teefer2 drivers is to install the SEP client again with the NTP feature on the machine in question. After doing this reboot the machine. Then remove the SEP client from add/remove programs. This should safely remove SEP along with the teefer2 drivers from the system.

If this still does not remove it then you may go for the removeteefer.exe tool from Symantec support.

Let me know if this helps :-)

Depending on what version of SEP is installed, in MR2 and older releases if you check the TCP/IP properties of the NIC you should see the Teefer2 driver listed. You can then uncheck the box to disable it. This feature has been removed in newer builds of SEP however.

I have also had good success in removing Teefer2 by uninstalling the NIC from Device Manager and then restarting the machine. Windows should be able to automatically re-install, however you may need to have the NIC drivers handy.

RemoveTeefer.exe is another good option, however this would require that the client is installed on the machine as the utility needs to call on the MSI to complete removal. There are a few other criteria that would determine if this is a good candidate for this particular machine. This would require opening a case with Symantec Technical Support.

There is a manual removal procedure for getting Teefer2 removed from a machine via registry editing. This can be quite confusing for someone not familar with what they are looking for and the keys to be modified would be specific to the client machine, meaning each system having the issue would have a different set of keys in the registry, so you would certainly want to open a support case should you wish to go this route. Most likely an export of the registry would be needed so that it can be mined for the specific information.

Hi 
       I understand dealing with machine specific values of registries have to be avoided as they differ from machine to machine. I will try to get teefer2 removal tool, I guess it will work irrespective of machines( but as you said SEP needs to be installed on it) , will it ask for password for uninstallation? if yes then I would not waste my time in raising a case to get it. 
      
      Can anybody tell why NIC breaks when I remove teefer2 service and drivers?