This article contains a list of changes to the current version of Archive Shuttle 9.7 versus the original release of Archive Shuttle 9.7.

Change List

Build Commit Description
Core: 9.7.39307.1
Modules: 9.7.39307.1
Original release of Archive Shuttle 9.7
9.7.39312.1 50c934b1 Adjusted Retrying of failed/hanging items to run in chunks.
9.7.39323.1 9f0a754c Fixed problem with case sensitive duplicate SenderRecipient addresses got during JE.
9.7.39323.1 3c84fb61 Update Quadrotech.Powershell NUGET
9.7.39326.2 1689ca01 Adjusted sorting of items which are got to import to pst.
9.7.39326.2 e7cc59eb Update Quadrotech.Powershell.Exchange NUGET
9.7.39326.2 072586ee Fixed incorrect marking of users as deleted during Sync Office365 deleted users.
9.7.39326.2 dd906640 Adjusted EVPM args to use configured prefix value from config file when needed.
9.7.39336.1 7fc509b5 Fixed that in case exception occurred during check quota for PrimarysmtpAddress, whole batch is discarded.
9.7.39336.1 546d7dc0 Skip non-processed batch in case mailbox fail check quota
9.7.39336.1 d0a3bfcc Fixed problem with O365 duplicates shown on BulkMappings page.
9.7.39337.1 52e51f2d Update Nuget for Quadrotech.Messaging.
9.7.39338.1 2157c0ef Added missing CTE into bulk mapping view.
9.7.39339.2 ff989f58 Adjusted Cred. Editor and module side to support Application Secret for Oauth.
9.7.39339.2 1880d322 Fixed obtaining of last UserSid in critical section – implemented inter-process locking via Mutex.
9.7.39344.1 50089a5c Fixed issue with failing export items to excel (xslx) due to excel limits for number of hyperlinks in worksheet.
9.7.39345.1 478b913e Fixed problem when StagingAreaBasePath collection will change during deletion.
9.7.39351.2 d7e00d49 Merged the bulk mapping view rework into 9.7.
9.7.39351.2 20b94b2b Fixed (optimized) query for obtaining last UserSid by prefix (SyncCloudOnlyUsers, AddO365LeaverMailbox, etc.)
9.7.39351.2 134afe81 Fixed discrepancy in records count for JELeaverUserView (changed to left joins to always show all leaver users from JELeaverUser table)
9.7.40010.1 7eecb038 Adjusted EVExport to load message body instead of load of whole message.
9.7.40010.1 434a6ba7 Handle exception in case one cloudOnlyUser is problematic so whole batch of items won’t fail.
9.7.40013.1 9db22b22 Added missing DevExpress dlls references to Service installer
9.7.40014.1 706effe3 Progress & Performance – do not include export historic statistics.
9.7.40014.1 b38452f8 Progress & Performance – do not display archived statistics (also imported).
9.7.40015.2 b29da846 Do not process mappings with already started stage2 in scheduled task
9.7.40015.2 8767fe49 Don’t allow to run O365CollectMailbox and O365CollectArchive mailbox when command is still executed.
9.7.40016.2 21c278d8 Fixed issue with AD/O365CloudOnly/O365Deleted user sync.
9.7.40020.1 d1aea94d Fixed creation of leaver mapping when is created via RecreateDeletedUsers task
9.7.40020.1 4725b733 Execute check collection in progress only in case of Office365CollectMailboxes and Office365CollectArchiveMailboxes commands.
9.7.40020.1 69a96fdd Fixed issue with AD/O365CloudOnly/O365Deleted user sync.
9.7.40027.3 d4778be9 Fixed issue with Office365SyncDeletedUsers
9.7.40028.2 939703a Fixed issue with Office365SyncDeletedUsers – do not sync users without UPN.
9.7.40035.1 d7f5277 Created check if all PST link related mappings have Stage 2 finished before changing Temp path
9.7.40035.1 9fe35865 Optimized synchronisation of O365 deleted users.
9.7.40035.1 984301e Rework and optimisation of synchronisation of O365 deleted users (get all MSOL/AzureAD users and check by proxy addresses)
9.7.40035.1 0ccfd17a Adjusted changing Temp path for PST to check also if related NFI module is disabled or inactive
9.7.40037.2 1c0fa066 Adjusted check on module activity and stage 2 finished when changing temp path.
9.7.40037.2 c92a259f Sync O365 deleted users – adding more optimisation by using two level checking and dictionary lookup.
9.7.40037.2 3d2fb205 Adjusted changing temp path if Set as Default is set; reworked some details
9.7.40037.2 7ec6ab60 Enhanced QAM item collection to get folderless items also
9.7.40037.2 0c4cea01 Changed alert and warning messages to be more specific when temporary path is changed for PST
9.7.40042.1 c303ad29 Add possibility to collect PST archives for QAM
9.7.40051.1 a5bc4472 Set visible on bulk mapping page: O365 containers with ExchangeMailboxType = 128
9.7.40052.2 99197824 Don’t create new QAM archive in case of sync command results are processed
9.7.40062.1 5bf57609 Extended time out for item routing SQL queries to 180 seconds
9.7.40079.2 dfd35259 Adjusted PS command string to use ‘ and fix single quote in string with double quotes.
9.7.40079.2 170ae6d6 BulkMappingView – do not filter out any source container(s).
9.7.40079.2 af886ff4 SQL: fixed store procedures for retrying failed/hanging items.
9.7.40105.1 a59e2a16 Adjusted retrieval of commands via queue with lock functionality.
9.7.40105.1 f1e7868e Run NativeRenameCommand in separated SmartThreadpool to not block ingest to be executed.
9.7.40113.1 4b2df120 Update DAM CF – correctly fill Message CreationDate while collection of items to export

Latest Version

Core: 9.7.40113.1
Modules: 9.7.40113.1

Known Issues

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.
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.

Print Friendly, PDF & Email