Jump to content

karel.krobath

Members
  • Posts

    22
  • Joined

  • Last visited

karel.krobath's Achievements

Newbie

Newbie (1/14)

  1. Hi, the parameters for automation are not working anymore starting with version 4.2.5. Could you update the possible parameters for silent install and uninstall please..? If I use: "%PROGRAMFILES(x86)%\Total Network Inventory 2\unins000.exe" /SILENT i get the error: Runtime Error (at 95:119): Could not call proc. Greetings, Karel
  2. Hi Alex, could you please increase the priority for the scanning of ESXi 6? The new version 3.2.1 still does not support it. kind regards
  3. Hi, please add support for vmWare ESXi 6 to the scan agent. kind regards
  4. Hi Zak, thank you for the info. Works great! Greetings, Karel
  5. Hi Zak, is there a parameter for the TNI v3 setup to install nmap as well? currently I use for the installation the commandline and it is working great: tni-setup.exe /SILENT /MERGETASKS="!desktopicon" Kind greetings, karel
  6. Confirmed: the command line switch /nodriver is working fine. No blue screens on previously affected computers. A little suggestion: a good thing would be a help in the tniwinagent.exe like "tniwinagent.exe /?" where the parameters a explained a bit, and the default settings are wirtten.
  7. The bluescreen does happen in the version 3.0.1 build 1675 with the TNIWINAGENT.EXE as well.
  8. First I would like to emphasize the idea of customizing the TNIWINAGENT.EXE with command line parameters. This would be helpful for systems that work with scripted scans (as we do). Secondly a possible workaround for the BOSD issue: Use the TNIWINAGENT.EXE from the TNI version 2.x. This scanner did never cause any blue screens, because the deep hardware scan is possibly not being used. The .inv files which are created with the agent v2.x can be read with the TNI version 3.x.
  9. The bluescreen does happen in the version 3.0.0 build 1653 with the TNIWINAGENT.EXE as well.
  10. hi, I have bad news. The Bluescreen occurs with the agent build 1630 as well. Greetings.
  11. Hello, I experience a bluescreen on Windows 7 x64 every time i run the tniwinagent.exe from the version 3.0.0 build 1601 and build 1627 on workstations with a certain ahci controller. The bluescreen occurs in the driver iaStorS.sys (Fileversion: 3.8.1.1006) of the “Intel C600 Series Chispet SAS”-Controller. At the moment I have Lenovos S30 and D30, where this happens. The driverexeption does not happen, when I scan the pc with the tniwinagent.exe from the TNI version 2. I could not attach the minidump file from a scan I ran today. If you need it, I will send it via E-Mail. If you need further information, I would be happy to help. Greetings
  12. Hi Zak, I have tested a bit the new Version 3.0 of TNI. The Driver Version feature is still missing in the Devices Section. (There is only a rudimentary implementation for the display drivers.) I would like to point out, that this is really a very important and a very useful feature. (Some vendors have their own Driver-management solutions. Like Lenovo System Update or HP SoftPaq Manager. Some Vendors do not have a driver management at all.) In my humble opinion many people would be thankful for an implementation of this. Greetings, Karel
  13. Hi, the classic engine works quite well after the start of the program. About 10 minutes later the status disappears.
  14. Hi, I would like to emphasize, that it would be important to scan drivers and driver versions on a PC. For a system administrator it is very important to identify installed driver versions on a PC that have bugs or security issues. It would be a great feature, if the scanning agent could get this information as well. Here is some further reading to the issue: http://www.tomshardware.com/news/nvidia-gpu-security-driver-exploit,20039.html http://www.esecurityplanet.com/views/article.php/3631261/Dont-Ignore-DeviceDriver-Dangers.htm http://www.securityfocus.com/news/11189 Greetings, Karel
×
×
  • Create New...