Alex

The exact type of each device is detected after the first successful scan. Therefore, it's not possible to scan devices of a certain type if you haven't scanned them before. On the first scan attempt, you can only select or skip certain scanning methods. This allows you to scan only Windows devices (via SMB or RPC), Unix-based devices (via SSH), various network devices (via SNMP and Telnet) and VMware assets (via HTTPS). After the first successful scan, you can build a table report, filter your devices by type and then add them to the scanner through the context menu.

Hello, You can use the 'Quick add' field in the scanner to add a custom scan task. Please see this page: https://docs.softinventive.com/tni/user-manual/network-scanning/adding-scan-tasks/#Quick-Add Here you can find a list of all supported types of tasks and formats that you can add. For example, to add an IP range, simply add a task in the following format: 192.168.0.1-192.168.0.254

Hello Alex, Thanks for your message. Unfortuantely there is no such sensor in the current version of Network Olympus. We've forwareded your request to the dev team. We will consider adding such a feature.

Hello Karel, Thanks for your message. We apologize for the inconvenience. You are right, silent uninstallation doesn't work correctly in the latest TNI version. This issue will be fixed in the next update.

Este es un problema conocido que se solucionó en TNI 4. Usted escanea un dispositivo, sin embargo, TNI actualiza otro dispositivo en el almacenamiento. Puedes probar la siguiente solución: Abra las propiedades del almacenamiento (haga clic con el botón derecho en el nodo raíz en el árbol de la red). Luego cambie la configuración de distinción del dispositivo a "Por nombre de red y dominio".

Gracias por su mensaje. Cuando esta opción está habilitada, TNI recopila menos detalles sobre las impresoras conectadas a las computadoras. La información general de la impresora seguirá estando disponible.

Buenos días, Gracias por su mensaje. Por favor, intente la siguiente solución: Abra las Opciones del programa mientras mantiene presionada la tecla Alt y marque la casilla de verificación "Omitir algunas clases" en la sección Escáner. Deje el texto PrinterConfiguration allí. Luego vuelva a escanear la computadora.

Hello, I've checked the log, and if I am not mistaken, this may be the PAM auth module problem. In any case, we were unable to reproduce this issue in our environment. Not sure if this will help, but a similar problem is described on this page: https://stackoverflow.com/questions/57657645/pam-unixsudoauth-conversation-failed-auth-could-not-identify-password-for

We apologize for the delay. We've checked all possible scenarios on this Ubuntu version, but we haven't encountered this problem on both root and standard users. Please try one of the following solutions: 1. Create a new user and add it to the sudoers group. There may be a problem with your current user. 2. You can enable the root account and use it to perform the scan: a. Use the following command to change or create the root password: sudo passwd root b. Edit the OpenSSH config: sudo gedit /etc/ssh/sshd_config Change the "PermitRootLogin" string to "yes" and make sure the line is not a comment. c. Restart the SSH service: sudo systemctl restart ssh.service After that, try scanning this computer remotely using the root credentials.

Thanks for the information. We'll check the scanning agent on this Ubuntu version and let you know the result.

Hello, Thanks for your message. Please let us know what Linux version you are trying to scan. Usually these two commands should run the agent without a problem if you are using an account with administrative privileges: chmod 755 tnilinagent_x64 tnilinagent_x64 Have you tried performing the scan using the root account? Let us know if "lifuser" is in the sudoers group?

Hi! Thanks for your message. Yes. Usually, this information can be collected via SNMP. Add the network printers to the scanner and use the SNMP column to enter the credentials and select the protocol version. After a successful scan, the information will be available on the Viewer & reports tab in the SNMP tree category.

Hello Alex, We agree that this is one of the essential features that should be implemented in TNI. You can be sure that it will be implemented in any case. The registry scan feature may be implemented in various ways, and its functionality may also vary. We'd like to ask you to describe the exact use cases and tasks that you'd like to solve with it. Currently, we know of several limitations for this functionality: 1. As we know, it won't be possible to scan and transfer the whole registry data to the TNI storage. Each INV file would be too big in this case. 2. In addition, searching for a specific value in the registry may take up to 10 minutes in some cases (unless we're just checking for a specific key or if we're checking for a large number of keys). 3. The previous point is valid for the HKLM keys, but HKCU keys may vary for servers that have multiple users logged in at the same time.

Hello again, We created several polls in our blog to determine the popularity of certain queries: https://www.softinventive.com/blog/vote-for-new-features-of-tni https://www.softinventive.com/blog/vote-for-new-features-of-tni-2 We've already implemented the most popular requests of the 2016 poll, plus many other improvements. And as you can see from the 2019 poll, your request will also be implemented in the future. In addition, we keep records of all user requests and have them ranked by popularity. Our plans for the next 6 months are as follows: The next TNI release introduces the improved identification mechanism for network devices. After that we plan to release an update that should bring improvements and critical fixes to the Software Asset Management module, plus your request regarding the detection of Bitlocker encryption should also be implemented. We will also start working on the new 64-bit version of TNI to overcome the memory limitations of the current version. In addition we plan to improve the network map and the scheduler mechanism.

Hello. >12 months on...any update...? Is it on the schedule for the next 6 months...? Sure. We plan to implement this feature in autumn.

Buenos días, Puede encontrar el archivo del agente en la carpeta de instalación de TNI: C:\Program Files (x86)\Total Network Inventory Ejecute el archivo de agente tnimacagent desde la consola: chmod 755 tnimacagent ./tnimacagent

Hello, Thanks for your message. You can configure the resident agent on each computer that cannot be reached directly. Such agent performs scheduled scans and can send the data file generated after each scan via e-mail or FTP, or save it to a network share. You can find the description here: https://docs.softinventive.com/tni/user-manual/scanning-using-agents/resident-agent-scan/ Unfortunately, the current version of the resident agent cannot send the INV files directly to the main TNI unit.

Dear Gabe, Please note that in TNI 4.1.5 you can already create and manage scheduled backup tasks for the TNI storage. This option is available in Options - Scheduler.

Hello, Gabe. Thanks for your message. Please let us know if you are getting this error on the latest TNI version (4.1.5). We fixed this problem a while ago.

>Is this software still being updated if "We hope to implement it in the future." has been going on for over 6 years? We are a small team. We implement new features based on the popularity of requests from our users. You can check the full changelog over the past years in TNI (Help - Check for updates). We've made many improvements so far. The feature that you are requesting will be added, but we still can't provide you with an estimate. We have strict development plans for the next 6 months. Total Network Inventory operates a database of its own format. It's not possible to update or modify any data that is collected automatically.

Hello, >Was this ever implemented? I would like to read data from the windows 10 registry to populate a custom field created in a TNI report. This request is still on our to-do list. We hope to implement it in the future.

Hello, Thanks for your message. Unfortunately it's not possible to automatically add any information to the TNI database. You can only add and customize additional fields manually in the properties of a device.

Hi Richardmax, The development team has confirmed this limitation for MySQL databases. The latest driver version is not yet supported. This issue will be solved in one of the updates. Meanwhile we can only use the driver version 5.3.6 for MySQL or install the Postgresql database. We apologize for the inconvenience.

Hi Denis, If the remote computers are not part of a domain, we recommend running the .reg file with the following contents: Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa] "forceguest"=dword:00000000 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\system] "LocalAccountTokenFilterPolicy"=dword:00000001 Please try running it on several computers and let us know if this helps. In addition, you can check the following using the same credentials as you specified in TNI: - is it possible to open \\computername\admin$ folder in File Explorer (to access the admin$ folder on the other computer)? - is it possible to access "computername" from the services.msc (Action - Connect to another computer)? Remote computers must be accessible in both cases.

Puede encontrar información detallada sobre los números de puerto y los protocolos utilizados para escanear en TNI en las siguientes páginas de nuestra documentación: https://docs.softinventive.com/tni/faq/scan-questions/#Port-numbers https://docs.softinventive.com/tni/techpaper/scanning-microsoft-windows-assets/ https://docs.softinventive.com/tni/techpaper/scanning-unix-based-assets/ https://docs.softinventive.com/tni/techpaper/scanning-other-network-assets/ Háganos saber si encuentra algún problema.