Next Steps
Action1 offers a broad range of capabilities to further streamline your patch management workflows. Once you are familiar with the basics, consider exploring the following features:
Leverage app-based multi-factor authentication
Multi-factor authentication (MFA) provides enhanced protection for user accounts by adding an extra layer of verification. While email-based MFA is enabled by default, Action1 strongly recommends using app-based MFA for increased security. You can use, for example, Google Authenticator, Twilio Authy, Duo Mobile, or Microsoft Authenticator. For details, see Multi-factor Authentication.
Create endpoint groups
Segment endpoints by server role, OS version, location, department, or other criteria to apply customized automation rules. Navigate to Endpoints and click Create Group. For details, see Endpoint Groups.
View installed software
Go to the Installed Software section to a list of applications installed on your endpoints, along with their version details and update availability. For details, see View Installed Software.
Deploy applications
Remotely install and configure applications using the pre-configured packages available in the Software Repository. Navigate to Software Repository, select one or more applications, and click Deploy to Endpoints. To deploy custom applications, click +Add to Repository. For instructions on installing Linux packages, see Deploy Software.
Uninstall applications
Remove outdated or unnecessary applications manually, or automate the process. Select one or more endpoints and click Uninstall Software, or create an Uninstall Software automation to streamline automatic uninstalls. For details, see Uninstall Software.
Run scripts
Use the Script Library to perform remote management tasks, such as blocking Windows Feature Updates, deleting temporary files, deploying or removing Linux packages, restarting Linux and macOS endpoints, and more. You can also add your custom scripts to the list. For details, see Script Library.
NOTE: Custom scripts, software application versions, automations, and custom data sources for the reports are security-sensitive and should be signed with your Action1 Key when created or modified.