Cleaning out unmanaged detector list
Created: 18 Jan 2013 | Updated: 10 Feb 2013 | 2 comments
This issue has been solved. See solution.
Hello,
I've "inheritied" our SEPM 12.1 environment when I started at this company, and now I'm trying to "reverse engineer" it's setup.
I've set up a managed detector and it seems to work fine - for what it is. I understand that it's not perfect, and that's OK.
But it seems to still bringing up 2 machines that I KNOW have SEPM installed.
So, is there a way to clear out what the unmanaged detector is sending to the SEPM? Or is this list on the SEPM server and i need to do something there?
Discussion Filed Under:
Comments 2 Comments • Jump to latest comment
Not really and this seems to be a limitation.
You can add these two devices as exceptions.
You can also try disabling the unmanaged detector and re-enabling to see if that works
I've had these same issues in the past.
SEP Knowledge Base
Endpoint SWAT
As per above recommnedation disable and enable again the unmanaged detector - this should clear up the old logs. Have a look at the previous threads as well:
https://www-secure.symantec.com/connect/forums/how...
https://www-secure.symantec.com/connect/forums/sti...
Would you like to reply?
Login or Register to post your comment.