Prevent Duplicates During Enrollment

A desktop device (FileWave Client) is identified in FileWave by its Client Name and Device Fingerprint. If a device is duplicated in FileWave, enrollment can stop, inventory can be wrong, and deployments may target the wrong record.

Quick answer: If enrollment is blocked by a duplicate client name, duplicate device fingerprint, or client conflict message, resolve the record in the New Client dialog before updating the model.

FileWave will not enroll multiple devices with the same client name or fingerprint. When FileWave detects a conflict, an administrator needs to choose how to handle the new and existing records.

There are three options:

Resolve a duplicate enrollment conflict

Devices in conflict appear in the New Client dialog. To resolve the conflict, select the device and click Solve Conflict in the bottom-left corner.

New Client.png

Mew Client from Server.pngClient Conflict Resolution.png

Choose the option that matches the situation, then run Update Model.

Use "Replace the old client with the new client" when the device should keep the old record's associations and group placement. Use one of the remove options only when the old record is obsolete or the new enrollment should be refused.


Revision #3
Created 2023-06-22 20:45:06 UTC by Josh Levitsky
Updated 2026-06-22 12:52:25 UTC by Josh Levitsky