Catalog Overview
The Agent Section contains an inventory of all the Agents discovered by JetPatch Agent Manager in your environment, and enables you to add new Agents and Agent versions.
Action Buttons
In the top right corner, action buttons enable you to perform the following operations:
| Action | Description |
| Download Report | Download an Agent service report containing: Service Name, Agent Package, Revision, Created Date, Created By, and Comments. |
| Tools Discovery |
Manage discovery files: • Download the suggested discovery file. Upload a discovery file (must be in JSON format) Learn more about Software Discovery. |
| Upload Image |
Add a new Agent by uploading image files in .vai, .bsx, or .exe format. Learn more - Adding a Managed Agent to JetPatch. |
| Remove VAIs / Images from Catalog | To remove a tool from the catalog, access the JetPatch server and remove the relevant VAI files from the package directory (see path below). |
Managed Agents
A Managed Agent is a third-party tool or agent whose full lifecycle JetPatch Agent Manager actively controls across endpoints - not just monitors.
To view all configured Managed Agents, navigate to Agents → Managed Agents. Each agent is displayed as a tile with its name and icon. Use the search bar to filter by agent name.
Clicking an agent opens its detail view, which includes the following tabs:
- Overview - displays installation coverage (percentage and number of endpoints), current status distribution across endpoints, and version breakdown. The endpoint table lists each server by name, IP, operating system, installed version, and agent status. Supported status values are: Running, Not Running, Error (High), Warning, Not Installed, and No Data Available.
- Policy – configure the rules and enforcement settings that govern the agent's behavior across endpoints.
- Services – view and manage the services and resources associated with the agent.
- Images – manage the installer packages used for deploying and upgrading the agent.
- Alerts – configure and review alerts related to the agent's health and status.
For each Managed Agent, JetPatch provides the following capabilities:
- Central configuration and monitoring – manage the agent and its related services and resources from a single control plane
- Lifecycle actions – start, stop, and upgrade the agent across endpoints
- Health enforcement – apply watchdog mechanisms and policy rules to ensure the agent remains operational
Managed Agents are the counterpart to Native Agents: where Native Agents offer visibility only, Managed Agents give JetPatch full operational control over the agent lifecycle.
Native Agents
A Native Agent is a third-party tool or agent that JetPatch can discover, inventory, and monitor, but does not fully manage.
- Unlike Managed Agents, JetPatch is not responsible for deploying or updating the Native Agent's installer packages.
- To view all discovered Native Agents, navigate to Agents → Native Agents. Each agent is displayed as a tile with its name and icon.
- Use the search bar to filter by agent name.
Clicking an agent opens its detail view, which includes a single tab:
- Overview – displays installation coverage (percentage and number of endpoints) and version distribution. The endpoint table lists each server by name, IP, operating system, and installed version.
| Note: Unlike Managed Agents, the Native Agent detail view does not include Policy, Services, Images, or Alerts tabs. JetPatch provides inventory and visibility for Native Agents only - no lifecycle management actions are available. |
For each Native Agent, JetPatch displays the following information:
- Installation location – the endpoint on which the tool is installed
- Version – the installed version of the tool
The Scan & Update button
Provides two options:
- Download suggested discovery file – download the current discovery configuration file for review or editing
- Upload discovery file – upload an updated discovery file to apply changes to the Native Agent discovery process
Removing VAI Files from the Server
To remove a tool from the catalog, access the JetPatch server and delete the relevant VAI files from the following path:
| /usr/share/intigua/package |
| Warning: Ensure the VAI file is not in use by any rules or services before deleting it. |
Additional Resources
- For more information on deploying the JetPatch (Intigua) Connector, refer to the Deploying JetPatch Connector article.
Comments
0 comments
Please sign in to leave a comment.