-
Title
Archive Shuttle 9.8 Mini Revision Notes -
Description
Archive Shuttle 9.8 Mini Revision Notes -
Resolution
This article contains a list of changes to the current version of Archive Shuttle 9.8 versus the original release of Archive Shuttle 9.8.Change List
Build Commit Description Core: 9.8.40069.2
Modules: 9.8.40069.2Original release of Archive Shuttle 9.8 9.8.40073.4 560ea999 Fixed SyncCloudOnlyCommand – sync only cloud only users 9.8.40073.4 08f3c35e JE – do not display user/leaver on popUp if user/leaver mapping already exists 9.8.40079.1 da85e169 Adjusted PS command string to use ‘ and fix single quote in string with double quotes. 9.8.40079.1 7be4491b BulkMappingView – do not filter out any source container(s). 9.8.40079.1 b09ebed9 SQL: fixed store procedures for retrying failed/hanging items. 9.8.40097.1 94d9967e Adjusted MAPI recreation command to support settings per module; the same for corrupted PST in processor after import. 9.8.40097.2 92eae320 UI: javascript – enhanced email validation regex to include also upper-case letters 9.8.40097.2 6f3f5e57 New feature: Restore EV foreign shortcuts. 9.8.40101.1 a2cba3de Adjusted retrieval of commands via queue with lock functionality. 9.8.40105.1 4922fbd4 Run NativeRenameCommand in separated SmartThreadpool to not block ingest to be executed. 9.8.40113.2 bc482dcb Update DAM CF – correctly fill Message CreationDate while collection of items to export. 9.8.40113.2 9eee7fee Stop to execute NativeRename commands for mappings disabled for migration. 9.8.40118.1 2313f5fb Fixed issue with import percentage showing “Bytes” in exported report for PST sub grid 9.8.40125.1 2d27f2d6 Feature: Allow to suppress legal hold check 9.8.40125.1 75953bc5 NativeRename – enhanced query to filter out corrupted/verification failed subcontainers. 9.8.40125.1 ddc570c4 Do not delete restored EV shortcut if messages contain RestoreEVForeignShortcutGuidProperty property. 9.8.40125.1 39394df1 UI: Health page – do not display missing retention category mappings (EV – O365) in case setting to collect O365 retention tags is not turned.
Solution here9.8.40125.1 ca38a2c9 JE – reevaluate ReadyForImport status on collect mailbox result (unset invalid smtp address) 9.8.40125.1 ce9dd5c5 JE evaluate ReadyForImport status upon mailbox collection – fixed issue with overwriting paused JEUMs 9.8.40125.1 d7dad962 UI: JEUserManagement – extended validation for enbale for import 9.8.40128.1 4b9c3663 Adjusted S1 GetUsers query to return pst, journal and exchange archive types only. 9.8.40134.2 00f4ec8b Added missing catch statement while license check PS command execution. 9.8.40134.2 d47ec218 Feature: Add possibility to use O365 compliance tags during item level retention assignment from EV to O365 9.8.40134.2 9eb9dd9a Adjusted RemoveUser license check to include EXCHANGE_S_ENTERPRISE_GOV planId. 9.8.40142.1 f118466b O365 module: GetMailbox – fixed issue with PS command (missing ‘ ) 9.8.40142.1 299f9ada Disable Item Skipping functionality by default 9.8.40153.2 c5e97cbf UI: do not allow configure OAuth per module 9.8.40153.2 15a4f522 Set ExportedDate as date received in Core 9.8.40163.1 fdff9304 Added TransferEVContainerInfo command trigger after EV item collection command is finished. 9.8.40163.1 1aa84a52 Adjusted UpdateContainerInfo to not reset ProcessedItems count on error (-1); adjusted deleting mapping logic to remove ContainerInfo record only when “Include Item data” is checked 9.8.40170.1 369a6a07 S1: Return stats only for items which have existing Volume. 9.8.40170.1 ea7d59f9 S1: Extended IsCentera condition to check also CurrentUNCPath column while collection of items. 9.8.40174.1 969e7a3f Adjusted Source one item collection to check and update inconsistency in total and processed items counts. 9.8.40182.1 9969f2f6 Speed up queries used for processing of errors while ingest to Exchange and O365. 9.8.40196.1 e0075ac6 Introduced setting to allow automatically import items without O365 retention mapping. 9.8.40304.2 3314c3e6 Adjusted check for auto stage 2 switch as the wait for import finished command Latest Version
Core: 9.8.40304.2
Modules: 9.8.40304.2Known Issues
Due to exclusive file locks on the PST file or message being imported, one of the following errors may occur:
- STG_E_SHAREDVIOLATION
- The process cannot access the file
Consecutive attempts at processing the file should be successful. There is a known issue with Outlook 2013 used with the Native Format Import module. More information is available here.
Ticket ID: 5969 & 5654
When customizing Stage 2 Workflows, it should be noted that DisableMailbox and DisableOrphanedArchive are mutually exclusive. This means that only one of those should be present in the workflow. If both are included then unpredictable results will be observed with some commands appearing to ‘hang’ during Stage 2.
KB: 625
The dates relating to oldest and youngest item in archive can vary from what is eventually collected from the item-level metadata in the source archive. This is because the data comes from different databases tables in the source environment. More details in the knowledge base article
Office 365 hold types
As of 1st July 2017, Microsoft is changing the way that legal holds can be used in Office 365. Archive Shuttle currently allows the usage of one, or the other, or both of these types of hold:- Litigation Hold
- In-place hold
From 1st July it is required to use the legal hold type called ‘Litigation Hold’. More information is available in this Microsoft article.
The ‘In-place hold’ will be removed from a future version of the product.
Migrations involving folders with leading and trailing spaces.
This issue affects only Enterprise Vault migrations (to any supported target). All versions of Enterprise Vault are affected. A known issue in Enterprise Vault means that leading and trailing spaces in folder names are not provided to Archive Shuttle by the Enterprise Vault API. This can result in mis-named folders in the target environment. Veritas is aware of this issue, but there are no current plans to fix the issue.
Note: Confer with Microsoft to determine whether the terms of your licensing agreement are impacted by the legal hold feature.