Jump to content

All Activity

This stream auto-updates     

  1. Yesterday
  2. Last week
  3. Hi fuzed, It's most likely a limitation of the hotmail server. Those usually don't allow to download everything in one ago. We usually recommend to download such data with a mail client first (or ome 3rd party app), and then index the result (mbox, pst, etc) with Intella. Also, some mail servers such as gmail allow you to download data separately into a file. We are not sure if such feature exists for hotmail though, so you may need to look into that.
  4. All, is there a way with intella to collect imap accounts, as I've been provided with the username and password, but Intella does a very small number of messages and then appears to just time out - its sat for 4 hours and got me a very small number of items. I'm assuming some sort of timeout is in place, is there much that can be done to get the mails in the account?
  5. @AdamS and @jon.pearse, firstly many thanks for responding to my query below. I'd neglected this project a little but I'm looking at it again and I'm almost there. Just one query though. So, I have used an AI translation provider to translate documents and have the translated files named by their ItemID ready for importing via the --importText CLI option. This works fine however the content isn't as I hoped when verifying it in Intella. Checking one of the .txt files that has been imported, it has the below phrase in:- "Dans les années 2000, la société pharmaceutique" however when this is imported via the --importText CLI option, it reads as the below in the 'Imported Text' tab:- "Dans les ann es 2000, la soci t pharmaceutique" It would appear that the handling of foreign characters such as the 'é' aren't being imported correctly and are being replaced by a whitespace. I'd imagine this is an encoding issue. Is there anything I can do to address this? I'm just conscious that if a reviewer searches on any 'foreign' characters, it may not return hits, so for example, if the reviewer searches on 'société pharmaceutique', there would be no hits when technically this is correct but isn't correct at the same time too (if that makes sense).
  6. Earlier
  7. It would be great if a user can select files in table view and then right-click and choose “show duplicates.” This works as at an individual file level but not at a multiple file level. Our workaround at the moment is to export the MD5s into a CSV and then reupload it.
  8. Introduction: We have had a number of customers asking us - How do I upgrade to the latest version of Connect, and keep all of my settings? This post will look into how this can be done, and what to look out for when upgrading Connect to the latest version. Why upgrade to the latest version: It is always best to install and use the latest version of our products. With any software development, it is near impossible to test every scenario in which the software will be used, and what type of data is indexed with the tool. Although we have a vigorous testing regime for our products, some customers find issues which they report back to support. These issues are generally fixed, and added to the next release. Therefore, using the latest version will give you all of the fixes from all previous versions. Another good reason to upgrade is because the latest version has a number of new features that are not in previous versions. These features can make processing faster, can make analysis of the data easier, and can add better functionality to the tool. Upgrading Connect: There is no problem with installing the latest version of Intella Connect on the same server. Note that this will need to be installed next to the current version. E.g. as long as the new version is installed in a different folder, the existing version should not interfere with new version. In addition, there is no need to uninstall the previous version. When installing a new version of Connect, we make sure that any configurations from the previous version are also migrated over. We often keep old configuration as backup as well, so your previous configurations are not lost. Installing the latest version of Connect is quite straight forward, but you should be aware of these aspects: Make sure that you are always using the same Windows Account when installing different versions of Intella Connect. The configuration and settings for your current version are stored in user-sensitive location, and those locations will not be available to other user accounts. E.g., we have seen cases when users were installing version 2.0 with the "John" user account, then later installed version 2.1 with the "Administrator" user account. They were surprised to see that they ended up with a clean instance of Connect, with all default configurations and settings. You need to be careful when installing Connect as a Windows Service. There is only ONE Intella Connect Windows Service allowed on the system. Installing a newer version of Connect as a service should overwrite the paths to executables in Windows Services. Once the install process is complete, and the service is restarted, there should be no issues. However, we have seen a number of cases when this did not work as it should have. The outcome is that the service was still pointing to the old version of Connect. In those situations, you should refer to this section of the Administrator's manual on how to manually update the service. https://www.vound-software.com/docs/connect/2.3.0/admin/03_01_connect_as_service.html#manual-un-installation-intella-connect-windows-service Note: From version 2.3.1 we will have an extra check during the installation process that will prevent the installation process from continuing if you have not shutdown the service manually. It is always best to run the latest version of all of our tools. This also applies to Intella Node. Having both Connect and Node on the same version will help when troubleshooting any issues. The risk of any incompatibility issues between Connect and Node are reduced when both products are on the same version. Before you start the upgrade: You should consider the following before you start the Connect upgrade process: With every release of Intella and Connect we provide Release Notes. The very last section of the release notes is the 'Upgrade Notes' section. In that section we list information regarding backwards compatibility with earlier case versions. This section also points out any features which may be limited due to the version upgrade etc. We always suggest backing up your Connect/Node systems before undertaking any upgrades. This minimises the risk of downtime, as you have an avenue to go back should you have any issues with the upgrade process. You should make a backup of these folders (which contain entire configurations) prior to proceeding with the upgrade. "C:\Users\CONNECT_USER\AppData\Roaming\Intella" and "C:\Users\CONNECT_USER\AppData\Roaming\Intella Connect" After the upgrade is complete: Once the upgrade process is complete, start Connect and check that Connect is reporting the correct version. You can do this by clicking on the Admin tab and selecting the 'About Intella Connect' option from the dropdown list. If the latest version is not running, there may be old version of Connect still running. Migrating keystores and self-signed SSL certificates: Once the new version of Connect is running, you may need to reconfigure some advanced setting like SSL. This should be straight forward if you have purchased your SSL certificate from a well known provider like Go Daddy etc. That said, we do see a number of issues with SSL certificates coming through support. But, these issues are mostly related to when the user/company manages their own certificates. In these cases the users report that the upgrade went well, but they cant get SSL to work. In the SSL wizard they get errors like this: "Unable to activate the keystore because it's not valid. Details: Keystore contains multiple certificates, but they were not imported to the private key chain". The issue is that unlike self managed certificates, certificates from a well known providers are generally added to Java's trusted keystore. That means that certificates from a well known provider will work 'out of the box' when setting up SSL in Connect or Node. When users/companies create their own self-signed certificates, they usually create two Certification Authorities (ROOT & Intermediate), and then let the Intermediate CA issue the certificates. But, Java doesn't know anything about ROOT & Intermediate certificates for that company, and these certificates are not automatically trusted. Therefore, the self-signed certificates do not work when a new version of Connect or Node are installed. Note: When you are upgrading Connect or Node, the existing (trusted) Java store is wiped out, and replaced with a clean one. For our products (Connect & Node) to trust the self-signed certificates, you have to add the certificates to the trusted CA store of the JAVA RUNTIME that we shipped with the installer used for the upgrade. This process is described in the Connect administrator's manual at the link below. https://www.vound-software.com/docs/connect/2.3.0/admin/04_03_01_ssl_guide.html#advanced-using-self-signed-certificates So in short, if you are generating your own SSL self-signed certificates, then you will need to update Java's trusted CA store (for both, the Connect and Node systems) after each upgrade.
  9. Flexible Reporting with Intella 3 December, 2019 | Online In Intella 2.3 we introduced flexible reporting functionalities. These features allow different data types to be configured in independent, customisable sections, which provides great flexibility for report creation in Intella. In this webinar, you will learn how to use the reporting tool to customize and produce professional looking reports. You can download the PDF notes here, or view the full video recording below:
  10. Memory Management in Intella 5 November, 2019 | Online There are several memory settings in Intella that allow you to allocate more memory and crawlers to the indexing phase of your case. In this webinar, you will learn how—and when—to configure those settings to ensure you experience optimal performance. Note: The memory settings mentioned in this webinar are also configurable in Intella Node. You can download the PDF notes here, or view the full video recording below:
  11. Vound is pleased to announce the official release of W4 1.0.4. W4 1.0.4 is available from the Downloads section in the Vound Support Portal, after logging in with your email address and password. Users with a W4 1.0.x license can use this version. Please read the Release Notes before installing or upgrading, to ensure you do not affect any active cases. Highlights Added Geolocation view, showing the geographic locations of search results, e.g. based on GPS data and IP addresses. Better support for Windows 10 artifacts (BAM Cache, RecentApps). Added support for BitLocker and APFS disk images. Added support for Skype 14.x chat messages. Release Notes W4-1.0.4-Release-Notes.pdf For additional information, please visit our W4 website website.
  12. I renamed the button to "Finish source management", to avoid confusion. This change will be present in upcoming 2.3.1 release.
  13. 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.
  14. When a data source has been added to a case and indexing is complete, the node that was used to index does not automatically "release" itself or make itself available for any other processing. Also, the Admin cannot share the case as the Node has it "locked". The intended workflow is to click the "Close Case" button to (1) release the node for processing and (2) release the case for sharing. The term "Close Case" typically means we’re finished from the standpoint of legal involvement and we’re free to delete the project from the system; the matter is adjudicated, a settlement was reached, we fired the guy, and like that. Suggest renaming this button to something like "Release Node" or "Finished" - or, assuming there aren't other programmatic reasons to keep it connected, just *automatically* release the node when indexing is complete without requiring user inputs.
  15. 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.
  16. 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.
  17. Intella 2.3 lets the user specify crawler resources to be used. This is good and bad. Our feature requests: - Add back the ability to configure the number of crawlers and crawler memory allocation to the inj config files. - Add the option / checkbox in the case config to specify that the Intella installation-specific limits should be used for processing this case. - Use the crawler and memory allocation specified in the config files as an upper limit to prevent over-allocation of resources. Background: In our team we have several people running Intella cases on system with differing HW specs. A crawler config that might be perfectly fine for one system will bring down another system to its knees, crashing not only the running Intella processing job, but also any other task that might have been running on this system.
  18. Neil it would be a simple matter to use Intella's inbuilt ability to detect foreign language documents, isolate the 5000 Spanish documents, then export only those documents into the load file.
  19. Hi Neil, The user manual has more details about using the CLI feature. You could try some of the follow options mentioned in the manual. That would allow you to use any facets including the language facet: > 27.2 Command-line arguments > -et, -exportText – Export the extracted texts to a folder. The options -matchQuery, -savedSearch, -deduplicate and -exportDir can be used to control this operation. The resulting files will be named based on their item ID, e.g. 123.txt. > -ss, -savedSearch [File] – Can be used to limit the exported items to those that match the specified saved search. The argument is the path to an XML file holding the saved search. Such a file can be exported from the Saved Searches facet. This allows for using other facets, such as the Date and Type facets, and to combine queries.
  20. Hi. I'm aware that Intella v2.2+ allows users to export all items as text files using the -exportText parameter. Is there a way to add a further parameter prior to this so that only text of a specific language is exported? For example, I may have a case with 10,000,000 text items but only 5000 are Spanish and I want to selectively export these 5000 using -exportText and translate them using a third-party provider. Is it possible to add this extra layer specifying a language before running -exportText? Thanks
  21. Hi Qasim, You may be using an older version of Intella Desktop and that is why you are seeing the additional metadata. We have tested this in version 2.3 and only the preview is printed and nothing else (unless there are attachments and you choose to report those as well).
  22. The Print Report button opens a print dialog that shows the native rendering of the item with a minimal amount of metadata. If the item has attachments, you are asked if these should also be printed. This button therefore has the same functionality in Intella as it does in Connect, but indeed the Connect user manual needs to be changed to reflect this. I will make sure to change the online version of Connect user manual and for future versions, but the PDF version of the Connect user manual that you already have cannot be changed remotely. Sorry for inconvenience.
  23. In Intella desktop when the print report option was select all of the tabs for the item were printed into the pdf e.g. contents, properties etc... but in Connect on the preview is printed and nothing else - only one tab is being printed in the print report option; even though the user manual says that the print report option will print all of the tabs. Is there a specific setting that I am not aware of or does something extra need to be done? Thanks
  24. Hi llanowar, Thanks for testing W4! At the moment, all timestamps on the "Events" view are always shown in your current timezone. The source timezone setting only applies to timestamps in the table and the properties tab. The reason we did that is because the Events view can display data from multiple sources which might come from different timezones. In the next version we'll add an option to select the timezone for Events view.
  25. Chris the only time I've seen this before was when the indexing process was interrupted or failed to complete properly. I would try reindexing (if you haven't already). Also for urgent issues I'd always suggest starting a ticket or emailing support directly, as much as the team try to monitor and reply here I have noticed that from time to time they are not as active as I'd not they'd like to be. I suspect close to update release time they get caught up in the work and can't be here as much....
  26. Hi Jon, do you know if this is high on the priority list to fix, could I humbly suggest bumping it up if it's not? While the work around is simple enough for a couple of documents it's not really something I'd like to contemplate on your average discovery matter with thousands (tens of) documents. Added to that I feel safe in thinking just about any set of documents is going to have this issue. Is there a way for us to identify documents which may have landscape pages en masse with Intella currently?
  1. Load more activity
×
×
  • Create New...