Getting Started

The ActivID® Device Initialization Tool is a standalone Windows-based application that provides a set of services and management, around the ActivID authentication devices, such as:

  • Configuration of the device with a set of existing profiles (security services, behavior, etc.) or with new ones. Typically, local initialization ofdevices allows you to secure your own sets of security keys to which no other party has access, including HID Global®.
  • Management of the device credential (import, export, encryption).
  • Defining access rights to the console, reinforcing the database protection, and providing audit services.

System Requirements

  • Hardware:

    The database space required depends on the number of devices end users intend to host. 100MB is the minimum requirement for a small configuration based on:

    • Intel Core™ i5 3.3GHZ

    • 4 GB RAM

    • 200 MB of available disk space (for the Device Initialization Console)

    • ActivID Coupler for the relevant ActivID OTP tokens to initialize (see the Couplers section)

  • Operating system (64-bit platforms):

    • Microsoft® Windows® 10 (64-bit)

    • Microsoft® Windows® 11 (64-bit)

  • Database:

    • Microsoft Access® (integrated in the Device Initialization Tool and requires the Microsoft Access Database Engine (MADE)).

      Note: By default, the Device Initialization Database is not protected by a password. For security reasons, it is highly recommended that you set a password. For further information, refer to Securing the Microsoft Access Database.
    • If you need a more robust database, you must install either Microsoft SQL® Server 2019 or Oracle® 18c and then create a new database. If you choose this option, you can install only one SQL Server or one Oracle database. For further information about the database deployment, see Setting Up an SQL Server Database or Setting Up an Oracle Database.
Important: The 4.2 Service Pack cannot be installed within the same installation command as the 4.0 installer: version 4.0 must be installed first, then 4.2.

Standards and Compatibility

The Device Initialization Tool is compatible with: