![]() the command looks something like msiexec /X /switches blah blah blah. However, that's only after you have queried the remote registry of each and every computer it will run on to ensure that the GUID used on each is identical (you'll need a msiexec removal lilne for each version found). To be fair, there are command strings that can be executed to remove the product via command line using msiexec in some instances. and what I mean by that is to date, they still have no tool available to their customers that can be scripted or managed via GPO (.msi) to remove SEP. In these specific cases, Technical Support may recommend the use of CleanWipe. I hate to necro a thread this old, but surprisingly it is still relevant considering Symantec still has yet to provide its customer base with a viable solution despite the cacophony of cries for one. In certain circumstances, CleanWipe can be useful in removing old versions of components or drivers (LiveUpdate or firewall drivers, for example) that can conflict with the new versions. In instances where the difficulty in installing Symantec Endpoint Protection is related to GPO policy, lack of hard drive space, or other environmental factors, running CleanWipe will not resolve the underlying issue. Only use CleanWipe as a last resort when the usual uninstallation methods are unsuccessful. WARNING: Symantec does not recommend using this specific approach at the first sign of installation trouble.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |