Location: Platform Configuration → Settings → Advanced Settings
Available Settings
| Setting | Description |
| Server Status Polling Interval (s) | Interval of polling to refresh endpoint and managed agent information in the web interface. (default: 40) |
| Show Server as Disconnected After (m) | Controls the amount of time without communication before a managed server is labeled as “disconnected”. Recommended to modify only when your environment contains servers that do not communicate via HTTPS and there are rate limits on hypervisor-based communication. For example, set a high value when VMs communicate via vSphere and the number of vCenter calls is limited. (default: 15) |
| Allowed Total Concurrent Operations | Allocates worker threads to work with endpoints (default: 15). Threads are not coupled with endpoints - one thread can send a command and be released, another can retrieve the result on next status retrieval (SSH/SMB) and be released. In the case of WEB connection, the result comes via HTTP(S). |
| 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 for deploying the connector on endpoints. (default: 50) |
| Allowed Total Concurrent Network Operations | Threads that take part in result processing. (default: 50) |
| Restore Physical Agent When Removing Managed Agent | 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 tool is automatically restored. If Off, the legacy 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” is enabled. |
Notes
| Note 1: Changing the default setting of Allowed Total Concurrent Operations requires a service restart: |
| Version | Restart Command |
| Prior to 5.0 | systemctl restart tomcat |
| Post 5.0 | docker restart intigua-worker |
| Note 2: The parameter that controls the number of parallel activities (patching, scripting, start/stop agent, upgrade, etc.) is located in: |
| Version | File Path |
| Prior to 5.0 | /usr/share/tomcat/default/conf/intigua.config.xml |
| Post 5.0 | /usr/share/intigua/services/data/app-config/intigua-worker/application.properties |
The parameter is called:
<system> ... <max-allowed-concurrent-operations>175</max-allowed-concurrent-operations> </system> |
| Note: The property might not be present in intigua.config.xml and has a default of 175. If needed, add it manually right before </system>. |
Comments
0 comments
Please sign in to leave a comment.