Absolute Agent – Application Deployment with Intune for Window Devices

Absolute Agent is an endpoint visibility and control tool that helps track, manage, and secure devices remotely. In this article, we will walk through the process of deploying Absolute Agent using Microsoft Intune as a Win32 application.

This deployment package includes three essential files:

  • AbsoluteFullAgent.msi
  • AbsoluteAgent.dat
  • AbsoluteAgent.sig

📌 All three files must be bundled together in the deployment package to ensure successful installation.

Download Link: You can download the application from the admin console.

Things to consider during the packaging of applications

Please specify the source folder: [APP_FOLDER_NAME]
Please specify the setup file: AbsoluteFullAgent.msi
Please specify the output folder: [OUTPUT_APP_PACKAGE_FOLDER_NAME]

(Refer Win32 Packaging Instructions: https://sysopsinsiders.com/packaging-win32-app-for-intune-upload)

Uploading and Deploying Absolute Agent Win32 Package into Intune

Login to Microsoft Intune Admin Center: https://intune.microsoft.com/

Upload the AbsoluteFullAgent.intunewin win32 file

I have mentioned only the following parameters during the deployment process. Other settings are similar for every application, or you can set them as required. Make sure the following parameters, such as Install, Uninstall, and Detection Rules, are set for this application.

ParametersCommand / Value
Install Command (silent)msiexec /i "AbsoluteFullAgent.msi" /qn
Uninstall Command (silent)msiexec /x "{productcode}" /qn
(You can let Intune auto-detect the product code)
Detection RulesAdd - rule type - File

Path - %systemdrive%\Windows\SysWOW64\

File or Folder - rpcnet.exe

Detection method - File or folder exists

Associated with 32 bit app - No

Refer to the complete instructions provided regarding uploading and deploying the win32 App to Intune from the link below
https://sysopsinsiders.com/upload-and-deploy-win32-application-using-microsoft-intune/

Leave a Reply

Your email address will not be published. Required fields are marked *