Exemptions
Exempted servers are servers 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)
|
| Powered Off |
Endpoint is Powered Off. Cannot patch |
Power On 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 got 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 |
Endpoint is reachable but Connector is stopped Temporarily Cannot Patch |
Re-establish connector connectivity |
| Not Reachable |
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 |
If a remediation plan has already started and maintenance window has been changed / deleted it might cause failures upon patching installation. If the remediation plan hasn't started - patching actions are prevented |
Learn more on Maintenance Schedules |
| Maintenance Window Required | ||
| Maintenance Window Expired | ||
| Maintenance Window Timeout | ||
| Suspended by User | Currently cannot be patched - An endpoint was suspended manually by user for a number of cycles or between specific dates | Remove endpoint Suspension |
| Patching Inapplicable |
Linux - Endpoint running not support Operating System for patching activities Windows - Endpoint does not exist in WSUS |
Learn more on JetPatch Supported Platforms |
| Unsupported PowerShell Execution Policy | Cannot patch |
|
| Unsupported PowerShell Version | Cannot patch |
|
| Advisories Not Exist | Cannot patch | Learn more on Readiness |
| Packages Not Exist | Cannot patch | Learn more on Readiness |
| Wrong Repositories Configuration | Cannot patch | Learn more on Readiness |
| Subscription Missing | Cannot patch | Learn more on Readiness |
| Wsus Communication Problems | Cannot patch | Learn more on Readiness |
| Unknown Endpoint |
The endpoint was discovered by the Vulnerability System but is not managed. Cannot patch |
|
| Pending User Action | ||
| Pending Reboot Suspension | Cannot patch |
1. Reboot 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.