The following settings are available:
- Server status polling Interval (s): Interval of polling to refresh endpoint and managed agent information in web interface.
- Allowed total concurrent operations: The maximal number of concurrent operations on all endpoints via all communication channels.
- Note: Requires a tomcat restart.
- Max concurrent operations per VMware host: The maximal number of concurrent operations on all VMs on a single ESX host.
- Maximum total concurrent deployment operations: The maximal number of concurrent operations of deploying the connector on endpoints.
- Allowed total concurrent hypervisor-based operations: The maximal number of communications with endpoints via VMware APIs.
- Allowed total concurrent network operations: The maximal number of communications with endpoints via standard TCP networking.
- Restore physical agent when removing managed agent from a server: When a managed agent is deployed to an endpoint, any legacy (non-virtual) version of the same management tool is disabled to avoid conflict. If the managed agent is later removed, and this option is On, the legacy management tool is automatically restored to its working state. If this option is Off, the legacy management tool remains disabled.
- Use configuration files for packages: Enable uploading a configuration file instead of pasting it for agent-specific settings in management service configuration.
- Prompt user for ticket number when applying or removing managed agents: Enable change request tracking.
- Follow LDAP referrals: During Active Directory queries, follow LDAP referrals received from the initially-queried Active Directory server. Disable if you experience timeouts due to LDAP referrals to unreachable Domain Controllers.
- Enforce policy consistency: If subsequent to applying a management service to an endpoint by policy, JetPatch Agent Manager finds that the service or managed agent has been manually removed from the endpoint (not just stopped), JetPatch Agent Manager redeploys the service and managed agent to the endpoint. Relevant only if Auto-remediate policy drift (below) is enabled.
- Maximum number of retries when applying policy: When applying a management service to an endpoint by policy fails, retry this number of times. Relevant only if Auto-remediate policy drift (below) is enabled.
- Auto-remediate policy drift: Enforce policy rules by applying management services to endpoints according to policy rules. If disabled, non-compliance is still marked in the Endpoint list.
* Note that there are fields that will take effect only after server restart. These fields are marked accordingly.
- Show server as disconnected after (m): Control the amount of time without communication before a managed server gets labeled as "disconnected". It is recommended to modify this only when your environment contains servers that do not communicate with JetPatch Agent Manager via HTTPS, and there are rate limits on hypervisor-based communication with managed servers. For example, set a high value when your VMs communicate via vSphere and the number of vCenter calls is limited.