PrimozKokol

Hi Chris, Please follow the instructions below: 1. Do Email Address facet query: All senders -> [person X] This will result in a cluster representing all emails sent by [person X]. 2. Expand Email Address facet -> All receivers branch 3. Right click on All receivers branch and select Organize -> Sort by item count 4. Click 'Show only highlighted values' icon at the bottom of Email Address facet 5. The last step is to just export the results by right clicking on All receivers branch and selecting 'Export values...'

We don't have any experience with ECC but maybe this blog post: To ECC or Not To ECC (and discussion underneath it) will help you to decide on this.

Hi Lukasz, I suggest you to read through these threads: Selecting a Computer to Host Your Intella Software Connect Hardware Requirements The last one is targeted at Intella Connect but I believe you can get some usable information there anyway. Please understand that it's really hard (or near impossible) to predict how much different hardware combinations will improve processing speed because of countless variables. I guess you've already got a sense of that by reading through the threads above. Anyway, there are few guidelines/recommendations in the order of effectiveness: SSD: we recommend using SSD drives over HDD RAM: 32 GB should be (just) OK for indexing with 6 cores, having more may help with certain types of evidence CPU: moving from 4 to 6 (or more) cores will help to reduce indexing time, provided that the machine has sufficient RAM GPU: not a factor Note that there is no need to switch to Windows 10 as far as Intella is concerned. But given the fact that mainstream support for Windows 7 ended in January 13, 2015 you might consider upgrading it anyway. With regards to your last question - as already said it's hard to predict what will be the increase of performance when using: i9 instead of i7 64GB RAM instead of 32GB so we can't give you any definite answer on that.

Did you maybe try to open the resulting PDF in some standalone PDF viewer? Is the second page still missing in that case?

Hi AdamS, Are you experiencing this with Intella or Intella Connect? Are you referring to: ... when saying that this only occurs when selecting the "print preview view"? Also did you try to open the resulting PDF in some standalone PDF viewer (i.e. Adobe)?

Hi Brendan, We cannot give you an exact date. However it is on our roadmap already.

Hi PF1, Thank you for suggestion. I will make a note of it and discuss it with our dev. team.

Hi Todd, This should be possible with the use of Identities facet. Please follow the steps below: Switch to Social graph view Set Edges to Only Identities Use Identities facet: Search for Identity A Search for Identity B Select the edge connecting Identity A and Identity B

Hi KTD3287, In order to index only Skype conversations from specific source the alternative approach to the one described by Jon is to add just SQLite type as this is a database type which is used by Skype to store it's data. The thing is that Intella can't know whether certain SQLite database is actually produced by Skype unless it's indexed - that's why selecting just "Skype conversations" doesn't have any effect at the moment. We might improve this in the future. Side note: If you want to index also SQLite databases inside archives, you have to include also the appropriate archive types.

Hi Cayerpm, Our database consists of multiple proprietary databases developed by Vound so there is no "one database" that could be effectively queried. Could you please elaborate on the problem you are trying to solve?

Hello fuzed, We had never heard of such issue before. I suggest you to open up a support ticket as we will need server log files and some additional information in order to investigate this further.

Adam, you're right. If chat messages were not selected Intella would skip them - that means that also embedded zip files would be skipped. The performance gain can be observed when un-selected data types are present in the source data (as those are not indexed in this case). For example: If we know that a data set contains registry files (which are time-consuming from indexing perspective, and give no information), we deselect Registry indexing and gain better performance.

Hi Fuzed, The safest way to achieve this would be to create an export (Original Format) of the data you want so share with the 'other side' and then create new case out of it.

I am glad you solved it. Braking a single query "john smith" OR "bob smith" OR "dav* jones" into three separate queries "john smith" "bob smith" "dav* jones" and then making use of a cluster map to find items of interest is a way to go. Similar thing can be achieved using "Include Search" (see User Manuals - 13.2.1 Including a facet value). Let's say that you phrase of interest is "john smith" - in this case you would make two queries like: "john smith" (include search) "bob smith" OR "dav* jones" (search) Doing it that way only one cluster map would be produced containing all items that contains phrase "john smith" and one or both of the phrases "bob smith" or "dav* jones". As you see the beauty of Intella is that you can achieve same thing with different approaches. Side note: There is an interesting post on "Testing keywords queries" topic that might be of interest for you: http://community.vound-software.com/index.php?/topic/134-keyword-testing-tips/

Hi CFA, It's hard to judge based on the description that you've provided whether this is a user error or something else. Running a phrase search "john smith" finds items containing "John Smith" and highlights queries properly in my test case. See example: You can check out whether search is working properly in your case by searching for "John Smith" and then checking out few items from the result set whether "John Smith" phrase is actually present. In order to provide you with more information I suggest you open up a support ticket attaching an item for which you think highlighting doesn't work properly (or at least provide us with some screenshots demonstrating the issue).