Autonomo 4 - Operational insights

Wi-FI

The Asset that Autonomo is being installed on MUST have a Wi-Fi adaptor and it must be enabled.  

During installation, Wi-Fi or Ethernet MUST be connected so that the Asset created on the Troverlo platform can be auto-provisioned.

Autonomo requires the Microsoft Wi-Fi Direct Virtual Adapter to operate (ie it is used to control the scan and beacon management).

You can check if the device has Wi-FI in several ways, here are the two easiest:

1. Click on the start windows key and type "cmd," click on "run as an administrator"
   1. 
2. Type "ipconfig /all" at the command prompt - you are looking for:
   1. Microsoft Wi-Fi Direct Virtual Adapter #...
3. Type "wmic nic get MACAddress, Name" at the command prompt, you are looking for:
   1. Microsoft Wi-Fi Direct Virtual Adapter #...

Autonomo Connectivity Modes

1. Scan Mode – when the device that is running Autonomo IS online (ie connected to Wi-Fi or Ethernet), it will scan for APs (access points) and post the results every 5 min to the Troverlo platform.

2. Beacon Mode – when the device that is running Autonomo is offline (ie NOT connected to Wi-Fi or Ethernet), it will beacon regularly so it can be detected by an Observation Endpoint.

   

Autonomo Operational Modes

1.  “Active”

1. 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.
2. Can publish or receive Action Commands
3. This is the default.

1. “OESR” – Observation Endpoint Self-reporting

1. Assets are used as an Observation Endpoint and there is a desire to it.
2. 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.
3. Never advertises its location – when offline it don’t beacon.
4. Can publish, but cannot receive Action Commands

1. “OE” – Observation Endpoint

1. Autonomo operates as an Observation Endpoint and there is NOT a desire to track it.
2. 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.
3. Never advertises its location – when offline it don’t beacon.
4. Can publish, but cannot receive Action Commands

Event Viewer

 Event viewer overview

The Windows Event Viewer is where all logging related to Autonomo resides. The above link provides good overview video on how to use the tool.

There are views if the user is looking for things specifically within a process or thread of a process. These are not files, they are filters setup permanently that pull data from our log file titled “Troverlo Autonomo.” The Troverlo Autonomo.evtx can be found here - C:\Windows\System32\winevt\Logs.

Click on "customer views -> Troverlo Autonomo Views" on upper left

These are "segmented" views of all the logs that come from Autonomo

To see all the logs, there is value in seeing timing between threads of activity, click on "Applications and Service Logs -> Troverlo Autonomo" on the upper left side

On the right side are options to

1. Open files (customers will send)
2. Create your own view (never done, could be useful)
3. Filter current log - powerful, where you will spend your time.
4. Properties - can change size of file and what happens when size is met
5. Find - sometimes it seems to get lost and takes forever to find something, other times it is fast. No idea. Very useful
6. Save log file
   1. Takes whatever you have on screen (ie if have filters, it saves what is on screen) and lets you save in diff formats
   2. 
   3. Top is default, powerful in tool, compresses about 90%
   4. Xml - never use
   5. Text - much smaller, can't bring back into tool
   6. CSV - never use
7. View - no idea, never used
8. Refresh - this is static view, need to hit this to see latest data