Advanced Settings

Location:  Platform Configuration > Settings > Advanced Settings

The following settings are available:

• Server status polling Interval (s): Interval of polling to refresh endpoint and managed agent information in web interface. (default 40)
• 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. (default 15)

• Allowed total concurrent operations: allocates worker threads (default 15) to work with endpoints. The threads are not coupled with endpoints, i.e. it does not mean that a thread is waiting for a command to finish. One thread can send a command to endpoint and be released. Another one can get a result on next status retrieval (SSH/SMB) and be released, and move to the next command. In the case of WEB connection the result comes via HTTP(S)

  • Note 1: Changing default setting of concurrent operations requires a tomcat restart (service tomcat restart)
  Note 2: The parameter that controls the number of patching activities, but not just patching activities - also scripting activities, start/stop agent, upgrade, etc… -  that can run in parallel is located in:
  

  <usr/share/tomcat/default/conf/intigua.config.xml>

  and is called:
  

  <system>
  ...
  <max-allowed-concurrent-operations>175</max-allowed-concurrent-operations>
  </system>

  
  The property might not be present in the  intigua.config.xml and has a default of 175 (increase from 100, starting in 4.2.5+) simultaneous active operations. If needed, please add manually, right before </system>
• Max concurrent operations per VMware host: The maximum number of concurrent operations on all VMs on a single ESX host. (default 4)
• Maximum total concurrent deployment operations: The maximum number of concurrent operations of deploying the connector on endpoints. (default 5)
• Allowed total concurrent network operations: threads (default 50) that take part in result processing.
• 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. (default on)
• Use configuration files for packages: Enable uploading a configuration file instead of pasting it for agent-specific settings in management service configuration. (default no)
• Prompt user for ticket number when applying or removing managed agents: Enable change request tracking. (default yes)
• 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. (default yes)
• Allow automatic fix of policy exceptions: Enforce policy rules by applying management services to endpoints according to policy rules. If disabled, non-compliance is still marked in the Endpoint list.
• 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 Allow automatic fix of policy exceptions (above) is enabled.