macOS

The macOS agent allows Mac devices to be included in the service consoles, enabling support teams to see all devices used within the organization.

Supported versions

Support for macOS includes version Monterey 12 and later. Regarding architectures, FlexxAgent supports both Intel processors (amd64 architecture) and Apple processors with arm architecture (arm64).

Limitations

Certain features are not available for macOS, such as remote assistance, the execution of on-demand microservices from Workspaces or user microservices and flows, or the sending of notifications.

Due to how the operating system functions, the expected behavior on macOS is that when the device screen is locked, the operating system stops background processes, causing the device to stop reporting information to the consoles or receiving actions until the screen is unlocked or the session is started again.

Proxy Configuration

FlexxAgent for macOS supports communication through both authenticated and unauthenticated proxies. The proxy information must be provided to Flexxible to include it in the configuration file mentioned in the next point.

Required data:

• For unauthenticated proxy, it will be necessary to provide URL and Port.
• For authenticated proxies, User and Password must be added to the above.

Download and installation

To install FlexxAgent, you must run the installation script using a preset configuration file.

Installation Scripts

Path to download the installation script for x64 architecture:

https://update.workspaces.flexxible.com/agents/FlexxAgent/latest/macos/x64/flexxagent-install.sh

Path to download the installation script for ARM architecture:

https://update.workspaces.flexxible.com/agents/FlexxAgent/latest/macos/arm64/flexxagent-install.sh

The configuration file is required for the installation. It can be obtained by contacting Flexxible.

Steps for installation:

1. Download the installer from the URL.
2. Grant permissions to the script, open the terminal, and execute:

   sudo chmod +x ./flexxagent-install.sh

3. Run the script.

   sudo ./flexxagent-install.sh -c [configuration file]

4. Clean files.

Installation script parameters

Parameter	Caption
-v,--version <VERSION>	Use a specific version, by default, latest.
--verbose,-Verbose	Displays diagnostic information.
-c,--config <CONFFILE>	Applies the configuration from a configuration file by default settings.conf.
-?,--?,-h,--help,-Help	Shows help.

Examples

Install FlexxAgent with the configuration file:

flexxagent-install.sh [-c|--config <path/file.conf>]

Install a specific version of FlexxAgent:

flexxagent-install.sh [-v|--version <VERSION>]

Access the help:

flexxagent-install.sh -h|-?|--help

Uninstall

The uninstallation script can be downloaded from

https://update.workspaces.flexxible.com/agents/MacOS/FlexxAgent/latest/flexxagent-uninstall.

Steps for uninstallation:

1. Download the uninstaller from the URL.
2. Grant permissions to the script.

   sudo chmod +x ./flexxagent-uninstall.sh

3. Run the script.

   sudo ./flexxagent-uninstall.sh

Uninstallation script parameters

Parameter	Caption
-c,--cleanup <VERSION>	Cleans configurations and logs; default is false.
-?,--?,-h,--help,-Help	Shows help.

Examples

Uninstall and clean up configurations and logs:

flexxagent-uninstall.sh [-c|--cleanup]

Access the help:

sudo ./flexxagent-uninstall.sh --help

Update

The agent can be updated to the latest version in two ways:

• From Workspaces, select the device and perform: Operations -> FlexxAgent -> Update to the latest version.
• Re-running the installation script to download and install the latest version.

Obtained fields

FlexxAgent obtains and sends the following general information to the consoles:

• Device Name: device name
• Device Status: on or off
• FlexxAgent version
• FlexxAgent Status: running or stopped
• Last FlexxAgent report: date and time of last report received
• Connection: wireless LAN, mobile network, ethernet or unknown.
• Network: device network addressing and public IP for internet access. These networks are created automatically when more than four workspaces are connected to the same network.
• Subnet: device network segment
• MAC address
• Wireless network: network name
• Network signal: reception percentage
• Network changes: last time the network changed
• Sessions: number of user sessions
• Last User: last user who logged in
• Connected From: name of the device from which the user has logged in
• Connection time: session start date and time
• Code: this field lets users identify the workspace with a personal code. This code must be manually filled in individually using the Edit option in the Operations menu of the workspace details.
• RAM: total available RAM capacity
• Cores: number of processor cores
• IP address: device IP address on the local network
• OS: operating system name
• Operating system: operating system version
• System disk: total disk capacity and usage in percentage
• Public IP and ISP: the ISP is obtained using the public IP. It might not be accurate if connected to a corporate network or using a VPN.
• Region: obtained using the public IP. It might not be accurate if connected to a corporate network or using a VPN.
• Session Analyzer: whether configured or not
• Session Analyzer version: Session Analyzer version number
• Report Group: report group to which the device belongs.

Performance counter format information is also retrieved:

• CPU
• RAM
• Bandwidth
• Wireless connection signal percentage
• List of sessions
• List of disks with total and occupied capacity