Skip to main content

Servers

servers

The Servers view allows access to the list of servers in the environment. When FlexxAgent is installed on a device, it will appear by default in the Workspaces section. To move the device to the Servers view, select the device from the Workspaces section and execute the operation Machine Type-->Server.

More information on how to include a device in this list.

List view​

The list view contains all the servers configured as such in Workspaces and allows the same actions with the listed devices as in the Workspaces view.

Available operations​

From the list view, the following tools are included in the upper right part of the interface:

Filtering options​

This view allows the same filtering functionalities available in Workspaces.

microservicios​

From the >- button, it is possible to execute any of the Microservices enabled for the organization that have System as the configured context. This allows the execution of microservices with administrative permissions on the devices. The actions of enabling, creating, modifying, or deleting microservices are carried out from the Portal.

Operations​

The Operations button allows executing the same device management actions as the Workspaces view.

Detail view​

server

The detailed view of a server, in addition to the operations available at the top of the interface, contains the following sections:

General​

The general information block of the device contains:

  • Name: Device hostname.
  • Status: Power status (on-off).
  • FlexxAgent Version: FlexxClient version number.
  • FlexxAgent Status: FlexxAgent execution status (running - stopped).
  • Date of last FlexxAgent report: Date of the last report received from FlexxAgent on the device.
  • Domain: Domain to which the device belongs.
  • Connection type: Type of connection used by the device (ethernet - wireless).
  • Subnet: Network addressing.
  • MAC address: MAC identifier.
  • Code: Allows setting a string as a code.
  • Network changes: Indicates if the device has recently changed its network configuration.
  • Tags: Allows associating identifying tags.
  • OU: Organizational unit of the domain where the device account resides.

Extended​

The extended information block of the device contains:

  • RAM: Total amount of RAM.
  • Cores: Number of processor cores.
  • IP address: Device IP address.
  • Windows Edition: Edition of the operating system.
  • OS build: Operating system build number.
  • Uptime: The time the workspace has been running since it was last started or restarted. It's important to note that if Fast Startup (fastboot) is enabled, the workspace is only off when it is restarted.
  • Fast Startup: Indicates if the server has fastboot enabled.
  • Last Windows update: Date of the last patch application.
  • Duration of the last boot: Duration of the last start (boot).
  • Pending restart: Determines if the device has a pending restart to apply updates.
  • System Disk: Indicates the used space of the system disk.
  • Public IP and ISP: If public IP data collection is enabled, it shows the public IP and the provider.
  • Region: If it is an Azure virtual machine, it will show the Azure region of the host.
  • BIOS Manufacturer: BIOS manufacturer.
  • BIOS Version: Current BIOS version.
  • SMBIOS Version: Current SMBIOS version.
  • BIOS Serial Number: Unique identifier of the BIOS.
  • Session Analyzer: Indicates the status of the FlexxAgent Analyzer process, which can be:
    • Not configured: FlexxAgent is configured not to launch Session Analyzer.
    • Disabled: FlexxAgent does not initiate Session Analyzer because it has been disabled using the 'AvoidLaunchAnalyzer' registry key.
    • Configured: FlexxAgent is configured to start Session Analyzer in all user sessions.
    • Installed: FlexxAgent will not attempt to start Session Analyzer because Session Analyzer is already installed in the workspace.
    • Not compatible: FlexxAgent does not start Session Analyzer because it is not compatible with the workspace's operating system (e.g., a 32-bit version of Windows).

Tabs​

The tabs at the bottom show grouped specific information; the following tabs are included:

Jobs​

tabjob All actions performed from servers on one or more devices are audited in the job queue. This tab allows you to check the jobs performed for the active device, without the need to go to the jobs section.

Performance​

The performance tab shows graphical information about CPU, Memory, and bandwidth usage.

Alerts​

tabalert This tab displays a list of all active alerts, if any, for the active device. When a device has an active alert, a message is additionally displayed at the top of the screen. header-alert

Event Log​

tabevent This tab presents information about the log events present on the device. By default, it filters the errors and only shows those errors with severity Error or Critical, and it fetches them from the device at 10-minute intervals.

Using the options available in the settings, it is possible to modify the sampling time or include specific events by their ID.

Disks​

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

Boot History​

tabs This tab allows viewing a graph of historical records of the time taken in the booting (boot) of the device.

Security (EDR)​

FlexxAgent will detect if a device has Crowdstrike Falcon installed and display the information in the EDR tab of the device detail view. There you can check the installed version, the correct or incorrect execution status, as well as the CPU and memory resource usage.

EDRtab

If we also want to capture detections to display them in Workspaces, access data must be configured via API to the Crowdstrike Falcon instance in the CrowdStrike section of Level 3->Messaging service (IoT Hub)

Group Policy (GPO)​

tabgpo This tab shows the information of the group policies applied to the active device, allowing visualizing information such as the policy name and verification time.

PnP Devices​

This tab allows viewing at the top the PnP devices that are in an error state. This could be due to hardware or driver malfunction or incorrect configuration of the device or its driver. pnp At the bottom of the tab, all PnP events are recorded. That is, every time a peripheral device is connected or disconnected, a log is generated in this table with the device information.