Change installation location of Trend Micro Client Server Security Agent

At some time you may need to change the default location of the Trend Micro Client/Server Security Agent on a desktop/server. In our case the server was very low on disk space on the C: drive, but the default install when executing \servernameofcscanautopccp.exe would go to the C: drive.

  1. Open the ofcscan.ini file, and go all the way down to the bottom of the file
  2. Change the path on the line “WinNT_InstallPath=$ProgramFilesTrend MicroClient Server Security Agent”
  3. Save the file and run autopccp.exe and it will go to the new path that you have saved

Exchange Transport Service Stops after Installation of Scanmail 8.0 on SBS 2008

After installing the latest version of Trend Micro Scanmail 8.0 on an SBS 2008 server, the Exchange Transport service kept stopping and reporting the following errors in the Application event log:

Event ID: 16023 Source: MSExchangeTransportMicrosoft Exchange couldn’t start transport agents. The Microsoft Exchange Transport service will be stopped. Exception details: Failed to create type ‘TrendMicro.SMEX.hookE12TransportAgent.hookE12RoutingAgentFactory’ from assembly ‘D:Program FilesTrend MicroSmexhookE12TransportAgent.dll’ due to error ‘Invalid agent assembly path.’ …

Event ID: 1052 Source: MSExchange Extensibility

The creation of an agent factory for the agent ‘ScanMail Routing Agent’ failed with error ‘Failed to create type ‘TrendMicro.SMEX.hookE12TransportAgent.hookE12RoutingAgentFactory’ from assembly ‘D:Program FilesTrend MicroSmexhookE12TransportAgent.dll’ due to error ‘Invalid agent assembly path.’.’. Verify that the corresponding transport agent assembly and dependencies with the correct version are installed.

The issues turned out to be a permission issue on the SMEX program file directory.  Exchange uses the Network Service account for the Transport Service credentials but this account didnt get security permissions to the Trend Micro SMEX program folder after install.  Adding the appropriate read permissions did the trick.

Trend Micro Scanmail Console Displays cgiDispatcher.1 Error

I experienced this issue on an SBS 2008 server with IIS7.  The fix was to enable the “Execute” permission on the CGI and ISAPI modules for the web application, but it was tricky with IIS7.  Heres how to do it. 

  1. Open IIS Manager (Start->Run->Inetmgr)
  2. Select the SMEX Virtual Directory
  3. Select Handler Mappings
  4. Find CGI-Exe and ISAPI-dll and select “Edit Feature Permissions” in the action pane.
  5. Make sure “Execute” is checked and close.

Prior to this, make sure you complete the following other actions (from the Trend Readme):

      (1) Install ASP and CGI Role Services
          a.Go to the Server Manager.
          b.Select Roles and then right-click on the Web Server (IIS).
          c.Click Add Role Services.
          d.Under Application Development, select ASP and CGI.
          e.Click Next > Install.

      (2) Allow ScanMail CGIs (if ISAPI and CGI restrictions are
          a.Go to the IIS Manager.
          b.Select the server node and then select ISAPI and CGI
          c.Verify that both cgiDispatcher and cgiCmdNotify are
          d.Re-open the ScanMail product console.

Trend Micro Internet Security 2007 – PcScnSrv.exe Consumes Too Much CPU

Trend Micro’s PcScnSrv.exe process can be seen spiking often to almost 100% of the CPU.  This issue is caused by the Immunization feature of Spybot S&D.  Apprently the two products do not play well together…in fact, during the install of Trend Micro Internet Security 2007, the removal of Spybot S&D is recommended.  If you do have both products installed, Trend Micro’s recommended solution can be found here

The basic steps are this:

1. Open Spybot and go to the Immunize section.
2. Click the undo button to allow all bad products previousely blocked by Spybot.
3. Delete: C:Program FilesTrend MicroInternet Security 2007usrwl.dat
4. Reboot

Fix OfficeScan console when upgrading from 7.0 to 7.3

1. Go to Administrative Tools > Internet Information Services (IIS) Manager.

2. Expand the Server Name directory and then click on Application Pools.

3. Click Action > New > Application Pool.

4. Create a new Application Pool with the following characteristics:

Application Pool ID: OSCE
Application Pool Settings: Use default settings for new application pool

5. After creating the new OSCE Application Pool, right-click on it and select Properties.

6. Go to the Identity tab.

7. Under the Predefined option, select Local System.

8. Click Yes at the prompt.

9. Click Apply > OK.

Next, you would have to set the web site to use that Application Pool:

a. Right-click on web site created and click Properties.

b. Under the Home Directory tab, look for Application Settings.

Click the Remove button to remove the existing application settings.

Click on the Create button. This should re-create the application settings.

c. Still under the Home Directory tab and Application Settings, locate the Application Pool drop-down list and select OSCE.

d. Click Apply > OK.