By default, the Endpoint Agent is deployed with the features selected at the Management Zone level in the Agent Features panel of Endpoint Management Console. After the deployment, you can configure the agent’s cache, set retry settings, and select whether to let users uninstall the agent. The User Management feature is only supported on Windows managed devices across all the OpenText Endpoint Management products.
You can configure settings at three levels:
Management Zone: The setting applies to all devices in the Management Zone.
Device Folder: The setting applies to all devices contained within the folder or its subfolders. It overrides the Management Zone setting.
Device: The setting applies only to the device for which it is configured. It overrides the settings established at the Management Zone and folder levels.
The following sections contain more information:
In Endpoint Management Console, click the Configuration tab.
In the Management Zone Settings panel, click Device Management.
Click Endpoint Agent.
Fill in the fields. For more information, see Section 3.3.4, Endpoint Agent Settings.
Click OK to apply the changes.
In Endpoint Management Console, click the Devices tab.
Click the Servers or Workstations folder.
Click Details next to the folder for which you want to configure settings.
Click the Settings tab, click Device Management, then click Endpoint Agent.
Fill in the fields. For more information, see Section 3.3.4, Endpoint Agent Settings.
Click OK to apply the changes.
In Endpoint Management Console, click the Devices tab.
Click the Servers or Workstations folder.
Click the device for which you want to configure settings.
Click the Settings tab, click Device Management, then click Endpoint Agent.
Fill in the fields. For more information, see Section 3.3.4, Endpoint Agent Settings.
Click OK to apply the changes.
The following sections provide details about the configuration settings available for the Endpoint Agent. Each section assumes that you have accessed the settings at the level where you want the settings applied.
You can configure whether or not to allow users to uninstall the Endpoint Agent. In addition, you can require a password for the uninstall, define an override password to provide access to restricted administrative features in the agent, and enable self-defense to protect agent files from being removed.
If you are configuring the Endpoint Agent settings on a device folder or a device, click Override settings to activate the settings.
The following setting applies to all versions of the Endpoint Agent:
Allow Users to Uninstall the Endpoint Agent: Enable this option to allow users to perform a local uninstall of the Endpoint Agent. If this option is disabled, the agent can only be uninstalled through the Endpoint Management Console.
You can configure the Endpoint Agent’s cache and agent retry settings.
If you are configuring the Endpoint Agent settings on a device folder or a device, click Override settings.
The following settings can be configured:
Cache Life: The Endpoint Agent’s cache directory contains content data used by the agent. Each piece of data, referred to as a cache entry, is stored in the cache database.
When a cache entry is added to the cache database, it is assigned a creation time and an expiration time. The creation time is simply the time it was added to the database. The expiration time is the creation time plus the number of hours specified by the Cache Life setting (by default, 336 hours or 14 days). For example, suppose that a cache entry is added on June 10 at 3:00 p.m. With the default Cache Life setting, the expiration time is set to June 24 at 3:00 p.m.
The agent does not attempt to update a cache entry until after the entry’s expiration time. At that point, the agent updates the cache entry the next time it contacts the cloud server to refresh its information.
NOTE:Updates to expired cache entries occur only for cache entries that are content-related (bundles, policies, configuration settings, registration settings, and so forth). Updates to cache entries that are event-related (remote management, inventory, reporting, and so forth) only occur at the time the event takes place on the device.
A higher Cache Life setting reduces the traffic load on your network because cache entries are refreshed less frequently. A lower setting provides newer information but increases the traffic load.
This setting affects only how often the agent requests updates to a cache entry. Cache entries can also be updated before their expiration time if information is changed in Endpoint Management Console that causes the information to be pushed from the cloud server to the agent.
Cache Orphaning Threshold: Over a period of time, it is possible for entries to be inserted in the cache database but not removed. This can cause the cache to grow unnecessarily.
An orphan is an entry that is inserted into the cache but not accessed within the number of days specified by the Cache Orphaning Threshold setting. For example, suppose that a cache entry is accessed on July 1 at 10:00 a.m. Without the default Cache Orphaning Threshold setting (30 days), the entry becomes an orphan if it is not accessed again before July 31 at 10:00 a.m.
A higher Cache Orphaning Threshold setting ensures that infrequently accessed information is not removed from the cache database. A lower setting can reduce the cache size.
Times to Retry Requests to a Busy Server: Lets you specify the number of times that the agent retries a request to a busy server before considering the server as bad instead of busy.
The default value is 15. The maximum value that you can specify is 20.
Initial Retry Request Wait: The Initial Retry Request Wait setting lets you specify the initial amount of time that the agent waits before retrying a Web service request after receiving a busy response from the server. The wait time increases by one second with every busy response. The default setting is four seconds. The maximum value that you can set is ten seconds. Each subsequent request is incremented by one second.
For example, suppose that you leave this setting at the default (four seconds). After receiving a busy response from the server, the agent waits four seconds for the first retry attempt. If the server is still busy, the agent waits five additional seconds (4 + 1) before making the second retry attempt. The third retry attempt is 15 seconds after the initial retry attempt (4 + 5 + 6). The time increments until the value specified in the Maximum Retry Request Wait setting is reached. The retry attempts stop when the value specified in the Times to Retry Requests to a Busy Server setting is reached.
Maximum Retry Request Wait: Lets you specify the maximum amount of time to wait before retrying a Web service request after receiving a busy response from the server.
The default setting is 16 seconds. The maximum value that you can specify is 20 seconds.
To provide optimal performance the default status upload frequency of the Endpoint Agent is 30 minutes. You can choose to override the default status upload frequency by configuring the following preferences on a Windows managed device:
On a Windows managed device, create the StatusSenderConfig.xml file in <CONF_DIR>.
Open <CONF_DIR>/StatusSenderConfig.xml in a text editor.
Provide the following values:
<configuration> <StatusSender> <Parameter Name="SleepTime" Value="milliseconds"/> </StatusSender> </configuration>