jon.pearse

Information can be found under: https://support.vound-software.com/help/en-us/8-installation/69-running-intella-within-a-hyper-v-virtual-machine-environment

Hi John, Sorry, I read the heading of the thread literally and answered based on Irrelevant items, which is a feature that we have in Intella. Adam has provided a good answer. I hope this helps.

Hi John, You can hide the irrelevant types by using the 'Hide irrelevant' button next to the Deduplicate button. A list of what is classed as irrelevant can be seen in the Irrelevant items tab (go to File > Preferences).

Information can be found under: https://support.vound-software.com/help/en-us/1-troubleshooting/68-troubleshooting-checklist

Hi, Thanks for the explanation. I don't think there is any way to allow a user to have permissions to the Search tab, but restrict them to viewing activities only. The only work around that I can think of is for the "common reviewer", or an admin to create batches of the items which were tagged by the "common reviewer". The "read-only" reviewer then only gets the Review permission so that they can review the documents, and make a judgement as to whether they are tagged correctly or not.

Hi, Can you provide more information about the 'read only' user that you want to create please. Being able to add, delete and modify existing tags from documents does not sound like a read only user. Can you give some more examples regarding what this user can, and cannot do please.

Information can be found under: https://support.vound-software.com/#knowledge_base/1/locale/en-us/answer/67/

Information present under: https://support.vound-software.com/help/en-us/1-troubleshooting/65-sample-checklist-for-users

Hi Jason, Currently it is a single threaded process. This may be changed to a multi threaded process in a future version.

Hi Jason, It is shown in the 2.0 release notes. "Added PDF and Thumbnail pre-generation tasks". https://www.vound-software.com/docs/2.0/Intella-Connect-2.0-Release-Notes.pdf

Hi Jason, This feature is actually in the current release (2.0.1.1) which you can download from the support portal. We are aiming to release version 2.1 next week is all goes well with testing.

Hi Jason, We have added a feature that allows the user to pre-generate PDFs for specific files. This is a background task that you can setup and run before document review. If your review dataset has a lot of Word docs, PDFs etc, you can group all of these files into a tag. You can then run a background task (under Settings) to pre-generate the PDF view for these items. Once complete, the documents will load instantaneously during review process.

Hi Daniel, Outlook for MAC is not currently supported. We advise customers to convert the .olm files using a 3rd party tool to a format that is supported by Intella.

Hi George, Can you check these items to make sure they a not a factor for the slowness. 1) Could your AV be causing the slowness issue during the export? May be try exporting with the AV disabled. 2) Is your disk fragmented or near full?

Hi George, Are you using the latest version of Intella (2.0.1.1)?

Hi Jason, We are getting close to the 2.1 release. This has the ability to remove complete sources. A snapshot should be available in approx a week. We will let you know when this is available.

Hi George, What type of system/spec to you have? Also, have you moved the evidence or case data from when you initially created the case? These speeds do not sound right. It could be an I/O issue. Are the case and evidence drives local to the system (e.g. mounted within the system). USB connected drives can be a factor and we recommend not to use them. Jon

Answer can be found in: https://support.vound-software.com/#knowledge_base/1/locale/en-us/answer/64/

Hi gcahlik, In the current version there is no automatic function to export tagged items into another case. The work around is what you have already mentioned - export the items in original format, then index these items in a new case. May be others on the forum have done it a different way, and can share their workflow with us? This question of privileged material has been asked before. It is likely that we will include such functionality in a future version of Intella. Jon

Licensing Intella and/or Intella Connect in the cloud Introduction Many software vendors offer cloud services at reasonable rates. The benefits are that the customer can pick and choose which services they want to use, based on their business requirements. Customers do not have to maintain expensive IT infrastructure, which reduces the number of IT staff needed and the cost of the firm. Given the benefits, many firms are moving all of their IT services to the cloud. We are now starting to receive increased queries regarding running Intella or Intella Connect in a cloud environment. A cloud server is just another computer. Intella and Intella Connect should run fine on these systems provided that the system's hardware/software meets, or is better than, the recommended specifications. The achilles heel of running Intella in the cloud is that we use dongle-based licensing. A physical license dongle needs to be plugged into the system running the Intella software. The issue with the cloud server is that it is normally vast distances away (e.g., overseas) from the end user. There is no way to walk a dongle 'down the road' to the cloud vendor. Even if the vendor is located just 'down the road', they are likely to have policies in place which restrict physical devices (such as a license dongle) from being plugged into the host system. This post discusses using a cloud system to run Intella or Intella Connect, and to be able to obtain a license located on a physical dongle which is not plugged into the cloud. Physical Layout Intella and Intella Connect use physical dongles for licensing, a dongle (with a current license) still needs to be available for these applications to operate. That said, the dongle does not necessarily need to be plugged into the cloud system. We provide network dongles that are designed for applications to obtain a license over a network. Furthermore, the network dongle can be configured to work across different subnets. If the cloud system has access to your local system, then the network dongle can be plugged into your local system. The cloud system is then configured to obtain a license from the dongle in your local system. Prerequisites Before you begin with configuration, there are some things to check: Make sure that port 1947 is not blocked by any firewall (or other security software) as the Sentinel LDK License Manager uses it for communication. Make sure that the server and client machines can ping each other. You may need technical help from your IT and network administrators during this setup. Make sure that they are available to assist you should they be required. Local System Configuration The local system that holds the network dongle needs to have the Sentinel LDK License Manager installed and running on it. This is as simple as installing Intella or Intella Connect on the local system. The necessary drivers and applications for the License Manager will be installed during the Intella installation. Install Intella or Intella Connect on the local system. Once you have confirmed that Intella starts with no HASP or dongle issues, you need to make some changes in the Sentinel Admin Control Center (SACC). The first setting is located in the 'Access from Remote Clients' tab which can be accessed at this link: http://localhost:1947/_int_/config_from.html. Make sure that the setting for 'Allow Access from Remote Clients' is checked. Click Submit if you have made changes. The second setting is in the Basic Config page (http://localhost:1947/_int_/config.html). Make sure that the setting for 'Allow Remote Access to ACC' is checked. Click Submit if you have made changes. When prompted, set a password for remote access. Once the installation is complete, test that everything is set up and working properly by running Intella or Intella Connect. If you encounter any HASP or licensing issues, you can troubleshoot these issues with the information in this article. Cloud System Configuration When the settings on the local system are complete, you can go ahead and configure the cloud system. The steps are like the local system. Install Intella or Intella Connect on the cloud system. You now need to configure the ACC so that the cloud system can access the local system to pick up a license. The first setting is the same as shown at step 3 for the local system (above). In the Basic Config page (http://localhost:1947/_int_/config.html), make sure that the setting for 'Allow Remote Access to ACC' is checked. The second settings are located in the 'Access to Remote License Manager' tab (http://localhost:1947/_int_/config_to.html). (i) Check the setting for 'Allow Access to Remote Licenses'. (ii) Check the setting for 'Broadcast Search for Remote Licenses'. (iii) Enter the IP address for the local system in the 'Remote License Search Parameters' field. Once done, click Submit. To test the communication between the cloud system and the local system, open a browser on the cloud system, and type the following in the Address bar: http://localhost:1947/_int_/devices.html. Verify that you can view the network dongle which is plugged into the local system. If you can see the network dongle, then this verifies that the cloud system is able to communicate with local system at a HASP level. When Intella or Intella Connect is opened on the cloud system, a license will be obtained from the local system. This will allow the application to run.

Hi Graeme, I'm not sure why the hits are not highlighted. I will check with our technical team. In the interim you could run several searches to narrow down and highlight the hits for the search criteria. 1) Run a search for research~ and run a separate search for centre~ 2) Run a search for "research~ centre~" 3) Review the items in the intersecting cluster The hits will be highlighted in the document from step 1. Step 2 narrows the number of documents down so you should only get relevant hits for the phrase. I hope this helps Regards Jon

Hi llanowar, Can you post the first 2 lines of the DAT file, and also the first line of the OPT file please. The file/folder paths are what we are interested in. If there is any confidential information in the second line of the DAT file, this can be changed or redacted before you post it.

Hi, I see that this was resolved in your support ticket. I'm not sure if you have seen this it not. We have some information, and a video on load files and overlays at the link below. This may be useful if you are new to creating load files in Intella. http://community.vound-software.com/index.php?/topic/402-creating-a-load-file-in-intella/

Introduction: The Tasks feature allows the user to run predefined processes either directly after the indexing process has completed, or at a later stage. In this article we will look at using the Tasks feature to automate the searching, filtering and export processes associated with an eDiscovery matter. Note: This example is for demonstration purposes only. Your searching, filtering and export requirements will likely be different to what is used here. Also, we start the tasks from the point of running searches. This presumes that all other required checks and pre-processing tasks, such as investigating items that were not processed (e.g. OCR and encrypted items) have been completed. Basic ED processing/filtering steps: For this example we will cover the following basic eDiscovery processing steps. · Search/filter the data in the case using a keyword list and a date range. · Show the top level parents for the items that were respondent to the searches. · Deduplicate the top level parents. · Return all family items. This shows email attachments and all embedded items. · Remove the irrelevant items such as folders, containers, embedded items and non document types. This leaves the remaining items which are ready for review. · Export the document ready for review to a load file. Creating the Tasks: In Intella Desktop the Tasks wizard is located under the File menu. Start the Task wizard and click on the New button in the Tasks window. Type a name for the task. I have used a prefix of '01 -' in the task name. Using a sequential prefix makes it is easier to see the order for the tasks. Step 1 allows you to search for items. In this case we will select the 'Keyword list' option from the dropdown. Once done we can either select a keyword list which is already in the case, or we can load a keyword list from a file. Next, click on the 'Add' button to the right and select 'Date' from the dropdown. Enter the date parameters. Step 2 allows the user to refine the search. We don't use Step 2 for this task. Step 3 allows the user to apply actions to the results. In this case we are going to tag the respondent items. Hierarchy tags are available so we will set all of the output tags under a top level tag named 01 - eDiscovery Processing, e.g. 01 - eDiscovery Processing/01.01 - KWSearch-DateRange The second task is configured to return all of the parent items from the items which were respondent to the search and date filter. Like we did for the first task, click on New and type a name for the task. In Step 1 we want to select the tag that holds the items that were respondent to the search criteria. This is basically the starting dataset to be filtered further. Note that we tagged the results in the first task into a hierarchical tag. This tagging structure must be maintained for the starting dataset in Step 1 of this second task. E.g. 01 - eDiscovery Processing/01.01 - KWSearch-DateRange Click the Add button for Step 2 and use the dropdown to select the 'Identify parents' option. Select the Top level parents radio button and check the check box for 'Add items that are already top level parents'. In Step 3, tag the items into a new tag under the tag group '01 - eDiscovery Processing', e.g. '01 - eDiscovery Processing/01.02 - Show Top Level Parents'. Once the top level parents have been identified, we need to create a task to deduplicate the top level parents. Create a new task and name it appropriately. In Step 1 select the tag that holds the top level parent items. Click the Add button for Step 2 and use the dropdown to select the 'Deduplicate results' option. In Step 3, tag the items into a new tag under the tag group '01 - eDiscovery Processing'. Now that we have our top level items deduplicated, we need to bring back the family for those items. Create a new task and name it appropriately. In Step 1 select the tag that holds the deduplicated top level parent items. For Step 2, click the Add button and use the dropdown to select the 'Identify children' option. Select the 'All descendants' radio button, and check the 'Ignore folders' checkbox. In Step 3, tag the items into a new tag under the tag group '01 - eDiscovery Processing'. The next step is to add the top level parents and family items into one tag, then clean up the dataset to remove any embedded items and containers such as zip files and PST files. We have already extracted the content of these files so we no longer need the container or zip files. Click on New and type a name for the task. In Step 1 select the Match dropdown, and select 'Any' from the list. We need to set this to 'Any' as we will be adding all of the date from the two tags, we don't want just the intersection of the tags. Still on Step 1, enter the tag name that holds the deduplicated top level parent items. Also, click the Add button to the right and enter the tag name that holds the family items. Click the Add button for Step 2 and use the dropdown to select 'Suppress irrelevant items' In Step 3, tag the items into a new tag under the tag group '01 - eDiscovery Processing'. We now have all of our respondent data de-duplicated and the family items returned. Although we have cleaned out the irrelevant items, there may be other file types in the dataset that we need to clean out. These could be items located in System and Others categories under the Type facet. We need to create a saved search for this task as we will be using Exclude searches. To create the saved search for this process: · Run a search over the tag the contains the items with the irrelevant items removed. · Run Exclude searches over the Containers, System and Others categories under the Type facet. Once complete, click on the Save button in the Results box on the right, and enter a name for your saved search. E.g. '02 - Excluded: System, Others, Containers' Once done, open the Tasks wizard again. Click on New and type a name for the task. In Step 1 select the Saved Search option, and use the second dropdown to select the newly created Saved Search. Note that a Saved Search can also be loaded from a file. We don't use Step 2 for this process. In Step 3, tag the items into a new tag under the tag group '01 - eDiscovery Processing'. This concludes the searching and filtering tasks to provide a dataset ready for review/export. Exporting the results: Now that we have our dataset ready for export, we can go ahead and create a task to export the data to a load file. Click on New and type a name for the task. In Step 1 select the tag option, and enter the tag name that holds the items which are ready for review. We don't use Step 2 for this process. In Step 3, select Export from the dropdown. Select your pre-configured load file template from the list. Once the tasks have been created and run, they should look like this.

Hi, We have this improvement to the GMail collection feature scheduled for a future version. This may be released in version 2.2.