Jump to content

Michael Delgado

IPRO Employee
  • Posts

    46
  • Joined

  • Days Won

    2

Everything posted by Michael Delgado

  1. Hello, Thank you for your patience, I have listed below the available commands and an example that be used for a silent installation: setup.exe /s /v" /qn addlocal=Thirdparty,View,IPROBuild" /v"INSTALLDIR="C:\Program Files (x86)\Ipro Tech"" Thirdparty -- This is always required to install the prereqs View iNet PremiumScan VirtualJuke Replicate ReportsUtilities IPROBuild IPROPrint IPROOCR VCodeServer VCodeRemote VCodeAdmin Publish Workstation Thank you, Michael Delgado Escalation Engineer
  2. Hello, Thank you for your patience, I have listed below the available commands and an example that be used for a silent installation: setup.exe /s /v" /qn addlocal=Thirdparty,View,IPROBuild" /v"INSTALLDIR="C:\Program Files (x86)\Ipro Tech"" Thirdparty -- This is always required to install the prereqs View iNet PremiumScan VirtualJuke Replicate ReportsUtilities IPROBuild IPROPrint IPROOCR VCodeServer VCodeRemote VCodeAdmin Publish Workstation Thank you, Michael Delgado Escalation Engineer
  3. Hello, Thank you for your patience, I have listed below the available commands and an example that be used for a silent installation: setup.exe /s /v" /qn addlocal=Thirdparty,View,IPROBuild" /v"INSTALLDIR="C:\Program Files (x86)\Ipro Tech"" Thirdparty -- This is always required to install the prereqs View iNet PremiumScan VirtualJuke Replicate ReportsUtilities IPROBuild IPROPrint IPROOCR VCodeServer VCodeRemote VCodeAdmin Publish Workstation Thank you, Michael Delgado Escalation Engineer
  4. For a Streaming Discovery job, the way to filter out Thumbs.DB file from being export would be to uncheck the "Compound Document" option located under the "Unknown" Category on the Filter Options tab. The Thumbs.DB file will still be listed in the discovery report but it will be excluded from the export. [ATTACH=CONFIG]n2154[/ATTACH]
  5. For a Streaming Discovery job, the way to filter out Thumbs.DB file from being export would be to uncheck the "Compound Document" option located under the "Unknown" Category on the Filter Options tab. The Thumbs.DB file will still be listed in the discovery report but it will be excluded from the export.
  6. The below steps can be used to change the location where CA looks for and stores newly created Indexes. It also will store the ND and Email Threading staging area data here as well. 1. Stop the CA site using the shutdown.cmd located in the BIN folder 2. Navigate to "C:\CAAT\etc\itemstore.properties" 3. Open the file in text editor, locate the following section and make the following changes: Current: device-caat=C\:/CAAT default-device-name=caat show-device-prefix-on-api=true Changed to: #device-caat=C\:/CAAT #default-device-name=caat #show-device-prefix-on-api=true device-caat2=//servername/ecapture/Analytics/ default-device-name=caat2 show-device-prefix-on-api=true 4. Important to note that any backslashes in the file path need to be reversed for it to work 5. Start the site using the startup.cmd located in the BIN folder 6. Navigate to the new network path > validate it contains a .ufx folder and a @README.txt file 7. In the root of the new folder copy in all the indexes folders 8. Start the site using the startup.cmd located in the BIN folder 9. Connect to the CA site nexus portal to verify the indexes now show
  7. The below steps can be used to change the location where CA looks for and stores newly created Indexes. It also will store the ND and Email Threading staging area data here as well. 1. Stop the CA site using the shutdown.cmd located in the BIN folder 2. Navigate to "C:\CAAT\etc\itemstore.properties" 3. Open the file in text editor, locate the following section and make the following changes: Current: device-caat=C\:/CAAT default-device-name=caat show-device-prefix-on-api=true Changed to: #device-caat=C\:/CAAT #default-device-name=caat #show-device-prefix-on-api=true device-caat2=//servername/ecapture/Analytics/ default-device-name=caat2 show-device-prefix-on-api=true 4. Important to note that any backslashes in the file path need to be reversed for it to work 5. Start the site using the startup.cmd located in the BIN folder 6. Navigate to the new network path > validate it contains a .ufx folder and a @README.txt file 7. In the root of the new folder copy in all the indexes folders 8. Start the site using the startup.cmd located in the BIN folder 9. Connect to the CA site nexus portal to verify the indexes now show
  8. Hello, I have tested Ingesting Natives from a mounted forensic image (using FTX Imager) successfully using the 64-bit Streaming Engine. I would highly recommend either selecting the Native File Option "Copy files to case directory" or extracting the files from the mounted forensic image and then ingesting from that location. Reason being is if you do not then any ingested natives will reference the mounted forensic image path which will be invalid to all machines except the one it is mounted on. Thank you, Michael Delgado Technical Support Engineer II
  9. Hello, I have tested Ingesting Natives from a mounted forensic image (using FTX Imager) successfully using the 64-bit Streaming Engine. I would highly recommend either selecting the Native File Option "Copy files to case directory" or extracting the files from the mounted forensic image and then ingesting from that location. Reason being is if you do not then any ingested natives will reference the mounted forensic image path which will be invalid to all machines except the one it is mounted on. Thank you, Michael Delgado Technical Support Engineer II
  10. Additionally I wanted to add that Windows 10 support for eScan-IT was not added until the 2015.0.0 version and Microsoft Office 2016 support was just added in release 2017.0.2. I would recommend upgrading the to eScan-IT 2017.0.2 to be able use Windows 10 and Office 2016 successfully.
  11. Additionally I wanted to add that Windows 10 support for eScan-IT was not added until the 2015.0.0 version and Microsoft Office 2016 support was just added in release 2017.0.2. I would recommend upgrading the to eScan-IT 2017.0.2 to be able use Windows 10 and Office 2016 successfully.
  12. Additionally I wanted to add that Windows 10 support for eScan-IT was not added until the 2015.0.0 version and Microsoft Office 2016 support was just added in release 2017.0.2. I would recommend upgrading the to eScan-IT 2017.0.2 to be able use Windows 10 and Office 2016 successfully.
  13. The following workflow can be used to take the Date value from a Date_Time field and transfer only the Date value into a second field. 1. Use Eclipse SE Administration create new fields for all DATE_TIME fields you wish to convert. Make sure to set the Field Types = "Date". 2. In Administration under Client/Caser Management select Global Search and Replace. 3. Select the correct Client ID and Case 4. Next select the documents to be updated by choosing one of the following options: "Entire Case", "Image Key Range", "Advanced Search", or "Saved Search". 5. Select the Option "Replace Field" and "Copy" 6. In the From Field selection list select the DATE_TIME field (field to copy from). 7. In the To Field selection list select the DATE field (field to copy too). 8. Click Start The utility will copy the data from the DATE_TIME field into the DATE field excluding the time value.
  14. The following workflow can be used to take the Date value from a Date_Time field and transfer only the Date value into a second field. 1. Use Eclipse SE Administration create new fields for all DATE_TIME fields you wish to convert. Make sure to set the Field Types = "Date". 2. In Administration under Client/Caser Management select Global Search and Replace. 3. Select the correct Client ID and Case 4. Next select the documents to be updated by choosing one of the following options: "Entire Case", "Image Key Range", "Advanced Search", or "Saved Search". 5. Select the Option "Replace Field" and "Copy" 6. In the From Field selection list select the DATE_TIME field (field to copy from). 7. In the To Field selection list select the DATE field (field to copy too). 8. Click Start The utility will copy the data from the DATE_TIME field into the DATE field excluding the time value.
  15. The following workflow can be used to take the Date value from a Date_Time field and transfer only the Date value into a second field. 1. Use Eclipse SE Administration create new fields for all DATE_TIME fields you wish to convert. Make sure to set the Field Types = "Date". 2. In Administration under Client/Caser Management select Global Search and Replace. 3. Select the correct Client ID and Case 4. Next select the documents to be updated by choosing one of the following options: "Entire Case", "Image Key Range", "Advanced Search", or "Saved Search". 5. Select the Option "Replace Field" and "Copy" 6. In the From Field selection list select the DATE_TIME field (field to copy from). 7. In the To Field selection list select the DATE field (field to copy too). 8. Click Start The utility will copy the data from the DATE_TIME field into the DATE field excluding the time value.
  16. Hi Jeff, A LFP file can be used for new record(document) creation. On Step 2 of Import Data process make sure you are selecting the correct Import Mode. The three import modes that apply to this situation are Append All Records, Overlay / Append and Overlay Only. -Append All Records - Use this option to add new records to a case. -Overlay Only - Use this option to update existing records (adding additional metadata or overlaying new metadata) -Overlay / Append - This option is a combination of the above two options. It allows for new record creation and updating of existing records at the same time. When you are importing a LFP file and need to make brand new records then the overlay option "Append All Records" is what should be selected. The document boundary values in the IM lines will be used to set the document boundaries and will populate the BEGATT/ENDATT system field values for family relationships. Thank you, Michael Delgado Technical Support Engineer II
  17. Hi Jeff, A LFP file can be used for new record(document) creation. On Step 2 of Import Data process make sure you are selecting the correct Import Mode. The three import modes that apply to this situation are Append All Records, Overlay / Append and Overlay Only. -Append All Records - Use this option to add new records to a case. -Overlay Only - Use this option to update existing records (adding additional metadata or overlaying new metadata) -Overlay / Append - This option is a combination of the above two options. It allows for new record creation and updating of existing records at the same time. When you are importing a LFP file and need to make brand new records then the overlay option "Append All Records" is what should be selected. The document boundary values in the IM lines will be used to set the document boundaries and will populate the BEGATT/ENDATT system field values for family relationships. Thank you, Michael Delgado Technical Support Engineer II
  18. Hi Jeff, A LFP file can be used for new record(document) creation. On Step 2 of Import Data process make sure you are selecting the correct Import Mode. The three import modes that apply to this situation are Append All Records, Overlay / Append and Overlay Only. -Append All Records - Use this option to add new records to a case. -Overlay Only - Use this option to update existing records (adding additional metadata or overlaying new metadata) -Overlay / Append - This option is a combination of the above two options. It allows for new record creation and updating of existing records at the same time. When you are importing a LFP file and need to make brand new records then the overlay option "Append All Records" is what should be selected. The document boundary values in the IM lines will be used to set the document boundaries and will populate the BEGATT/ENDATT system field values for family relationships. Thank you, Michael Delgado Technical Support Engineer II
  19. Jeff is correct, the Eclipse SE scan Module interfaces with the scanner drivers UI. The Scanner drivers UI is what selects if the scan will occurs from the ADF or Glass. A potential workaround for this would be to scan to file directly from the scanner, import the scanned images into Eclipse SE and then you can unitize if needed in Eclipse SE Desktop.
  20. Jeff is correct, the Eclipse SE scan Module interfaces with the scanner drivers UI. The Scanner drivers UI is what selects if the scan will occurs from the ADF or Glass. A potential workaround for this would be to scan to file directly from the scanner, import the scanned images into Eclipse SE and then you can unitize if needed in Eclipse SE Desktop.
  21. Jeff is correct, the Eclipse SE scan Module interfaces with the scanner drivers UI. The Scanner drivers UI is what selects if the scan will occurs from the ADF or Glass. A potential workaround for this would be to scan to file directly from the scanner, import the scanned images into Eclipse SE and then you can unitize if needed in Eclipse SE Desktop.
  22. Hi Peter, It sounds like you are using a native ingestion, if not please let us know. During a Native Ingestion in the center of the screen is the Metadata Field Mapping section that contains two columns. The first column is the list of available metadata fields that can be extracted during the native ingestion process. The second column is the Database Field that the extracted data will be mapped too. To map a custom field, double-click the field and take one of the following actions in the Database Field list: -To change a mapped database field, click the correct field. -To unmap a field, click <Not Assigned> at the top of the list. -To create a new field for the metadata, click <New Field> at the top of the list and complete the New Field dialog box. Thank you, Michael Delgado Technical Support Engineer
  23. Hi Peter, It sounds like you are using a native ingestion, if not please let us know. During a Native Ingestion in the center of the screen is the Metadata Field Mapping section that contains two columns. The first column is the list of available metadata fields that can be extracted during the native ingestion process. The second column is the Database Field that the extracted data will be mapped too. To map a custom field, double-click the field and take one of the following actions in the Database Field list: -To change a mapped database field, click the correct field. -To unmap a field, click <Not Assigned> at the top of the list. -To create a new field for the metadata, click <New Field> at the top of the list and complete the New Field dialog box. Thank you, Michael Delgado Technical Support Engineer
  24. Hi Peter, It sounds like you are using a native ingestion, if not please let us know. During a Native Ingestion in the center of the screen is the Metadata Field Mapping section that contains two columns. The first column is the list of available metadata fields that can be extracted during the native ingestion process. The second column is the Database Field that the extracted data will be mapped too. To map a custom field, double-click the field and take one of the following actions in the Database Field list: -To change a mapped database field, click the correct field. -To unmap a field, click <Not Assigned> at the top of the list. -To create a new field for the metadata, click <New Field> at the top of the list and complete the New Field dialog box. Thank you, Michael Delgado Technical Support Engineer
  25. Hi Peter, It sounds like you are using a native ingestion, if not please let us know. During a Native Ingestion in the center of the screen is the Metadata Field Mapping section that contains two columns. The first column is the list of available metadata fields that can be extracted during the native ingestion process. The second column is the Database Field that the extracted data will be mapped too. To map a custom field, double-click the field and take one of the following actions in the Database Field list: -To change a mapped database field, click the correct field. -To unmap a field, click <Not Assigned> at the top of the list. -To create a new field for the metadata, click <New Field> at the top of the list and complete the New Field dialog box. Thank you, Michael Delgado Technical Support Engineer
×
×
  • Create New...