Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


ŁukaszBachman last won the day on April 19

ŁukaszBachman had the most liked content!

Community Reputation

15 Good

About ŁukaszBachman

  • Rank
    Advanced Member

Profile Information

  • Gender
    Not Telling
  1. I renamed the button to "Finish source management", to avoid confusion. This change will be present in upcoming 2.3.1 release.
  2. Hi Tom, Indeed we have plans for changing the flow, so that the case will be closed automatically. This requires larger architectural changes to the software, so it will likely take a couple of releases though. However, I do agree with your point about unfortunate naming of this button. We will consider this change in a shorter time span.
  3. Hi Chris, When seeing issues like this it's indeed best to submit a support ticket. Out engineers are working around the clock so often you get a response very vast. Now, what Adam has suggested (reindexing) is actually the best way to ensure that the case indices (databases) have been properly rebuilt. However, it's worth to check indexing logs, Exceptions Report and "Errors" branch in Features Facet beforehand. It will give you a better overview of the state of your case.
  4. Hi Adam! You should note that Primary Dates are calculated based on values stored in Intella columns. Different file formats are populating it differently: sometimes from RAW DATA, sometimes from item properties directly, etc. Therefore I wouldn't go this road because it would be hard to achieve 1:1 consistency. However, I think that the solution to your problem is rather simple. I would create a CSV export (or a load file) containing two columns: Item ID Primary Date Primary date will be populated using full date format (date + time + time zone). Then I'd use some text processing tool (Excel, advanced text editors, etc.) to remove date + time from the 2nd column. Now you'll need to create a new Custom Column of type "TEXT". The final step would be to add a new source as a Load File Overlay with following settings: As you can see the column which you modified (PRIMARY DATE) will be mapped to new custom column you created (TZ ONLY). Item ID is used to match items. After the overlay is imported, you will see: Is that what you need? I hope it helps a bit.
  5. Hello Adam, When using auto-tag feature you can provide the tag name in the following format: parent_tag/new_tag. That way a parent tag will be created first and you should be able to maintain your structure. Is that what you were seeking? As for the other part of your question - what changes/features in the UI you would like to see to influence the scope of this search/tagging operation? Filtering by type or something else?
  6. Vound is pleased to announce the official release of Intella and Intella Connect 2.3. Intella and Intella Connect 2.3 are available from the Downloads section in the Vound Support Portal, after logging in with your email address and password. Users with a 2.2.x license need to use the Dongle Manager to update their dongle to the 2.3 license. Please read the Release Notes before installing or upgrading, to ensure you do not affect any active cases. Highlights Introducing a new product: W4, for the rapid analysis of user activity. Added support for load file overlays. Items can now be exported to an item report. Added support for MS Exchange EDB 2013/2016 files. Added support for Outlook for Mac olk15* files. Added a user interface for managing memory and crawling settings. Note: W4 installers will be published in next couple of days.
  7. Intella Connect 2.3 version has just been officially released.
  8. Hi Sam, Selective indexing of pages inside documents is not something we are currently supporting. I would suggest to open that document using native application and print desired pages to individual PDFs. Then you could use Intella to index those loose files and perform your investigation on individual pages.
  9. Hi QasimProtiviti, In general this shouldn't be the case. What I can suggest to you is do the following: Clear searches Add a regular search query that will produce 1500 items (like before) Add a regular search query for 100 items tagged as "Irrelevant" Now look at the clustermap - if it contains only two clusters, then that is fine. If it contains three, then it means some of items which you tagged as "Irrelevant" are not in the scope of your initial search for 1500 items. Example: I searched for term "look" and marked 10 of those items as "Irrelevant". When I do those three steps listed above I see: Now, I marked 2 more items as Irrelevant, but I made sure that they don't contain term "look". This is what I see after I repeat my exercise: This pictures clearly says that I have 12 irrelevant items, but only 10 of them are also responsive to "look". So if I now search for "look" and exclude items tagged as "Irrelevant", I see: This might look misleading at first, because for an untrained eye "260 - 12" should equal 248, but it's should now be clear that those two extra items were never a part of the "look" cluster, therefore they shouldn't be accounted for. Hope that I was on the right track here and it helps you down the road.
  10. Hi Kalin, LDAP is currently only being used for Authentication, not Authorization. We decided to keep our Authorization configuration on the Connect side, so that the integration with AD/LDAP wouldn't be overly complicated. The level of automation you are seeking is not something that can be achieved in the current version of our software. I would love to hear from other users too if this is something they would like to see being added, though. CLI/CMD support is currently a PRO/Team specific feature. We are planning to add more automation to Connect in next few release cycles, but we are more leaning towards developing some sort of RESTful API. Again, any feedback from the community about this would be appreciated.
  11. Hello uscheerbaum, This can happen in some circumstances, but it depends highly on the type of evidence you are processing. One possible reason of such behavior is Intella running a recovery of deleted mail in a large PST file. This is rather CPU intensive process, which may not necessarily yield large count of items. That would explain why the graph flattens at the end. A rule of thumb when diagnosing behavior like this is monitoring case logs and hardware usage. If CPU is still busy running even one java.exe process and logs suggest that Intella is doing something, then there is no reason to panic. If you see that nothing new gets logged over long period of time and CPU is idle, you may want to address that by issuing us a support ticket.
  12. Hi tcbailey239, I don't think importing these proprietary keys is possible. You will have to find some way to export them to supported format.
  13. Hi John, You should go to the https://console.developers.google.com/apis/library and click on the dropdown in the upper left corner. That opens up a dialog from which you can choose "Create project". I can show you a screenshot of how to do it if this helps (pardon the fact that it's in a different language):
  14. Similar panel is available in Intella Connect:
  • Create New...