Jump to content


  • Content Count

  • Joined

Posts posted by Alex

  1. Sorry for the delay. If the activation is not part of the installation process, it cannot be performed with the marco method. Unfortunately there is nothing we can do here.

    In this case, we recommend that you contact the developers of the software you are trying to deploy. Usually they can share specific parameters that can be used for silent installation and activation.

    The default parameters for each type of installer can be found in Software editor:

    Additional parameters can only be requested from the developers of the software you would like deploy.

  2. Hello,

    Thanks for your message.

    If the activation of the program is part of the installation process and TSD can record (capture) the activation window, there should be no problem with the creation of the deployment package.
    Otherwise, the Macro method cannot be used for activation. In this case, you can ask the developer of the software that you are trying to install whether there is an activation parameter that can be used for silent installation.

  3. Dear Kevin,

    There may be a problem with the scanning agent. Please let us know how the VMs are configured so that we can reproduce the problem in our environment.
    We need the following information:

    1. Virtualization platform.
    2. What do you use as a domain controller for the Linux VMs. How the connection to the DC is configured.
    3. Additional packages installed on the VM and their configuration (related to authorization and domain).

  4. Dear Kevin,

    Yes. These are the latest versions of the Linux agents.

    It appears that the mechanism that performs privilege checking does not work correctly with your virtual system. I've forwarded this information to our QA team.

    Could you please check if you encounter the same problem on another VM or a physical Linux system?

  5. >Where I can download the current agent?
    If you have the latest version of the program (4.9.0) installed, the current version of the agent is always located in the folder where the program is installed:
    C:\Program Files (x86)\Total Network Inventory

    Regarding the user privileges, have you tried the chmod command for the 64-bit version of the agent (before running the agent)?

    chmod 755 tnilinagent_x64


  6. 1 hour ago, Gustavo Torres said:

    Como soluciono cuando me una PC me da este error: "fallo de escaneo: SMB: No se ha generado archivo de datos"

    Este error es bastante raro. Háganos saber si este error ocurre en la última versión del programa (4.9.0).
    Verifique si puede escanear esta computadora remota manualmente usando el agente de escaneo. Puede encontrar el agente de escaneo en el directorio de instalación de TNI. Copie el archivo tniwinagent.exe en la computadora remota y ejecute el archivo. El agente debería generar un archivo INV en unos minutos.

  7. Hi Kevin,

    Such an error may occur if you run a 32-bit agent on a 64-bit OS. Are you sure that the OS version is not 64-bit? Otherwise, you need to use the tnilinagent_x64 agent version instead of tnilinagent.

    If you are sure that the version of the agent is correct, please check if the agent is present in the folder, from which you are trying to run it.

    In addition, you can also try executing the chmod command under the sudo account.

    Let us know if the problem persists.






  8. Hi, Kevin.

    Please let us know if you can connect to this Ubuntu machine via SSH using the same credentials that you have in the TNI scanner (in the SSH column).

    In addition, please try scanning this system by running the linux agent manually. Copy the agent file tnilinagent_x64 from the TNI installation folder to this Ubuntu machine and run the agent using the following command:

    chmod 755 tnilinagent_x64

    Let us know if there is an error message in this case. The agent should generate an INV file in the same folder in a few minutes.

  9. We apologize for the delay.


    Please restore the netsnmp.dll file. Check the following:


    1. Once again, make sure that you are using the Tr4Ps.2020 community when you scan this device.

    2. Make sure that the UPD 161 port is not blocked by Windows on the system where TNI is installed.

    3. Since SNMP v1 and v2 utilize the UPD protocol, it is possible that some packets are lost in your network. Please try to ping this switch using the ping -t command. Let us know the percentage of the packet loss.

  10. Thank you for the information.


    There is one more thing that we can try.


    Please close the program and temporarily remove the netsnmp.dll file from the TNI installation folder (move it to another folder). Start the program and try scanning this switch.

    Let us know the result.

  11. Hi, cestarik.

    Thanks for your message.



    There should be no problem with the Security alert message. TNI accepts it automatically. The problem may be related to the shell of the OS that you are trying to scan or the scanning agent.

    Please try to scan this system manually. You can find instructions on how to do this here:


    Let us know if the local scan returns the same error.


    First of all, please check if the name of the community is specified correctly in the SNMP column. There may be a typo.
    It is also possible that access to some OIDs of the remote device is restricted. In this case, you will receive the same error "Incorrect v1/v2 communities", and TNI will not be able to collect other OIDs and perform an SNMPwalk.

  • Create New...