This article contains a list of changes to the current version of Journal Commander 1.0 versus the original release of Journal Commander 1.0.
|Original release of Journal Commander 1.0.|
|1.0.40428.1||42e8c83d||Made fabric icons load offline.|
|1.0.40253.1||600138d9||UI – about popUp – changed link for technical support|
|1.0.40253.1||cbd1317b||Changed product link|
|1.0.40260.1||7c4cc060||WaitForImportFinished – fixed issue with processing archives with 0 items|
|1.0.40265.1||2ed6ff02||Existing mappings page – properly display green tick for column Stage 2 enabled|
|1.0.40265.1||c47a67be||Added condition for stage 2 finished when getting eligible stage 2 commands for execution (GetReadyContainerMappings)|
|1.0.40268.1||91f45889||Fixed calculation of LastChunk for collection of items from PST.|
|1.0.40268.1||c1e931c5||Added missing DevExpress.Data.Desktop.v20.1.dll to Core installer|
|1.0.40286.2||f5c3a6c5||Created Get-ASArchive PS command.|
|1.0.40286.2||565bece6||Fixed problem with not showing P&P stats for QAM.|
|1.0.40288.1||3c2751ee||Enhanced export speed for S1.|
|1.0.40293.1||a0d731c6||Fixed problem with not showing P&P stats for QAM.|
Due to exclusive file locks on the PST file or message being imported, one of the following errors may occur:
- 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.
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.