Skip to main content
Version: 24.5

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, from the Workspaces section, you must select the device and execute the operation Machine Type-->Server.

Mas información de como incluir un dispositivo en esta lista.

List view​

The list view contains all servers configured as such in Workspaces and allows the same actions with the listed devices as 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.

microservices​

From the >- button, it is possible to execute any of the Microservices enabled for the organization that have System as a configured context, allowing 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 running status (running - stopped).
  • Last FlexxAgent report date: 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 a string to be set as 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's account resides.

Extended​

The extended information block of the device contains:

  • RAM: total amount of RAM.
  • Cores: number of processor cores.
  • IP Address: IP address of the device.
  • Windows Edition: Edition of the operating system.
  • OS Build: operating system build number.
  • Uptime: time that the workspace has been running since the last time it was started or restarted. It is important to note that if Fastboot is enabled, the workspace is only off when it is restarted.
  • Fastboot: Indicates if the server's fastboot is enabled.
  • Last Windows Update: date of last patch application.
  • Duration of the last boot: Duration of the boot of the last startup.
  • 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 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 consult the jobs performed for the active device, without the need to go to the job section.

Performance​

In the performance tab, graphical information on CPU, Memory, and bandwidth usage is displayed.

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 filtering errors and showing only those errors with Error or Critical severity obtained from the device at 10-minute intervals.

Through the options available in the settings, the sampling time can be modified or specific events can be included through their ID.

Disks​

disks This tab offers a list view with all 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 show 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 on group policies applied to the active device, allowing you to view policy names and check time.

PnP Devices​

This tab allows you to see at the top the PnP devices that are in error state; this may be due to malfunctioning hardware or the driver or incorrect configuration of the device or its driver. pnp In the lower part of the tab, all PnP events are recorded. Every time a peripheral device is connected or disconnected, an entry is created in this table with the device information.