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.

Installation steps

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.
-o, --offline	Installs FlexxAgent from a given package file, instead of downloading it. Please check the Offline installation section for more details.
-?,--?,-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

Offline installation

Offline installation is available if there is some networking restriction in your environment. To perform an offline installation, please ask your contact at Flexxible how to obtain the package and installer for your macOS device (ARM or x64).

The package file will be provided in ".pkg" format.

Offline installation steps

1. Place the FlexxAgent package file, the configuration file, and the installation script in the same folder.
2. Allow the Terminal application to access the disk where the files are located:

• Go to System preferences -> Security and Privacy -> Privacy.
• Select Full disk access.
• Add the Terminal application to the list.
• Close the Terminal application i it was running and open a new one.

3. Go to the folder where the FlexxAgent files are located, and grant permissions to the script:

sudo chmod +x ./flexxagent-install.sh

4. Run the script with the -o or --offline parameter:

sudo ./flexxagent-install.sh -c [archivo de configuración] -o [paquete de Flexxagent]

5. Clean the files used.

Uninstall

The uninstallation script can be downloaded from

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

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.

Information obtained from the device

FlexxAgent collects data locally from the device and sends it to the service consoles.

General information

• Name: device name
• Device Status: the device's power state, it can be On, Off, or Not reporting.
• FlexxAgent Version: version number of FlexxAgent installed on the device
• FlexxAgent Status: Running or Stopped
• Last FlexxAgent report: date and time of the last FlexxAgent report on the device. This date might not be recent if the FlexxAgent service is stopped or the device is off.
• Connection type: indicates whether the device is connected by Wi-Fi, 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.
• Network signal: reception percentage
• Subnet: device's network addressing
• MAC Address: unique identifier of the device's network card
• Wireless network: network name
• Connection Signal: signal reception percentage when the device connects via a wireless method.
• Network changed: date and time of the last network change
• Sessions: number of user sessions on the device
• Last User: last user connected to the device in domain\account format
• Connected from: when the selected device is a VDI or similar, it shows the name of the device from which the virtual device is accessed.
• 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.
• Description: allows the user to identify the device with a personal description. This field must be assigned manually and individually using the Edit option in the Operations menu of the device details.

Extended Info

• RAM: total available RAM capacity
• Cores: number of processor cores
• IP Address: device's IP address on the local network
• OS: type of operating system
• Operating System: operating system version
• Region: obtained using the public IP. It might not be accurate if connected to a corporate network or using a VPN.
• Session Analyzer: indicates whether or not it is configured to launch Session Analyzer in all the user sessions.
• Session Analyzer version: Session Analyzer version number
• Report group: reporting group to which the device belongs

Information in tabs

FlexxAgent groups information about the following aspects of the device:

Sessions

Displays a table with the log of user sessions established on the device and timely information about the session type, connection status, or start date.

Performance

Displays graphs of the device's main performance counters, based on data collected over the last two hours. The following are included:

• CPU: processor usage percentage
• Memory: amount of memory used and available
• Bandwidth Usage: amount of incoming and outgoing traffic

At the top, a link grants access to the Analyzer module.

Job

All actions performed from the Workspaces module on one or more devices are audited in the Jobs queue. This tab allows you to check the work done for the active device.

Alert

Presents a table with the list of all active alerts on the device. When an alert is logged, a notice is displayed at the top of the page.

Connection Log

Presents a list of the connections established with the device, including each instance where a user logs in or reconnects a previously disconnected session.

The session end date is recorded only for sessions that have been disconnected or closed. While the session remains active, this field will remain empty.

Disks

Displays a list of all partitions present on the disks identified in the system, as well as statistics of their capacity and occupancy levels.

Notifications

Allows you to see if the device has any active notification. When there is one, a message is displayed at the top of the page.

Reporting groups history

Allows you to see which reporting groups the device belongs to, the date of incorporation, and if it has been assigned to the group manually or automatically.