Readiness Criteria Summary

There are a total of eight readiness criteria. The Readiness Criteria is decided based on the Endpoint Specific OS and environment.

Windows Criteria

	Connector Installed	Repository Configured	PS Version	PS Execution Policy	WUA Communication
All Windows	✓	✓	✓	✓	✓

Note: If an endpoint is configured for WSUS-less patching, JetPatch validates that the endpoint is correctly pointed to the Microsoft Update service. The "hasUpdateServiceLocation" check will verify the cloud service endpoint rather than an intranet WSUS URL.

Linux Criteria

	Connector Installed	Subscription*	Advisories Ready	Packages Support	Repository Configured
RHEL / SUSE	✓	✓	✓	✓	✓
RHEL / SUSE (Cloud)	✓		✓	✓	✓
Oracle Linux / Alma Linux / Rocky Linux / Amazon Linux	✓		✓	✓	✓
CentOS	✓			✓	✓
Ubuntu / Debian	✓				✓

Note: * "Subscription" criterion check is also dependent on "Linux Subscription" settings.

Solaris Criteria

	Connector Installed	Subscription	Advisories Ready	Packages Support	Repository Configured
Solaris 11	✓	✓	✓		✓
Solaris 10	✓	✓

Note on WSUS-less Windows: For endpoints configured in WSUS-less or Hybrid modes, the readiness criteria remain the same, but the underlying checks for Repository Configured and WUA Communication shift from local WSUS validation to Microsoft Cloud connectivity validation.

Criteria Guide

Note: General Unknown Message – JetPatch didn’t get any data. Please check the Connector communication.

Connector

General Information

Description: The connector should be installed and communicated properly with JetPatch and in a supported version.

Supported Operating Systems:

• All OSs supported by the JetPatch Patch Management module

Readiness Statuses

Status	Description
Ready	Connector is Connected and in the right version.
Not Ready	Connector is installed but having problems with communication with JetPatch.
Not Supported Version	Connector is not in a Readiness feature supported version.
Unknown	Connector does not exist on the endpoint.

Exemption: If the connector is not connected.

How to Fix

• Unknown or Not Supported Version: Deploy Connector on the endpoint.
• Not Ready: Check for communications issues.

Subscription

General Information

Description: Checking for the subscription data.

Supported Operating Systems:

• RHEL (not in AWS)
• SUSE
• Solaris

Readiness Statuses

Status	Description
Ready	The endpoint has a valid subscription.
Not Ready	The endpoint does not have a valid subscription.
Unknown	JetPatch does not know what is the subscription status of the endpoint.
Not Applicable	For endpoints that do not need a subscription or running an unsupported OS.

Exemption: In case the endpoint criterion is "Not Ready," the following exemption will appear for the endpoint – Subscription Missing.

How to Fix

• Unknown: Deploy Connector on the endpoint.
• Not Ready: Check for communications issues.

Note #1 – Local Repository Architecture Configuration: Endpoint Readiness feature supports local repository architecture configuration. Please check "Linux Subscription" settings. Based on the settings, endpoints won’t need the "Subscription" criterion for readiness status – it will be considered as "Not Applicable".

Advisories Ready

General Information

Description: Checking for available Advisories in the endpoints from the required repositories.

Supported Operating Systems:

• All Linux platforms except CentOS and Ubuntu

Readiness Statuses

Status	Description
Ready	The endpoint has Advisories information from configured repositories.
Not Ready	The endpoint does not have the Advisories information from the configured repositories in JetPatch settings.
Unknown	If there is no data from the endpoint or in the settings.
Not Applicable	Unsupported OS.

Exemption: In case the endpoint criterion is "Not Ready" and the Repository Configuration readiness criterion is "Ready," the following exemption will appear: Advisories Not Exist.

How to Fix

• Unknown (❓)
  • There are no Configured Repositories in JetPatch Settings matching the endpoint OS.
• Not Ready (❌)
  • Repository List: 
    • Make sure all the added repo IDs have advisories. 
    • For example, if you use the automatic repo configuration option, it will add all enabled repos, including those without advisories, like Custom repos, Extra / EPEL Repos, and Pool repos (for SLES).
  • Repository Issue: 
    • If the endpoint is using a local repository, make sure it can pull Advisories information (updateinfo.xml / updateinfo.xml.gz). Run: "find /var/cache/ -iname *updateinfo.xml*" on the endpoints. 
    • If nothing shows up, advisories are not configured on the repository. 
    • Please refer to the article on How to fix Missing Advisory Information in Local Repository.
  • Endpoint cache issue: 
    • Sometimes, the endpoint is not pulling the full Advisory information. 
    • To pull the updated information, run:
      • YUM-based systems: "yum clean all && yum updateinfo."
      • ZYPPER-based systems: "zypper clean."

Packages Support

General Information

Description: Checking for available packages in the endpoints from the required repositories.

Supported Operating Systems:

• All Linux platforms except Ubuntu

Readiness Statuses

Status	Description
Ready	The endpoint has available packages from configured repositories.
Not Ready	The endpoint does not have packages from the configured repositories.
Unknown	If there is no data from the endpoint or in the settings.
Not Applicable	Unsupported OS.

Exemption: In case the endpoint criterion is "Not Ready" and the repository Configuration readiness criterion is "Ready," – the following exemption will appear: Packages Not Exist.

How to Fix

• Unknown (❓)
  • Connector compatibility – The connector version should support Endpoint Readiness. 
    • Check for the installed Connector version.
  • There are no Configured Repositories in JetPatch Settings matching the endpoint OS.
• Not Ready (❌)
  • Duplicate Repo ID: 
    • Make sure the same repo ID is not accidentally added twice (known issue to be fixed in 4.2.7).
  • Connectivity/Repository Issue: 
    • Check the endpoint repository configuration. 
    • The endpoint should be able to connect to the repository and pull the right information.
      • YUM-based systems: "yum repolist -all" – number of packages should be higher than 0.
      • ZYPPER based systems: "zypper se -r <REPO_ID>" (to fetch REPO_ID run: "zypper repos -E")
  • Endpoint cache issue: 
    • Run:
      • YUM: "yum clean all && yum updateinfo."
      • ZYPPER: "zypper clean"

Repository Configured

General Information

Description: Checks if the repository configuration of the endpoint is pointing to the right repositories, determined by the user in the Readiness settings, and checks for other related settings.

For Windows, WSUS is treated as a repository. 

In addition to WSUS configuration, Endpoint Readiness checks additional GPO settings:

• "Configure Automatic Updates" = enable (in endpoint readiness output: wsusAutomaticUpdates = true)
• "Specify intranet Microsoft update service location" = enable (in endpoint readiness output: hasUpdateServiceLocation = true)

Supported Operating Systems: All OSs supported by the JetPatch Patch Management module.

Readiness Statuses

Status	Description
Ready	The endpoint is pointing to the right WSUS / Linux repositories. Only one configured repository can match the incoming configuration from the endpoint.
Not Ready	Endpoint configuration is wrong and does not match the Readiness settings.
Unknown	If there is a problem in the Endpoint for fetching the repositories or there is no data in the settings.

Exemption: JetPatch considers the Configured Repository Flag. 

If the flag is marked – exemption is raised for "Not Ready" and "Unknown". If unmarked – exemption is raised for "Not Ready" only.

How to Fix

• Unknown (❓)
  • Check the Required Repository Configuration in the Readiness Settings and make sure there is an entry representing the EP Operating System and CIDR.
  • The Readiness information didn’t get any “Repositories” data from the endpoint – please contact JetPatch support.
• Not Ready (❌)
  • Check if the endpoint configuration for WSUS/Repositories is the same as configured in Readiness Settings → Configured Repository Configuration.
  • Check if the endpoint configuration for the repositories is enabled (and with the expected values for Windows repository settings).

Note #1 - Configured Repository Configuration Scenarios

For “Ready” status, only one configured repository in the readiness settings can match the incoming configuration from the endpoint. 

Example Scenarios:

	Scenario #1	Scenario #2	Scenario #3
Repository configuration on the Endpoint	REPO1 REPO2	REPO1	REPO3
Configured Repositories in JetPatch Readiness Settings	REPO3 REPO1 + REPO2 REPO4	(same as #1)	(same as #1)
Result	✅ Ready	❌ Not Ready	✅ Ready
Explanation	The endpoint matches the second configured repository in JetPatch settings.	No Configured Repository in JetPatch matches the endpoint. It matches only part of the repositories in #2.	The endpoint matches the first configured repository in JetPatch settings.

Note #2 - Configured Repository Readiness Status Decision Matrix

The following scenario describes the result of matching the endpoint repository configuration to the Configured Repositories in JetPatch. 

Top row = Configured Repositories in JetPatch Settings. 

Left column = Endpoint repositories configuration.

JetPatch vs Endpoint	REPO1 + REPO2	REPO1	REPO2	Empty
REPO1 + REPO2	✅ Ready	✅ Ready	✅ Ready	❓ Unknown
REPO1	❌ Not Ready	✅ Ready	❌ Not Ready	❓ Unknown
REPO2	❌ Not Ready	❌ Not Ready	✅ Ready	❓ Unknown
Empty List	❌ Not Ready	❌ Not Ready	❌ Not Ready	❓ Unknown
Not Exist (problem in Readiness)	❓ Unknown	❓ Unknown	❓ Unknown	❓ Unknown

PS Version

General Information

Description: Checking the endpoint PS version.

Supported Operating Systems:

• Windows only

Readiness Statuses

Status	Description
Ready	The major PS version is 3 or above.
Not Ready	The major PS version is 2 or below.
Unknown	If there is no data from the endpoint.
Not Applicable	Unsupported OS.

Exemption: In case the endpoint criterion is "Not Ready," the following exemption will appear: Unsupported PowerShell Version.

How to Fix

• Unknown: Connector compatibility – Connector version should support Endpoint Readiness. Check for the installed Connector version.
• Not Ready: Need to upgrade PowerShell version to 3 or above.

PS Execution Policy

General Information

Description: Checking the endpoint PS Execution Policy (highest Scope).

Supported Operating Systems:

• Windows only

Readiness Statuses

Status	Description
Ready	The PS Execution Policy is Unrestricted/RemoteSigned.
Not Ready	The PS Execution Policy is AllSigned/Restricted.
Unknown	If there is no data from the endpoint.
Not Applicable	Unsupported OS.

Exemption: In case the endpoint criterion is "Not Ready," the following exemption will appear: Unsupported PowerShell Execution Policy.

How to Fix

• Unknown: Connector compatibility – Connector version should support Endpoint Readiness. Check for the installed Connector version.
• Not Ready: Need to change the PS Execution Policy to a supported policy.

WUA Communication

General Information

Description: Checking the endpoint (Windows Update Agent) Connectivity to the WSUS server. This information is extracted from the "wsus get groups and computers in group" task (the field to check is "LastReportedStatusTime"), as part of the WSUS Discovery Source scripts.

4.2.8 Enhanced Check: > The WUA connectivity check has been updated (check_WUA_search.ps1) to provide simplified pass/fail testing. For WSUS-less: The check now verifies if the Windows Update Agent can successfully reach and search the Microsoft Cloud. Error Surfacing: This updated script now surfaces specific error codes if the search fails, allowing for faster troubleshooting of network or proxy blocks.

Supported Operating Systems:

• Windows only

Readiness Statuses

Status	Description
Ready	The endpoint reported in the last X minutes (configurable value in Readiness Settings).
Not Ready	The endpoint didn’t report in the configurable time.
Unknown	If there is no data on the endpoint.
Not Applicable	Unsupported OS.

Exemption: In case the endpoint criterion is "Not Ready," the following exemption will appear: WSUS Communication Problems.

How to Fix

• Unknown:
  • WSUS Discovery Source – make sure it is added and is working.
  • WUA Configuration:
    • Verify Windows Update Settings are set correctly to the WSUS.
    • Verify the device shows up in the WSUS Console.
• Not Ready:
  • WUA Connectivity:
    • WSUS Discovery Scripts – download manager logs and verify there are no errors in discovery.log for the WSUS scripts, including wsus get groups.
    • Windows Update Agent can’t reach the WSUS. Solution – Check connectivity between the Windows Update Agent and the WSUS.
    • Endpoint reporting is happening in a lower interval than the configured value in the Readiness settings. 
      • Go to the WSUS console, find the problematic endpoint in the “Computers” section, check the “Last Status Report” column, and make sure it was last communicated in the time interval provided in the Readiness configuration. 
      • If not, increase the Readiness setting for “Endpoint Communication with WSUS”.
    • Replica endpoint reports synchronization – See Note #1 below.

Note #1 – WSUS Replica Architecture: The reports of endpoints communicating with a WSUS Replica (downstream) will be sent to the WSUS Main (upstream) only after downstream synchronization.