Completing the installation process - Security Center

Security Center Installation and Upgrade Guide

Security Center
Content type
Guides > Installation guides
Last updated

After you install Security Center, there is a series of steps you can take to check the status of your system.

Before you begin

Install Security Center.


  1. If you chose to create the databases yourself, create them now.
    If you use default database names, the service user can connect to them automatically. The default database names are the roles name without the spaces, with the following exceptions:
    • The default database name for the ALPR Manager role is LPRManager.
    • The default database name for the Record Caching Service role is RecordCache.
    If your database names are different from the default ones, you must change the setting in Server Admin for the Directory database and in the roles' Resources page in Config Tool for the role databases.
    IMPORTANT: Delete the default databases before creating new ones. Use a different database name for each role to avoid confusion.
  2. Log on to Server Admin, click Overview, and check the following:
    • Directory database is connected ().
    • Directory is ready ().
    • License is valid () and all required features are present.
    • All installed servers are connected ().
    • SMA contract number is confirmed with expiration date.
    • Mail server (SMTP) is configured.
    • Genetecâ„¢ Watchdog is configured for email notifications and recipients.
  3. Under Servers (), click the main server (), and check the following:
    • Automatic Directory database backup is enabled and configured.
      NOTE: If the database is local to the Directory server, check under Database properties (). If the database is hosted on an external machine, confirm that automatic backup is configured on that machine.
    • Retention periods for various types of data are properly configured.
      NOTE: Keep in mind the database size when SQL Express is being used. A long retention period might cause database size issues if your system generates a lot of events.
    • Data collection policy is properly configured.
    • Correct network interface card (NIC) is selected.
    • Server authentication certificate is configured.
  4. Under Servers (), click each expansion server, and check the following:
    • Correct NIC is selected.
    • Server authentication certificate is configured.
  5. Log on to Security Center through Config Tool, open the Network view task, and check the following:
    • All servers are online with no health issues.
    • Proper network protocol is in use based on network capabilities.
    • Public addresses are configured properly where needed.
    • Network address and subnet mask correspond to the actual network.

    For more information, see About the Network view.

  6. Open the System task, click Roles, and check the following:
    • Roles are online with no health issues (not displayed in a yellow warning state).
    • Roles are connected to their database (when applicable).
    • Automatic backup is configured for role databases (if required).
      NOTE: If a database is local to the server that hosts the role, check under Resources > Backup/Restore (). If the database is hosted on an external machine, confirm that automatic backup is configured on that machine.
    • NIC is selected for each role, and in the case of the Media Router, for each redirector.
    • Whenever role failover is configured for roles other than the Archiver and the Directory, the role database is hosted on a third computer.
  7. Open the User management task, and ensure that the Admin user has a password.
  8. Check that you can log on to Security Center through Security Desk.
    If that doesn't work, you can troubleshoot the main server.
  9. On all Security Center servers, check the following:
    • Unused NICs are disabled.
    • NIC binding order is properly configured.

      For more information, see "Network cards order and prioritization" in Best practices for configuring network cards on your servers for Security Center.

    • Server is not a domain controller.
    • Windows update is set to not automatically install.
    • Windows clock is synchronized to a time source.

      For more information, read our online articles on time synchronization.

    • No unwanted application is running.
    • System drive has sufficient free space.
    • CPU memory and usage are under acceptable thresholds.

      Recommended CPU usage is under 85%. Refer to Microsoft documentation for memory usage thresholds.

    • Windows storage indexing is disabled on all drives used for video archiving.
    • Windows Event Viewer is free of critical errors or restarts.
    • Antivirus software is configured properly and all exclusions are made.

      For more information, see Best practices for configuring antivirus software for Security Center.

After you finish

  • Read and follow our Best practices for configuring Windows and Security Center.
  • Depending on your deployment requirements, complete your system configuration for:
    • User management (users, user groups, and partitions)
    • Schedules (follow our best practices for naming conventions)
    • Video surveillance and management
    • Access control
    • License Plate Recognition

For information about how to enhance the security of your Genetecâ„¢ Security Center system, see the Security Center Hardening Guide.