remFREE Support
Support / Devices & Agents / Deleting, Rebuilding, and Re-enrolling Devices

Deleting, Rebuilding, and Re-enrolling Devices

When an existing endpoint should keep its identity, when a new enrollment is appropriate, and how to avoid duplicate devices.

Guide Agent Security Enrollment Troubleshooting Devices

Most managed endpoints should keep the same remFREE device identity throughout their normal lifecycle.

Re-enrollment is not intended to be routine maintenance.

Temporary connectivity problems

Do not re-enroll a device merely because it temporarily appears offline.

First investigate:

  • agent service status
  • network connectivity
  • DNS
  • WebSocket communication
  • firewall or proxy policy

If the existing agent identity is healthy, restoring communication is preferable to creating another device record.

When re-enrollment may make sense

Re-enrollment can be appropriate when:

  • the operating system was rebuilt
  • the existing remFREE device record was intentionally deleted
  • agent identity was lost
  • the device is moving to another tenant
  • the endpoint is being treated as a new managed system

Rebuilding an operating system

A major operating-system rebuild may effectively create a new endpoint identity from the management platform's perspective.

Before re-enrolling, determine whether historical information from the previous device record should be retained.

Deleting historical records merely to make the device list look tidy can remove useful operational evidence.

Duplicate devices

Repeated enrollment can create duplicate records representing the same physical machine.

Before enrolling again, determine whether an existing record already represents the endpoint.

Duplicate devices can make:

  • inventory confusing
  • compliance reporting misleading
  • job history harder to follow
  • online state ambiguous

Deleting a device

Deleting a managed device is an administrative action.

Before deletion, consider whether the record contains information that may still be useful, including:

  • job history
  • inventory
  • compliance evidence
  • activity
  • administrative history

Deletion and cleanup policies should reflect the organization's operational and retention requirements.

Moving between organizations

A device should belong to the intended remFREE tenant.

Moving an endpoint between organizations should be treated as a trust-boundary change rather than merely changing a display label.

The new tenant relationship should be established intentionally.

Device identity matters

A device record represents more than a hostname.

Hostnames can be reused.

Machines can be renamed.

An endpoint identity exists so remFREE can maintain continuity between:

  • communication
  • inventory
  • jobs
  • compliance
  • remote support
  • administrative history

Preserving that continuity makes the platform more trustworthy.

Recommended approach

If the device is merely offline, troubleshoot it.

If the agent installation is damaged, repair it where practical.

If the endpoint was fundamentally rebuilt or intentionally removed, re-enrollment may be appropriate.

Avoid using re-enrollment as a generic fix for problems that are actually connectivity or service issues.