Access Manager configuration tabs

Access Manager - Properties tab

Click the Properties tab to configure the general settings of the Access Manager.

Keep events:
Specify how long you want to keep the events in the Access Manager database before deleting them. The access control event are used for reporting and maintenance purposes (they include events related to doors, elevators, areas, and other access control entities).
- Indefinitely:
  Keep the events until you manually delete them.
- For:
  Select the number of days for the retention period.
CAUTION: If you are using the SQL Server 2014 Express database engine (included with the Security Center installation files), the database size is limited to 10 GB. A door event uses (on average) 200 bytes in the database. If you configure the Access Manager to keep door events indefinitely, the database eventually reaches the 10 GB limit and the engine stops.
Activate peer to peer:
Select this option to enable the communication between Synergis™ units managed by this Access Manager. Up to 15 units can be connected as peers, supporting a maximum of 512 outputs and 128 inputs in I/O linking configurations.
BEST PRACTICE: Only enable peer to peer communication if you plan to create I/O zones that involve multiple Synergis™ units, or apply antipassback to areas controlled by multiple Synergis™ units. Leave this option off for better system security and performance.
Activate global antipassback:
Select this option if you need to apply antipassback to areas controlled by multiple Synergis™ units. To enable this option, you must first enable peer to peer.
BEST PRACTICE: If all your antipassback areas are controlled by a single unit, do no enable global antipassback. Enabling global antipassback increases the communication between Synergis™ units.
Include identifiable personal data in synchronization:
(Synergis™ units only) Select this option to sync cardholder names with the Synergis™ units. If this option is cleared (default), only credentials without personal data are synced. Enable this option when you have devices that can display cardholder names and you want them to appear.

Access Manager - Extensions tab

Click the Extensions tab to configure the manufacturer-specific connection parameters shared by access control units that are controlled by this Access Manager.

Genetec™ Synergis™:
Extension for all Synergis™ units. This extension requires at least one discovery port. For more information, see the Synergis™ Appliance Configuration Guide.
HID VertX:
Extension for all HID units, including the legacy VertX models (V1000 and V2000), the VertX EVO, and the Edge EVO controllers. For the complete list of supported controller units and firmware, see the Security Center Release Notes.

Access Manager - Resources tab

Click the Resources tab to configure the servers and database assigned to this role.

Servers:
Servers hosting this role.

Database status:
Current status of the database.
Database server:
Name of the SQL Server service. The value (local)\SQLEXPRESS corresponds to Microsoft SQL Server 2014 Express Edition installed by default with Security Center Server.
Database:
Name of the database instance.
Actions:
Maintenance functions you can perform on the role database:
- Create a database ():
  Create a new database with the option to overwrite the existing one.
- Delete the database ():
  Delete the database.
- Database info ():
  Show the database information.
- Notifications ():
  Set up notifications for when the database space is running low.
- Resolve conflicts ():
  Resolve conflicts caused by imported entities.
- Backup/Restore ():
  Back up or restore the database.
Authentication:
Specifies which SQL Server authentication is to be used:
- Windows:
  (Default) Use Windows authentication when the role server and the database server are on the same domain.
- SQL Server:
  Use SQL Server authentication when the role server and the database server are not on the same domain. Mandatory for Azure SQL Database. You must specify a username and password in this case.
Database security:
Security options for communication between the role and its database server.
- Encrypt connections:
  (Default) Uses Transport Layer Security (TLS) protocol for all transactions between the role and the database server. This option prevents eavesdropping and requires no setup on your part.
- Validate certificate:
  Authenticates the database server before opening a connection. This is the most secure communication method and prevents man-in-the-middle attacks. The Encrypt connections option must first be enabled.
  NOTE: You must deploy a valid identity certificate on the database server. A valid certificate is one that is signed by a certificate authority (CA) that is trusted by all servers hosting the role and that is not expired.