Summary
This article provides a summary of different methods to perform fresh installation of an OfficeScan/Apex One agent.
All installation methods require local administrator rights on the target computers.
Details
Refer to this deployment consideration guide:
| Installation Method/ OS Support | Deployment Considerations | |||||||
|---|---|---|---|---|---|---|---|---|
| WAN Deployment | Centrally Managed | Requires User Intervention | Requires IT Resource | Mass deployment | Supports All OS | Unsupported OS | Bandwidth Consumed | |
| Remote Installation | ✘ | ✔ | ✘ | ✔ | ✘ | ✘ |
• Windows Vista Home Basic and Home Premium | High |
| UNC-based Installation | ✘ | ✘ | ✔ | ✔ | ✘ | ✔ | - | High, if installations start at the same time |
| Login Script Setup | ✘ | ✘ | ✔ | ✔ | ✘ | ✔ | - | High, if installations start at the same time |
| Client Packager | ✘ | ✘ | ✔ | ✔ | ✘ | ✔ | - | Low, if scheduled |
| Client Packager (MSI package deployed through Microsoft SMS) | ✔ | ✔ | - | ✔ | ✔ | ✔ | - | Low, if scheduled |
| Client Packager (MSI package deployed through Active Directory) | ✘ | ✔ | - | ✔ | ✔ | ✔ | - | High, if installations start at the same time |
| Client disk image | ✘ | ✘ | ✘ | ✔ | ✘ | ✔ | - | Low |
| Trend Micro Vulnerability Scanner (TMVS) | ✘ | ✔ | ✘ | ✔ | ✘ | - |
• Windows Vista Home Basic and Home Premium | High |
| Security Compliance Installations | ✘ | ✔ | ✘ | ✔ | ✘ | - |
• Windows Vista Home Basic and Home Premium | High |
When migrating OSCE agent or installing Apex One with unsupported OS to Apex One, take note of the following:
- Apex One server can manage OfficeScan agents which migrated from other OfficeScan servers. However, if the agent was installed on the OS which is not supported in Apex One, it will be rejected by the Apex One server during the agent migration process. Thus, it cannot be displayed nor managed on the Apex One server web console.
- For OfficeScan agents installed on the non-supported OS, it is advised to keep it in the existing OfficeScan server.
- Apex One supported OS list can be found in System Requirement document.
