Jump to content

Support

Administrators
  • Posts

    695
  • Joined

  • Last visited

Everything posted by Support

  1. Karel, What about the Classic engine in build 1490? What we changed between 1483 and 1490 is that the ARP ping is not used for monitoring of the online state anymore. In 1483 it's still used. However it gives incorrect results on Windows XP (when an asset goes offline, it still shows as online for about 10 minutes, as its MAC is still present in the ARP table), and also if there is Proxy ARP enabled on a switch or router. Are all your PCs on static or dynamic IP addressing? (static IPs have a padlock icon next to the IP address in the tree, and dynamic IPs don't have it).
  2. Hi Karel, This was a planned enhancement for the standard WOL action, but adding a possibility to pass a remote broadcast address in custom actions is a nice feature too, thanks. Marius, Thank you for updating this topic with new useful actions.
  3. Hi Karel, Thank you, we will try to implement this as soon as possible.
  4. Hi Joel, Use the power of the table report conditions to your advantage. Add some conditions to exclude unnecessary titles like "Title does not contain plug-in", "Title does not contain add-in", etc.
  5. Unfortunately no. Please check if you can retrieve it using the attached VBScript. Run it on the server that has the HBA installed. Let us know if it's working. We might add it in the future versions then. HBA.zip
  6. Thanks, Marius, that's a nice start! We're looking forward for more actions from our users.
  7. Hi everyone, An awesome new feature in TNI 2 is out there—Actions! Read more in our blog. On this occasion I'm creating this topic for questions and feedbacks on this feature. Also let's share useful working custom actions with other TNI users here.
  8. Please update to the latest version 2.2.2 (build 1483) released today and let us know if it fixes the issue. Thank you.
  9. We have already thought of such customizations as custom scan for registry keys and files (though not for WMI classes) too. We would like to add them in the future. Meanwhile we will add FirmwareRevision field for the disk drive objects. Thank you.
  10. Hi Jaban, This is a common situation and we understand your concern. However there is no snapshot comparison in the program yet. We plan to implement snapshot comparison and change tracking in the future versions. Please stay tuned for the updates.
  11. Thanks, we have fixed the program to show IE10 version correctly. This fix will be available with the next update.
  12. Hi Craig, Thanks for the idea. We are considering this possibility in the nearest future.
  13. A possibility to disable new version auto-check has been added in v. 2.2.0.
  14. Please try the latest version of the program available now (v. 2.2.1 build 1455).
  15. Hi Karel, Unfortunately not. All new features are mentioned in the version history and in our blog.
  16. Hi, Have you selected the added login in the scanner? If you mark it as default, make sure that it's specified in the Windows logins column when you add a scan task. Also check if this login has enough rights to access this particular server. Try to open "\\servername\admin$" shared folder in Explorer using this login.
  17. Hi Karel, The message box asking for feedback during uninstall will not appear anymore when running the uninstaller with any of the silent switches. This change will be added in the upcoming update (version 2.2.1).
  18. You can send an inquiry to recover your license key here: https://www.softinventive.com/support/ As for your second question, we could not understand it quite clearly, but perhaps you were asking about software accounting, here is the documentation section: https://docs.softinventive.com/tni/user-manual/software-asset-management/
  19. Hi Martin, Please follow the advice from this forum: http://www.pcreview.co.uk/forums/wmi-problems-t1898592.html This will rebuild the WMI repository and should fix the problem.
  20. I'm not sure what are you trying to do here. Allow this regular account to run only specified programs (with specified full paths) or what? If so, this will fail, because tnilinagent is always uploaded to a randomly named directory in the home directory of a user, and then also unpacked to another random temp directory, so the path where it's run from is never known beforehand. You can always run the scan manually, if needed: chmod 755 tnilinagent_x64 ./tnilinagent_x64 -silent I'm not a master of setting up the sudoers file, but from what I know, you only need to specify the user in it to allow him to elevate to root. If you have further restrictions, that may not work: you should consult with your Unix admins.
  21. The problem is not in the support of child domains, there is no need to support them specifically. The problem is in access rights. If you can access a computer's "admin$" shared resource, you will be able to scan it (via SMB protocol; RPC protocol is more tedious to set up properly). If you are using a user that is domain admin in your parent domain, make sure that it's an admin in the child domain too and that it's a member of the Local Admins ground on the computers from that domain. If you are using a user from a child domain, make sure to specify the user name in full format (DOMAINNAME\Username) to avoid any ambiguity.
  22. This is a known issue and we are working on it. Hopefully it will be fixed in the future updates.
  23. Please disable one of the options: Options - Scanner - Use Nmap engine Options - General - Check the online status of assets periodically and see if it helps. Then please enable it back and disable another option of these two. See if it helps also or not. Please let us know which of them (or both) helps.
  24. Yes, it's possible. Actually, this error message is quite specific and it would better be sent to our support email rather than the forums, but... As we are already here, this is the original error message: >>> etc\sudoers: syntax error near line 26 sudo: parse error in \etc\sudoers near line 26 sudo: no valid sudoers sources found, quitting The problem is that you have syntax error in your "\etc\sudoers" file. Your admins should fix this file. The non-root user that you use should be specified in sudoers correctly to be able to run the scan, and the file should not contain errors. The error that the program itself throws: Cannot create file "C:\Users.....". The filename, directory name, or volume label syntax is incorrect is secondary and appears because the program receives the filename for saving the scan results after the ">>>" sequence which appears in the sudo error. So as soon as the sudoers file is fixed, you should be running fine.
×
×
  • Create New...