Views:
  1. Download the SMEX scan engine files and copy it to a local folder on the target SMEX server.

    Depending on the server operating system, there are two types of SMEX scan engine files: 32-bit and 64-bit. The 32-bit package contains a vsapi32.dll, while the 64-bit package contains a vsapi64.dll file. Both packages contain their corresponding bpmnt.dll file.

    If you are using a beta version scan engine or would like to roll back to an older scan engine version, then copy your package to a local folder on the target SMEX server.

  2. Stop the following ScanMail services:
    • ScanMail for Microsoft Exchange Remote Configuration Server
    • ScanMail for Microsoft Exchange Master Service
     
    For cluster systems, take note that this step will bring the SMEX-<EVS server name> cluster resource offline.
  3. Go to each of the following folders and rename or delete the files from each folder:

    Folders:

    • ..\Trend Micro\SMEX\engine\vsapi\latest
    • ..\Trend Micro\SMEX\engine\vsapi\primary
    • ..\Trend Micro\SMEX\engine\vsapi\secondary

    Files:

    • BPMNT.DLL
    • VSAPI32.DLL (for 32-bit OS)
    • VSAPI64.DLL (for 64-bit OS)
  4. Unzip/Copy your replacement BPMNT.DLL and VSAPI32.DLL/VSAPI64.DLL into the 3 folders:
    • ..\Trend Micro\SMEX\engine\vsapi\latest
    • ..\Trend Micro\SMEX\engine\vsapi\primary
    • ..\Trend Micro\SMEX\engine\vsapi\secondary
  5. For cluster servers, do the same steps on each node to ensure that all nodes will have the same scan engine version.
  6. For scan engine roll back procedures, to ensure that the SMEX server will not have any other newer scan engine version in its folders that might automatically replace your older version, delete ALL the contents of the folder ..\Trend Micro\SMEX\web\activeupdate.
     
    Delete only the contents and NOT the "activeupdate" folder itself. This folder is the SMEX ActiveUpdate module's temporary and duplicate package repository.
  7. For roll back procedures on clustered servers, aside from step 6, delete ALL the contents of the following folder in the cluster shared drive <shared drive:>\SMEX\activeupdate
     
    Delete only the contents and NOT the "activeupdate" folder itself. This folder is checked by SMEX during failovers to determine if there exists a newer scan engine version and if it needs t replace the files of the newly active node.

    Naturally, for roll back purposes, the contents of this folder need to be deleted. Otherwise, the newer version will be used and it will overwrite the node's newly rolled back scan engine files.

  8. Start the following ScanMail services:
    • ScanMail for Microsoft Exchange Master Service
    • ScanMail for Microsoft Exchange Remote Configuration Server
  9. For cluster servers, you will also have to bring the SMEX-cluster resource online.
Keywords: scan engine manual update,rolling back scan engine manually,bpmnt.dll file,SMEX scan engine update