Enterprise Vault™ Setting up Exchange Server Archiving
- About this guide
- Distributing Exchange Server Forms
- Setting up archiving from mailboxes
- Points to note before you set up Enterprise Vault mailbox archiving
- Defining Exchange Server mailbox archiving policies
- Mailbox policy settings when setting up Exchange Server archiving
- Mailbox policy settings when setting up Exchange Server archiving
- Defining desktop policies in Exchange Server archiving
- Desktop policy settings in Exchange Server archiving
- Options tab (Exchange Server archiving desktop policy setting)
- Advanced tab (Exchange Server archiving desktop policy setting)
- Desktop policy settings in Exchange Server archiving
- Adding Exchange Server archiving targets
- Using customized shortcuts with Exchange Server archiving
- About editing automatic messages for Exchange Server archiving
- Enabling mailboxes for Exchange Server archiving
- Setting up users' desktops
- Enterprise Vault Outlook Add-In for Exchange Server archiving
- Enterprise Vault Client for Mac OS X with Exchange Server archiving
- Getting users started with Exchange Server archiving
- Setting up Vault Cache and Virtual Vault
- Vault Cache synchronization
- Vault Cache header synchronization and content download
- Vault Cache advanced settings
- Virtual Vault advanced settings
- Setting up archiving from public folders
- About public folder policy settings
- Exchange Public Folder policy settings
- Exchange Public Folder policy settings
- Adding public folder archiving targets
- Setting up archiving of journaled messages
- Envelope Journaling
- Setting up Enterprise Vault Office Mail App for Exchange Server 2013 and later
- About the Enterprise Vault Office Mail App
- Deploying the Enterprise Vault Office Mail App
- Troubleshooting the Enterprise Vault Office Mail App
- Setting up Enterprise Vault access for OWA clients on Exchange Server 2010
- About Enterprise Vault functionality in OWA clients
- Enterprise Vault OWA Extensions in an Exchange Server 2010 environment
- Configuring access to Enterprise Vault from Outlook RPC over HTTP clients
- Using firewall software for external access to OWA and Outlook
- Configuring filtering
- About filtering
- Configuring selective journaling
- Configuring group journaling
- Configuring custom filtering
- About custom filtering ruleset files
- About controlling default custom filtering behavior
- About the general format of ruleset files for custom filtering
- About rule actions for custom filtering
- About message attribute filters for custom filtering
- About the general format of Custom Properties.xml
- About content categories
- Defining how custom properties are presented in third party applications
- Custom properties example
Managing FilesInUse dialog boxes in a manual upgrade or an uninstall of the Outlook Add-In
The information in this section is provided so that if necessary you can advise users about which option to choose in a FilesInUse dialog box. The section also outlines how you can prevent FilesInUse dialog boxes from appearing.
When a user upgrades the Outlook Add-In manually on Windows 7, Windows 8 or Windows 10, the Windows Restart Manager may detect that one or more files are locked. In this case, the Restart Manager displays a FilesInUse dialog box that says that the relevant application or applications should be closed. The dialog box may also appear during an uninstall of the Outlook Add-In. In a new installation of the Outlook Add-In, the dialog box is much less likely to appear, though it is still possible.
The user can choose one of the following options:
Close the applications automatically and attempt to restart them after setup is complete. This option is the default.
Do not close the applications, but a system restart may be required.
We recommend that users should choose the option to close and restart the applications automatically.
Table: Applications in a FilesInUse dialog box shows the applications that users are most likely to see in the dialog box.
Table: Applications in a FilesInUse dialog box
Application name | Notes |
---|---|
Windows Explorer | A file is locked because Windows Explorer has loaded it to support search functionality. If the user chooses to close Windows Explorer automatically, all Explorer windows are closed. The Desktop also closes, which the user may not expect; that is, the Desktop icons and the Taskbar disappear for a short time. The installation continues and Windows Explorer is restarted. |
Windows host process (Rundll32) | Windows may have used this process to load an Enterprise Vault DLL to support integration with the Indexing Options in the Windows Control Panel. If the user chooses to close the process automatically, the installation continues and the process is restarted. However, users may not recognize the process name. They may not want to close this application in case it closes Windows, and may not know which option to choose. |
Outlook | We recommend that users close Outlook before they install or upgrade the Outlook Add-In, but it is not essential. The user can choose to close Outlook automatically. |
If Restart Manager is disabled, the FilesInUse dialog box may provide different options, as follows:
Cancel the installation. This option is the default.
Retry after the user has closed the application.
Ignore the locked file. With this option, a system restart may be required.
We recommend that users should choose the option to ignore the locked file.
To disable the Restart Manager, you can set MSIRESTARTMANAGERCONTROL to Disable in the msiexec command line.
Alternatively, you can apply a transform to the MSI package to disable the Restart Manager. You can also use the transform to remove the FilesInUse dialog box from the installer.