Installation with Microsoft Intune

This section provides a step-by-step guide for using Microsoft Intune to deploy the Action1 agent on endpoints enrolled in Microsoft 365. This deployment approach can be useful for enabling administrative management of newly set-up endpoints, especially in cases where a Microsoft 365 user without local administrator rights has enrolled the device.

Phase 1: Prepare the Win 32 App Content Prep Tool and Action1 Agent Package

NOTE: A Win32 App in Intune refers to both 32-bit and 64-bit Windows applications.

1. Download the Microsoft Win32 Content Prep Tool for Intune provided as the IntuneWinAppUtil.exe utility file: https://github.com/microsoft/Microsoft-Win32-Content-Prep-Tool

2. Unzip the Microsoft Win32 Content Prep Tool to a local folder (for example, C:\IntunePackages), and create subfolders for the Source and Target packages.

3. Download the Action1 agent for Windows from the Action1 console.
4. Copy the downloaded agent package to a subfolder of the Source folder — for example, C:\IntunePackages\Source\Action1.

NOTE: Default Action1 agent package name is action1_agent(My_Organization).pkg. If you rename the package to remove your organization-specific information (organization name), then you will need to specify your account ID as a parameter during the installation.

5. Open a command prompt and create an Action1 agent deployment package by running IntuneWinAppUtil.exe with the relevant parameters:
   IntuneWinAppUtil -c <setup_folder> -s <source_setup_file> -o <output_folder>
   For this example:
   IntuneWinAppUtil.exe -c C:\IntunePackages\Source\Action1 -s C:\IntunePackages\Source\Action1\action1_agent.msi -o C:\IntunePackages\Target\Action1

Once run, successful output should look like this:

Your Intune package should now be created in the Target \ Action1 folder, having intunewin extension.

Phase 2: Deploy the Agent Package Using Microsoft 365 Intune Console

1. To deploy the Action1 agent to a specific set of endpoints or users, rather than using the default All Devices or All Users groups, start by creating a dedicated group within the Microsoft 365 Intune Console. This group will contain the endpoints managed by Action1. Navigate to Groups, select New Group, and configure it as needed. From the Membership type dropdown list, choose Assigned and add the relevant devices or users as Members.

2. In the Microsoft 365 Intune Console, navigate to Apps, then click All Apps.
3. Click Add, then from the App Type select Windows app (Win32).

4. At the App information step, browse and select the .intunewin app package created earlier in the Target folder. Add the Action1 details and logo and fill in the relevant information such as Privacy URL and Administrator details for your organization. The app information will be shown to end users in the Intune Company Portal.
5. Click Next.

6. At the Program step, review and adjust the package settings as per your requirements, then click Next.

7. At the Requirements step, specify the necessary app requirements like operating system or required disk space. Refer to Action1 Requirements for details. Click Next.

8. At the Detection rules step, from the Rules format select Manually configure detection rules.
9. Navigate to Type and click Add to set up a new rule.

10. For the new rule, set the Rule type as MSI. This should populate the MSI product code in this dialog and in the app configuration wizard.

11. At the Dependencies step, click Next.
12. At the Supersedence step, click Next.
13. At the Assignment step, specify the settings you need.
14. Finally, at the Review step review the configuration and click Create.

15. If the Intune Management Extension is installed, the Intune sync process runs every 60 minutes; otherwise, it runs every 8 hours. To initiate a sync manually, in the Microsoft Endpoint Manager portal, navigate to Devices, select All Devices, choose the relevant device, and click Sync.

TIP: Sync can also be initiated under Bulk Device Actions.

16. Finally, navigate to All Apps, select the Action1 agent app and then examine the Device install status.

Once the agent is deployed, the target endpoint will be shown in the Endpoints view of Action1 console.