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 8.3 Cumulative Hotfix 2 Release
Hello Everybody, I wanted to let you all know that as of October 2, 2017, eDiscovery Platform 8.3 CHF2 has been released eDiscovery Platform 8.3 CHF2 Release https://www.veritas.com/support/en_US/article.000128033. Besides a good many fixes, this release contains several highlights: Automatically convert OST to PST Data Files for processing The eDiscovery Platform can now seamlessly convert OST files to PST files for processing. Starting with 8.3 CHF2, 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 Starting with 8.3 CHF2, Veritas eDiscovery Platform supports Integrated Windows Authentication (IWA) SingleSign-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 is deprecating support for RPC over HTTP on October 31st 2017. With 8.3 CHF2, the Veritas eDiscovery Platform will now use MAPI/HTTP to connect to Office 365 in support of this change. After the 8.3 Cumulative Hotfix 2 is installed, Administrators who want to collect data from Office® 365 mailboxes must also download and install the KB3114941 updates for Outlook 2013 32-Bit Edition that enables Office® 365 connection using MAPI/HTTP to the eDiscovery Platform servers connecting to Office 365. Administrators can download the KB3114941 Outlook update from https://www.microsoft.com/en-us/download/details.aspx?id=51720 and then manually install it. See technical article for details and troubleshooting steps: https://www.veritas.com/support/en_US/article.000128048 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 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 8.3 Cumulative Hotfix 2 Release Notes for your review.
