Skip to main content

Manual Client Conflict Resolution (Multiple Devices)

What

Use manual conflict resolution when several newly enrolled clients need the same conflict decision. Resolving those conflicts together is faster than opening each device one at a time.

When/Why

Client conflicts are common during reimaging or refresh projects. For example, wiping a device and setting it up again with the same name can create a conflict because the new device certificate does not match the existing record. Use bulk resolution only when the selected conflicts should all be handled the same way.

Device enrollment conflicts based on name, fingerprint, certificate, or similar identity data help prevent duplicate records and protect device identity. Test the resolution on one device first, then use bulk resolution only for conflicts you have grouped and reviewed.

How

In FileWave Central, open New Client, then Desktop clients to reach New Client From Server. This workflow is for macOS and Windows computers running the native FileWave Client, not the Apple MDM enrollment queue. See Enrolling Computer Clients into FileWave if the computer has not yet contacted the Server.

To resolve multiple conflicts at once, select the records in the New Clients window, then choose Solve Conflicts:

manual-client-reso1.png

Sort by the status column to group similar conflicts before resolving them.

In the conflict window, click Show Details when you need to inspect why the selected devices are in conflict:

manual-client-reso2.png

In the detail view, you can inspect any particular device:

manual-client-reso3.png

In the resolution window, choose how to resolve the selected devices, then click OK. The example below replaces the existing records with the new clients.

manual-client-reso4.png

Publish and verify the result

After resolving the intended conflicts, review pending work with the other administrators and run Update Model. This commits shared pending changes, not just your conflict decisions. Confirm that the accepted computers appear in Clients with the intended identities and group placement, then check recent Last Connect information. A completed Model Update alone does not prove that the computers have received their work.