The Agent must be deployed on every workstation that you want to manage. It requires the following:
- Windows Vista (32 or 64 bits), Windows 7 (32 or 64 bits), Windows 8 (32 or 64 bits), Windows 10 (32 or 64 bits)
- .NET Framework 2.0 or 4.5
- A CPU compatible with Intel SpeedStep or AMD Cool'n'Quiet is recommended to take full advantage of the EfficientPower technology.
The agent is distributed as a pre-configured MSI package. It can be deployed silently by your usual deployment tool, such as SCCM, Landesk, or by GPO. In the case of a manual installation, administrator rights are required.
The agent can be configured to connect to a Handler on the local network, or to a shared AVOB Handler.
Connection to a Handler on the local network
The agent is preconfigured to connect to the Handler using a URL such as
https://avob.yourdomain.tld:6000/. TCP connections must be possible on this port from the agents to the Agent Handler.
In addition, when synchronizing a policy, or sending an instant action, the Handler sends an HTTP packet to the agent on TCP port 6001. This port is opened automatically in the Windows firewall, but must be opened manually in any third-party firewall.
Handler’s requirements
The Agent Handler requires the following components:
- 2 cores, 2 GB ram
- Windows Server 2008 R2 or higher (64-bit only)
- .NET Framework 3.5 enabled in the features (Windows server 2008 R2) or .NET Framework 4.8
- TCP port 6000 open inbound from the local network (for agent connection)
- Outbound connection to the AVOB cloud platform over HTTPS is possible (URL like https://yourplatform.avob.com/avobitespcnetwork/)
- If a proxy must be used, then the appropriate login credentials
In order to pre-configure the agent package, the internal address of the VM (either the IP address or a DNS name) must be sent to AVOB.
Connection to an AVOB-hosted Handler
- TCP connections must be possible to that URL on port 443 from the agents.
- If a proxy must be used, it cannot require authentication.
Please note that when using an AVOB-hosted handler, features such as instantly synchronizing a policy, or sending an instant action are impossible because there is no direct connection from the Server to the agents.