Skip to main content
All CollectionsRemote Monitoring & ManagementAsset Management
Managing asset re-registration in SuperOps
Managing asset re-registration in SuperOps

Learn what happens when you re-register an asset in SuperOps

Updated over 10 months ago

Case 1: Agent uninstallation without hard deletion

When an agent is uninstalled from a registered asset on the SuperOps portal without hard deletion, we verify its existence using specific identifiers.

  • For Windows: We cross-check the asset's primary MAC address and store the asset ID in the registry editor. Upon re-registration, the agent collects the asset ID, among other details. If both the MAC address and asset ID match existing records, we associate the asset accordingly.

  • For Mac: We match the asset to the existing asset using its serial number.

  • For Linux: At present, there is no associating logic for Linux assets. For all types of OS assets, we check the hostname and append numeric values if they already exist in our records. Hence, the asset will be considered new.

Case 2: Agent uninstallation with Registry Key removal and no hard deletion.

When an agent is uninstalled without hard deletion and the SuperOps registry key containing the asset ID is removed, further steps are taken.

  • For Windows: As the asset ID isn't sent during registration by the agent installer, we cannot find a matching asset in SuperOps. Consequently, such an asset is considered new, and to prevent duplicate names, numeric values are appended after the hostname.

  • For Mac: We match the asset to the existing one using its serial number.

  • For Linux: At present, there is no associating logic for Linux assets. For all types of OS assets, we check the hostname and append numeric values if they already exist in our records. Hence, the asset will be considered new.

Did this answer your question?