Sophos Clean Wipe Tool

Hello Neel,

are you referring to a specific issue?
The Windows Installer is used for installation and consequently it's the tool to uninstall. It should remove all active components, registrations, and system modifications. A few items might be left behind (IIRC used to be used upon a reinstall of a managed endpoint) - naturally "unknown" content (i.e. something put into a Sophos folder by a non-Sophos process or the installer) is preserved.

One common cause for "issues" is the removal of the cached .msi from \Windows\Installer\, and an upgrade fails because the previous version can't be uninstalled without it. The tool in this case would be the previous .msi (guess you could get this from Support if you have no other means).

In case of an Installer database corruption - well, this is likely not really a Sophos issue anyway.

Christian 

Thanks Christian, 

Scenario would be, Corrupt Sophos Endpoint Client, I have uninstalled  via Add/Remove Program However post reboot while installing its failing to Install.

I suspect Old Install Previous Entries is causing this conflict. 

So i was wondering if  Sophos has one?? If you have used Symantec Endpoint ever they do have a Clean Wipe Tool for Un Installing the client.

Neel

Hello Neel,

Corrupt Sophos Endpoint Client
always the question how this comes about.
"Wipe" tools can't expect the unexpected. 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). There's the danger that such tools are used indiscriminately (Symantec themselves display a warning on the CleanWipe page - use as a last resort).

A 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. Perhaps I'm an antediluvian^* but I believe analysis and specific correction are the better course of action.

while installing its failing to Install
there's normally sufficient information in the logs to pinpoint the reason (if not the prime cause).

Christian

*a person that yet understands the meaning of antediluvian

Thanks Chris for the deep insight.. Very much appreciated

Thanks Chris for the deep insight.. Very much appreciated