To ensure that Security Agents stay protected from the latest security risks,
update agent components regularly. Also update Security Agents
with severely out-of-date components and whenever there is an outbreak. Components
become severely out-of-date when the Security Agent
is unable to update from the Apex One (Mac) server or the ActiveUpdate server for
an
extended period of time.
Agent Update Methods
There are several ways to update Security Agents.
|
Update Method
|
Description
|
|
Administrator-initiated manual update
|
Initiate an update from the following web console screens:
|
|
Automatic update
|
After the server finishes an update, it immediately notifies Security Agents to update.
For details, see Configuring Agent Automatic Update.
|
|
User-initiated manual update
|
Users launch the update from their endpoints.
|
Agent Update Source
By default, Security Agents download components from the Apex One (Mac)
server. In addition to components, Security Agents also receive updated configuration files when
updating from the Apex One (Mac) server. Security Agents need the configuration files to apply new
settings. Each time you modify Apex One (Mac) settings on the web console, the
configuration files change.
 |
NoteIf an agent only has an IPv6 address, read the IPv6 limitations for agent updates
in Pure IPv6 Agent Limitations.
|
Agent Update Notes and Reminders
-
Security Agents can use proxy settings during an update. Proxy settings are configured on the agent console.
-
During an update, the Security Agent icon on the menu bar of the endpoint indicates that the product is updating. If an upgrade to the Security Agent program is available, Security Agents update and then upgrade to the latest program version or build. Users cannot run any task from the console until the update is complete.
-
Access the Summary screen to check if all Security Agents have been updated.