SCS CleanWipe is derived from NoNAV9 and is contains regsitry and file information related to 
SCS 3.0 (codename Almagest).

SCS CleanWipe is currently compliant with SCS 3.0 builds up to STM -build 359

SSC			10.0.0.0
SAV-Server		10.0.359.0
SAV-Client		10.0.359.0
SCS			SAV 10.0.297.0 and SCF 8.5.0.47
Quarantine Server	3.3.0
Quarantine Console	3.3.0
SCFA			8.5.0.0
AMS			9.0.0.0
SCF 1.0			5.0.0.375
SAVC 1.0		8.0.0.374
7.6 NAVServer		7.6.0.000

IMPORTANT NOTES:

   *******************************************************************************
1) * Please copy the contents of this folder into a local drive and RUN LOCALLY. *
   * Running from the network may results in issues.                             *
   *******************************************************************************

2) Symantec Tamper Protect Must be turned off for SCS CleanWipe to work properly. If TamperProtect is enabled,
   SCS CleanWipe will still function but several files may be left behind (although not affecting re-installation)

3) SCS CleanWipe has been primarily tested using SCS 3.0 and inclusive applications on Windows 2000 and Windows Xp.
   SCS CleanWipe functions on Windows 9x Systems, however, several files may be left behind (although not affecting
   re-installation)

4) SCS CleanWipe is build-forward-ready (meaning it can handle all builds) after SCS 2.0 assuming existing upgrade codes.
   If upgrade codes are changed, SCS CleanWipe is not guaranteed to work. Moreover, SCS CleanWipe at its current state with 
   regards to static keys and files is reliant upon consistent updates of SCS CleanWipe.bat. Without frequent updates,
   several files may be left behind (although not affecting re-installation)

5) SCS CleanWipe can now handle custom folder path uninstalls depending on the availability of the 
   HKEY_LOCAL_MACHINE\SOFTWARE\Symantec\InstalledApps registry key. If this key and values are present,
   the system will assign the variables to the corresponding custom folders. If this key and/or its 
   values are NOT present, default values will be used. This means that if there is a custom installation
   present on the system but the key is not available, all files corresponding to the custom folders
   will be left behind and will have to be manually removed. 