MySQL 5.6.39 Upgrade for eDiscovery Platform 8.3 and 9.0
Hello Everybody, I wanted to let you all know that as of March 29, 2018, MySQL 5.6.39 Upgrade for eDiscovery Platform 8.3 and 9.0 has been released MySQL Upgrade for eDiscovery Platform 8.3 / 9.0 https://www.veritas.com/support/en_US/article.100034299 The Veritas eDiscovery Platform MySQL Upgrade installer has been created to allow customers to upgrade their eDiscovery Platform 8.3 and 9.0 installs to the latest tested version of MySQL to meet security needs. This installs MySQL version 5.6.39. The upgrade includes both the MySQL Server software as well as the MySQL connector library used by the eDiscovery Platform. If you're not already, make sure you subscribe to the article to get notified of future MySQL upgrades as they're released. The upgrade can be applied by downloading from the aforementioned link and installing from the exe file. Please make sure to follow the steps listed in the article, especially the step of performing a full node backup.eDiscovery Platform 9.0.1 Release
Hello Everybody, I wanted to let you all know that as of March 11, 2018, eDiscovery Platform 9.0.1 has been released eDiscovery Platform 9.0.1 http://www.veritas.com/docs/100041628. This release addresses several issues in the Infrastructure, System Administration, Legal Hold, Identification and Collection, Case Administration, Processing and Production/Export components identified with the eDiscovery Platform 9.0 release or earlier. This release also provides many significant feature enhancement highlights: Header-based single sign-on authentication for Legal Hold notices Earlier eDiscovery Platform supported integrated Windows authentication (IWA) single sign-on (SSO) for Legal Hold authentication. Starting with 9.0.1, header-based authentication single sign-on is also supported for Legal Hold authentication. If header-based authentication is enabled, the custom HTTP header with the username provided by the configured Identity Service Provider (ISP) is used for login through a reverse proxy. The custodian is directed to the Legal Hold notice without the need to enter login credentials. For details, see 9.0.1 Legal Hold User Guide. Support for IPv6 address formats Earlier, eDiscovery Platform only supported IPv4 address format. Starting with 9.0.1, end-to-end workflow of eDiscovery Platform supports IP addresses in IPv4, IPv6, and dual stack mode. For details, see 9.0.1 Distributed Architecture Deployment Guide and System Administration Guide. Onsite collection without user intervention 9.0.1 provides a programmatic way to run OnSite Collector in hidden mode without the need of any user intervention. For details, see 9.0.1 OnSite Collections Reference Card. Users can use a command as shown in the following example to launch an OnSite Collector in hidden mode: D:\Clearwell\OnSiteCollector\exe\scandir\OnSiteCollector.exe -h where, <D:\Clearwell\OnSiteCollector> is the folder where OnSite Collector is installed. Configurable option to process partially converted OST files 9.0.1 provides a way to process the partially converted OST files. When the esa.ost2.conversion_partial_success property is set to "true" using System > Support Features > Property Browser, the partially converted OST files are processed successfully instead of sending them to the OST_Partial_ConvertedFiles directory. By default, the value of this property is set to "false" so that the existing workflow is retained where the partially converted OST files are copied to the OST_Partial_ConvertedFiles directory. For details, see 9.0.1 Case Administration Guide. Configurable option to generate a slip sheet for excluded items Earlier a slip sheet was generated by default for the items of the document family that are not a part of the Production instead of completely skipping them. Starting with 9.0.1, users get a choice whether to include or exclude a slip sheet while setting up Production folders. For details, see 9.0.1 Case Administration Guide. Improvements in archive filtering for Enterprise Vault Collection, Search, and Hold tasks 9.0.1 provides an enhancement in archive selection while creating Enterprise Vault Collection, Search, or Hold tasks. When archives are deleted on Enterprise Vault after you perform the Enterprise Vault discovery on eDiscovery Platform, these deleted archives do not appear in the Archive Picker while selecting archives to add to the Collection, Search, or Hold task. This enhancement prevents the Collection, Search, or Hold tasks resulting into Partial Success when vault store is selected instead of individual archives as the deleted archives are correctly filtered from the vault store. For details, see 9.0.1 Identification and Collection Guide. Enhancements in collection set management 9.0.1 provides several improvements in collection set creation and management. For details, see 9.0.1 Identification and Collection Guide. Task Description - While creating a collection set, you can hover on the task name to see its identifying information that helps to distinguish the task from the other tasks in the list. You can see "Task description: Task source: Size" if description is present in the collection task. If description for the collection task is not available, then "Task ID: Task source: Size" is displayed. Type Selection - Earlier, you could create collection sets of either “Metadata only“or “Content and metadata” type. Now, “Content only” collection sets can also be created. Data for this collection set can only be exported in native format. The data is arranged in an appropriate hierarchy with respect to task, custodian, and source. The collection sets created using the "Content only" option do not appear in the list of collection sets on the Processing > Sources and Pre-Processing > Manage Sources screen. If you need to process the "Content only" collection sets, then you can add the data of these collection sets for processing under Processing > Sources and Pre-Processing > Manage Sources > Add Case Folder Source screen. Type Configuration - Earlier, the default option on the Create Collection Set screen was “Metadata only.” Now you can change the default collection set type by setting the esa.icp.collection.set.create.default_type property using the Property Browser. The values can be set to set the default collection set type to METADATA_ONLY, METADATA_AND_CONTENT, or CONTENT_ONLY. Support for collection of additional data sources 9.0.1 supports collection of FileShares hosted on Windows Server 2016. This release also supports direct FileShare collection of Microsoft Office 2016 data. The supported Microsoft Office 2016 file types are OneNote 2016, Word 2016 Documents, Excel 2016 Spreadsheets, and PowerPoint 2016 Presentations. Users may now download a zip file in Distributed Architecture environments Previously users in a Distributed Architecture environment were not able to download requested Export packages, such as Production, Metadata, and Native Exports. The user was given an info bubble with a location for the zipped file. In a DA environment, not all users will have permissions allowing them access to the designated location on the specified appliance. In this fix, users will have a choice. Selecting the Create downloadable (zip) file radio button on the Metadata tab on the export options window gives the user the option to download the export package, instead of accessing it from the specified appliance location. For details, see the Export and Production Guide. Please refer to the eDiscovery Platform 9.0.1 Documentation https://www.veritas.com/support/en_US/article.100040616 for more detail concerning the aforementioned feature enhancements. There is a download link provided at the bottom of the article. As with any upgrade, please first refer to the upgrade support documents: Supported upgrade paths for eDiscovery Platform https://www.veritas.com/support/en_US/article.000095769 eDiscovery Platform Compatibility Matrix https://www.veritas.com/support/en_US/article.000019811 Attached are the eDiscovery Platform 9.01 Release Notes for your review.eDiscovery Platform 9.0 General Availability
Hello Everybody, I am excited and proud to announce the General Availability of eDiscovery Platform 9.0 as of December 22, 2017. This is a major release that incorporates many significant feature, product and security enhancements, improvements and fixes. With GDPR (General Data Protection Regulation) as the primary theme around this release, new features for data classification, improved performance, resiliency, scalability and workflow have been added to enhance the eDiscovery experience. Some of the highlights of the release include the following: Information Classification Starting with version 9.0, the eDiscovery Platform lets you automatically classify sensitive and critical case data based on a set of built-in and custom policies. Note: The Information Classification feature can only be enabled for cases created in version 9.0 and later. Cases created before version 9.0 are not supported. The platform integrates with Veritas Information Classifier (VIC) to analyze and classify eDiscovery data. VIC uses both predefined and user-defined policies to assign classification tags to your eDiscovery data during the processing phase. Once these tags have been applied,users can view pre-selected classification filters (system tags) in the Analysis and Review mode to quickly identify documents that match the VIC tags. Bulk Redaction and Delete Bulk Redaction Bulk redaction provides the ability to redact multiple documents in a Redaction Set without having to individually open and review each and every document in the Native Viewer. You can easily specify the redaction text along with the reason code that needs to be applied on theredacted text to all selected documents. Bulk redaction works on redaction sets with preset reason codes and with free-text reason codes. The delete bulk redaction option makes it easy to delete all redactions and annotations for a set of documents in a redaction set. Redaction sets with preset reason codes Currently, case reviewers can add free text as a reason for redaction while redacting a document. New functionality is available so the Case Administrator can define preset reason codes. Reviewers will then be able to redact documents by applying reason codes consistently. The Case Administrator can create redaction sets with either predefined reason codes or free text reason codes. Case reviewers can apply the preset reason codes to redaction markups. Case reviewers can search, filter, or export documents based on the preset reason codes. Annotations in review mode In addition to the existing capability to redact a document, this release adds the ability to annotate a document in review mode. Case reviewers can annotate a document by adding comments or graphical stamps, or strike out some text. Case reviewers are also allowed to delete annotations. Case reviewers can also search the document for the Redacted Tag. Once annotated, the document can be reviewed by another reviewer, who can also add annotations. Case Backup Integrity During an eDiscovery Platform backup, empty directories may be created in the backup structure. If a case backup directory is then moved and empty directories are not copied, a restore job will subsequently fail. With this release, restore job for a case backup with empty directories does not fail. With the Case Backup Integrity feature, a checksum of the case backup directory is created during both the backup and the restore job. The checksum file created during the restore job is compared with the checksum file created during the backup job. If any empty directory is identified, then these empty directories are created at their specific paths during restore. This results in the success of the restore jobs. Automatically convert OST to PST Data Files for processing The eDiscovery Platform can now seamlessly convert OST files to PST files for processing. OST data files are converted to PST data files during the discovery phase. Upon successful completion of this operation, normal PST processing is applied to the files for easy access,review, and analysis. See technical article for details: https://www.veritas.com/support/en_US/article.000128050 Integrated Windows Authentication Single Sign-On for Legal Hold Veritas eDiscovery Platform supports Integrated Windows Authentication (IWA) Single Sign-On (SSO) for Legal Hold authentication. When IWA SSO is configured, the logged-in Windows credentials of the custodian are used for authentication, and the custodian is subsequently directed to the Legal Hold Confirmation page without the need to enter login credentials. To use the SSO option, LDAP must be configured and enabled against the Active Directory domain from which Windows users will be authenticating. See technical article for details: https://www.veritas.com/support/en_US/article.000128049 Office® 365 connection using MAPI/HTTP Microsoft deprecated support for RPC over HTTP on October 31st 2017. With this release, the Veritas eDiscovery Platform will now use MAPI/HTTP to connect to Office 365 in support of this change. The eDiscovery Platform 9.0 installer automatically installs the KB3114941 updates for Outlook 2013 32-Bit Edition that enables the MAPI/HTTP protocol required to collect data from Office® 365 mailboxes. See the 9.0 Identification and Collection Guide for details and troubleshooting steps. Refer eDiscovery Platform 9.0 Release documentation as follows: Late Breaking News for eDiscovery Platform 9.0 http://www.veritas.com/docs/100041303 New Features Overview 9.0 https://www.veritas.com/content/support/en_US/doc/edp90_NFO_guide_v1_v90_00 Veritas eDiscovery Platform 9.0 Release Notes https://www.veritas.com/content/support/en_US/doc/edp90_release_notes_v1_v90_00 eDiscovery Platform 9.0 - Documentation http://www.veritas.com/docs/100040616 As with any upgrade, please first refer to the upgrade support documents: Supported upgrade paths for eDiscovery Platform http://www.veritas.com/docs/000095769 eDiscovery Platform Compatibility Matrix 9.0 http://www.veritas.com/docs/000019811
eDiscovery Platform 8.2 Cumulative Hotfix 2 Release
Hello Everybody :robothappy: I wanted to let you all know that as of October 24, 2016, eDiscovery Platform 8.2 CHF2 has been released eDiscovery Platform 8.2 Cumulative Hotfix 2 Release http://www.veritas.com/docs/000116248 Besides a good many fixes, this release contains a few highlights that are worth the mention: Certificate Management - This feature is used in the installation of 3rd party SSL certificates. Storage Location Pointer Modifier - This feature would be used to modify pointers for Collections and Collections Sets in particular. You can apply the hotfix by downloading from the aforementioned link and installing from the exe file. As with any upgrade, please first refer to the upgrade support documents: Supported upgrade paths for eDiscovery Platform http://www.veritas.com/docs/000095769 eDiscovery Platform Compatibility Matrix http://www.veritas.com/docs/000019811 Attached are the eDiscovery Platform 8.2 Cumulative Hotfix 2 Release Notes for your review.
Trying to Upgrade clearwell from 7.1.2 to 7.1.3
Im trying to upgrade to 8.1.1 eventually but inorder to get there I need to go to 7.1.3 then to 8.1 etc.... My PROBLEM is that when I try the upgrade from 7.1.2 to 7.1.3 I click on the setup program for 7.1.3 and I get the following message right away. "MySQL 5.5.8 has been identified on the system. To successfully upgrade MySQL (part of Clearwell), you must run the installer under the same account that was originally used to install MySQL 5.5.8. Please login with the correct account before running the installation" So the problem is I dont know what account was used. Is there a force command to install/upgrade my version of 7.1.2 to 7.1.3. I have tried the following that someone had used to upgrade 7.1.3 to 7.1.4 and it worked but it did not work for my upgrade path and gave me same message regarding the need to login as account that origianlly insstalled software etc.. Tried this but still nothing.. ...\setup.exe /v"FORCEMYSQLUPGRADE=1" Not sure what do do now. We have searched the registry to see if we could determine a MySQL install instance but cant see to find it. Also there is no uninstall package for MySQL 5.5.8 in the control panel remove program section. MySQL is definitly on the system as I can login into it and get to the MySQL prompt via the command prompt. Any suggestions would be appreciated. Thanks
Change Clearwell Local User Passwords in CW 8.1
I've just upgraded to Clearwell 8.1 from 7.1.3. I need to change the passwords for the local accounts that were created when on the previous version. When I go to System->Users and select a local CW account, there is no option to change the password, how can I accomplish this? TIA
Clearwell 6.1 to 8.1 case migration
Is it possible to backup/archive cases in version 6.1, and restore them to a clearwell appliance running version 8.1? I know the upgrade path needs to go to 7.1.2 before you can go to 8.1, but I am not upgrading. I just want to backup cases and restore them. I am unclear as to whether or not it is possible to restore a case that was created in 6.1 to 8.1. Thank you!
