WSUS Deprecation: Your Next Move in Patch Management

This Wednesday | 12 PM EST / 11 AM CET

Action1 5 Documentation 5 Troubleshooting

Troubleshooting

 

The following are the most common issues our users typically run into.

Installation: most frequently, installation errors are caused by running Action1 Deployer or agent installer without the administrative rights. Make sure you launch files by running as administrator. 

Deployment: check out the Logs page to review errors that occur during the agent deployment and operation. If you do not understand certain error messages, feel free to contact our technical support, and we will help you.

Network connectivity: most commonly, the connectivity issues are related to a firewall settings denying connection. Ports 22543 and 443 must be open for outbound connections; port 22551 must be open for inbound connections. You may need to configure your corporate firewall to allow these connections. Feel free to contact our technical support for help with network configuration. See Firewall Configuration for more information.

Reports run too long or return no results: some reports can take substantial time to complete (sometimes hours, depending on the number of files and endpoints). You can refresh report results (without re-running it) to see the most recent results after a while.

Alerts are not generated: make sure you allowlist [email protected] and www.action1.com email domain in your email settings. Also, to protect your inbox from overflowing, alerts will be suppressed if one alert rule generates more than 10 alerts per hour from one endpoint (and you will get notified in this case). Reconfigure the rules by adding additional filters to reduce alert triggering frequency.

Got an antivirus software that blocks PowerShell scripts? Sometimes AV apps such as Avast and AVG can block PS scripts executed by Action1. To avoid blocking, allowlist the Action1 folder in your antivirus settings. To do it, in your antivirus app, navigate to Menu / Settings / General / Exceptions and add the following files and folders:

  • C:\Windows\Action1\scripts 
  • C:\Windows\Action1\action1_agent.exe
  • C:\Windows\Action1\action1_remote.exe