Autonomo - Installation via Intune (remote and volume installation)
Instructions for setting up Intune to deploy Autonomo.
Prerequisites
The user installing the Autonomo application must be assigned as an admin, manager or install role.
Before starting, please review the install check list in the first section.
There are three ways you can install Autonomo:
- Autonomo - Installation via UI
- Autonomo - Installation via command window (quiet)
- Autonomo - Intune remote setup info - This document.
Please see the below to find more details when installing Autonomo:
- Autonomo - Asset Category and Asset Sub-Category options
- Autonomo - Asset Groups
- Autonomo - Auto-provisioning
- Autonomo - Install Troubleshooting Guide
Steps for Installing Autonomo onto designated devices using Intune
- Create an account in the Troverlo Portal if one does not exist for your company.
- Download AutonomoSetup.intunewin package
- This same link can be accessed by selecting the last option on the Navigation panel of the Portal.

- Click on the link called AutonomoSetup.intunewin to download the Intune package.
- Or click on this link AutonomoSetup.intunewin to download the Intune package.
- With most browsers, by default files downladed are put into the \users\<username>\downloads folder.
- This same link can be accessed by selecting the last option on the Navigation panel of the Portal.
- Open Intune - troverlo.com - Microsoft Intune admin center
- Navigate to Apps -> Windows
- Click on Create (top menu)
- Select App type - Windows app (Win32)
- Click on "Select"
- Click on "Select app package file"
- Navigate to where AutonomoSetup.intunewin can be found and select it
- Press "Ok"
- App info
-
Field Value Name Troverlo AutonomoDescription Troverlo Autonomo endpoint agentPublisher Troverlo
-
- Program
-
Field Value Install command AutonomoSetup.exe --install USERNAME="user@company.com" PASSWORD="YourPassword" CATEGORY="YourCategory" SUBCATEGORY="YourSubcategory"Uninstall command AutonomoSetup.exe --uninstallInstall behavior System Device restart behavior No specific action -
Optional Install Parameters
Append any of these to the install command:
Parameter Description Default AUTONOMOMODE=Active|OESR|OEOperating mode ActiveASSETGROUP="Group1,Group2"Asset group names (none) CURRENTUSER=yes|noReport logged-in user noLOGFILEInstaller troubleshooting log c:\Windows\SystemTemp \AutonomoInstaller.log
-
- Return codes
- 0 - Success
- All the failure codes will come out in IEM log file and are listed at the bottom as a reference.
-
- Requirements
-
Field Value Operating system architecture 64-bit Minimum operating system Windows 10 21H2
-
- Detections rules
-
-
Select Manually configure detection rules → Add:
Field Value Rule type Registry Key path HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{3936E1BC-C06C-45AE-B1DB-430CF31DD48B}Value name Version to display Detection method Value exists Associated with a 32-bit app on 64-bit clients No
-
-
- Dependencies
- None - installer takes care of all dependencies
- Supercedence
- None - installer takes care of all dependencies
- Assignments
- Please put your define group of devices in the "Required" section
- Click Review + create
Verification
After deployment, devices in the assigned group will install the agent on next Intune sync. To verify:
- Intune portal: Apps → Monitor → App install status → select Troverlo Autonomo
- On the device: Check Add/Remove Programs for "Troverlo Autonomo" or verify the service
AutonomoWServiceis running
Notes:
- Please note: the user that is installing Autonomo must have the "installer" role assigned to them. - see User (Team Member) Management
- Click to learn more about CATEGORY, SUBCATEGORY and ASSETGROUP.
-
ASSETGROUP, CURRENTUSER, AUTONOMODE, LOGFILE are optional parms
- ASSETGROUP
- This allows you group assets together to aid in searches.
- There can be multiple items, they must be separated with a comma, no spaces.
- AUTONOMODE
- These are the Autonomo Modes you can choose from
-
- “Active”
- Autonomo operates as an Observation Endpoint and there is a desire to track this device as an Asset.
- Autonomo will post Wi-Fi scan data for all detected APs and other Troverlo Assets (if any) within an observation window and will include its own ID in the post.
- Can publish or receive Action Commands.
- This is the default.
- “OESR” – Observation Endpoint Self-reporting
- Autonomo operates as an Observation Endpoint and there is a desire to track this device as an Asset.
- Autonomo in this mode will ONLY post Wi-Fi scan data about itself, Assets and APs when other Troverlo Assets are detected within an observation window.
- Never advertises its location – when offline it doesn’t beacon.
- Can publish, but cannot receive Action Commands.
- “OE” – Observation Endpoint
- Autonomo operates as an Observation Endpoint and there is NOT a desire to track this device as an Asset.
- Autonomo in this mode will ONLY post Wi-Fi scan data that contains Troverlo Assets and APs when other Troverlo Assets are detected within an observation window.
- Never advertises its location – when offline it doesn’t beacon.
- Can publish, but cannot receive Action Commands.
- “Active”
- CURRENTUSER
- Autonomo monitors the current account user and transmit this information security via SSID to the Troverlo platform with each observation for that Asset.
- WARNING: You canNOT use CURRENTUSER="yes" with AUTONOMODE="OE". If you select this combination, you will see this error.
- LOGFILE
- Designate file name and full path for the installation log file to be used for troubleshooting
- Example usage:
- LOGFILE=C:\windows\temp\autonomoInstaller.log
-
Default log filename is AutonomoInstaller.log and it can be found in the c:\Windows\SystemTemp directory
Steps for Uninstalling Autonomo from designated devices using Intune
This is the same as above w change to assignments
- Assignments
- Please put your define group of devices in the "Uninstall" section
Troubleshooting
Autonomo-install.log and AutonomoSetup.log
These files can be found in the c:/windows/systemTemp folder, unless LOGFILES designates it to be in a diff location or have different name.
This is a log file that provides information output from the MSI file when quiet install is used (command line).
Use it to validate
- Autonomo version, date and time installed.
- All the parameters entered on the command line.
Use it to troubleshoot:
- It will show all the steps covered.
- It will show if successful or any errors if not successful.
Return codes for AutonomoSetup.intunewin
| Code | Meaning |
|---|---|
0 |
Success |
10 |
Invalid command line |
20 |
Another setup instance is already running |
30 |
Could not check for a newer setup version |
31 |
This setup package is outdated and should be replaced |
40 |
.NET 8 Desktop Runtime bootstrap/install failed |
41 |
.NET 10 Desktop Runtime bootstrap/install failed |
50 |
Installer download failed |
60 |
Installer launch failed |
100 |
Invalid command line |
101 |
Unknown command |
102 |
Multiple commands were supplied |
103 |
Invalid GUI-only option |
104 |
Unknown argument |
200 |
Failed to load startup state |
201 |
Missing install configuration data |
202 |
Update server unavailable |
203 |
Release manifest was invalid |
204 |
Manifest not loaded |
300 |
General validation failure |
301 |
Missing credentials |
302 |
Missing category or subcategory |
303 |
Invalid category or subcategory selection |
304 |
Maintenance validation failed |
305 |
Network validation failed |
306 |
Requested release channel unavailable |
307 |
Requested version is not available for the selected channel |
308 |
Requested version is below the minimum supported version |
309 |
Requested version is unavailable |
310 |
No install files were present in the manifest |
400 |
Authentication is required |
401 |
Authentication failed |
402 |
Missing refresh token |
403 |
API token creation failed |
404 |
Access token refresh failed |
500 |
Asset registration unauthorized |
501 |
Asset registration failed |
502 |
Asset update unauthorized |
503 |
Asset update failed |
504 |
Asset archive failed |
505 |
Device serial number unavailable |
700 |
Installer engine failed |
701 |
Package download failed |
702 |
Downloaded file hash mismatch |
703 |
Insufficient disk space |
704 |
Device registration MAC address unavailable |
705 |
Event manifest missing |
706 |
Event resource module missing |
707 |
Event log registration failed |
708 |
Service registration failed |
709 |
Service permissions update failed |
710 |
Service recovery configuration failed |
800 |
No existing installation was found for uninstall |
900 |
Unexpected internal error |
Please reference the Autonomo - Install Troubleshooting Guide if you encounter issues not addressed above or you may contact Troverlo Support via our Support Center.