Getting Started

Endpoints

Patch Management

Vulnerability Management

Software Deployment & IT Assets

Automation & Remote Desktop

Real-Time Reports & Alerts

Account Access & Management

SSO Authentication

Security Concerns

Integrations

Need Help?

Review and Deploy Patches

All endpoint information, including missing patches, installed software, and OS details, is refreshed in real time. You don’t need to schedule a periodic assessment to determine if any updates are missing.

To review and deploy patches:

  1. In the Action1 console, navigate to the Endpoints view and click on the endpoint name.
  2. Go to the Missing Updates tab and select the updates you want to deploy. All applicable updates — both for OS and third-party applications — are shown in a single view, including the update type and security severity.
  3. Click Deploy Update to start the update wizard. It will prepopulate the list of selected updates.

 

Important! OS updates and the latest application versions available in the Software Repository include built-in Action1 signatures and do not require an additional administrator signature. For a custom application that is not included in the Software Repository, make sure the version you want to deploy is signed by an authorized Enterprise Admin. The deployment automation must be signed separately, even when the selected updates or application versions already have built-in Action1 signatures.

  1. Adjust the Reboot Options as needed. By default, users will have up to 60 minutes to save their work if any of the updates require a reboot.
  2. Click Next Step and select only the test endpoint used in this walkthrough.
  3. Proceed to the scheduling options. For testing purposes, leave the default Run Now option selected. Review the selected updates, reboot options, and schedule. When prompted, sign the deployment automation using your Action1 Key / Key passphrase.

Action1 will begin deploying the selected updates and will report progress and results in real time.

NOTE: If the automation was scheduled with settings other than Run Now, it is possible to skip the signing step, but it will not execute on its schedule while unsigned. In this case, the automation will be shown as Unsigned, and an authorized administrator must sign its configuration before the scheduled start time.