Endpoint Readiness is a feature that allows users to make sure all the right checks and balances are in place before running their patch cycle.
It is also a great place to start understanding where problems with an endpoint may be occurring.
JetPatch will check the readiness of your endpoints based on the prerequisites required to patch that endpoint.
| Tip: During initial exploration of this feature, it is highly recommended to pause and try out each section yourself to reinforce understanding. |
Enabling Endpoint Readiness
To get started, navigate to Endpoints → Readiness.
If you have never used Endpoint Readiness before, you will need to enable it first:
- Go to Settings.
- Enable Endpoint Readiness.
- Click Save at the bottom.
Endpoint Readiness Page
Once enabled, the Endpoint Readiness page provides a high-level overview of what is going on in your environment.
The page is divided into the following sections: Filters, Graphs, Buttons & Actions, and the Endpoints Readiness Table.
Filters
- Search – Search for any endpoint name.
- Operating System Family - All / Linux / Windows / Solaris.
- Endpoint Group - Filter by the existing Endpoint Groups in JetPatch.
- Unmet Criteria - List of Readiness Criteria. Choosing an item from the list will show all the endpoints with this unmet criteria.
- Endpoint Readiness - Ready (100%) / Not Ready (information is known and does not meet the readiness criteria) / Unknown (has missing information).
| Note: Changing the filter will also change the graphs and the Endpoint Readiness table accordingly. For example, filtering on a specific group will adjust all analytics to show only machines in that group. |
Graphs
The top section of the page gives you a high-level visual overview of endpoint readiness across your environment:
- Effective Readiness - Calculated on all statuses (Ready, Not Ready, and Unknown). Represents your total readiness as a percentage.
- Total Readiness - Calculated on what’s Ready vs Not Ready (excluding Unknown).
- Endpoint Readiness - Summarizes the global readiness status, breaking down your endpoints into three categories: Ready, Unknown, and Not Ready.
- Unmet Criteria - Summarizes the unmet criteria in the environment, detailing the reasons that your endpoints are either Unknown or Not Ready.
| Note: The “Endpoint Readiness” and “Unmet Criteria” graphs are clickable! When clicking on a section in the graphs, it will add it to the filters above, displaying the endpoints with the selected issue. |
Buttons, actions, and last synced information
- Run Readiness Tests – Readiness collection is executed every few minutes, depending on the settings (see “Readiness Checks Interval and Timeout” settings below). This button allows the user to initiate a Readiness status check from the endpoints immediately, without waiting for the next scheduled collection time.
- Settings – Opens the Endpoint Readiness settings configuration.
- Last Synced Data – Represents the last time readiness information was pulled from JetPatch.
Endpoints Readiness table
The Endpoints Readiness table shows every readiness-applicable endpoint in JetPatch with the readiness criteria for each one. The table provides additional information, such as the last readiness information collected and the readiness percentage.
Endpoints can be selected to collect the Readiness data immediately from the endpoint.
| Note 1: JetPatch will send the request to collect the readiness data. The readiness criteria will be updated in the table once the collection has finished and transferred the information using the Connector status file. It may take several minutes. |
| Note 2: The Endpoints Readiness table can be downloaded using the bottom-left report action. |
| Note 3: “Last time 100% ready” column displays the exact date and time when the endpoint last achieved full readiness status (all readiness checks passed). |
Readiness Signs
Also modified to support WSUSLess and Hybrid mode.
For every endpoint in the Readiness table:
| Status | Icon | Description |
| Ready | ✅ Green ✓ | The criterion is met. |
| Not Ready | ❌ Red X | The criterion is not met for the endpoint. |
| Unknown | ❓ Yellow ? | JetPatch did not get the information, or there are missing settings for the relevant criteria. Possibly because JetPatch is unable to check if the criteria is met. |
| Not Applicable | — Gray dash | Not all readiness criteria are applicable for every endpoint. A gray dash represents that the criterion is not applicable for this OS. |
| Connector Not Supported | ! Red | The Connector version installed on the endpoint does not support the Readiness feature. |
Additional Endpoint Information
There are two additional columns for each endpoint entry:
-
Readiness Report Time
- The last time the Connector communicated with JetPatch (not the last time Readiness information was collected on the endpoint).
- Hovering the value will show the last time JetPatch detected a change in the endpoint readiness information.
-
Endpoint Readiness
- The average readiness of the endpoint, based on the applicable criteria.
- If there is an “Unknown” criterion, it will be reflected in the Endpoint Readiness score as well and will show as “Unknown”.
Report Download
Endpoints Readiness Report – By clicking on the Report icon in the bottom left of the table,
JetPatch will send the Readiness table of the filtered endpoints.
Endpoint Readiness Settings
To access settings, click the Settings button on the Endpoint Readiness page, or navigate to Settings → Enable Endpoint Readiness.
The following options are available in Readiness Settings:
- Add User Repository – Ensures that your endpoints are pointing to the correct repository.
- To add a repository, select Add Repository and fill in the following information:
- Name
- Operating System
- CIDR Block List
- Repository ID
- Linux Subscription Toggle – Enable this setting if applicable to your Linux environment. The “Subscription” criterion check is also dependent on this setting.
- Readiness Checks Interval and Timeout – Allows you to change the default check-in intervals for how often JetPatch collects readiness data from endpoints.
- WSUS Check-in Interval (Windows only) – Specifies how often JetPatch should check in with WSUS for Endpoint Readiness communications.
| Note: Always click Save at the bottom of the Settings page after making any changes. |
Summary of Readiness Criteria for Operating Systems
The Readiness Criteria is decided based on the Endpoint’s specific Operating System and environment. Depending on the operating system, there are different criteria that need to be checked. If an endpoint does not require a certain criterion, a gray dash will appear to indicate it is not applicable.
Windows Criteria
| OS | Connector Installed | Repository Configured | PS Version | PS Execution Policy | WUA Communication |
| All Windows | ✓ | ✓ | ✓ | ✓ | ✓ |
Linux Criteria
| OS | Connector Installed | Subscription* | Advisories Ready | Packages Support | Repository Configured | |
| RHEL (Not in AWS) | ✓ | ✓ | ✓ | ✓ | ✓ | |
| RHEL (AWS) | ✓ | ✓ | ✓ | ✓ | ||
| SLES | ✓ | ✓ | ✓ | ✓ | ✓ | |
| CentOS | ✓ | ✓ | ✓ | |||
| Amazon Linux | ✓ | ✓ | ✓ | ✓ | ||
| Oracle Linux | ✓ | ✓ | ✓ | ✓ | ||
| Ubuntu | ✓ | ✓ |
* The “Subscription” criterion check is also dependent on the “Linux Subscription” settings.
Solaris Criteria
| OS | Connector Installed | Subscription | Advisories Ready | Packages Support | Repository Configured |
| Solaris 11 | ✓ | ✓ | ✓ | ✓ | |
| Solaris 10 | ✓ | ✓ |
More information on our readiness criteria.
Readiness Aspects in the Connector
- The Connector runs a Readiness script on a scheduled basis (defined in the Readiness settings).
- Readiness results are communicated over regular communication to JetPatch (Status files) without the need to make any active operation.
The Readiness configuration, result, and script can be found in the ep-readiness folder inside the Connector vAgentManager folder.
Related Articles
- Endpoint readiness settings
- Readiness criteria guide and troubleshooting
- What is the patching checklist?
- Running a task
Comments
0 comments
Please sign in to leave a comment.