MorphoManager 15.4.3 - User Manual
MorphoManager 15.4.3 - User Manual
Contents
Introduction ......................................................................................................................................5
Support .............................................................................................................................................5
Overview ...........................................................................................................................................6
What is a client? .......................................................................................................................................... 6
What is a server? ......................................................................................................................................... 6
What is a fingerprint enrollment device? .................................................................................................... 6
What is a Biometric Device? ........................................................................................................................ 7
Setting up MorphoManager .............................................................................................................7
Computer hardware requirements ............................................................................................................. 7
Supported Operating Systems ..................................................................................................................... 7
Supported USB Enrollment Devices ............................................................................................................ 7
Supported Biometric devices ...................................................................................................................... 8
Supported Card Reader / Encoders ........................................................................................................... 10
Biometric Device Capacity ......................................................................................................................... 11
Biometric Device supported firmware ...................................................................................................... 11
Installation of MorphoManager software ......................................................................................12
Updating to MorphoManager 15.x ........................................................................................................... 12
Setting up MorphoManager on a single PC ............................................................................................... 13
Server and Client Installation .................................................................................................................... 14
MorphoManager Client Configuration ...................................................................................................... 15
Basic........................................................................................................................................................................ 15
Advanced ................................................................................................................................................................ 16
Login Options .......................................................................................................................................................... 18
MorphoManager Server Manager ............................................................................................................ 19
Home ...................................................................................................................................................................... 19
Database Configuration .......................................................................................................................................... 19
Advanced Configuration ......................................................................................................................................... 20
Running MorphoManager...............................................................................................................23
Product Activation ..................................................................................................................................... 23
Procedure for License request ................................................................................................................................ 23
Procedure for License activation ............................................................................................................................ 25
Login .......................................................................................................................................................... 26
Express Configuration .....................................................................................................................27
Device discovery ........................................................................................................................................ 27
Authentication modes ............................................................................................................................... 28
Card selection ............................................................................................................................................ 29
Home Screen ...................................................................................................................................31
Administration ................................................................................................................................32
Operator .................................................................................................................................................... 32
Creating a new Operator ........................................................................................................................................ 32
Key Policy .................................................................................................................................................. 35
Creating a new Key Policy ....................................................................................................................................... 35
Lock & Unlock ......................................................................................................................................................... 43
Biometric Device Configuration ................................................................................................................ 44
Creating a new Biometric Device Configuration (Express) ...................................................................................... 44
Creating a new Biometric Device Configuration (Advanced) .................................................................................. 60
Creating a new Biometric Device Configuration (External) ..................................................................................... 65
Biometric Device ....................................................................................................................................... 66
Create a Biometric Device....................................................................................................................................... 66
Modify a Biometric Device ...................................................................................................................................... 68
Delete a Biometric Device ....................................................................................................................................... 68
Biometric Device Status and Tasks.......................................................................................................................... 68
Troubleshooting and Maintenance ......................................................................................................................... 69
Toolbar Functions ................................................................................................................................................... 69
Refresh.................................................................................................................................................................... 69
Synchronize ............................................................................................................................................................ 69
Get Logs .................................................................................................................................................................. 69
View Sync Log ......................................................................................................................................................... 70
Introduction
MorphoManager is the latest generation of biometrically powered Access Control and Time &
Attendance capture software. The software works with Biometric Device hardware to capture users’
fingerprints, photos, and personal details. The fingerprint information is sent to specified Biometric
Devices where access control is required and where users clock on and off throughout the day.
MorphoManager also works with Morpho 3D Face Readers to capture user’s facial traits.
Support
Please contact your installer for additional support.
Overview
A MorphoManager system consists of four components:
• A MorphoManager Server
• At least one MorphoManager Client
• A fingerprint/finger vein/hand/3D Face enrollment device.
• At least one Biometric Device.
What is a client?
A client is a computer that has the MorphoManager Client software installed. There can be more than
one client in a MorphoManager system.
The client application provides the management of access points, enrolling of personnel, and reporting.
A PC that has the enrollment scanner connected and is used as the user registration PC. A client PC may
be used to view data and not have an enrollment device connected.
What is a server?
A server is a computer that has the MorphoManager Server software installed.
The server manages the communication between the Biometric Device and the PC and interacts with
the database. It also handles requests from clients.
The readers are connected to a computer that is running MorphoManager Client software. All
enrollment of personnel is performed using MorphoManager software. Device drivers for this hardware
are automatically installed when MorphoManager Client software is installed.
Setting up MorphoManager
This section outlines the requirements for MorphoManager systems.
MorphoManager Client:
• Microsoft Windows 10 32-bit / 64-bit (Anniversary update or later)
• Windows Server 2008 R2 SP1 64-bit - KB4019990 update installed
• Windows Server 2012 64-bit- KB4019990 update installed
• Windows Server 2012 R2 64-bit - KB2919355 update installed
Database server:
SQL Server 2014 SP3 or newer
2K/2
1K 4-byte NUID
16K/2 2K 2K
1K 7-byte UID
Card Variant Prox 16K/16 Seos® 4K 4K
4K 4-byte NUID
32K (16K/2+16K/1) 8K 8K
4K 7-byte UID
32K (16K/16+16K/1)
2K/2
1K 4-byte NUID
16K/2 2K 2K
1K 7-byte UID
Card Variant Prox 16K/16 Seos® 4K 4K
4K 4-byte NUID
32K (16K/2+16K/1) 8K 8K
4K 7-byte UID
32K (16K/16+16K/1)
Read CSN/ID ✔ ✔ ✔ ✔ ✔ ✔
If an attempt is made to add more devices from a family than MorphoManager Supports, that device
will not be added to the system.
Devices with a firmware version lower than the supported version will remain offline. The
status of these devices will change to Online only once the devices are updated to the
minimum firmware version or higher
It is not possible to update to MorphoManager 15.x from any other version than 14.6.x
If you are an existing customer, it is advised to run Compatibility Check Utility before upgrading your
copy of MorphoManager.
For added security, many businesses and departments have chosen to dedicate a PC for
MorphoManager and often use a dedicated hub to which only the MorphoManager PC’s and Biometric
Devices connect.
Alternatively, an existing hub can be used, but it is recommended that the IP range of the
MorphoManager PC and Biometric Devices are different from the corporate PC’s.
The MorphoManager server application can be installed on a separate PC which may or may not be a
dedicated server.
Basic
Hostname: By default, it will be localhost. Use this setting when the client and
server are installed on the same PC.
Port: Specifies the server port that the MorphoManager Server is accepting
client connections on. The default port is: 42100. The port must be
the same as the remoting port specified on the server configuration.
The port values should only be changed if the default ports are being
used by another application.
Advanced
Client protocol settings: This is the protocol the client will use to connect to the
MorphoManager Server. This value should be SOAP 1.2 Binary, unless
instructed to change this by customer support.
TLS Mode –
Transport: The communication between server and client will be encrypted. This
mode does not validate the authenticity of the MorphoManager
Server.
TLS Mode –
Transport and
Mutual Authentication: The communication between server and client will be encrypted. This
mode will also validate the authenticity of the MorphoManager
Server.
Client Certificate thumbprint: Used to specify the thumbprint of the client certificate. This
thumbprint will then be used to find, validate, and return the
certificate from the certificate store. MorphoManager will use this
certificate to encrypt communications between client and server.
Server certificate
Authentication mode: If Disabled is selected, MorphoManager will perform no further
validation on the certificate.
Login Options
Automatic Login: When enabled, the MorphoManager Client will use the username and
password entered here to login automatically. This can be a security
problem and should be used on clients that are secured by other
means or have only one user. It is primarily used for convenience, so
the user does not have to enter their username and password if it is
unnecessary.
Operator override: The operator will be able to change the advanced settings before
logging in.
The MorphoManager Server Manager can be found by clicking on the start menu, then selecting
“MorphoManager” and “MorphoManager Server Manager”.
Home
The server control is used to start and stop the MorphoManager server. Stopping the server should only
be performed if instructed by the support staff. To start or stop the server, click the Power icon.
Database Configuration
Database Connection
Database Type: There are two database provider types:
SQL server Compact Edition 4.0 is not supported by IDEMIA and shall
be reserved to Demonstration purposes. It is recommended to use
SQL Server for any live production environment.
Database Connection String: This is the connection string that will be used to connect to the
database. Enter the connection string and click Test Configuration.
Ensure the connection is successful before saving changes.
Database Schema Management
Delete Database Schema: Deleting a database schema will remove all tables and all data from
the database. This is a non-recoverable operation and cannot be
undone. A drop database schema cannot be reverted. A prompt will
be displayed confirming this action.
Create Database Schema: Creating a database schema can only be performed on a new, empty
database. This operation will set up a database and create all the
tables and default data for MorphoManager.
Validate Database Schema: Validating a database schema will reveal if there are any errors or
issues in the current database schema.
Advanced Configuration
Basic
Listening Port: This is the port that the client will communicate with the server on. It
must be the same as the one specified in the client configuration.
TLS Mode –
Transport: The communication between server and client will be encrypted. This
mode does not validate the authenticity of the MorphoManager
Server.
TLS Mode –
Transport and
Mutual Authentication: The communication between server and client will be encrypted. This
mode will also validate the authenticity of the MorphoManager
Server.
Server Certificate
Discovery Mode: Search and create self-signed certificate if discovery fails will first
search the Windows certificate store to determine if the server
certificate already exists. The certificate is searched by Hostname as
the Common Name. If no certificate is found by the hostname,
MorphoManager Server will create a new self-signed server
certificate.
Hostname Mode: Automatically detected can detect the hostname of the server and
will use this detected hostname to search and/or create the server
certificate
Server Certificate Thumbprint: Used to specify the thumbprint of the server certificate. This
thumbprint will then be used to find, validate, and return the
certificate from the certificate store. MorphoManager will use this
certificate to encrypt communications between client and server.
Client Certificate
Authentication Mode: When Client Server Certificate Common Issuer is selected, the server
certificate and client certificate must have the same issuer.
Running MorphoManager
Product Activation
The Trial Period is not available anymore.
MorphoManager Client Software requires the MorphoManager Server software to be activated before
starting.
The MorphoManager Product Activation process will be automatically shown at the first launch of
MorhoManager Client.
2. Copy license ID
Please note, in case you back-up and restore your Machine, a new Activation Key is
required.
Once your License file is available on your computer (or on any portable device connected to your
computer), then you can click on Browse to add this file in MorphoManager. When validated, the path
of the selected file will be displayed on your page, this will allow you to check it before finishing the
activation.
When the process is complete the following screen will appear. Your copy of MorphoManager is now
activated. After clicking OK you will be taken to the MorphoManager Login Screen.
Login
MorphoManager Client software requires a username and password to be entered before starting.
Once you have entered the correct username & password, click Login to login.
Express Configuration
Express Configuration will allow MorphoManager to be configured based on a series of wizard screens
and prompts. For example, will the system be using biometric only, or will contactless cards be involved?
Once Express Configuration is created, MorphoManager will have a corresponding User Authentication
Mode, User Configuration, and Biometric Device Configuration set as a default in MorphoManager.
Therefore, when a Biometric Device is added to the system, the default Biometric Device Configuration
for that terminal will be set to the one created by the first Express Configuration. The same will happen
when creating a user and their default User Configuration. The system defaults for these items can be
managed in System Configuration> System Functionality. Further details can be found in the System
Configuration portion of the manual.
At the initial login to MorphoManager the Express Configuration creation wizard will launch
automatically.
Follow the wizard prompts and answer the questions based on how the site installation will function.
Device discovery
The second screen of the Express Configuration Wizard will detect devices. MorphoManager uses User
Datagram Protocol (UDP) to discover devices.
If you have multiple network adapters, you will need to disable all but one that is used for network
communications before starting the device discovery.
All detected devices will be displayed in the grid. Devices that did not respond within the timeout, will
not be displayed.
In this grid you can alter the Name and Description to suit your needs.
Mark all the devices you would like to add to MorphoManager by marking the checkbox in the Add
column.
Devices that are already in MorphoManager will be marked in gray with a checkmark in the “Already in
System” column.
Authentication modes
The following authentication modes are supported for Express Configuration:
1. Biometric Only
A user is authenticated by biometrics only. E.g. the user places the enrolled fingerprint on the
biometric device, and they are granted access.
2. Card Only
A user is authenticated by a card only. E.g. the user presents their card to the device and they
are granted access. No Biometrics required.
3. Card and Biometric
A user is authenticated by a card and a biometric. Each user requires a card and a biometric. E.g.
the user presents their card to the device, the device prompts them for their fingerprint, after
the fingerprint is placed, the user is granted access.
4. Card or Biometric
A user is authenticated by a card or a biometric. A user requires only a Biometric, or only a card.
E.g. user A places their enrolled fingerprint on the biometric device to gain access. User A is not
furnished with a card.
User B presents their card to the device to gain access. User B does not have any fingerprints
enrolled.
It is also possible to furnish user A with a card, and User A will be able to gain access with a card
only or with fingerprints only.
5. Card and PIN
A user is authenticated by a card plus a PIN. E.g. the user presents their card to the MA device,
they are prompted to enter a PIN. Access is granted if the PIN matches.
6. Card and Biometric and PIN
A user is authenticated by a card, a biometric and a PIN. They are required to have all three. E.g.
the user presents their card to the MA device, they are prompted to present their fingerprint,
they are prompted to enter their PIN. Only if all three matches will access be granted.
7. Wiegand in and Biometric
This mode is used in conjunction with another device that is connected to the MA device’s
wiegand input connecters. E.g. the User presents their card to a separate card reader. This card
reader is connected via wiegand to the MA. After the card was presented, the user is prompted
to place their fingerprint on the MA device. Access is granted if the fingerprint is verified.
For each of the Authentication modes that include a biometric, the administrator can configure whether
Contact templates, Contactless templates, or Face templates are required. For the Card Only and Card+
PIN authentication modes, Biometrics are not configurable and will never be required.
Card selection
On the card selection page, you can decide to manually select the cards you will use, or to automatically
detect the cards that you have.
A supported USB Card reader must be attached to the Client if you wish to use the Automatic Card
detection Mode:
After the Express Configuration wizard is completed, the following items will be created in
MorphoManager:
These items will be given the same name as the Express Configuration they were created from. For
further details on those items please see the corresponding section(s) of this manual.
The Express Configuration Wizard can also be launched at any time after the initial login to
MorphoManager from an icon on the Home Tab.
Home Screen
At the top of the home screen, there is a set of tabs:
Home
Administration
User Management
Biometric Identification
Access Logs
Reports
And a set of buttons on the home screen. Select an item to enter that section.
At the bottom of the home screen is a link to MorphoManager updates. If you have access to the
internet, you will be directed to this area which will be updated with news and information regarding
MorphoManager patches and important messages.
The right-hand side of the screen displays the system status and system information. “System status”
contains a count of the total number of Biometric Devices and their status. It also contains a count of
the total number of users within the system and the total number of access logs. System Information
contains the installed version number, and your server serial code.
Administration
The administration section is used to configure and setup MorphoManager. Error and event logs are
also viewable in this section.
When creating or editing an item, a colored text entry box means the information is
required and must be filled in before the item can be finished and saved.
Operator
An operator is a person who uses the MorphoManager Client software. Operators are the only people
who can login to the MorphoManager application. The Administrator operator has full access to all
functions. Other operators with limited rights can be created.
The System Administrator operator cannot be deleted or modified. This operator has
access to every part of MorphoManager and so keeping the password for this user secure
is essential.
First / Middle / Last Name: The first, middle and last name of the operator being added
(First and Last names are mandatory fields).
Key Policy
This section allows the setting of Contactless Card keys and whether they are stored in an encrypted or
unencrypted format.
Require password: Select this option to secure the Key Policy with a password. The gets set
on the next page. Securing the Key Policy with a password adds an extra
layer of security to MorphoManager. An operator will need to enter the
password to view the card keys. This password is not required during
card encoding.
Contact Fingerprints:
Start write sector: Sets the card write sector from where the encoding/reading should start
for contact fingerprints.
Start write block: Sets the block within the sector where the encoding/reading should
start contact fingerprints.
Absolute block number: This value correlates directly to the sc_tlv_mifare.start_block parameter
for 5G devices. It is the overall block number of the card layout.
Contactless Fingerprints:
Start write sector: Sets the card write sector from where the encoding/reading should start
contactless fingerprints.
Start write block: Sets the block within the sector where the encoding/reading should
start contactless fingerprints.
Absolute block number: This value correlates directly to the sc_tlv_mifare.start_block parameter
for 5G devices. It is the overall block number of the card layout.
DESFire FID: The File ID that should be used to read and write to the DESFire card.
Set DESFire AID: This button leads to the page where Application ID can be set. The DesFire AID
may be entered in ASCII or in HEX by choosing the relevant radio button.
Start reading from book setting applies only to 32K cards. When using 32K cards, the block and page
settings will be considered for Book 0.
Unchecking the “Use HID iClass factory Keys” checkbox, will open further settings where custom iClass
keys may be set.
This page is used to set the Transport keys for iClass Seos cards. When the operator uses default keys,
the details will be hidden.
When using the default keys, it is necessary to load the default transport keys into the 5G terminal with
a configuration card.
The operator may set the Omnikey reader keys on this screen. These settings only apply to the Omnikey
5427. An Omnikey 5x21 will not be affected by these settings.
Omnikey 5021 & 5022 is not supported anymore and will be removed in a future release.
You can allow smart cards (MiFare/iClass) that have been encoded with Secure Admin or Secure Admin
Lite to be read by the MA Sigma family of devices. You can enter the site keys manually, if they are
known, or you can import the site key file that was generated in Secure Admin or Secure Admin Lite.
“Allow Secure Admin Cards” needs to be turned on/off in the Biometric Device
Configuration.
The device parameters on this screen will be overwritten when you use and Advanced Biometric Device
Configuration.
When importing a site key file, you will need to specify a “code” to unlock the site key file. Generally
Secure Admin uses the MAC address of the PC to lock this file. You can either select your MAC address
from the dropdown list or enter the 12-character key that was used during the creation of the file. These
12 characters need to match the code used during the file creation.
Add a Certificate:
After clicking Add on the main Certification Management screen, the screen above will appear. Click
Browse and find the Certification File to be utilized. Next, choose the Certificate Type (either PC or MA)
to be utilized. Lastly, enter the mandatory Certificate Password. Click Next to return to the management
page.
Only ONE PC certificate can be stored on the Key Policy. Any number of MA certificates can be
stored on the Key Policy.
If the status is Unlocked, the Lock operation will be enabled. This will prompt for the user defined key,
which once given will be sent to the Server to lock the Key Policy. The user defined key will be qualified
to ensure it is a valid key. If it is, it will clear unencrypted data from the Server. The Key Policy cannot be
read again until the Key Policy is unlocked.
Configuration Mode: Can be either Express, Advanced, or External, but in this example,
Express is selected.
Log Retrieval Enabled: When this option is selected downloading logs from individual biometric
devices is supported. This is the default functionality. If not selected,
retrieving logs from devices is disabled which allows for third party
products to retrieve device logs rather than MorphoManager. Realtime
logging is not affected.
Log Retrieval Interval: Each Biometric Device is periodically polled to collect any new data and
remove stored data from memory. This is the amount of time between
each polling sequence. The default is 300 seconds.
Duplicate Check
on Biometrics: When turned on, users will be checked for duplicates as they are added
to devices. The device can only check new users added. This check is
performed by the device and NOT MorphoManager.
This feature severely impacts the performance of the “Add User” task. It
should only be enabled when absolutely necessary.
When enabling duplicate checking on the device, it is necessary to
reduce the MA5G User batch Size to no greater than 100.
Morpho Access
Heartbeat Interval: The interval to ping MorphoAccess terminals. If the terminal does not
respond to the ping, the device status will be updated to Offline.
Key Policy: Select the Key Policy to be utilized on the Biometric Device.
General Settings:
If you are utilizing the Wiegand output on the Biometric Devices, you will need to set the
Wiegand Profile for the Biometric Device(s) here. The Wiegand Profile you choose for
your devices should match the one being utilized for your users which is set in the User
Configuration section of this manual.
Language: Choose the language you wish to use on your Biometric Device display
screen.
Realtime Logging Enabled: Enable this check box to have access logs sent from the biometric device
to MorphoManager in real time. Logs are sent instantly for every finger
presentation. By default, this setting will be disabled. It can be enabled
only after configuring the settings in System Configuration.
*The port used as the server listening port will need to be opened in your
firewall settings.
Biometric Threshold: The default is Recommended. However, it can be set to Low, High, Very
High, and Custom. Choosing the Custom setting will allow you to set
individual threshold properties for the four device types greyed out in the
screenshot above. For further detail on the Vein/ Print mode options
please see the User Configuration – Screen 2 section of the manual.
It is recommended the threshold mode set in User Configuration for enrollment should
be the same threshold mode or a more restrictive mode than the mode set in Biometric
Device Policy. Using a less restrictive mode in User Configuration than in Biometric
Device Configuration is likely to increase the False Rejection Rate (FRR) of biometric
devices.
This area dictates the matching mode used by the Biometric Devices. This is only enabled when the
Biometric Device type has been detected.
Multi-Factor Mode: There are ten individual options and the ability to do a custom selection
for each hardware family. The options are as follows:
• Biometric Only – Select this option if the Biometric Device is used for
identification by biometrics only. With this option, a person does not
have to provide any input other than the biometric utilized by that
device for identification.
• Wiegand in – This option authenticates Wiegand Input to match
against a biometric template.
• Keypad – This option allows the user to enter a user code or a pin
number via the terminal keypad to match against a biometric
template.
• Proximity Card – This option allows Proximity Cards to be utilized with
a Proximity card capable device. Fingerprints will be stored on the
device instead of card.
• HID iClass – This option allows HID iClass Cards to be utilized with a
HID iClass card capable device.
• Mifare Classic – This option allows Mifare Classic Cards to be utilized
on a Mifare Classic capable device
• Mifare DESFire 3DES – This option allows Mifare DESFire Cards to be
utilized on a Mifare DESFire capable device.
• Mifare DESFire AES– This option allows Mifare DESFire Cards to be
utilized on a Mifare DESFire EV1 capable device.
• Custom – The Custom setting will allow you to set individual
properties for each of the three hardware families (The Morpho 3D
This area sets the properties for Access Control on your Biometric Devices.
Access Control Mode: Controls how the Biometric Device will integrate with an Access Control
Panel
None – All parameters will be disabled related to Access Control
Mode
Integrated by Wiegand / Panel Feedback – Used when the biometric
device will communicate with an access control panel via wiegand
and/or Panel feedback
Integrated by OSDP – Used when the biometric device will
communicate with an access control panel via OSDP
Wiegand Out Enabled: This will determine if your biometric device will output a Wiegand value.
Panel Feedback Mode: Allows you to choose between LEDIN and RS485.
Panel Feedback No
Response Timeout: This value will determine the length of response time allowed from the
Access Control Panel.
Relay Enabled: Each Biometric Device has an on-board relay that can be used to control
an external device on successful presentation of a fingerprint. Use this
option to activate the relay when a user is authenticated.
Relay Duration: If the relay is activated, this value will determine the length of activation
time.
Push to Exit Enabled: This allows the Access Panel to open a door even though the user is not
identified on device.
Push to Exit Duration: This sets the length of time the door will remain open if Push to Exit is
enabled.
Duress Wiegand Mode: This determines whether the use of Wiegand for duress finger is Disabled,
Reversed, or Custom.
Duress Wiegand Profile: If the Duress Wiegand Mode is Custom, this will set the Wiegand Profile to
be used during presentation of a duress finger.
Baud Rate: Allows you to set the baud rate for any RS485 communication.
Function Key Mode: This area determines what function keys, if any, will be available on a
device (where applicable). Options in this drop down are No Keys, Two
Keys, Four Keys, or Nine Keys to be displayed on device. Each key enabled
in the list of keys can be renamed to meet individual needs for events in
Time & Attendance and Access Log records.
Enable MA 500
Multi-database Mode: This will allow you to enable the Multi-database mode on this family of
devices if they have the proper license installed.
Display Name
Encoding Code Page: This section allows you to set encoding for the display name for
downloading to MA2G devices. Your choices will be:
Screen 7 – MA Sigma, Sigma Lite, Sigma Lite +, Sigma Extreme, MA VP MD, & MorphoWave
Settings
Face Detection Mode: Allows you to set the Sigma units to capture a photo when someone is
presenting to the device (this works in conjunction with the Face Logging
Mode). There are four individual options:
Disabled – Use this option if you want to completely turn off Face
Detection photo capture.
None – Will take a 1 photo for the log whether a face is detected or not.
Optional – Takes a series of pictures and choses the best face it detects
out of them for the log. However, if the user is rejected (biometric
mismatch) AND it does not detect a face, no photo will be used.
Mandatory – Takes a picture in all scenarios (rejected or accepted
presentation).
Face Logging Mode: This works in conjunction with Face Detection Mode. Which transactions
require a face capture to occur.
Face logs are saved to the MorphoManager database. It is not recommended to use the
face logging functionality with a SQL CE database due to the file size limitation.
Volume: Set the device volume level to anything from 0-100 for all Sigma family of
devices and the MorphoWave.
Enable idle timeout: Allows the following to be set on the Sigma and MorphoWave devices
(video capacity does not exist for the Lite+ and MA VP MD):
Show Administration Menu: Select to allow the Administration Menu to be accessible on the device. If
not checked the Administration Menu icon will remain on the screen but
access will be disabled. This is selected by default
Show date and time: Select to display the date and time at the bottom of the device LCD
screen. This is selected by default.
The Show Administration Menu & Show Date and Time feature is applicable only on
devices with an LCD display.
Screen 8 – MA Sigma, Sigma Lite, Sigma Lite +, Sigma Extreme, MA VP MD & MorphoWave
Settings (continued)
SecureAdmin Cards: When enabled, you will be able to use smart cards that have been encoded in
Secure Admin or Secure Admin Lite. This setting only pertains to the Sigma
family of devices. You will need to set the Secure Admin Site Keys in the Key
Policy menu.
Enable Finger
Authentication Rule: Enables the ucc.finger_bio_auth.rule Sigma parameter. When enabled, the user
will be prompted to present a fingerprint as verification.
Access Schedules: When enabled, the access schedule functionality will be switched on for MA
Sigma, Sigma Lite, Sigma Lite+ and MorphoWave.
If this system is an upgrade from MorphoManager 9.6.4 or lower, you will need to
manually rebuild all MA Sigma devices after enabling the Access Schedules option.
Screen 9 – MA Sigma, Sigma Lite, Sigma Lite +, Sigma Extreme, MA VP MD & MorphoWave
Settings (continued)
Device Password: When enabled a numeric non-default password can be set for the device(s).
The password can be between four to eight digits long. Once the non-default
password has been set, the default password will need to be manually re-
entered here to reverse the change.
Secure
Communications Mode: Turn this on to use TLS communications between the Biometric Device
and the MorphoManager Server.
When using TLS Communications, the port on the Biometric Device will need to be
changed from the default which does not use TLS. This can be edited in Biometric Device.
Enforce Certificate Validation: When this checkbox is selected the certificate on the device must match
the certificate associated to the Key Policy assigned to this Biometric
Device Configuration. If the certificates do not match, a connection to
the device will not be established
Incoming
Connection Timeout: This will set the amount of time that MorphoManager will wait for devices
to connect to the server when they are in a device-to-server
communications mode.
Screen 10 – Function Key Mode for MA Sigma, MA Sigma Lite+ and MorphoWave Key Mode
Settings
Function Key Mode: This area determines what function keys, if any, will be available on a MA
Sigma, MA Sigma Lite and MA Sigma Lite +, and MorphoWave Key Mode
Settings. Options in this drop down are No Keys, Four Keys, or Sixteen
Keys to be displayed on device. Each key enabled in the list of keys can be
renamed to meet individual needs for events in Time & Attendance and
Access Log records. In Sixteen Keys mode any key name field left blank
will not show as a button on the device screen.
Screen 11 – Biometric Device Database Synchronization
MorphoManager supports automatic & manual Biometric Device database synchronization. This process
allows MorphoManager to periodically poll selected devices to retrieve its user database and compare
against the Server’s database and determine if there are any inconsistencies. If inconsistencies are
detected, these will be logged for operator review, or can be optionally configured to be automatically
resolved without operator interaction.
Synchronization schedule: This schedule applies to the Automatic Synchronization Mode. It used to
determine the days on which the synchronization task should run.
Time of day to Synchronize: This only applies to the Automatic Synchronization Mode. Time of day
when the synchronization task will start.
This wizard screen allows the addition of custom Video, Picture, and Audio files to be used on an MA
Sigma and MA Sigma Lite + Custom Media Files. Applying the Biometric Device Configuration containing
these files to the Biometric Device will place the files onto that device.
The MA Sigma Custom Parameters screen allows the user to specify parameters to be sent directly to
any MA5G device associated to the Biometric Device Configuration. The parameters are not verified
prior to being sent to the device and will override default parameters.
To enter a custom parameter, click the Add button then provide the parameter name and its value and
click Next.
Individual parameters can be edited or deleted by selecting the appropriate button. To remove all
existing parameters, select the Clear All button.
Enrollment Capture Timeout: Time the device will attempt to capture a 3D Face during enrollment
(default 30 seconds).
Authentication
Capture Timeout: The maximum time the device will attempt to authenticate/verify a user
in verification mode.
Preview Image Type: Specifies whether to show the enrollment preview image in color or 3D
face surface mode.
Onscreen Message Timeout: The amount of time that on-screen messages will be shown to the
user.
Click Add to add the Name, IP Address and Port of your Video Phone Server.
The Advanced Profile Screen 2 allows you to configure the various parameters for the Morpho Access
100, 500, J, and VP.
Parameters available for MA2G devices. If you have made changes to the parameters and wish to return
to the original defaults on this screen, you can simply click the Default Values button.
Parameters available for MA Sigma devices. If you have made changes to the parameters and wish to
return to the original defaults on this screen, you can simply click the Default Values button.
Parameters available for MA Sigma Lite devices. If you have made changes to the parameters and wish
to return to the original defaults on this screen, you can simply click the Default Values button.
Parameters available for MA Sigma Lite+ devices. If you have made changes to the parameters and wish
to return to the original defaults on this screen, you can simply click the Default Values button.
Parameters available for MorphoWave Tower. If you have made changes to the parameters and wish to
return to the original defaults on this screen, you can simply click the Default Values button.
Parameters available for MorphoWave Compact / XP. If you have made changes to the parameters and
wish to return to the original defaults on this screen, you can simply click the Default Values button.
Parameters available for MorphoWave SP. If you have made changes to the parameters and wish to
return to the original defaults on this screen, you can simply click the Default Values button.
Parameters available for MA Sigma Extreme. If you have made changes to the parameters and wish to
return to the original defaults on this screen, you can simply click the Default Values button.
Parameters available for MA VP MD. If you have made changes to the parameters and wish to return to
the original defaults on this screen, you can simply click the Default Values button.
Parameters available for MA VP MD. If you have made changes to the parameters and wish to return to
the original defaults on this screen, you can simply click the Default Values button.
Information for the wizard screens 13 – 19 can be found in the section for Creating a new
Biometric Device Configuration (Express).
Selecting External for your Configuration Mode allows you to set all parameters on device or via external
software that interfaces with the Biometric Device parameters. When selecting External mode this will
be the only wizard screen you will utilize.
Biometric Device
Biometric devices from five different hardware families can be added here; the MA 100, MA J, MA 500,
and MA VP family, the MA Sigma, MA Sigma Lite, MA Sigma Lite +, MA Sigma Extreme, MA VP MD, the
Morpho 3D Face, the MorphoWave Tower, MorphoWave Compact / XP, MorphoWave SP and the
VisionPass.
Create a Biometric Device
Select the Biometric Device section of Administration and then click Add in the toolbar.
Export Value: This value is typically used for Access log exporting when the
MorphoManager data needs to be exported to a third-party payroll
package. It can have a maximum of 20 characters.
When the access logs are exported, the value specified here will be used
as the Biometric Device name in the output exported file. This again
depends on the requirements of the payroll package and the access log
exporter that is configured in the System configuration under T&A
General settings.
Time Zone: It is important that this field is entered correctly as it will affect the time
displayed on the Biometric Device and in which time zone access logs are
recorded.
Hostname \ IP address: This value is critical. Enter the IP address of the selected Biometric Device.
The IP Address on each device must be manually assigned and must be within the IP range of the
network. The IP address must not be used by any other device on the network. An IP Address is
not needed for the Morpho Tablet Terminal hardware family.
Biometric Device
Configuration: This will allow a common settings and parameters profile to be set for the
device added. The profile itself is created in the Biometric Device
Configuration section of Administration.
OSDP Serial Address: Enabled if the selected Biometric Device Configuration is set to
communicate via OSDP. This field is applicable only for the MA Sigma,
Sigma Lite, MA Sigma Lite +, MA Sigma Extreme, and MA VP MD family
and MorphoWave Compact / XP, MorphoWave SP and the VisionPass.
Change User
Onsite/Offsite Status: Enable if Onsite/Offsite events are to be recorded.
Onsite Key: Determines which function key on the device will be utilized to set a user
Onsite.
Offsite Key: Determines which function key on the device will be utilized to set a user
Offsite.
After all information has been entered click Finish to save the changes or Cancel to discard the changes.
You will now see the new Biometric Device in the window and its status will be Online, provided the PC
and device are correctly connected and configured. The Tasks column shows the count of the queued or
the failed tasks.
The tasks column indicates the number of tasks remaining for the Biometric Device to process. Clicking
on the Queued Tasks and Failed Tasks tab in the details section allows these tasks to be reviewed.
Clicking on Logs allows review of access logs retrieved from that Biometric Device if this functionality is
enabled.
In the example screen above, the “Delete User” task failed. The message below explains the reason for
the failed task.
Toolbar Functions
Refresh
This does not get the latest status from the devices. The refresh button gets the last known status from
the MorphoManager server and refreshes the view of the MorphoManager Client.
Synchronize
Initiates the Synchronize task if it is enabled in the Biometric Device Configuration.
Get Logs
This functionality is enabled by default and allows currently stored transaction logs from the biometric
device to be downloaded into MorphoManager. Automatic retrieval occurs every 5 minutes, by default.
If this functionality is disabled in the Biometric Device Configuration a warning message is displayed if
Get Logs is clicked.
The Get Logs function will download 100 logs from the biometric terminal every time the task is
executed.
From the Synchronization log, you can choose to add the missing user to the device. Likewise, when an
unknown user exists on the device, the operator can choose to remove that user from the device.
Set Date/Time
Updates the Biometric Device’s clock to the time on the server.
This command is run automatically once a day at the time specified in the system configuration.
Rebuild
The rebuild function will remove all tasks in the queue and create new tasks to configure the device. The
following tasks are created when rebuilding a device:
Get logs – Gets all the access logs from the device, and clears the device access logs after
retrieval
Set date and time – Sets the date and time based on the MorphoManager Server time and
device time zone
Reset media files – Removes all existing media files
Delete existing access schedules – All access schedules on the device are removed
Set configuration – Applies the Biometric Device Configuration to the device
Delete all users – This is an optional task. Removes all users from the device
Add users – This is an optional task. All the users, that are eligible for upload, are sent to the
device.
This function should only be used if the device is not operating as expected. Unexpected behavior could
occur if a device were moved from another site and contained existing users from that site. During
normal operation, any users who are added or deleted through user management are updated on the
Biometric Device in real time.
Set Online
MorphoManager monitors and displays the status of every Biometric Device. If a device has gone offline,
clicking Set Online will attempt to connect to the device and go online. The status of the Biometric
Device will change to “Pending Online” while the connection is occurring. If there is a problem
connecting to the Biometric Device the status will revert to “Offline”.
Wiegand Profiles
This section allows you to view, add, edit & delete Wiegand Profiles in MorphoManager. Wiegand
Profiles define what information is output over the Wiegand Out interface of the Morpho Biometric
Devices when a user is identified. This is most typically used in conjunction with an Access Control
System.
Bit Length: Designate the overall bit length needed for your profile.
Parity: Indicates a single bit that is typically used for error detection. Parity is calculated over
one or more bits within the entire profile and can be Even or Odd.
Fixed: Indicates a value that is common to all users of this Wiegand Profile. Typical examples of
fixed values are Facility/Site codes. This value is set once in the Wiegand Profile and will then be
used by all users of this Wiegand Profile.
User: A value that can be entered during enrollment for each user. A typical example of a User
value is a User ID.
User (Proximity): Like the User value, this value is defined during enrollment, but is read from a
connected proximity card.
User (CSN): Like the User value, this value is defined during enrollment, but is read from an
ISO/IEC 14443 smart card’s serial number.
User (HID iClass/iClass SE PACS Data): Like the User value, this value is defined during
enrollment, but is read from the HID iClass/iClass SE PACS (Physical Access Control System)
information on the card.
User (HID iClass SEOS PACS Data): Like the User value, this value is defined during enrollment,
but is read from the HID iClass/iClass SEOS PACS (Physical Access Control System) information
on the card.
Clock and Data: A unique value that will be used as a user’s identifier. The difference between
the “User” element type and “Clock and Data” element type is the latter will save the value as a
string value. This means that an ID of 01 will be different than 001. Both these values are unique
when using this element type. This wiegand element is only supported for 5G devices.
Once the element has been selected the details screen for that element can be populated as in
the example below. Once the screen is populated click Next.
You will be taken back to the Wiegand Profile element screen (below) and it will now be populated with
the element you just added.
Once you have built out all the elements needed to make up your Wiegand Profile, you can click FINISH.
User Configuration
User polices are used to apply access rights and rules to all members of the group.
Users cannot exist in the database without being assigned to a User Configuration.
However, a User Configuration can exist without having access to any Biometric Device.
This can be useful for segregating users who, for security or other reasons, should not be
stored on a device.
Access Mode: This value determines the access to Biometric Devices that users in this policy will have.
All Biometric Devices and Clients: Users in this policy have access to all Biometric
Devices.
Per User: Users in this policy will have access to the Biometric Device(s) specified in the
User Distribution Groups selected for them in User Management and cannot be
overridden.
Checking the Allow MA 500 database selection during user enrollment allows you to choose the section
of an MA 500 where you want to add your user. The MA 500 must have an extended license for 50k
users. When adding a new user, you will have a drop-down menu of zero to four. This is where you
decide which of the five sections of the database you want to add the user to.
Access Schedule: Any Access schedules that have been created in the Access Schedule menu
(Administration / Access Schedules) will appear in this dropdown menu. Access times
will be restricted/permitted as set up in the Access Schedules menu.
Extended User Details: If enabled, additional user information such as Phone Number(s), Email, and
Address can be entered for a user.
Wiegand Profile: Select the Wiegand Profile you wish to use for users in this User Configuration.
The Wiegand Profile you choose for your users should match the one you utilize for your
biometric access devices set in the Biometric Device Configuration section of this manual.
User Authentication Mode: Designate the authentication mode you wish to utilize for user placed into
this User Configuration.
Show Photo Capture Page: If enabled, the Photo Capture wizard screen will be shown in User
Management when adding or editing users.
Preferred Finger One: Designate the first preferred finger for capture on the Finger
Biometric Enrollment wizard screen of User Management.
Preferred Finger Two: Designate the second preferred finger for capture on the
Finger Biometric Enrollment wizard screen of User
Management.
Preferred Duress Finger: Designate the Duress Finger to be captured on the Finger
Biometric Enrollment wizard screen of User Management.
Duress Finger can only be utilized on the Morpho Sigma, MA Sigma Lite, and MA Sigma
Lite + of readers.
Universal Fast: Universal fast is the recommended vein/print mode. Universal fast provides the
fastest biometric capture and is an excellent trade-off between security, biometric spoofing, and
ease of use. This mode offers the lowest failure to enroll rate. It is likely that users who
experience difficulties enrolling on fingerprint only devices can be successfully enrolled on
vein/print devices configured to this mode.
Universal accurate: Universal accurate is very similar to universal fast profile but with more time
allowed for biometric data capture during enrollment and matching. This mode is
recommended only when the biometrics of a significant number of users are difficult to enroll
due to extreme conditions, such as very cold temperature and/or highly damaged fingerprints.
Anti-spoofing: Anti-spoofing provides a very high level of biometric spoofing detection. Anti-
spoofing is more restrictive than universal fast and universal accurate. This mode is
recommended when detection of a physical live finger is desired. This mode requires that vein
network biometric data must be found under the skin of the finger. This mode is recommended
when a lower False Acceptance Rate (FAR) is more important than a low Failure to Enroll (FTE)
rate.
Full multimodal: Full multi-modal provides the highest level of security during biometric capture
and biometric matching. Full multi-modal is the most restrictive mode. This mode requires that
vein network biometric data must be found under the skin of the finger. This mode is
recommended when the lowest False Acceptance Rate (FAR) is more important than a low
Failure to Enroll (FTE) rate.
It is recommended the mode set in User Configuration for enrollment should be the same
mode or a more restrictive mode then the mode set in Biometric Device Policy. Using a
less restrictive mode in User Configuration than in Biometric Device Configuration is likely
to increase the False Rejection Rate (FRR) of biometric devices
Wave Enrollment Minimum Hands: Designate the minimum number of hands that will be
captured during user enrollment. Options are None, One, or
Two.
Show Wave Biometric Capture Page: If enabled, the Wave Biometric Capture wizard screen will be
shown in User Management when adding or editing users. It
can only be disabled if the Wave Enrollment Minimum Hands
is set to None.
Access Schedules
Access Schedules allow access times to be set for the Biometric Devices. Up to 58 individual Access
Schedules can be created. The Access Schedules are applied to users via the User Configuration section
of MorphoManager. Thus, a user’s access via the Sigma family of devices will be governed by the Access
Schedule set on their User Configuration.
Screen 2 – MA Sigma, Sigma Lite. Sigma Lite+ and MorphoWave access schedules
This section will create Access Schedules pertaining to the MA Sigma, Sigma Lite, Sigma Lite+, Sigma
Extreme, MA VP MD, and MorphoWave devices. They allow for up to two periods of access to be set per
day on the devices. Each period per day can be set up in increments of fifteen minutes.
From this screen set the times needed in fifteen-minute increments. If a day is not set (left blank), no
access will be allowed for users of the Access Schedule on that day.
The Access Schedules setting (page 38) needs to be enabled in the Biometric Device
Configuration menu for Sigma, Sigma Lite, Sigma Lite+, Sigma Extreme, MA VP MD,
and MorphoWave devices. If the setting is disabled, the access schedules will not be
applied to these devices.
times.
From this screen set the times needed in fifteen-minute increments. If a day is not set (left blank), no
access will be allowed for users of the Access Schedule on that day.
Select None or the desired authentication mode from the dropdown menu.
Identifier Template Downloaded to Device: The user is authenticated by presenting their finger at a
Biometric Device and matching with fingerprint data stored on the Biometric Device. Or they can key in
their authentication identifier at the device and then present their finger.
Identifier Template Encoded to Smartcard: The user carries a card with a Wiegand code on it and
touches it on the Biometric Device. If the code read from the card is in the list of accepted Wiegand
codes stored on the Biometric Device the fingerprint scanner is activated. The user is authenticated by
presenting their finger at the Biometric Device and matching with fingerprint data stored on the card.
Identifier PIN Encoded to Smartcard: The user carries a card with a Wiegand code on it and touches it
on the Biometric Device. If the code read from the card is in the list of accepted Wiegand codes stored
on the Biometric Device the keypad is activated. The user is authenticated if the PIN code entered
matches the stored PIN code.
Identifier Template PIN Encoded to Smartcard: The user carries a card with a Wiegand code on it and
touches it on the Biometric Device. If the code read from the card is in the list of accepted Wiegand
codes stored on the Biometric Device the keypad is activated. If the PIN code entered matches the
stored PIN code the fingerprint scanner is activated. The user is authenticated by presenting their finger
at the Biometric Device and matching with fingerprint data stored on the Biometric Device.
Identifier Encoded to Smartcard: The user carries a card with a Wiegand code on it and touches it on
the Biometric Device. The user is authenticated if the code read from the card is in the list of accepted
Wiegand codes stored on the Biometric Device.
Identifier Encoded to Smartcard Identifier Template Downloaded to Device: The user carries a card
with a Wiegand code on it and touches it on the Biometric Device. If the code read from the card is in
the list of accepted Wiegand codes stored on the Biometric Device the fingerprint scanner is activated.
The user is authenticated by presenting their finger at the Biometric Device and matching with
fingerprint data stored on the device.
Identifier from Smartcard Identifier Template Downloaded to Device: The user carries a card with a
Card Serial Number (CSN) Wiegand code on it and touches it on the Biometric Device. If the code read
from the card is in the list of accepted Wiegand codes stored on the Biometric Device the fingerprint
scanner is activated. The user is authenticated by presenting their finger at the Biometric Device and
matching with fingerprint data stored on the device
Identifier Template Download to Device: The user is authenticated by presenting their face at a 3D Face
Reader Biometric Device and matching with 3D Face data stored on the Biometric Device.
Screen 2 – Details for MA Sigma, MA Sigma lite, MA Sigma Lite +, MA Sigma Extreme, MA VP MD,
and MorphoWave Modes for this User
Download Identifier to Device: Will download the users Wiegand Code to the MA Sigma.
Allow: Will allow smartcard coding for a user but will not
prompt during user creation.
Allow and Prompt: Will allow smartcard encoding for a user and
will prompt to encode the card during user creation.
Template Location:
PIN Location:
Allow Start by Biometric: Allow the trigger for authentication to be started by presenting
the user’s finger to the Sigma.
Allow Start by Contactless Card: Allow the trigger for authentication to be started by presenting
the user’s smartcard to the Sigma.
Allow Start by Keyboard: Allow the trigger for authentication to be started by touching the
keyboard screen icon on the Sigma.
Allow Start by Wiegand in: Allow the trigger for authentication to be started by receiving a
Wiegand in signal to the Sigma.
Require Template Match: Makes using correct biometric template for user authentication.
Operator Role
Creating and modifying Operator roles is an advanced feature that should only be used by experienced
operators.
NOTE: This screen allows you to restrict or grant operators the ability to import / export users.
Notifications
Setting up a Notification event will allow specific notifications to be sent when a certain condition is
met. For example, a notification when a biometric device has gone offline.
Delay notifications by: The number of missed heartbeats before triggering the notification. E.g. when
this is set to 10, an offline notification will only be sent after 10 heartbeats
failed. This option is only available for the “Device Offline” trigger type.
Notify when online: Send a notification when terminals in this notification group are back online
Select the Biometric Devices that will be monitored for the trigger type selected on Screen 1. The Filter
option in the toolbar can be used to narrow down the devices which appear on the list.
The Email List screen will allow for configuring what the emails subject line will be and to whom it will be
sent. Email addresses can be Added, Edited, and Deleted. At least one recipient must be present to click
Finish.
Clients
Clients are computers that have the MorphoManager Client software installed and communicate with a
MorphoManager server.
- Any Biometric Device: MorphoManager will select the first terminal detected on your system.
- Selected Biometric Device: You choose now which Biometric Device will be used for all the
enrollment on this Client.
- Biometric Device selected during enrollment: the Biometric Device will be chosen by the
Operator during the process of User Enrollment.
The MorphoAccess device must be accessible from the MorphoManager Client for the
purposes of contact enrollments. The MorphoManager Client will make a connection
directly to the device and will not route the traffic through the MorphoManager Server.
Scheduled Reports
Scheduled reports enable the periodic generation and delivery of reports based on a predefined set of
criteria.
SMTP Settings must be configured in system configuration before a scheduled report can be
created.
Fill in the details for the scheduled report and click Next.
Select the format of the scheduled report. Options are pdf, word document, or excel spread sheet.
Select the type of report that will be generated and enter the details for that report type. The scheduled
report will use those details each time it automatically generates a scheduled report. Some report types
allow for an offset to be entered. This allows reports to be generated for a specific date range relative to
the current date e.g. A report can be set to run every week for the last seven days.
Click Next to go to the next page when the details are correct.
Enter the email subject, body of the email and the recipients.
To add a recipient, type the email address in the text box and click Add Email Address. To edit an
existing email address, select the address to change, type in the new address and click Change Selected
Email Address. To remove a recipient, select the email address and click Remove Selected Email
Address. This information will be used whenever this scheduled report is generated. Click Finish to save
the scheduled report.
To change the details of the selected scheduled report, click on Edit in the toolbar. To remove the
selected scheduled report, click on Delete. To generate the selected scheduled report now instead of
waiting for the predefined generation interval, click on Run Report Now.
Card Template
A card template is used to print ID cards for enrolled personnel.
Screen 1 - Details
Enter a name for the template and select the layout of the card.
Screen 2 - Design
Use this screen to design the layout of the card. A region is an item that can be moved around and will
be replaced by the actual data when the card is printed (e.g. First Name). A background image can also
be added for logos or artwork that is required on the card. To edit a region, click on it or select it from
the list below, and change the options using the toolbar items. The region’s alignment (left, center or
right), font and type can be changed. The size of the region can be changed by dragging the boxes on the
edges of the region. To change a background image region, select the region and click Load Image. To
remove a region, select it and click Delete Region.
Event Logs
Here you will find the history of internal actions performed by MorphoManager. A common error is a
failed attempt by MorphoManager to communicate with the Biometric Device. This situation will occur
if, for example, there is more than one Biometric Device, and all are in error – this may well point to the
network hub being switched off or if power to all Biometric Device has been interrupted.
Exception Logs
Exception logs store messages that are created by MorphoManager in the event of an internal action
not producing the expected results.
The Export Logs and Email Logs to Support icons provide the same functionality as previously outlined in
event logs.
System Configuration
Time and Attendance
These setting are used for manual and automatic access log exporting to a Payroll or Rostering software
package. You need to select the format you want the exported data to comply with. You may choose
from:
Comacc
Preceda
Timeminder
PowerForce
RosterOn
MYOB Enterprise
MorphoManager Standard*
Kronos
Pay Global (Employee ID/Wiegand Usercode)
SOdb
TimeAmerica.
ASTROW
TimeKeeper
MorphoManager Standard with GPS Coordinates**
The MorphoManager Standard format will be exported as a comma-separated file (*.csv) with the
following layout:
Date & Time, Device Export Value, Employee ID, First Name, Last Name, Time & Attendance Key
e.g.
20171229152619,Front Door,0023,John,Doe,IN
For logs to show in the Time & Attendance report, it is necessary to enable the option -
Include in Time & Attendance Exports - in the Biometric Device menu.
Click on the check box for Automatic export access log information and select a destination for the
exported file.
Enter the default file name and destination for the file. The directory MUST exist on the server computer
as the file will be saved to the server’s hard drive.
The file will be exported at the interval specified at Export access log data every.
© Refer to End User License Agreement for Copyright Notice Page 100
MorphoManager User Manual
Communications Engine
MA5G User Batch Size: Sets the batch size of users to be sent to a device.
Number of concurrent tasks per CPU core: Limits the number of concurrent tasks per CPU core to
improve system performance.
System Event Log: Select the types of information to write to the system
event log.
Realtime Access Log Recording Settings*: These settings are to be configured to use the Realtime
Access logs for a Biometric Device.
*The port used as the server listening port will need to
be opened in your firewall settings
© Refer to End User License Agreement for Copyright Notice Page 101
MorphoManager User Manual
System Functionality
Default Tab
This defines the tab selected by default when MorphoManager starts.
© Refer to End User License Agreement for Copyright Notice Page 102
MorphoManager User Manual
User Management
This allows you to control how many users will appear on your User Management screen. If you have
more than the amount in the value filed, you can use filtering to find the additional users.
User Onsite/Offsite
This will be turned off by default. When turned on Biometric Devices that are set to use their
Onsite/Offsite functionality will set the users to either Onsite or Offsite in the Onsite/Offsite section of
MorphoManager. The users Onsite or Offsite status is recorded during the Get Logs task. If this is left
disabled, no recording of Onsite/Offsite change is populated in the Onsite/Offsite section during the Get
Logs.
System Management
Log Management
These settings are in place to prevent any log files from becoming unmanageable due to their size. The
above values are the default values. When the log count reaches these values, the oldest logs are
deleted until they are within the values specified.
Never Delete: This is the system default. Users who are disabled will never be deleted
from MorphoManager.
© Refer to End User License Agreement for Copyright Notice Page 103
MorphoManager User Manual
Delete After: Users will be deleted from MorphoManager after the assigned amount
of day set here when disabled.
Gateways
The Gateway settings are used to receive emails for Scheduled Reports. These settings are specific to the
Mail server. For further assistance, to configure the gateway settings, please refer to your IT support.
Automatic Certificate Binding Mode.
© Refer to End User License Agreement for Copyright Notice Page 104
MorphoManager User Manual
BioBridge
Completely optional, BioBridge allows you to extract user data from compatible third-party systems.
User/grouping Information can be “synced” by the BioBridge Enrollment Client when you set the
configurations for the respective third-party system. You can set “rules” for when data is synced
between both parties.
System
Choose your BioBridge compatible system from the drop-down menu.
Configure connection
Connection credentials for the third-party software.
© Refer to End User License Agreement for Copyright Notice Page 105
MorphoManager User Manual
Wiegand Profile
Most (but not all) BioBridge compatible systems use a specific Wiegand format to identify
users/cardholders. This can be specified on Cards, Card Types or can be specified as a “Wiegand
Format”. Please select the Wiegand format in use from the drop-down menu.
Grouping Mode
This setting determines how MorphoManager should map BioBridge users into MorphoManager User
Distribution Groups. This can be done by either automatically trying to map based on the names
(Automatic), or by manually selecting which BioBridge Access Level maps to which MorphoManager
User Distribution Group.
For vendor specific details, please refer to the separate BioBridge Quick Start Guide
manuals.
© Refer to End User License Agreement for Copyright Notice Page 106
MorphoManager User Manual
Privacy Mode
This mode will allow customers to enroll card-only users (i.e. Card-only, Card + PIN, Card + Fingerprints,
Card + Fingerprints + PIN) without saving their details to the MorphoManager database. This mode will
apply to all User Policies and will only apply to new enrolments. Users who are enrolled in this mode will
not appear in User Management. Additionally, if Privacy Mode is enabled log retrieval will be disabled.
MorphoTablet
Enter the port the tablet will communicate with the MorphoManager Server.
© Refer to End User License Agreement for Copyright Notice Page 107
MorphoManager User Manual
© Refer to End User License Agreement for Copyright Notice Page 108
MorphoManager User Manual
Computer Template Coding Options: Configures the template formats that will be coded when an
enrollment is performed using MorphoKit.
ANSI/ISO template Unlock code: If you wish to use ANSI or ISO templates, you need to contact Morpho
Support to unlock these template types
Device Template Coding Options: configures the (single) template format that will be coded when an
enrollment is performed using MorphoSmart.
Allow juvenile template coding: Used when capturing fingerprints of a young person
Force Device Template coding: This option will override any license present and use the configuration
for “Device Template Coding Options”
Store WSQ image: Stores the WSQ image of the fingerprint. A license is required for this option.
© Refer to End User License Agreement for Copyright Notice Page 109
MorphoManager User Manual
Display Options
Selecting to display user defined fields will show another page in the user wizard that collects the
information as set in these fields. Select the fields to display, if information is mandatory, and assign
names for the fields.
MorphoWave
MorphoWave Unlock
There is an alternative Wave Desktop Enrollment available that may be used in advanced cases. Please
contact Morpho support to unlock Enrollment 2 for MorphoWave Desktop.
User Management
This setting can only be unlocked with an unlock code obtained from Morpho support.
© Refer to End User License Agreement for Copyright Notice Page 110
MorphoManager User Manual
Duplication Control
ID Duplication
To prevent an operator from enrolling duplicate fingerprints when users are added to the system.
During user enrollment a verification will be performed to verify the presented fingerprint is only
enrolled once. This setting only checks for duplicates within a user’s own record during the enrollment
process.
© Refer to End User License Agreement for Copyright Notice Page 111
MorphoManager User Manual
After saving a user enrollment, the fingerprint uniqueness is determined against existing users in the
MorphoManager database. This setting will prevent enrolling a user more than once. This functionality
works in conjunction with the matcher settings.
It is important to note that this check can only occur when the matcher status is “Ready”.
Only new template enrollments will be checked for duplicates. Editing a user, without changing the
templates, will not be checked for duplicates against the database.
A system-wide fingerprint duplicate search will occur based on the schedule defined in this section. This
search collects and stores the results to view in a report. The search can be CPU intensive, therefore the
search should be scheduled during off-peak times.
The system-wide fingerprint duplicate search details can be viewed in the Matcher Settings.
An IDENT and VERIF license, on the MorphoManager server, is required to run the
matcher
This button will launch the system-wide duplicate fingerprint search. The button is only enabled when
the matcher status is “Ready”. This search may take many hours before the results can be viewed in the
Duplicate fingerprint report.
© Refer to End User License Agreement for Copyright Notice Page 112
MorphoManager User Manual
MorphoManager runs a matching engine to determine if fingerprints are unique and to search for
duplicates in the database.
Identification threshold
A higher setting translates to more minutiae points that need to match before a duplicate can be
confirmed. A higher setting may lead to less duplicates being detected and potentially not find
duplicates that do exist
A lower setting translates to less minutiae points that need to match before a duplicate can be
confirmed. A lower setting may lead to more duplicates being detected and potentially falsely flag two
fingerprints as duplicates.
© Refer to End User License Agreement for Copyright Notice Page 113
MorphoManager User Manual
User Management
Users are people who will have their biometric data (or minutia) sent to the selected Biometric Device
for identification purposes for either access control or time and attendance. Select the user
management tab to access this area.
User Details
Information about a user’s Details, Logs, and Biometrics is available when a user is highlighted in the list
of users.
Details:
If a user has been Disabled, their disabled date and the Operator who disabled them will appear on the
Details tab.
© Refer to End User License Agreement for Copyright Notice Page 114
MorphoManager User Manual
Logs:
Biometrics:
The templates captured for the user will be shown. Templates for the user can be Exported and
Imported from this screen.
© Refer to End User License Agreement for Copyright Notice Page 115
MorphoManager User Manual
User Configuration: Select the User Configuration that this user will belong to. This is an
important selection, as the policy will determine Biometric Device
access and other access control and time & attendance settings.
Date of Birth: Enter the date of birth of the user. This can be entered in several
different ways. E.g. 30th May 1975 could be entered in the following
ways 30/5/75, 30-5-75, 30 May 1975, 30 5 1975.
© Refer to End User License Agreement for Copyright Notice Page 116
MorphoManager User Manual
Employee ID: A company specific code that may be assigned to a user. If used for
“Time and Attendance”, this field should match the employee
number from the Payroll or Rostering software.
Biometric Device Display Name: The information displayed upon acceptance by the Biometric Device
and defaults to the First and last name of the user.
© Refer to End User License Agreement for Copyright Notice Page 117
MorphoManager User Manual
This page and the User Defined Fields page to follow are only visible if “Display Extended User
Configuration details” has been enabled on the selected User Configuration. If so, enter the details for
the selected user.
These fields are set in System Configuration>Display Options. Up to ten fields can be named and set as
mandatory.
The User ID can be put in manually or by utilizing the Randomize button. This screen is only available if
you have changed the User Configuration to have a Wiegand Profile set, rather than leaving the default
setting of “Automatically generated random 64 bit”. Additionally, a Read Card Serial Number button will
be present if you utilize one of the Wiegand Profiles referencing Card Serial Numbers.
© Refer to End User License Agreement for Copyright Notice Page 118
MorphoManager User Manual
Position the person in front of a plain background so that all their face is visible in the picture, like a
passport photo. Once the user is positioned correctly click Capture Photo. Click on the image in the top
left corner and drag towards the bottom right drawing a square around the part of the photo to keep.
This can be done many times until the correct area is selected. Click Accept Changes to accept the
changes if no camera is connected just click Next.
If the person is not available to have their photo taken, click Person not at Camera, to skip photo
capture.
© Refer to End User License Agreement for Copyright Notice Page 119
MorphoManager User Manual
If the photo is not acceptable, click Update Photo to recapture the photo. Photos can be imported and
exported using the corresponding buttons. Additional configuration options for the camera can be
changed by clicking on Configure Camera.
PIN Code: Will be utilized and appear on screen when the authentication
mode is set to one including PIN. Ex. Smartcard + PIN.
© Refer to End User License Agreement for Copyright Notice Page 120
MorphoManager User Manual
Screen 9 – 3D Face
The 3D Face reader will scan a user’s face and capture a 3D rendering of the image. To scan a user’s
face, align the face on the device until the device indicates the face has been recognized.
Once the face is recognized the message on the device will change to “Look here and center your
image.” Once the face is centered and the scanning process begins the message on the device will
change to “Face detected Do not move.” A progress bar is shown on the device showing the user being
scanned the status of the scan. Once complete the message “Enroll Success” will be displayed on the
device.
© Refer to End User License Agreement for Copyright Notice Page 121
MorphoManager User Manual
If the face was not able to be scanned the image below will be seen and the face capture process will
need to be performed again. When this occurs, it is most often because the user moved during the
scanning process.
The number of hands required for full enrollment of the user is dictated by that setting in User
Configuration. To start the captures, click on one of the hands.
© Refer to End User License Agreement for Copyright Notice Page 122
MorphoManager User Manual
If either of the following conditions occurs a “No Device” message box will be displayed when you select
a finger to enroll:
If the reader is connected correctly the following screen below will be displayed.
Move your hand through the Wave sensor which should now be illuminated. You will then see the
results of Wave 1 appear on screen. If it is successful, you will then be prompted to present for Wave 2.
© Refer to End User License Agreement for Copyright Notice Page 123
MorphoManager User Manual
If it is not successful, you will see a red X in the elements of Wave 1 that were not successful. Move your
hand through the sensor again until Wave 1 is completed.
Upon successful completion of both Wave 1 and Wave 2, the following screen will appear.
Once the enrollment is complete for Wave 1 and 2, click Next. The screen below will appear showing
captured hand and quality displayed on the right. In the event a user is not being recognized at any
MorphoWave Device, click Clear <enrolled finger> finger enrollment to allow re-enrollment.
© Refer to End User License Agreement for Copyright Notice Page 124
MorphoManager User Manual
The default fingers that the system suggests you enroll are set at the User Group level and are flashing
orange. You do not need to use these fingers as you can click on others. However, you will need to set at
least Finger 1 from the respective drop-down list after fingerprint capture.
If either of the following conditions occurs a “No Device” message box will be displayed when you select
a finger to enroll:
© Refer to End User License Agreement for Copyright Notice Page 125
MorphoManager User Manual
Click on a finger and have the user place their finger in the center of the scanner glass. You will then see
the print appear on screen. There are four scans performed on each finger; the first three are used to
create the biometric template. The system selects the best elements of each print and consolidates
those features, allowing a greater range of presentations to be recognized. The fourth print is used for
verification purposes. Below each enrollment image a color bar will be displayed indicating the quality of
the print as it is being captured. Green indicates quality is above recommended quality. Orange
indicates the quality is above the minimum but below the recommended quality. Operators with
administrative rights are permitted to accept fingerprints of this quality. Red indicates the quality is
below the minimum, the user must re-enroll.
Follow the instructions on screen. Green indicates ready to capture. Orange indicates that a finger is
presented but the capture has not finished yet. Check the instructions to ensure the finger is placed
correctly. When the border is red, the current finger capture is finished. Continue until all boxes are
filled.
The real fingerprints as acquired by the MorphoWave device during enrollment can be
hidden from screen. Use this feature with care, as bypassing the visual inspection of
enrolled fingerprints may reduce the biometric performance of the system. It is enabled
by adding the below parameter in the Server configuration file:
<ShowPrints>false</ShowPrints>
Once the enrollment is complete, you will see the screen below (this example is utilizing a Duress
Finger). Captured finger quality is displayed on the right. In the event a user is not being recognized at
any Biometric Device with enrolled fingers, click Clear <enrolled finger> finger enrollment to allow re-
enrollment.
© Refer to End User License Agreement for Copyright Notice Page 126
MorphoManager User Manual
The key to capturing a high-quality fingerprint is to visually look for a clearly presented pattern that is
centered and square with the right amount of pressure. Do not hesitate to retry the capture if you are
unsatisfied. For assistance refer to the fingerprint capture guide. Click Finish to save the user or cancel
to discard changes.
To get the best performance from your MorphoManager software and Biometric Device hardware, care
must be taken with enrollment of users into the system. Below are examples of fingerprint capture
which could result in either false acceptance or false rejection of users at your Biometric Device. We also
suggest that the Biometric Device be mounted at a height of approximately 1 meter from the ground.
Mounting the Biometric Device at this height will facilitate full finger presentation when using the
Biometric Device. Mounting the Biometric Device significantly higher or lower on the wall makes
presentation of a full fingertip much more difficult.
Figure 1
© Refer to End User License Agreement for Copyright Notice Page 127
MorphoManager User Manual
This is an example of a finger that has been cleaned of oil by methylate spirit. Very little information is
shown on the print to develop the algorithm. This can happen if you use hand wipes or hand cleaners
prior to using the Biometric Device. If the hand cleaners are used for infection control or similar
requirements, either use the hand cleaner after using the Biometric Device or provide a hand cream
solution to replace the natural body oils stripped from the hands.
Figure 2
This is an example of a print where the person being enrolled has used only light pressure and partial
presentation of the tip of the finger. The user will have difficulty presenting the same portion of the
finger when clocking “On” or “Off” if this is allowed during enrollment. This type of enrollment could
also lead to a significant number of false acceptances which is where a user is identified incorrectly. This
is because there is little information in this portion of a fingerprint to develop a good algorithm.
Figure 3
© Refer to End User License Agreement for Copyright Notice Page 128
MorphoManager User Manual
Figure 3 shows the finger being presented in two different places on the enrollment device. The
MSO300 or 1300 will discard any non-matching prints and average those remaining out of the three
presentations. If the third print was in a different place again, the software would either accept one as
being a match and use that or reject the enrollment. However, matching on two prints is not as good as
three identical prints
Figure 4
In this example the captured finger has a large amount of oil on it and pressure was quite high on the
reader lens. This will probably work okay but is not ideal. A user needs well defined ridges and troughs
as well as intersection points in the print. These sites are the matching points used to develop the
algorithm which is the finger template that subsequent finger presentations are matched against at the
Biometric Device.
Figure 5
© Refer to End User License Agreement for Copyright Notice Page 129
MorphoManager User Manual
This is an example of the presentation required for the best possible enrollment by a user. This example
has good information like visible ridges and intersection points for development of the algorithm by the
enrollment device. A full print is presented to the window and even pressure from the finger. The print
should use as much of the finger phalange as possible.
Edit
Opens the already saved user details for viewing or editing.
Delete
Use with caution as the user’s details will be permanently deleted. This operation cannot be undone.
Refresh
Refreshes the user list from the database. This will update the display with the most current data.
Disable User
When a user is disabled, they no longer have access to any Biometric Device. All access logs and user
information will be retained for reporting. Disabled users can be enabled at any time. Disabled users are
considered when checking for duplicate ID’s and biometrics.
Import
Individual or Multiple users can have their information imported into MorphoManager via the Import
feature. Individual users can have their demographic data and biometric templates imported. However,
Multiple users will only have the demographic data for those users. Biometric template capture for the
users can then be done later.
© Refer to End User License Agreement for Copyright Notice Page 130
MorphoManager User Manual
For more information about the importing of multiple users, please refer to the Import Users from CSV
File Guide.
Verification - Database
A VERIF license is required on the MorphoManager Client Computer to perform biometric
authentication
Verifies a presented fingerprint against the fingerprint stored in the MorphoManager database. If the
fingerprints match, a “Verification Successful” message is displayed along with the verification score. If
the fingerprints do not match, a “Verification Failed” message is displayed.
Verification can verify contact and contactless fingerprints. The current selected tab will determine
which fingerprint type will be verified.
The device that will be used for verification is set in the Clients menu and is the same device as the
enrollment device.
Export Photo
The photo stored in the User record can be saved to disk.
Add Photo
A photo from disk can be used as the user’s photo. This is useful if a camera is not connected to the PC.
© Refer to End User License Agreement for Copyright Notice Page 131
MorphoManager User Manual
Filter
The display of users can be filtered by clicking the Filter button. Select the required items and click Ok.
The list of users will automatically be updated using the new filter information. To return the filters to
their original state click Reset Filters. To display all users click Show All.
© Refer to End User License Agreement for Copyright Notice Page 132
MorphoManager User Manual
Biometric Identification
Used to identify a user by their fingerprints. It is possible to do an identification on contact templates
and contactless templates.
An IDENT and VERIF license, on the MorphoManager server, is required to run the
matcher which performs the identification.
Once the user presents their fingerprint to the device an “Identified” or “Not Identified” screen will be
shown.
Identified: The identified user’s name, photo and identification score will be displayed.
Not Identified: If the captured fingerprint is not matched against a previously enrolled finger, the “Not
Identified” screen will be shown.
© Refer to End User License Agreement for Copyright Notice Page 133
MorphoManager User Manual
Once the user presents their hand to the MorphoWave device an “Identified” or “Not Identified” screen
will be shown.
Identified: The identified user’s name, photo and identification score will be displayed.
Not Identified: If the captured hand is not matched against a previously enrolled hand, the “Not
Identified” screen will be shown.
© Refer to End User License Agreement for Copyright Notice Page 134
MorphoManager User Manual
Onsite/Offsite
The Onsite/Offsite tab is hidden by default. To access this section, it will need to be
turned on in the Clients section of Administration. Once it has been checked, log out and
back into MorphoManager. Additionally, its functionality to record Onsite and Offsite
movement needs to be enabled via the User Onsite/Offsite section on the System
Configuration>System Functionality tab.
The Onsite section is used to show which users are currently onsite or offsite. The Onsite and Offsite
items in the tree view on the left can be expanded to show user groups.
NOTE:
To manually set a user onsite/offsite, click on the User in the Main screen and click on Set User Off-Site
or Set User On-Site.
Depending on the Biometric Device Onsite mode that has been set, the users will be shown in onsite or
offsite.
© Refer to End User License Agreement for Copyright Notice Page 135
MorphoManager User Manual
Transaction Logs
An access log is a record of transactions recorded by the system.
To filter the display of access logs, click Filter. Enter or select the details for filtering and click Ok. To
reset the filters to their original state, click Reset Filters.
© Refer to End User License Agreement for Copyright Notice Page 136
MorphoManager User Manual
Before the access log can be exported, you need to create an Export profile. This is an initial setup
procedure and is performed only once unless you need to export to another type of time and
attendance application. The following error will be displayed if the profile has not been created.
Refer to the system configuration section for instructions on configuring an access log export profile.
Once an access log exporter has been set-up, click on Export Access logs and you are presented with a
window showing the destination of the file. Enter a file name with its extension and click on Save.
Note: Employee ID and Export value must be present to be exported into the logs. Biometric Device
name and User ID are NOT exported.
© Refer to End User License Agreement for Copyright Notice Page 137
MorphoManager User Manual
Reports
The reports center has a variety of reporting options for displaying information about user activity.
List Report: Displays a list of all items in the selected category (Biometric Device,
Operators and Users)
Activity Reports: These reports will show all activity for the selected item type.
© Refer to End User License Agreement for Copyright Notice Page 138
MorphoManager User Manual
Permissible Report
• Select the Report type (Biometric Device or User).
• Search for the Biometric Device name or the username and click on Generate Report.
© Refer to End User License Agreement for Copyright Notice Page 139
MorphoManager User Manual
A Certificate Import Wizard will appear. Under the Store Location option, select Local Machine and click
Next.
The next page will allow you to specify the file to import. The location of you certificate should already
be provided in the File Name field space.
© Refer to End User License Agreement for Copyright Notice Page 140
MorphoManager User Manual
Next, enter the certificate’s password. This is the password that should already be associated with the
certificate, not a new one. Check any additional import options that may be applicable.
The next page allows you to select which store the certificate will be imported to. You can choose to
have the store automatically selected, however, since MorphoManager will be expecting the certificate
to reside in either the Personal store or the Trusted Root Certification Authorities store, select the
© Refer to End User License Agreement for Copyright Notice Page 141
MorphoManager User Manual
option that allows you to place the certificate to the store of your choosing and browse to the store’s
location.
Finally, ensure that the information provided on the last screen is correct and click the Finish button to
begin the import process. Once complete a prompt will appear informing you that the import was
successful.
© Refer to End User License Agreement for Copyright Notice Page 142
MorphoManager User Manual
Once the certificate store opens, locate the folder that was specified during the import process. You
should see your new certificate. It may be hard to tell which one is newly imported, so you may want to
take note of which ones where there before hand. Additionally, multiple may have been imported from
what appeared to be one.
© Refer to End User License Agreement for Copyright Notice Page 143
MorphoManager User Manual
Database Management
Database Backup Tool
The Backup Tool allows for the backup of SQL CE database. Systems running SQL Server will need to
contact your DBA or Microsoft for backup information.
When you start the Database Backup Tool, you will be prompted for backup directory. Select the
directory you want to back up the database to.
The MorphoManager service must be stopped before starting the Database Backup Tool.
Browse
Click Browse to change the backup directory
Start Backup
Starts the backup process.
© Refer to End User License Agreement for Copyright Notice Page 144
MorphoManager User Manual
The Tool can be accessed by clicking on the start menu, then selecting “MorphoManager”, followed by
“MorphoManager Biometric Device Configuration Creation Tool”.
Port: Default
© Refer to End User License Agreement for Copyright Notice Page 145
MorphoManager User Manual
Screen 1
Set the date and time to run the firmware update job. By default, it will run immediately. However, this
can be scheduled to run at a future date and time. Click Next.
© Refer to End User License Agreement for Copyright Notice Page 146
MorphoManager User Manual
Screen 2
Select the Biometric Device(s) connected to MorphoManager that will be included in this Firmware
Update. Click Next.
Screen 3
Browse and select the firmware update version file to be applied to the Biometric Devices selected on
Screen 2. Click Finish. The tool will return to the main screen below.
© Refer to End User License Agreement for Copyright Notice Page 147
MorphoManager User Manual
The Firmware Update jobs generated will be listed on the main screen with their execution status, date,
and time. Unexecuted jobs can be edited or deleted. Completed ones can be deleted. If the job status
shows it has failed, further detail can be found in MorphoManager’s Event Log.
This utility could be located within the MorphoManager package under “Compatibility Check Utility/
CompatibilityCheck.exe”. Double click the file to launch the utility.
1. SUCCESS: Database is compatible with the new version. Please continue with upgrade.
2. FAILED: Database is not compatible with the new version. Please contact Idemia support for
further assistance.
© Refer to End User License Agreement for Copyright Notice Page 148
MorphoManager User Manual
Resilience
This feature is available for user adding and logs retrieval from version 15.3.1 and consists on an
automatic retry of these both requests in case of transient failure.
© Refer to End User License Agreement for Copyright Notice Page 149