Fingerprint Enrollment Best Practices

About to be rolling out a series of fingerprint scanners, the client does not want prox cards or PINs to be used. Should we use multiple fingerprints as a backup in case of scarring, swelling, or injury?

Also- Is it best practice to use multiple areas of a fingerprint under different fingerprints? Example, my thumb is larger than the fingerprint enrollment scanner, I can get 2, maybe even 3 "different" prints from using the end near my knuckle, or top half of my thumb near the tip, enroll those two sides under the same user? Or just try to use the main central area of multiple fingers.

Login to read this IPVM discussion.
Why do I need to log in?
IPVM conducts unique testing and research funded by member's payments enabling us to offer the most independent, accurate and in-depth information.

**** ** ** *********** ***** *** ****.

** *******, *** ** ********* ******** ******* **** ******** *****. Arms *** *** ******/****** ******* **** *** ***-******** ***/****/******* **** to ****.

** ***** ** ***** ***** ** * ***** ** **** - **** ****** ************* **** ******** ***** ** ****** ********* point ** *** ***** ***** ********** *** *********** ******* **** the ******. ******-*** ******* *** ****** *** ******** **** ** a ****** ** ******* ** ****** ******** *****, ** ********** the ****** ******** ***** ** ******** *********.

*******, **** ** ********* ** *** ****** ************ *** ****** model. ********* *** **** **** ******* **** ********** *** ****-********** practices, *** ****'* ***** *******.

****, ** ** ****** ********* ** **** *** **** ** get **** ********** ******. ***** *** ***** **** *** ** a ***** ** *** **** ** ***** *****, *** ****** the **** ** ** * **** **********, ****** *** ******** images, *** **-***** ** *********, ********* ******** *****, **** **** for * ****** ***-**** ********** **** ** ***** ** ******* the ***** ** ****.

***, * ******'* **** **** ** ******. * **** ********** is **** ***. ** ***** *** ********** *****

**favorite ******** ** ** ****** ** *******:

- ** **** *** **** **** (***** + **** ******* Index ****** *** ****** ******)

- ** **** *** ***** **** (**** ** *****)

** **** *** **** ***** *********** ** *** *********** ****** internal ****** **** ** ***** *** ********** ***** *** ***** capacity ** ***** **** *** *** *****.

*** *******, ** *****:

- *** ********** *********** ******* (*,*** *********** *******) => *,*** users *** ** *:*

- *** ********** *********** ******* (***,*** *********** *******) => **,*** users *** ** *:*

In **** **** *** *** **** ** ****** **** * ************ (because of HW limitation). In that case, think about the position of the fingerprint reader on the door/turnstile (is it on the left or on the right of the users?)

**** **** *********** ******* **** *** *********** **enroll ****** *******. The duress finger will open the door but it will send an alert to the Security Monitoring Room (in case someone force an employee to open the door). Duress often uses proprietary format (it cannot be sent via wiegand, so you will have to SQL DB sync events), but soon it shall be available via OSDP thanks to SIA efforts (in next OSDP v2.17?)

*** ** ****** * *********** (*****) =>

****://**.**********.***/*********/****.***?**=**:*********************************

********** **** ***** ** ***** *** ********. **** ************ ***** for ********** ** * ******** ****** *** ****** ****** ****/***** in ***** ********. * ***** ******* ******* *********** *** ******* as **** ** ********* ******** *** ****** ******** ****** ******* down **********.

**** ** * **** *** **** ********* **** ******** **** enrollment *** ***** ********* ** *** *** ****.

****://***.***********.***/*********/*******-*********/********/

* ** ***** * ******** ******, *** ***** ** ***** the **** ****** **** *'** **** **** ******** ********** ****** prints **** ********* ***** ** *** ****** - ******* ******* of *** ******** *** **** *** ****** ****** ** ***** someone *** ******* * ****** ** * ******* ** ********* positions/directions. * ********** *********** ****** **** ****** ** * *** different.

*** ***'* ******* *** ******* - *** *****.