Jump to content

Chris

Administrators
  • Content Count

    190
  • Joined

  • Last visited

  • Days Won

    8

Chris last won the day on July 8

Chris had the most liked content!

Community Reputation

10 Good

About Chris

  • Rank
    Advanced Member

Profile Information

  • Gender
    Male
  • Location
    Utrecht, The Netherlands

Recent Profile Visitors

960 profile views
  1. Thank you for your feedback on this. In Intella 2.3 we moved management of the memory settings from the .l4j.ini files to the case preferences, where they are edited via the Case Manager. Among the reasons to do so is the fact that the settings that are required to successfully index, or even open, a case may (also) be data dependent, e.g. related to the number of items, or the presence of files of a specific nature such as MS Exchange EDB files. Such memory settings need to travel with the case when it is migrated to a different machine, or when it is picked up by Intella Node. Furthermore, the old settings had to be repeated for every new Intella installation on that machine, as well as on other machines. End users may even lack the permission to alter the .l4j.ini files on their machine. Nevertheless, you are totally right in that the system used to open the case is also a major factor, especially when it comes to crawler settings. We are anticipating future enhancements to memory management, including system-specific preferences/upper limits, and sanity checks on the stored values w.r.t. the machine the case is currently opened on.
  2. Hello, You can indeed do a search like e.g. "car NOT path:car", but a drawback is that items that have a hit for "car" in another field besides the path field are then also excluded. What I suspect you really want is to simply ignore the text in the path field. Fortunately, the Keyword Lists does take into account the search options selected in the Keyword Search panel. You can simply unselect the Path field there. Note that in Intella 2.3 we added a separate "File name" field. Depending on your situation, you may want to uncheck that one as well. We plan to give the Keyword Lists facet its own search options list in a future version, to make this type of control more apparent.
  3. Hi, Selective re-indexing is indeed on our roadmap. I see how the change in how items are merged into a case makes sense and how that can be used as a workaround in the interim, so definitely worth looking into!
  4. Hello Bryan, Please try running the installer like this: setup-intella...exe /S It will run the installer in the background and install Intella in the default location. Some windows will still briefly open and close when certain settings are made, but no user interaction is necessary. Note: we have not tested this switch a lot and therefore we do not officially support it. It worked fine on my system though and I am quite confident that it will work on other systems.
  5. Hi Bryan, What's in the User Manual is all the documentation that we have on it. Please do make sure you use version 2.2.1, as it contains improvements in both documentation and software. That said, with every release we make significant adjustments to the documentation, based on the questions that we receive. So please do ask!
  6. Hello Bryan, Good to hear that you're up and running! Your output indicates that it is now indexing successfully. The "Product license not found" message seems to be a side-effect of how IntellaCmd currently checks for a license. It first looks for an Intella TEAM Manager license, and if that is not available, it will look for an Intella Professional license. This message seems to be a misleading logging statement resulting from it not finding a TEAM Manager license in your case. I'll see to it that that logging statement gets removed.
  7. Hello Bryan, It should certainly work with that product. Can you tell us: The command-line invocation that you use? You can redact e.g. folder and evidence names, this is only about the options that you use. The full output of the process, as visible in the console.
  8. Hi Bryan, Can you try launching the regular Intella? Does it start at all? If so, what product name is stated at the top of the Case Manager window (e.g. "Intella Professional")?
  9. Vound is pleased to announce the official release of Intella and Intella Connect 2.2.1. Intella and Intella Connect 2.2.1 are available from the Downloads section in the Vound Support Portal, after logging in with your email address and password. Users with a 2.1.x license need to use the Dongle Manager to update their dongle to the 2.2.x license. Please read the Release Notes before installing or upgrading, to ensure you do not affect any active cases. Highlights Added a Welcome tab. Improvements supporting the large-scale redaction of items, such as queuing items for redaction based on their keyword hits, pre-generating redaction PDFs to speed up the Redaction tab’s loading time, redacting entire page ranges, and the automatic redaction of duplicates. Reorganized the right-click menus in the Table and other components. Several facets load faster. Many indexing and OCR improvements.
  10. Hello Jonas, Great to hear that the collection with two-factor authentication went smooth. I take it that you are referring to the iMessage items that are stored in the iCloud account, right? This is a recently added iOS feature that we do not support yet. It is on the roadmap though.
  11. Hello Jason, Thank you for your kind words. As you have seen already, the Intella 2.2 release features improvements and sample scripts for enhancing the items in a case using Google Cloud's services, e.g. for text categorization, image classification, translation, entity extraction, etc. Similar scripts can also be made for other vendors; Google Cloud is merely used as a running example. See the attachment for an example of image classification in a case. I am also happy to say that several of the improvements that you mention are on the roadmap for the 2.2.1 and 2.2.2 releases, scheduled for later this year.
  12. Vound is pleased to announce the official release of Intella and Intella Connect 2.2. Intella and Intella Connect 2.2 are available from the Downloads section in the Vound Support Portal, after logging in with your email address and password. Users with a 2.1 license need to use the Dongle Manager to update their dongle to the 2.2 license. Please read the Release Notes before installing or upgrading, to ensure you do not affect any active cases. Highlights Added support for basic case merging. Items can now be exported to a new case. Case templates enable quick initialization of a new case. Added a GDPR Insight info panel, listing privacy-sensitive data found in the case. Added command-line options and samples for scripting and analysis purposes. Sample scripts are provided that enhance case data using Google Cloud AI services. Added support for indexing Windows 10 Mail. Added a Show Family search option.
  13. For the moment that is indeed not possible. Please note that the Table does have a Message ID column. So you can show the Message IDs and sort on them. If you have a large amount of Message IDs to deal with, you can try the following: List all items in the table and add the Message ID column. Export all results as a CSV, using only the Item ID and Message ID columns. Use Excel or some batch script to filter the CSV so that it only contains the rows with a matching Message ID. Remove the Message ID column from the CSV, so leaving only the Item IDs. Import this file in the Item ID facet. This gives you the set of items with a matching Message ID.
  14. Vound occasionally issues "patch releases", to quickly address issues of a severe nature. Below is a list of the patch releases and a description of their changes. The following patch releases have been issued since the 2.3 release: 2.3.0.1 Fixed an error that might occur when using an export template that contains tags that are not present in this case (item report export type only). Fixed an issue when Intella doesn't index certain draft or deleted emails without body, senders and recipients in EDB containers. The following patch releases have been issued since the 2.2.2 release: 2.2.2.1 Fixes a backwards compatibility issue introduced in 2.2.2 that concerns items redacted with an older Intella Connect version. When a crawler process crashes, the item IDs of potentially incompletely indexed items are now logged. The following patch releases have been issued since the 2.2.1 release: 2.2.1.2 Fixes an issue with the Branding page not loading properly when navigating to it on a clean installation. 2.2.1.1 Fixes an issue with the Previewer not loading item metadata correctly when using quick tag buttons in combination with the "Go to next item after tagging" option. The following patch releases have been issued since the 2.1.1 release: 2.1.1.3 Improvements in persisting batch status and progress making it more fault tolerant. Improvements aimed to discover and present ORGANIZER and ATTENDEE properties as a part of PST and EDB calendar items. Improvements that prevent or reduce data loss and case corruption in case of system or network failure. 2.1.1.2 Improvements to make indexing and case conversion more fault tolerant. Fixes an issue with redactions on rotated PDF documents not exporting properly. Fixes an issue with the installer taking a long time to complete, blocking on the HASP driver installation. Fixes an issue with a new source failing to be added when the "Analyze Paragraphs" option was not set on. 2.1.1.1 Fixes an issue with item download when no original content was present, but load file Image was Improves the speed of I/O operations for certain case files stored on a Network Drive Improves and simplifies communication between Intella Connect and Intella Node which also allows to selectively switch SSL support ON and OFF for each individual Node Fixes an issue with old login URLs not working properly. They will now be redirected to an updated login URL. The following patch releases have been issued since the 2.1 release: 2.1.0.1 Fixes a fatal error (BufferUnderflowException) that affects the entire indexing of an EDB file. 2.1.0.2 Fixes a fatal error (UnsupportedOperationException) that affects the entire indexing of an EDB 2010 file. Fixes a case conversion issue, concerning cases made with 1.9.x that failed to migrate at all. 2.1.0.3 Fixes a case conversion issue, resulting in parts of the case data not being migrated to the new case. Fixes excessive use of non-deleted temporary files when processing an EDB file. The following patch releases have been issued since the 2.0.1 release: 2.0.1.1 Fixes a cryptic error that occurs when re-indexing a case without the evidence files present, obfuscating what is actually going wrong and making it hard for the end user to resolve the situation. Fixes an issue with natively previewing items that have a single quote character in their file name. Fixes an issue with "Index new data" failing to populate the Location and Family Date attributes for items added in a subsequent indexing run. Fixes an issue with broken PST files not indexing properly. Fixes an IBM Notes validation issue. The following patch releases have been issued since the 2.0 release: 2.0.0.1 Rolls back the haspdinst.exe driver from v7.51 to v7.41, because the former appears to cause system crashes on some Windows installations. The following patch releases have been issued since the 1.9 release: 1.9.0.1 Fixes an issue with the export to PST failing to export all items. Fixes an MS Outlook validation issue. Fixes an "Error 500" error when creating new redaction profiles. Fixes an issue with some items failing to show in the Previewer. 1.9.0.2 Fixes an issue with the preferences file becoming syntactically incorrect when storing certain values. The following patch releases have been issued since the 1.8.4 release: 1.8.4.1 Adds support for the Intella P.I. product. 1.8.4.2 Fixes an issue with cases failing to open. Fixes an encoding issue when exporting non-ASCII data to a load file using ASCII encoding. The following patch releases have been issued since the 1.8.3 release: 1.8.3.1 Fixed an issue with redaction marks staying in view when moving from one item to another in the Redaction tab. Fixed an issue with the "Redact all" button adding multiple redaction marks on the same spot. Fixes an issue with the flagging functionality in the Thumbnails view not working properly. The following patch releases have been issued since the 1.8.1 release: 1.8.1.1 Fixes an issue with emails getting incorrect created and last modified dates when there is another email with identical content but with different raw data present in the case.
  15. Vound occasionally issues "patch releases", to quickly address issues of a severe nature. Below is a list of the patch releases and a description of their changes. The following patch releases have been issued since the 2.3 release: 2.3.0.1 Fixed an error that might occur when using an export template that contains tags that are not present in this case (item report export type only). Fixed an issue when Intella doesn't index certain draft or deleted emails without body, senders and recipients in EDB containers. The following patch releases have been issued since the 2.2.2 release: 2.2.2.1 Fixes a backwards compatibility issue introduced in 2.2.2 that concerns items redacted with an older Intella version. When a crawler process crashes, the item IDs of potentially incompletely indexed items are now logged. The following patch releases have been issued since the 2.1.1 release: 2.1.1.3 Improvements aimed to discover and present ORGANIZER and ATTENDEE properties as a part of PST and EDB calendar items. Improvements that prevent or reduce data loss and case corruption in case of system or network failure. 2.1.1.2 Improvements to make indexing and case conversion more fault tolerant. Fixes an issue with the installer taking a long time to complete, blocking on the HASP driver installation. Fixes an issue with the CSV export and table column chooser not working correctly when tag groups or content analysis columns were deleted. Fixes an issue with the "Restore Annotations" function not working correctly. 2.1.1.1 Fixes an issue with version update notifications not working properly Fixes an issue with an occasionally error being thrown in Previewer Improves the speed of I/O operations for certain case files stored on a Network Drive The following patch releases have been issued since the 2.1 release: 2.1.0.1 Fixes a fatal error (BufferUnderflowException) that affects the entire indexing of an EDB file. 2.1.0.2 Fixes a fatal error (UnsupportedOperationException) that affects the entire indexing of an EDB 2010 file. Fixes a case conversion issue, concerning cases made with 1.9.x that failed to migrate at all. 2.1.0.3 Fixes a case conversion issue, resulting in parts of the case data not being migrated to the new case. Fixes excessive use of non-deleted temporary files when processing an EDB file. The following patch releases have been issued since the 2.0.1 release: 2.0.1.1 Fixes a cryptic error that occurs when re-indexing a case without the evidence files present, obfuscating what is actually going wrong and making it hard for the end user to resolve the situation. Fixes an issue with "Index new data" failing to populate the Location and Family Date attributes for items added in a subsequent indexing run. Fixes an issue with broken PST files not indexing properly. Fixes an IBM Notes validation issue. The following patch releases have been issued since the 2.0 release: 2.0.0.1 Rolls back the haspdinst.exe driver from v7.51 to v7.41, because the former appears to cause system crashes on some Windows installations. The following patch releases have been issued since the 1.9 release: 1.9.0.1 Fixes an issue with the export to PST failing to export all items. Fixes an issue with the "Open in native application" option not working on some item types. 1.9.0.2 Fixes an issue with the preferences file becoming syntactically incorrect when storing certain values. The following patch releases have been issued since the 1.8.4 release: 1.8.4.1 Adds support for the Intella P.I. product. 1.8.4.2 Fixes an issue with cases failing to open. Fixes an encoding issue when exporting non-ASCII data to a load file using ASCII encoding. The following patch releases have been issued since the 1.8.3 release: 1.8.3.1 This releases uses the same baseline code as Intella Connect 1.8.3.1. There are no fixes in here that affect the desktop product. The following patch releases have been issued since the 1.8.1 release: 1.8.1.1 Fixes an issue with emails getting incorrect created and last modified dates when there is another email with identical content but with different raw data present in the case.
×
×
  • Create New...