Removing a Single or Shared ScanMail Installation on Linux

Views:

Tip

Refer to ScanMail for Linux in Appendix C Program File and Folder Lists for the list of ScanMail files and folder structures.

On the server where ScanMail is installed, search for smdsysV3.ini, and then use a text editor to open it. Keep the file open for reference when performing the succeeding steps.

Parameters that will be referred to in the succeeding steps include:

DomSvr{X}
ProductPath

Note

DomSvr{X} represents the ScanMail instance where {X} is the number corresponding to the ScanMail installation.

If the target server has only a single ScanMail installation, DomSvr{X} is DomSvr0. For multiple ScanMail installation, DomSvr{X} increments by 1. DomSvr0 is the first instance, DomSvr1 is the second instance, and so forth.

Here is a sample of smdsysV3.ini for a Linux server that has multiple instances of ScanMail:

[SMDConf] \\indicates the first ScanMail instance
ProductPath=/ibm2/linux/trend/SMID
ProductVersion=V5.8.1\\indicates ScanMail version is 5.8.1
InstallType=64-bit \\indicates it is a 64-bit ScanMail
DomSvrISMDCount=1 \\indicates the partition server number of first 
ScanMail instance
DomSvrISMDSecs=DomSvr0\\indicates partition servers of first 
ScanMail instance
DomSvr0=/ibm2/linux/notesdata0/notes.ini

[SMDConf0] \\indicates the second ScanMail instance
ProductPath=/ibm1/trend/SMID
ProductVersion=V5.8.1
InstallType=64-bit
DomSvrISMDCount=2 \\indicates the partition server number of second 
ScanMail instance
DomSvrISMDSecs=DomSvr1,DomSvr2 \\indicates partition servers of second 
ScanMail instance
DomSvr1=/ibm1/notesdata1/notes.ini
DomSvr2=/ibm1/notesdata0/notes.ini

[SMDConf1] \\indicates the third ScanMail instance
ProductPath=/ibm2/trend/SMID
ProductVersion=V5.8.1
InstallType=64-bit
DomSvrISMDCount=1 \\indicates the partition server number of third 
ScanMail instance
DomSvrISMDSecs=DomSvr3 \\indicates partition servers of third 
ScanMail instance
DomSvr3=/ibm2/notesdata0/notes.ini

If the SMD instance is removed from all the partition servers that share the Domino binary, then navigate to the Domino Binary directory, and then search for and delete the corresponding ScanMail files:
- ScanMail files in the Domino Program directory (ibmpow) on a Linux server.
Navigate to the Domino Data directory, and then delete the SMD installation and temporary folders.
Using a text editor, open the notes.ini specified in DomSvr{X}, and then perform the following:
1. Look for the ServerTasks section, and then delete the following items:
  - SMDemf
  - SMDreal
  - SMDsch
  - SMDmon
  - SMDcm
2. Look for the EXTMGR_ADDINS section, and then delete the item SMDext.
3. Look for the ScanMailInstallPath section, and then delete the whole line (including the file path).
Save and close notes.ini.
If the SMD instance is removed from all the partition servers that share the SMDbinary, delete the folder specified in ProductPath. This folder contains other ScanMail files, including the virus pattern and scan engine files for VSAPI and Trend Micro Anti-Spam.
Navigate to the folder where the ScanMail installation logs are located (see Locating Installation and Uninstallation Logs) and delete the log files.
Delete and modify the information of partition server which installs the specified SMD instance in smdsysV3.ini.
- DomSvrISMDCount
- DomSvrISMDSecs
- DomSvrX (delete the related information of the partition server of ScanMail instance)
If the SMD instance is removed from all the partition servers that share the SMDbinary, delete the SMDConfx instance in smdsysV3.ini.

If all SMD instances are removed from the target server, delete smdsysV3.ini.
Restart the Domino server.

Keywords: removing ScanMail manually