Automated Client Conflict Resolution
What
There is a capability allowing FileWave itselfcan toautomatically resolve conflicting new desktop clients onwhen yourthey behalf.enroll.
When/Why
Client enrollment conflicts are a natural occurrencecommon in any production environment. environments. Devices aremay be re-imaged and clientimaged, certificates mightmay notno longer match, or devicesa device may simplyreturn have been renamed andwith a name or fingerprint that conflicts with an existing record. The conflict itself is created. The conflicts themselves are not an issue, but they must be resolved so that the systemproblem; knowsit simply means FileWave needs to know how to behave withhandle the "new"incoming devices coming in. Particularly in larger environments, or during periods of intense device imaging, management of the conflicts can be overwhelming. To account for this, there is auto-conflict resolution.device.
Automatic conflict resolution iscan asave time-savertime toduring belarge sure,imaging or enrollment windows, but it also circumventsbypasses part of the securityprotection elementsprovided ofby client-based certificates,certificates. soOnly appropriateenable cautionit should be considered before enabling this feature. Forwhen the mostresolution securebehavior environment,is itunderstood mayand bematches moreyour appropriateenrollment toprocess. In higher-security environments, or when you are unsure which action is safe, use themanual mass-or mass conflict resolution tool instead.
HowPrerequisites
To
How

And, then choose

Makepolicy surefor toconflicting clickclients:
"Save"
Do not enable automatic conflict resolution just to clear a busy New Clients list. During re-imaging or back-to-school enrollment windows it can be useful, but a wrong automatic choice can replace or remove records faster than an administrator can review them.