Agent Remediation

Issue: Scheduler Not Running

Windows

To test Windows Scheduler, run this command:

Get-ScheduledTask -taskname SUPERVISOR_TASKS

Output Examples:

Task is enabled. This is a good state.

C:\Users\Administrator> Get-ScheduledTask -taskname SUPERVISOR_TASKS TaskPath TaskName State -------- -------- ----- \Armor Defense\ SUPERVISOR_TASKS Ready

Task is disabled. This is a bad state.

C:\Users\Administrator> Get-ScheduledTask -taskname SUPERVISOR_TASKS TaskPath TaskName State -------- -------- ----- \Armor Defense\ SUPERVISOR_TASKS Disabled

Task is missing. This is a bad state.

For bad states, please run this script:

Example:


Linux:

Verify job exists in /etc/cron.d/armor-job-SUPERVISOR_TASKS

If not, run this script:

Output Examples:

Task is enabled. This is a good state.


Task is missing. This is a bad state.


Script. This will re-add the cron job.

Grep cron log. This is a good state.

Grep cron log. This is a bad state. See commands for unexpiring.

Commands to check expired password. Good state.

Commands to check expired password. Bad state. Reset password.

Password reset


Connectivity/Firewall

Ensure that your firewalls are opened to the hosts as noted in Firewall Rules section of the Pre-Installation guide.

Windows Test Connectivity

IP address and port for these commands will need to be entered and are found in the Firewall Rules section of the Pre-Installation guide.

  • Windows connectivity test output should return a value of "true."

  • Windows connectivity test should not return a value of "false."

    • If test returns "false," investigate firewall blockages.

Examples:

This is the command run and value returned when there is connectivity to the service.

This is the command run and value returned when there is no connectivity to the service and your firewalls need to be checked for blockages.

Linux Test Connectivity

IP address and port for these commands will need to be entered and are found in the Firewall Rules section of the Pre-Installation guide.

  • Linux connectivity test output should return a value of "0."

    • If test returns anything other than "0," investigate firewall blockages.

Examples:

This is the command run and value returned when there is connectivity to the service.

This is the command run and value returned when there is no connectivity to the service and your firewalls need to be checked for blockages.


Powershell Version

Following Microsoft's documentation, upgrade to at least PowerShell version 5.

You can get PowerShell version 5 from the Microsoft.


No TLS 1.2

You can follow this Microsoft KB in order to enable TLS 1.2.

Having trouble with your upgrade? Here are some solutions to common issues.