Overview
There are several commands which affect the Enterprise Vault end-user experience which can be used in a migration with Archive Shuttle. This article explains those commands, and how they can be combined.
Details
The following commands affect the end-user experience of Enterprise Vault:
DisableMailbox – This command builds and executes an EVPM script to disable a mailbox from archiving. It will not work with a mailbox which is in Office 365. Autopots exe. After a subsequent Enterprise Vault mailbox sync, the Outlook client will show Search and Help buttons on the Enterprise Vault toolbar.
ZapMailbox – This command builds and executes an EVPM script to perform a ‘Zap' on a mailbox. It will not work with a mailbox which is in Office 365
DisableOrphanedArchive – This command executes SQL commands to set an Enterprise Vault archive to closed and the archiving state (MbxArchivingState) to disabled.
DeleteEVConfiguration – This command removes the Enterprise Vault hidden messages from a mailbox. It will not work with a mailbox which is in Office 365
RemoveVirtualVault – This command connects to a mailbox and modifies the Enterprise Vault hidden message so that at the next restart of Outlook the Enterprise Vault Outlook Addin will remove Virtual Vault from the Outlook profile.
RemoveEVButtons – This command connects to a mailbox and modifies the Enterprise Vault hidden message so that the Enterprise Vault buttons on the Outlook toolbar are removed
Office365DeleteEVConfiguration – This command removes the Enterprise Vault hidden message from a mailbox. It is specifically for Office 365 based mailboxes
Enterprise Vault Outlook Not Working
Notes:
– DeleteEVConfiguration (and Office365DeleteEVConfiguration) should not be used in the same workflow as RemoveVirtualVault. They are mutually exclusive.
– DeleteEVConfiguration (and Office365DeleteEVConfiguration) should not be used in the same workflow as RemoveEVButtons. They are mutually exclusive.
– To disable the Enterprise Vault Outlook experience, it is recommended to perform: DisableOrphanedArchive, RemoveVirtualVault and RemoveEVButtons as part of the stage 2 workflow (along with other appropriate commands) Evermotion archmodels vol 204.
Enterprise Vault Outlook Not Working
Notes:
– DeleteEVConfiguration (and Office365DeleteEVConfiguration) should not be used in the same workflow as RemoveVirtualVault. They are mutually exclusive.
– DeleteEVConfiguration (and Office365DeleteEVConfiguration) should not be used in the same workflow as RemoveEVButtons. They are mutually exclusive.
– To disable the Enterprise Vault Outlook experience, it is recommended to perform: DisableOrphanedArchive, RemoveVirtualVault and RemoveEVButtons as part of the stage 2 workflow (along with other appropriate commands) Evermotion archmodels vol 204.
Enterprise Vault Outlook Office 365
Enterprise Vault supports Outlook 2016 (32-bit version). Enterprise Vault supports the Windows Installer (.msi) package, which is available with the volume license. The following versions of Outlook 2016 are not supported: Outlook 2016 (64-bit version) Outlook 2016 (Click-to-Run version) Connections to Exchange 2010 with Outlook. Free office 2013 product key. In the Enterprise Vault Preferences dialog box, where you can select the email client with which to associate the Enterprise Vault toolbar, both Outlook 2016 and Outlook 2011 appear in the list. If you inadvertently choose the Outlook 2011 option, the Enterprise Vault toolbar does not subsequently appear when you start Outlook 2016.
