Viewing a device's Summary page

To view a device's Summary page:

1. On any page that shows linked device identifiers in the first column of the results grid, such as the All Devices page in the Devices area, click the link for the device that you want to view. Summarized information about the device shows in the page header.

2. Click the Details tab and then click Summary.

The following information shows in the header of the device's Summary page:

• OS Name The name and version of the operating system detected on a device. The operating system is software that manages the software and hardware installed on a computer and allows programs and services to run. It is responsible for the basic operations of a computer system.

• Agent Status The operating condition of a device's Secure Endpoint Agent. Possible values are Active (indicates that the device's agent has connected to the Absolute Monitoring Center), Inactive (indicates one of the following: the device was moved to another account; the device was unenrolled, but it is now set to be reactivated; or the device had Persistence enabled at the factory, but it has not yet called in to the Absolute Monitoring Center), and Disabled (indicates that the agent is either flagged for removal or removed from the unenrolled device). Inactive and Disabled devices do not consume a license.

  If the Agent Status is set to Disabled, all device action options are grayed out.

The following information shows in the Overview section of the page:

• Status: shows only if the device has been reported lost or misplaced, or stolen

  Possible values are Missing and Reported Stolen.

  If the Status is set to Reported Stolen, all device action options are grayed out.

• Identifier The unique Electronic Serial Number (ESN) assigned to the Secure Endpoint Agent that is installed on a device.
• Serial number The identification number assigned to the device by the device manufacturer. For Windows devices, this value may correspond to the serial number of the BIOS, the motherboard, or the chassis, depending on the manufacturer.
• Device name The name assigned to the device in the operating system. For Chromebooks, device name is not applicable and therefore shows as "Chrome" in the Secure Endpoint Console.
• Make The manufacturer of a device.
• Model The manufacturer's designated name for the type of device.
• Core agent version A field and report column showing the version number of the core agent (rpcnet) installed on a Windows or Mac device. For Chromebooks, it shows the version number of the Absolute for Chromebooks extension. You can find the latest version number in the topic "Secure Endpoint Agent release notes" for the current release. (rpcnet)

• Agent version The version number of the Secure Endpoint Agent installed on the device.

  To determine which agent version is the latest, go to the Agent Management page in the Settings area.

  Agent version values
  

  Value	Details
  <version number>	The version number of the Secure Endpoint Agent currently installed on the device Version numbers are in the format x.x for major releases and x.x.x.x for minor releases.
  <version number>	The version number is not the latest Hover over the icon to view the following message in a tooltip: A newer agent version is available, but the device hasn't called in or been upgraded. The device may be offline. The device will call in to the Absolute Monitoring Center after it comes online. If the device is online, one of the following conditions applies: If automatic agent updates are enabled, it may take up to two weeks for the agent version to be updated. If automatic agent updates are disabled, the agent version will be updated when a new agent version is assigned to the device's policy group. No action is required.
  Unknown	The version number is not available or it has never been reported Hover over the icon to view the following messages in a tooltip: Unknown value due to unsupported OS or unlicensed device or other reasons. One of the following conditions apply: The device is unlicensed The device is running an unsupported operating system, such as Linux The agent version failed to be detected No action is required.
  <version number> -or- Unknown	If a version number is shown, it may not be the latest because a recent agent upgrade is delayed or in progress, or it failed If Unknown is shown, the version number is not available or it has never been reported Hover over the icon to view the error messages. If the message Delayed installation and upgrade due to jitter shows, an agent upgrade is pending or in progress on the device. No action is required. When a new agent version is released, Absolute may stagger the agent downloads to minimize the load on your network. In this scenario: The Delayed installation and upgrade due to jitter message is displayed, and Downloads to your devices are randomly delayed and distributed over a specified period (for example, 8 hours), depending on the number of devices in your account. If any of the following error messages show, check the device's network connection, or wait to see if the error is resolved after the device's next scheduled connection to the Absolute Monitoring Center (approximately 15 minutes, if the device is online): Failed to download component Failed to download component policy Failed to download component action Failed to uninstall component Component failed to communicate with the server If the message Component uninstallation requires device reboot shows, ask the device user to restart the device, or wait for the next restart. For all other error messages, record the message and contact Absolute Technical Support.
  No version (Chromebook)	The Secure Endpoint Agent is not supported on Chromebook devices To view the version number of the device's Absolute for Chromebooks extension, see the device's Core agent version field or report column.

• Component manager The component manager (also known as CTES) is installed on top of the core agent and manages the agent components responsible for initiating device actions and collecting device data. Most agent components are controlled by policies, such as the Hardware and Installed Applications policies. The component manager typically connects to the Absolute Monitoring Center every 15 minutes, at a minumum, to send device data and receive instructions.: shows the version number of the component manager (Windows and Mac devices only)

  To map a version number to a release, see Latest agent component versions in the applicable Secure Endpoint Agent release notes.

• Persistence agent A field and report column showing the version number of the Absolute Persistence agent (rpcnetp), which is embedded in the firmware of a Windows device by the device manufacturer. If a device's Secure Endpoint Agent is tampered with or removed, the Persistence agent connects to the Absolute Monitoring Center, which triggers the core agent (rpcnet) to be downloaded and reinstalled on the device. (rpcnetp)

• Firmware Persistence fields (Windows devices only):

  • Firmware Persistence version The version number of the Absolute Persistence module, which is embedded in the firmware of a Windows device by the device manufacturer. The module is responsible for monitoring the health of the Secure Endpoint Agent and restoring it if it's missing, damaged, or tampered with. Possible versions are 1.0 and 2.x.x.x.

  • Firmware Persistence status The status of the Absolute Persistence module, which is embedded in the firmware of a Windows device by the device manufacturer. The module is responsible for monitoring the health of the Secure Endpoint Agent and restoring it if it's missing, damaged, or tampered with. Possible statuses are: Active, Deactivated, Not Supported, Pending, Pending Removal, and Unknown.

    Statuses

    Status	Definition
    Active	The Absolute Persistence module is activated on the device.
    Deactivated	The Absolute Persistence module has been deactivated on the device.
    Not Supported	The Absolute Persistence module is not installed in the firmware/BIOS of the device This status is always shown for Mac, Chromebook, and unsupported Windows devices.
    Pending	The Absolute Persistence module is not yet activated on the device.
    Pending Removal	The Absolute Persistence module is flagged for deactivation, but the process is not yet complete.
    Unknown	Currently unable to detect a valid status of the Absolute Persistence module. If this issue persists, contact Absolute Technical Support.

• Encryption Status: the full-disk encryption status of a Windows or Mac device

  Statuses

  Status	Details
  Encrypted	A full-disk encryption product is detected. The name and version number of the product shows.
  No Data	Encryption status is not yet available (waiting for device to check in to the Absolute Monitoring Center).
  Not Detected	A full-disk encryption product is not detected. Chromebook devices always show this status. Absolute doesn't detect encryption of these devices.
  Not Encrypted	A full-disk encryption product is detected, but the drive is not encrypted. The name of the product shows.
  The following additional statuses apply only to Windows devices:
  Used Space Encrypted	All disk space that contains data is encrypted by BitLocker Drive Encryption, but free space is not encrypted. This status indicates that the Used Disk Space Only encryption option is enabled in BitLocker. For more information about this option, see Microsoft BitLocker Drive Encryption documentation.
  Suspended	BitLocker Drive Encryption is suspended.
  Encryption in Progress	The system drive is in the process of being encrypted by BitLocker Drive Encryption.
  Decryption in Progress	The system drive is in the process of being decrypted by BitLocker Drive Encryption.

• Last BitLocker key change (Windows devices only)

  The date and time the device's BitLocker recovery key was last updated in the Absolute database.

  For this field to be populated, the Collect BitLocker recovery keys option must be enabled in the device's Full Disk Encryption Status policy. Learn more

• Full system name The Fully Qualified Device Name (FQDN) for the device, which consists of two parts: Device Name and Windows domain name. This field applies to Windows devices only.
• Activation date A field and report column that shows the date and time that the device completed its first check-in to the Absolute Monitoring Center and the device's Secure Endpoint Agent was activated.

• Playbooks (Windows devices only)

  Indicates the provisioning status of the device Learn more about running playbooks

  Depending on the Absolute product licenses associated with your account, this field may not be available.

  Statuses
  

  • Enabled: the Playbooks policy is activated on the device, and the device is provisioned to run playbooks.

    A playbook passcode The unique 12-digit passcode that a device user enters during the boot process to run a device-initiated playbook. After a device-initiated Run playbook request is processed on a device, a new passcode is automatically generated in preparation for the next request. is also displayed. For security reasons, the passcode is masked. To show it, click (Show). An Unfreeze code unmasked event is logged to Event History. To hide it again, click (Hide).

    • In some cases, two passcodes may be displayed temporarily. This occurs when the device's existing passcode was used to run a device-initiated playbook and a new one was generated to replace it, but the server has not yet confirmed that the device has received the new passcode. To run a new device-initiated playbook, try the second (newer) passcode first. If it fails, use the first (older) passcode.
    • The passcode can also be used to reset the device if it is in an unusable state after Playbooks provisioning or deprovisioning failed. For more information, contact Absolute Technical Support.

  • Pending: the Playbooks policy is activated, but device provisioning is still in progress. A reboot may be required.

    Hover over the icon to open a tooltip showing the following reason for the delay: Waiting for reboot.

  • Not enabled: one of the following applies:
    • The Playbooks policy is not activated
    • The policy is activated, but the device failed to be provisioned to run playbooks. Hover over the icon to open a tooltip showing the reason that provisioning failed.

  • Deprovisioning: the device's Playbooks policy has been deactivated and device deprovisioning is in progress. A reboot may be required.

    Hover over the icon to open a tooltip showing the following reason for the delay: Waiting for reboot.

  • Not supported: the device does not meet the system requirements for the Playbooks feature

    Hover over the icon to open a tooltip showing the system requirements that are not met.

  Learn more about:

  • Playbook system requirements

  • Troubleshooting unsupported devices

  • Troubleshooting devices that fail to be provisioned

• ThinkShield TraceLock (Windows devices only)

  Indicates whether the device is successfully registered in Lenovo ThinkShield TraceLock, powered by Absolute Security

  Hover over the icon to open a tooltip showing details about the status.

  Depending on the Absolute product licenses associated with your account, this field may not be available.

  Statuses

  • Not supported: the device does not meet the system requirements for ThinkShield TraceLock

  • Enabled: the device is registered in ThinkShield TraceLock and the device is ready to run Firmware Wipe requests

  • Pending: the device supports ThinkShield TraceLock and registration is in progress

    Wait for registration to complete (status updated to Enabled) before attempting to submit a Firmware Wipe request.

  • Not enabled: the device supports ThinkShield TraceLock but registration has not started, or it failed
  Status details
  

  • If any of the following three values show, the device does not meet the system requirements for ThinkShield TraceLock:

    • Platform not supported

      The device's make and model are not supported. Supported models

    • No cellular module

    • Missing associated device license

  • If the following value shows, registration is in progress:

    • Pending registration with communications platform

    Wait for registration to complete (status updated to Enabled) before attempting to submit a Firmware Wipe request.

  • If the following value shows, reboot the device and wait (up to 24.5 hours) for the next Core agent connection to the Absolute Monitoring Center:

    • Invalid IMEI

    If the issue is not resolved, contact Absolute Technical Support.

  • If any of the following values show, registration was not successful. For assistance, contact Absolute Technical Support:

    • Cannot complete registration on communications platform

    • Cannot complete deregistration with communications platform

    • Cannot determine TraceLock readiness

More detailed information about the device is presented in the following expandable sections:

For details about the specific device information collected for each supported operating system, see Data points collected by activated policies.