Implement client hostname changes from the backend

Products Endpoint Protector Ideas
,
1

What is a one sentence summary of your feature request?

Implement client system hostname changes from the backend

Please describe your idea in detail. What is your problem, why do you feel this idea is the best solution, etc.

However, to avoid duplicate device entries in the future, we would like to check if there is a possibility to implement hostname changes from the backend (for example, via Azure/Intune or any other centralized platform)features update, instead of performing them locally on the device. This may help maintain consistency and prevent re-registration of devices.

How do you currently solve the challenges you have by not having this feature?

This is expected behavior with the current implementation. When the macOS hostname/computer name changes, the EPP client may register the device again, which can result in duplicate entries.
Since this is considered expected behavior with the current implementation, there is no fix planned at this point.
The available workaround is to change the Mac name directly from System Settings, not from Terminal or Intune, then restart the EppClient process from Activity Monitor.
Please let me know if there is any other information that we can provide.

2

Hi,

Thank you for the detailed description and for providing context around your setup.

We’ve reviewed this request internally and want to be transparent about why this is not something we’re planning to address in the foreseeable future.

EPP identifies each device through a certificate-based model — device identity is tied to the client certificate rather than the hostname alone. When a hostname change is made through certain methods such as Terminal or Intune, it causes the EPP client to generate new credentials that the server doesn’t recognize as belonging to the existing device, which is why re-registration occurs. Resolving this properly would require changing the fundamental way device identity and authentication works across both the client and the server — it’s not an isolated fix.

The recommended workaround remains changing the Mac name directly from System Settings rather than via Terminal or Intune, followed by restarting the EPP client process from Activity Monitor, as this avoids triggering the credential regeneration.

We appreciate you raising this and we’re sorry we don’t have a more positive update to share.