Articles in this section

Endpoint Exemptions and Warnings

Overview

This article describes the exemptions and warnings that can prevent an endpoint from being patched in JetPatch. Understanding these statuses helps IT administrators quickly identify issues, assess their impact, and take the appropriate corrective action.

Exemptions are divided into two categories:

  • Cannot patch: The endpoint is blocked from patching until the underlying issue is resolved.
  • Temporarily cannot patch: The endpoint is currently unable to be patched but may become available once conditions change (e.g., after a maintenance window opens or connectivity is restored).

Exemptions

Exempted endpoints are endpoints that at the moment cannot be patched. 

The following list contains the exemptions that can prevent an endpoint from being patched.

Exemption What Does It Mean Impact How to Fix
Untested Endpoint

JetPatch has the endpoint in the inventory but does not aware of any Connector installations.
 

More information can be found in Endpoint List and Connector Connection Status Reference

 Cannot patch

If the issue is only affecting some of the endpoints

If the issue is affecting all of the endpoints (especially when the endpoints were previously connected)
Patching Inapplicable

Linux - Endpoint running does not support the Operating System for patching activities

Windows - One of the following reason:

  1. Endpoint does not exist in WSUS
  2. Endpoint exists in WSUS but not yet reported. 
  3. WSUS not added to JetPatch
 Cannot patch

Learn more on JetPatch Supported Platforms

 
Powered Off

The endpoint is Powered Off.

More information can be found in Endpoint List and Connector Connection Status Reference

 Cannot patch Power On the endpoint server
Power Suspended

Endpoint is suspended

More information can be found in Endpoint List and Connector Connection Status Reference

 Cannot patch
Power Unknown

JetPatch could not detect the Power state of the endpoint

More information can be found in Endpoint List and Connector Connection Status Reference

 Cannot patch
Disconnected

JetPatch could not connect to the endpoint (SSH/SMB protocols) / JetPatch didn't get any communication from the endpoint (WEB protocol)

 Temporarily cannot patch Re-establish connector connectivity
Connector Not Installed / Available

Valid credentials are known to be available, but JetPatch has not yet installed the JetPatch connector on the endpoint.

More information can be found in Endpoint List and Connector Connection Status Reference

 Cannot patch Deploy Connector on endpoint server
Connector Down

The endpoint is reachable but Connector is stopped

More information can be found in Endpoint List and Connector Connection Status Reference

 Temporarily Cannot Patch Re-establish connector connectivity
Not Reachable

The endpoint is not reachable (Communication problems)

More information can be found in Endpoint List and Connector Connection Status Reference

 Temporarily Cannot Patch Re-establish connector connectivity
Invalid Credentials

The supplied credentials are not accepted by this endpoint, so they cannot be managed.

More information can be found in Endpoint List and Connector Connection Status Reference

 Temporarily Cannot Patch Fix invalid Credentials 
Awaiting Maintenance Window Endpoint Assigned to Future Maintenance Schedule (Not Started) Temporarily cannot patch Learn more about Maintenance Schedules   
Maintenance Window Required No Maintenace Schedule was assigned to Endpoint. Temporarily cannot patch
Maintenance Window Expired Endpoint Assigned to Expired Maintenance Schedule (Already Ended) Temporarily cannot patch
No Maintenance Entry Endpoint Assigned to Maintenance Schedule with no maintenance Entries Temporarily cannot patch
Maintenance Window Timeout Endpoint Assigned to problematic Maintenance Window and didn’t manage to deploy all patches on time. Temporarily cannot patch
Suspended by User Currently cannot be patched -  An endpoint was suspended manually by the user for a number of cycles or between specific dates Temporarily cannot patch Remove endpoint Suspension 
Unsupported PowerShell Execution Policy

The PS Execution Policy is AllSigned/Restricted

 Cannot patch
Unsupported PowerShell Version

The major PS version is 2 or below

 Cannot patch
  • Upgrade to PowerShell version 3 and above 
  • Learn more about Readiness
Advisories Not Exist

The endpoint does not have the Advisories information from the configured repositories in JetPatch settings

 Cannot patch Learn more about Readiness
Packages Not Exist

The endpoint does not have packages from the configured repositories

 Cannot patch Learn more about Readiness
Wrong Repositories Configuration   Cannot patch Learn more about Readiness
Subscription Missing

The endpoint does not have a valid subscription

 Cannot patch Learn more about Readiness
WSUS Communication Problems

The endpoint Didn't / Couldn't report to the WSUS Withing the configurable time

 Cannot patch Learn more about Readiness
Unknown Endpoint

The endpoint was discovered by the Vulnerability System but is not managed

 Cannot patch Deploy Connector on endpoint server
Pending User Action

The endpoint (Virtual Machine) Freezes

 Cannot patch  
Pending Reboot Suspension

Patching Process Ended, but a Reboot is Needed

 Cannot patch

1. Reboot the machine

2. Remove endpoint Suspension 

3. Wait 1 day

Low Disk Space

The following list contains the warnings that can prevent an endpoint from being patched.

This warning will appear if any percentage is >= 90% on any of the hard drives on an endpoint.

To verify disk space, navigate to:

  • Platform Configuration → Servers → filter on the endpoint.
Note: Make sure that in Table Settings (button in the upper right corner) the "Disk Space In Use" column is enabled.

By hovering the mouse over the Disk Space In Use column and row of the needed endpoint, a pop-up window will appear with additional data.

mceclip0.png

Related articles

Comments

0 comments

Please sign in to leave a comment.