Jump to content

Hemo2

Members
  • Posts

    64
  • Joined

  • Last visited

Hemo2's Achievements

Newbie

Newbie (1/14)

  1. Karel, does this bluescreen occur in the newest v3.1.0 build 1684 release?
  2. I hope this issue is being reviewed as causing a BSOD during the inventory scan on your computers is not a functional situation.
  3. We haven't implemented TNI v3 yet due to logistics and other projects taking precedence. But this bluescreen issue reported by karel brings up a question. Are there new command line switches for the new v3 TNIWINAGENT.EXE program? Is there one that maybe tells it not to do a 'low level' hardware scan, or something similar to avoid this potential issue?
  4. Our Symantec Enpoint Protection anti-virus software this week started to flag and quarrantine/delete the "C:\Program Files\Total Network Inventory\Nmap\ncat.exe" file. If we are not using the NMap Engine for scanning and are instead using the Classic Scan engine, will anything in TNI be affected now that this ncat.exe file has been deleted by our anti-virus software? Or should we look at adding an exception within Symantec Endpoint Protection for this file?
  5. Hi Zak. Thanks for the quick reply. After seeing your comment, the version of the "tniwinagent" is the cause of our issue. We do have the newest version of TNI, but we never deployed the newer version of the tniwinagent.exe in our login script scanning because of the much larger size of it than previous versions and our concern with bandwidth. I'm not sure that we will deploy the newer tniwinagent because of this and will have to make do with deciphering the IE version looking at the overal number and not the '9' at the beginning.
  6. I noticed for machines with IE 10, we are getting a version number showing of "9.10.9200.xxxxx". (Note the "9" at the beginning of the reported version number.) I looked in the registry at "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer" and the "Version" value does in fact show this 9.10.9200.xxxxx version number, even though IE10 installed on the computer. I noticed in the registry at the same key, there is a "svcVersion" value entry and it is set to "10.0.9200.xxxxx", which is more what you'd expect to see from a computer with IE10 installed. Is the issue that Microsoft does not properly update the "Version" registry value that programs are reporting on, or would TNI now need to check multiple locations to properly report the IE version number? I think we can use that 9.10.9200.xxxxx verison number from TNI reports to tell who has IE10 installed, but it's a bit odd to see the "9" at the beginning of the version number.
  7. I believe I'm running into this issue too with TNI v2.2.3 build 1539. I was attempting to generate a simple list of computer names that did NOT have a piece of software installed on them. (I failed miserably at this and have no idea how to do this and discovered I am completely lost in the Software Accounting tab which is why I avoid that tab.) Anyway, I somehow managed to flag some software items in the Software Accounting list with that red colored 'Absence' icon. I can find no way to get rid of that. I click the gray colored 'x' but it simply does nothing. I can click the green colored 'Presence' item and it will change the selected item to that colored icon, but clicking the light gray colored 'x' next to the Track item doesn't clear things and I have items in the Software Accounting tab stuck with that colored Presence/Absence icon on them.
  8. I could see that idea as working and useful.
  9. Thanks for the info Zak. This feature could be helpful to others and we'll definately take a look at it to see if it can simplify the levels in our storage.
  10. Hi Zak. Thank you for the information. From a technical standpoint, I don't know that we want to pre-deploy the agent, so it kind of makes sense to leave the runtime library in the agent. The idea of caching it locally is interesting, but I'm not sure how we would then run the command in our login script. I think we'd still need to point the the network resource to run the agent just in case the locally cached file didn't exist. So for now, I think we'll run the older version and discuss the larger size of the new version. I don't think a change is needed on your end at this time. All our users don't obviously login at the exact same moment in time, so that helps. If techs run large scale scanning on remote networks, we can have them scale back the number or concurrent scans if we run into response and bandwidth issues.
  11. Hi Zak. I appreciate the reply. A notification that a sync is occuring would be great and of course if it can be made faster, that's even better! :) With the syncing with AD and the OU levels, I think it will work the way it is. Where our computers are in AD isn't on a branch immediately off the root of AD. When we originally setup our TNI Storage, of course the top level inside of TNI is where we started our computers and we simply manually created folders in the TNI Storage to mimic our AD structure. With the new sync with AD in TNI, after I have had time to work with it, I think it will work as is. Even though we are getting the entire AD structure in our TNI Storage now after a sync, things are still organized such that we can run reports, etc. on the main branches that have our computers contained underneath it. So I don't think a change is necessary on your end. Thank you.
  12. I noticed in the latest release, v2.2.3 build 1528, that the size of the TNIWINAGENT.EXE file has increased in size dramatically. Previous size we used was 291KB and it's now more than twice the size at 720KB in this release. We perform login script scanning on our workstations. The command we use in our login scripts runs this file from a centralized server. However, we have a great many workstations (thousands) on remote networks and many of these have limited connection into our primary backbone. We are understandably concerned about the size of this new file and the effect it will have on our bandwidth at these limited networks, so we haven't started using this newer version of the agent. The version of the agent we are currently running is v12.12.04.0. To help us decide if we want to use this newer version, we'd like to know what changes or enhancements are in this newer, and larger, agent file? Are the changes something that are needed for new features in the newest TNI update? Would we be missing anything or causing issues if we continued to use the older agent with the newest version of TNI? Thank you.
  13. Hmm, nevermind! Wouldn't you know it, 10 minutes after I posted this, my TNI Storage is going crazy with updating the storage folder structures, etc. now. Apparently it took a bit of time in the background to read in our AD structure before anything visible in TNI started to occur. If I have any further questions or issues, I'll post a followup topic here.
  14. I'm very excited about the Sync with Active Directory feature! However, I have a question on how to tell if it's doing something. I have installed the newest TNI update and enabled the option to sync AD on startup. I restarted TNI and nothing appears to be happening. (There's no indication that it's doing anything.) So I right clicked on my TNI Storage and selected "Synchronize with AD", but again, nothing has the appearance that any sync is occuring and the number of assets in my storage branches remains unchanged. I normally log into my workstation with a standard user account and also run TNI as a standard user account. So I closed TNI and did a 'run as administrator' on TNI thinking perhaps it needed to be run as a domain administrator on my workstation before the synchronization would take off. However, that also does not seem to be doing anything. My TNI is functioning as normal. Is the synchronization doing something hidden behind the scenes and I just need to wait longer for some indication that the synchronization is going? Not sure if this info makes a difference, but in my TNI, I had setup branches in my TNI Storage to mimic our AD branches and OU structure. But the OU level in AD that contains all our sub-OU branches with our AD workstations isn't actually at the top level of our AD.
×
×
  • Create New...