OfficeScan uses the autopcc.exe (16-bit) and autopccp.exe (32-bit) during client/agent installation via login script on supported Windows platforms. The executables are also used to pull client/agent updates from the server.
When autopcc is executed, it performs the following:
- Checks the platform it is running on. When running on a Windows NT-based client/agent, it starts autopccp.exe
- Checks if the OfficeScan client/agent is installed on the computer by checking either of the following registry keys:
For OfficeScan 11.0 and XG:
- HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Trend Micro\PC-cillinNTCorp
- If the registry key exists, it checks the value of the HKEY_LOCAL_MACHINE\SOFTWARE\TrendMicro\PC-cillinNTCorp\CurrentVersion\Application Path key which indicates the OfficeScan client/agent folder, then verifies if the folder exists.
In OfficeScan 11.0 and XG, it checks the value of HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\TrendMicro\PC-cillinNTCorp\CurrentVersion\Application Path.
- If the registry key does not exist, it runs ..\PCCSRV\Pccnt\disk1\install.exe or ..\PCCSRV\Pcc95\disk1\setup.exe to install the OfficeScan client/agent program.
- If the OfficeScan client/agent is already installed, it checks the OfficeScan server for the timestamp of each file listed in ApNT.ini or Ap95.ini, then compares it with the client.
- If the server files have a newer timestamp, the files are copied to the client/agent. This can be used to repair an OfficeScan client/agent.
- If, during the update process, OfficeScan tries to overwrite a file that is in use, it gets a fail return code and the whole autopcc process is aborted.