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 / Untested |
JetPatch has the endpoint in the inventory but does not aware of any Connector installations. 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 - Endpoint does not exist in WSUS |
Learn more on JetPatch Supported Platforms |
Powered Off |
The endpoint is Powered Off. Cannot patch |
Power On the endpoint server |
Power Suspended |
Endpoint is suspended Cannot patch |
|
Power Unknown |
JetPatch could not detect the Power state of the endpoint 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. Cannot patch |
Deploy Connector on endpoint server |
Connector Down |
The endpoint is reachable but Connector is stopped Temporarily Cannot Patch |
Re-establish connector connectivity |
Not Reachable |
The endpoint is not reachable (Communication problems) Temporarily Cannot Patch |
Re-establish connector connectivity |
Invalid Credentials |
The supplied credentials are not accepted by this endpoint, so it cannot be managed. 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 |
|
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 | Remove endpoint Suspension |
Unsupported PowerShell Execution Policy | Cannot patch |
|
Unsupported PowerShell Version | Cannot patch |
|
Advisories Not Exist | Cannot patch | Learn more about Readiness |
Packages Not Exist | Cannot patch | Learn more about Readiness |
Wrong Repositories Configuration | Cannot patch | Learn more about Readiness |
Subscription Missing | Cannot patch | Learn more about Readiness |
Wsus Communication Problems | Cannot patch | Learn more about Readiness |
Unknown Endpoint |
The endpoint was discovered by the Vulnerability System but is not managed. Cannot patch |
|
Pending User Action |
The endpoint (Virtual Machine) Freezes. Cannot patch |
|
Pending Reboot Suspension |
Patching Process Ended, but Reboot is Needed Cannot patch |
1. Reboot the machine 3. Wait 3 days |
The following list contains the warning that can prevent an endpoint from being patched
-
Low Disk Space
This warning will appear if any percentage is >= 80% on any of the hard drives on an endpoint.
Regarding low disk space, you can verify disk space by going to
> Platform configuration > Servers > filter on the endpoint.
Note: You need to make sure that in Table Settings (button in the upper right corner) have "Disk Space In Use" column 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.
Comments
0 comments
Please sign in to leave a comment.