
There's normally sufficient information in the logs to pinpoint the reason (if not the prime cause). Im arguing with myself over if I should just run the one-line script against a collection in ConfigMgr, or use the application model and do an application removal deployment.


I need to remove SEP from about 1000 servers (mostly virtual, some physical mix of 2012, 20). Perhaps I'm an antediluvian * but I believe analysis and specific correction are the better course of action. My organization is firing Symantec Endpoint protection (Finally). There's the danger that such tools are used indiscriminately (Symantec themselves display a warning on the CleanWipe page - use as a last resort).Ī tool is undoubtedly convenient but in most cases I have experienced (in a dozen years with several thousand endpoints) it's not necessary - and at best it doesn't induce other issues. If they can get the system from an unknown state to a consistent and clean one - why not using them in the first place or design the regular uninstall so that it can handle pathological cases? Even as they appear to be able to clean up the mess they have to be used with care (a prominent example is the former msicuu2.exe now replaced by the Fix-It for install/uninstall problems). "Wipe" tools can't expect the unexpected. Always the question how this comes about.
