Skip to main content

NIM

Install & launch NIM

  1. Run the NIM Windows .exe installer. The following settings are recommended:

    • HTTP: Enabled, port 80, redirect to HTTPS disabled

    • HTTPS: Enabled, port 443

    2023-09-14_14-54-15.jpg

    • Destination folder: C:\Program Files\Tools4ever\NIM\ (default)

    2023-09-14_14-54-27.jpg

    After you click Next, the following components are installed in the installation directory:

    • A web-based front end, aka the NIM Studio (an Angular application that runs on Node.js; contained in the \app\ folder)

    • A back end Windows service that runs on the same instance of Node.js (idmsvc.js)

    • Node.js version 14 (node.exe)

  2. Configure Windows permissions:

    • If you're using NIM with Active Directory, grant the NIM service permission to read and write from AD.

    • Grant the user account on which the service is running permission to create subdirectories and read files.

  3. During large mapping or role operations (e.g., tens of thousands of operations), Windows Defender can interfere with NIM. To resolve this, exclude the following from your Windows Defender whitelist:

    • C:\Program Files\Tools4ever\NIM

    • C:\ProgramData\Tools4ever\NIM

    • C:\Program Files\Tools4ever\NIM\node.exe

    • C:\Program Files\Tools4ever\NIM\nim.exe

  4. Launch the NIM studio:

    1. Ensure the back-end NIM service is running.

      2021-05-28_13-09-01.png

    2. Open your preferred web browser and go to localhost:80/index.html. If you're connecting from an external machine, instead go to <hostname-or-ip-address>:80/index.html.

    3. Choose a password for the default account (username Administrator).

      2023-09-14_15-16-45.jpg

    4. To confirm, click Set Administrator Password.

    5. Your chosen password is assigned to the Administrator account, and the NIM Studio is launched.

      2023-09-14_15-18-05.jpg

Next: Enter a license code

Minimum requirements

  • 2 cores

  • 16 GB RAM

  • 120 GB free storage space

  • Windows Server 2019 or higher (older editions may work, but we recommend staying within the Microsoft Lifecycle Policy)

  • PowerShell 5.1

  • .NET Framework 4.7

In this section: