The remFREE agent is part of the remFREE platform.
Customers should not need to manually maintain agent versions across every managed endpoint.
For that reason, remFREE manages approved agent releases centrally.
Why centralized updates?
A management platform depends on its endpoint agent.
Allowing every endpoint to remain on arbitrary software versions creates problems such as:
- inconsistent behavior
- incompatible features
- difficult troubleshooting
- missing fixes
- unnecessary administrative work
Centralized release policy keeps the fleet moving toward supported versions.
Approved releases
remFREE maintains the concept of an approved release for a supported platform.
The platform can compare the version reported by an endpoint with the approved version.
Possible states can include concepts such as:
- current
- update available
- updating
- newer than the approved release
- no approved release
- custom or unrecognized build
Automatic rollout
Where automatic rollout is enabled, remFREE can identify recently connected endpoints that need the approved agent release.
An update job can then be created without requiring the tenant administrator to manually update every machine.
Duplicate protection
The update system should avoid creating repeated active update jobs for the same device.
This prevents a single endpoint from receiving multiple simultaneous requests for the same upgrade.
Why tenants do not select arbitrary agent versions
Agent compatibility is a platform concern.
remFREE controls the release policy so the backend, gateway, and agent can evolve together.
That reduces the risk of a customer intentionally or accidentally pinning the fleet to a version that is no longer compatible with the service.
Platform support can differ
An approved release can exist for one operating system while another platform remains on a different rollout policy.
This allows remFREE to release and validate platform-specific builds independently.
Agent version reporting
The agent reports its version during normal communication.
This allows remFREE to understand fleet state without requiring a separate manual inventory operation solely to discover the installed agent version.
Updates and operational history
Agent updates are administrative operations and should remain observable.
The platform can track the update job and resulting agent version so troubleshooting does not depend on guesswork.
The goal
The desired customer experience is simple:
Install remFREE once.
After that, remFREE should take responsibility for keeping its own supported agent current whenever practical.