The words you are searching are inside this book. To get more targeted content, please make full-text search by clicking here.

Quest Archive Manager 8 Deployment Models Several different deployment options are available for Archive Manager, depending on organization size and type.

Discover the best professional documents and content resources in AnyFlip Document Base.
Search
Published by , 2016-04-30 06:21:02

Archive Manager 4.6 - us-downloads.quest.com

Quest Archive Manager 8 Deployment Models Several different deployment options are available for Archive Manager, depending on organization size and type.

Installing Archive Manager with Exchange

Bridgehead

On the BridgeHead HDR Store Setup screen, specify:

• Bridgehead HDRHOME location: Location of the HT data
repository, usually stored in the HDRHOME environment variable.

• Bridgehead Library path: Use the following path, not the path
listed on the BridgeHead HDR Store Setup screen:
C:\Program Files\ArchiveManager\Bridgehead\HDRDataStream.dll

• Repository ID: HT repository ID. This value must be a number.
• Application Name: The HT data application name. This is

usually AfterMail or ArchiveManager.
• Select the Store Message data for compliance checkbox to

keep a copy of your message archive outside of the message
database.

After you have completed entering information on the BridgeHead HDR Store
Setup screen, click Next to proceed to the Full Text Index Setup screen, as
described in the Archive Manager installation steps above.

IBM DR550

If you selected the IBM DR550, specify the following information on the IBM
DR550 Store Setup screen,

This information entered will be used by the TSM Client to connect to
the hardware. If an advanced configuration is required, complete the
following fields:

• Copy the generated file to %Program Files%\Archive
Manager\Tivoli\dsm.opt.

• Host: Provide a host to connect to.
• Node: Enter a Node name.
• Port: Provide a port to connect to. If this field is left blank, the default

port number of 1500 is used.
• Username: Specify the user name to use to sign in to the IBM DR550.
• Password: Specify the password that will be used to sign in to IBM

DR550. If this field is left blank, the value from the IBM DR550 Client
Registry will be used. For example:
HKLM\SOFTWARE\IBM\ADSM\CurrentVersion\Nodes\<NodeName>\

<Nodename>_SERVER1\Password, type of REG_BINARY
This registry entry is created by the IBM DR550 configuration utility
during the Client installation, or later on.

51

Quest Archive Manager

Open storage in Backup Mode/Archive Mode: The IBM DR550 can operate in two
modes: Backup and Archive. Backup mode is optimized for faster retrieval. Archive mode
is optimized for better space utilization. This is a mandatory parameter. The default setting
is Backup Mode.

• File Space for Attachments/File Path for Attachments: Specify
the File Space and File Path where attachments will go. It is
recommended that you use the default settings.

• Store Message Data for Compliance: Like other storage types,
users can choose to save copies of all of the emails to be stored in
external storage. This checkbox controls the behavior.

• File Space for Messages/File Path for Messages: Specify the File
Space and File Path where messages stored for compliance will go. It
is recommended that you use the default settings.

• Test button: Before proceeding with the installation of Archive
Manager, the Installer needs to make sure that the user input is valid,
and the IBM DR550 storage can be reached. The Test button performs
user input validation. The multi-line box next to it shows the
verification results.

For additional information on the IBM DR550 storage
parameters, see the IBM DR550 documentation on the
IBM Web site.

After you have completed entering information on the IBM DR550 Store Setup
screen, click Next to proceed to the Full Text Index Setup screen, as
described in the Archive Manager installation steps above.

NetApp Snaplock

If you selected NetApp SnapLock, specify the following information on the
NetApp SnapLock Configuration screen.

• Login: The account name used to connect to the SnapLock volume.
• Hostname: The name of the SnapLock volume.
• Retention Mode: Select either SnapLock Default or Archive Manager

Default. If you select SnapLock Default, Archive Manager uses
SnapLock’s default time to store messages. If you are running
SnapLock Compliance, there is a minimum of 0 days and a maximum
of 30 years. The default is the maximum of 30 years. If you are
running SnapLock Enterprise, the default is the minimum of 0 days.
• Password: The password for the account used to connect to the
SnapLock volume.
• Share Name: The path to the volume. The format is \\computer name
or IP address\volume name.
• Store Message data for compliance: Check this box to take the
XML files that are exported from the mail system and store them in the
NetApp device.

52

Installing Archive Manager with Exchange
• Launch SnapLock Setup Wizard: Click this button to launch the

NetApp SnapLock Setup Wizard. For information on the SnapLock
Setup Wizard, see the Running the NetApp SnapLock Setup Wizard
section of Appendix A, Attachment Store Types.
After you have completed entering information on the NetApp SnapLock
Configuration screen, click Next to proceed to the Full Text Index Setup
screen, as described in the Archive Manager installation steps above.

53

Quest Archive Manager
54

6

Reinstalling/Upgrading
Archive Manager

• Upgrading Archive Manager
• Reinstalling Archive Manager
• Post Installation Notes

Quest Archive Manager

Upgrading Archive Manager

Please refer to the release notes for information on supported upgrade versions.
When upgrading Archive Manager over the same existing version of Archive
Manager by selecting the Upgrade option in the installer, the following
conditions apply:

• Configuration files that have been modified by the Archive Manager
Administrator (.config or .xml) are preserved during the upgrade
process. Configuration files from the upgrade kit are placed in the
same directory as modified configuration files. A notice is added to
installation logs with Info level indicating when a modified
configuration file has been used and the configuration file from the
upgrade kit was set aside in the same directory.

• Configuration files from the upgrade kit that are set aside are named
file-yyyyMMddhhmmss.ext, keeping the file name as the prefix
and the original extension. The date portion represents the current
installation date and time.

• If no modifications have been made to the configuration files by the
Archive Manager Administrator, then the configuration files from the
upgrade kit replace the existing configuration files.

• This upgrade procedure applies only to systems serving an Exchange
(only) messaging environment. For assistance to deply a dual
GroupWise/Exchange environment, please contact Quest Support.

• The upgrade process does not recognize prior installations of the PST
Import Wizard, Search Exporter or Retention Editor. You must
manually uninstall these components before performing an upgrade.

To upgrade Archive Manager:

1. Uninstall the PST Importer, Search Exporter, and Retention Policy
Editor.

2. Verify that the web server and Archive Manager Services server
(usually, but not always the same machine) both conform to the
prerequisites listed in the System Requirements chapter of this
Guide. See in that chapter Prerequisites for Servers Running Archive
Manager Services for a complete checklist.

3. Stop all Archive Manager services.
4. Run the Archive Manager Installer (ArchiveSetup.exe).
5. On the Welcome screen, click Next.
6. In the Archive Manager End User License screen: Review the

license agreement and select the I have read and agree...
checkbox.
7. Click Next.

56

Reinstalling/Upgrading Archive Manager

8. On the License Key Details screen, specify the name of the
organization and the license key.
The organization and license key are case sensitive.

9. Click Next.
10. On the Archive Manager Installation Targets screen, select

Upgrade an existing Archive Manager instance.
11. Click Next.
12. On the Administrator Credentials screen, specify the credentials

for the account that will be used by the installation wizard. (Creden-
tials must be specified in the format DOMAIN\Username.)
13. Click Next.
14. On the Database Installation Progress window: The installer
checks the version and configuration of the existing Archive Manager
database, performs any necessary updates, and reports its progress
at each step.
The following options are available after the installation has
completed.

• If warnings or errors have been encountered, a Summary button is
displayed. Click the Summary button to view the warnings and/or
errors.

• Click the View Log button to view the Installation log.
If you encounter errors and then correct them, you can perform the
installation again without exiting the installer by clicking the
Previous button. This takes you back to the Summary screen. Click
Next to run the installation again.

15. Click Next.
16. On the Full Text Index Setup screen, select Default

Configuration if you would like your Full Text Index to be
partitioned into default sections. The default configuration is
recommended.
If you have a complex environment that requires custom partitioning
of the Full Text Index, it can be configured through the Archive
Manager Website with the assistance of Quest support.

17. Select one or more drives that will be used for partitioning the Full
Text Index.

18. Click Next.
19. If you have selected Default Configuration, the Full Text Index

Summary screen is displayed. Read the information on the screen.
20. Click Next.

57

Quest Archive Manager

21. If you did not select Default Configuration on the Full Text Index
Setup screen, the Full Text Index Summary screen is displayed
with a message that the Full Text Index settings must be configured
in the Archive Manager Administration website. Read the information
on the screen.

22. Click Next.
23. On the Installation Summary screen, review your setup settings.
24. Click Next to start the installation.
25. The Installation Progress screen is displayed.

The following options are available after the installation has
completed.

• If warnings or errors have been encountered, a Summary button is
displayed. Click the Summary button to view the warnings and/or
errors.

• Click the View Log button to view the Installation log.
If you encounter errors and then correct them, you can perform the
installation again without exiting the installer by clicking the Previous
button. This takes you back to the Summary screen. Click Next to
run the installation again.
26. Click Next when you have completed viewing the information.
27. The Archive Manager Installation is Complete screen displays
information and instructions for your Archive Manager installation.
Review the information.
28. Click Finish to exit the installation wizard.

Verify the Success of the Upgrade

To confirm the success of the Upgrade:

1. Verify that the installer has started the services.
2. Open the web-based interface and verify that the correct version

number appears in the top-left corner.

58

Reinstalling/Upgrading Archive Manager

Reinstalling Archive Manager

When installing or reinstalling Archive Manager, please refer to the release notes
for information on supported upgrade versions.
When installing or reinstalling Archive Manager over the same existing version
of Archive Manager by selecting the Install option in the installer, the following
conditions apply:

• Configuration files (.config or .xml extensions) that have been
modified by the Archive Manager Administrator are set aside as .bak
files by the installer. Archive Manager will use the default
configuration files contained in the installation kit.

• If no modifications have been made to the configuration files by the
Archive Manager Administrator, then the configuration files from the
installation kit replace the existing configuration files.

Post Installation Notes

• If you have previously used the Archive Manager installer, you can
rerun it at any time by running Start | All Programs | Quest
Software | Archive Manager | Installer

• It is strongly recommended that you add the ArchiveMgr_Service,
ArchiveMgr_Journal, and ArchiveMgr_ESM accounts to the
Performance Log Users and Performance Monitor Users groups
on the Archive Manager server after completing an installation.

59

Quest Archive Manager
60

7

Post-Installation Tasks

• Configure the Active Directory Connector
(ADC)

• Configure and Deploy the Offline Client
(Optional)

• Relocate FTI Temp Location (If Necessary)
• Add MAPI Data Loaders for Exchange

Journal Mailboxes

Quest Archive Manager

Configuring Archive Manager

After you install Archive Manager, you must perform certain configuration tasks
before you can begin to use the product. Most of these necessary post-installa-
tion tasks are explained in the contents of this chapter:

• Configure the Active Directory Connector (ADC)
• Configure and Deploy the Offline Client (Optional)
• Relocate FTI Temp Location (If Necessary)
• Add MAPI Data Loaders for Exchange Journal Mailboxes

In addition to the above-listed tasks, you must also set up at least one Message
Policy, and apply a Policy to a mail server or mailboxes.

Detailed instructions can be found in the Archive Manager Administration Guide.

To begin the initial configuration, sign in to the Quest Archive Manager web site.
The default administrator account is admin, and the password was specified
during installation. Use the domain DEFAULT.

Once you have signed in, click the Administration icon (top-right corner of the
window) to go to the administrative section of the Archive Manager web site.

Configure the Active Directory
Connector (ADC)

An ADC.config file is used to provide information for all of the domains that you
need to import into Archive Manager. You specify the path of the Active Directory
Connector configuration file in the Archive Manager Configuration Editor, using
the setting ADC Config File.

Scenarios for ADC.config File Deployment

There are some common scenarios when you should deploy an ADC.config file.

• Multiple Active Directory Domains: If you have more than one
Active Directory Domain that contains users you wish to process with
Archive Manager in an environment, you need the ADC.config file to
prevent users from getting stamped with the local Archive Manager
domain for their login domain and Archive Manager is installed in that
domain, causing them to be unable to login.

62

Post-Installation Tasks

• Parent/Child Domain: An ADC.config file is needed if Archive
Manager users are in both the Parent domain and the Child domain.
If all Archive Manager users are in a single domain and Archive
Manager is installed in that domain, an ADC.config file is not needed.

• Exchange Resource Forest (one-way trust): In a Resource Forest
and User Forest, the instance(s) of Archive Manager will likely be
located in the resource domain. You will need to use the ADC.config
file to make Archive Manager aware of the security accounts in the
user domain.

• Trusted Forest: In a two-way trust, the ADC.config file is needed to
find all mailboxes, users, and groups in each forest.

• Special filtering requirements: You only want certain users,
groups, or mailboxes to populate the Archive Manager database. You
can specify additional LDAP filters to limit the objects that are
exported by the ADC.

The ADC.config File

ADC.config consists of a main block named ArrayOfAfterMailInstance. This
can contain a number of blocks called AfterMailInstance. Each block of
AfterMailInstance defines the settings for one domain. The settings are:

• Name (deprecated): The name of this instance.
Note: This setting is not used. It is retained in the documentation
because it was needed in earlier configurations and is still
implemented at some sites.

• ConnectionString (deprecated): This is the connection to the
Archive Manager database. It contains the database server name and
the database name. Copy the connection string from the
Configuration Editor into this file as that will be correctly formatted for
your installation. If the connection string is empty or missing, the
connection string from the Archive Manager Configuration Editor will
automatically be used.
Note: You do not need to set the connection string. This setting is
retained in the documentation because it was needed in earlier
configurations and is still implemented at some sites.

• Server: The Fully Qualified Domain Name (FQDN) of the domain
controller, or the global catalog. For example:
server.domain.com

• UserNamingContext (LDAPPath): LDAP distinguished name of the
domain. For example:
dc=domain,dc=com

63

Quest Archive Manager

• NetBIOSName: This setting allows you to specify a domain to
override the current domain for the machine.
Note: This setting is no longer used. This setting is retained in the
documentation because it was needed in earlier configurations and is
still implemented at some sites.

• ResourceURL (Previously called ExternalLDAPPath): LDAP or
GC url that specifies the location of the domain controller or global
catalog for the Exchange resource forest. You only need this setting if
you have a user/resource forest configuration in your environment.
For example:
GC://server/dc=resource,dc=domain,dc=com
— or —
LDAP://server/dc=resource,dc=domain,dc=com
Note: For this setting to be used by the Active Directory Connector
Service, you must set the UseResourceURL setting to True.

• UseResourceURL (Previously called UseSecServer): This setting
is a boolean that enables the use of ExternalLDAPPath. The default
for this setting is False.

Deployment With Multiple Active Directory
Domains

If you have multiple domains in your environment, to import users into your
Archive Manager instance with the correct login domain you will need to set up
your ADC.config to reflect your domain layout. You need to have an
AfterMailInstance entry for each domain that you want the Active Directory
Connector to import.

When editing the ADC.config file, it can be easy to miss a tag. For every opening
tag <tag>, there must be a matching closing tag </tag>. All tags are
case-sensitive, e.g., using UseResourceURL is not the same as UseResourceUrl.
Opening the ADC.config file with Internet Explorer can help you find tag errors.

The following example contains two domains, example.com and mydomain.net.

64

Post-Installation Tasks

<?xml version="1.0" ?>
<ArrayOfAfterMailInstance>
<AfterMailInstance>
<Server>server.example.com</Server>
<UserNamingContext>DC=example,DC=com</UserNamingContext>
</AfterMailInstance>
<AfterMailInstance>
<Server>server.mydomain.net</Server>
<UserNamingContext>DC=mydomain,DC=net</UserNamingContext>
</AfterMailInstance>
</ArrayOfAfterMailInstance>

Deployment with a Parent/Child Domain

After installing Archive Manager, you need to configure the ADC.config file to
reflect your domain layout. For illustrative purposes, we'll assume you have a
parent domain named QUESTLOCAL and a child domain named QUESTCHILD.
The domain controller for QUESTLOCAL is named
server.parent.questlocal.com, and the domain controller for the
QUESTCHILD domain is named server.child.questchild.com.

When editing the ADC.conifg file, it can be easy to miss a tag. For every opening
tag (<tag>), there must be a matching closing tag (</tag>). All tags are case
sensitive, e.g., using UseResourceURL is not the same as USEResourceURL.
Open the ADC.config file in an Internet browser to show any tag errors.

Below is an example of a completed ADC.config file for the Parent/Child domain
of QUESTLOCAL and QUESTCHILD.

<?xml version="1.0"?>
<ArrayOfAfterMailInstance>
<AfterMailInstance>
<Server>server.parent.questlocal.com</Server>
<UserNamingContext>DC=PARENT,DC=QUESTLOCAL,DC=COM</UserNamingContext>
</AfterMailInstance>
<AfterMailInstance>
<Server>server.child.questchild.com</Server>
<UserNamingContext>DC=CHILD,DC=QUESTCHILD,DC=COM</UserNamingContext>
</AfterMailInstance>
</ArrayOfAfterMailInstance>

65

Quest Archive Manager

Deployment With an Exchange Resource
Forest (One-Way Trust)

If you are deploying in an Exchange Resource Forest, then the instance of
Archive Manager or instances should be located in the resource domain. In this
case, you will need to use the ADC.config file to make Archive Manager aware of
the security objects in the account domain.
When editing the ADC.config file, it can be easy to miss a tag. For every opening
tag (<tag>), there must be a matching closing tag (</tag>). All tags are case
sensitive, e.g., using UseResourceURL is not the same as USEResourceURL.
Open the ADC.config file in an Internet browser to show any tag errors.
The following scenario assumes that there is a one-way trust between the
Account and Resource domains. If that is not the case, then there is not a
Resource Forest setup.

1. Create three Archive Manager accounts in the user domain, typically
named ArchiveMgr_Journal, ArchiveMgr_ESM, and
ArchiveMgr_Service.

2. Create a Group called Archive Manager Exchange Admins in the
resource domain, add the ArchiveMgr_ESM account from the account
domain to it. Use that for permissions on all Exchange Servers.

3. Create the journal accounts in the Resource Domain. The
ArchiveMgr_Journal account from the account domain must have the
full mailbox access and read permissions to all the journal accounts
in the resource domain. When creating the MAPI data loader(s) in
the Administration interface, use the FQDN of the resource exchange
server as the Server Name, and the LegacyExchangeDN as the name
for the data load record. This will allow the Exchange Account to be
disabled as is typical in this scenario.

4. The Active Directory Connector must run as the Archive Manager
service account.

66

Post-Installation Tasks

Below is a sample ADC.config file that shows how a Resource Domain would be
specified:

<?xml version="1.0">
<ArrayOfAfterMailInstance>
<AfterMailInstance>
<ConnectionString>
server=QUESTSQL1;Trusted_Connection=yes,database=ArchiveManager
</ConnectionString>
<Server> UserForestDC.quest.local</Server>
<LDAPPath>DC=quest,DC=local<LDAPPath>
<UseResourceURL>1</UseResourceURL>
<ResourceURL>GC://ResourceForestDC/dc=user,dc=local</ResourceURL>
</AfterMailInstance>
</ArrayOfAfterMailInstance>

In order to limit the number of users that will be exported by the ADC, the
ADC.config file can be configured to use filters specific to the objects that you
want to limit.

Deployment With a Trusted Forest

If you have multiple forests in your environment in order to import users into
your Archive Manager instance with the correct login domain, you will need to
set up your ADC.config file to reflect your domain layout. You need to have an
AfterMailInstance entry for each domain that you want the Active Directory
Connector to import.

When editing the ADC.config file, it can be easy to miss a tag. For every opening
tag <tag>, there must be a matching closing tag </tag>. All tags are
case-sensitive, e.g., using UseResourceURL is not the same as UseResourceUrl.
Opening the ADC.config file with Internet Explorer can help you find tag errors.

The following example contains two domains, example.com and mydomain.net.

<?xml version="1.0" ?>
<ArrayOfAfterMailInstance>
<AfterMailInstance>
<Server>server.example.com</Server>
<UserNamingContext>DC=example,DC=com</UserNamingContext>
</AfterMailInstance>
<AfterMailInstance>
<Server>server.mydomain.net</Server>
<UserNamingContext>DC=mydomain,DC=net</UserNamingContext>
</AfterMailInstance>
</ArrayOfAfterMailInstance>

67

Quest Archive Manager

Limiting User Scope to Specific
Organizational Units

To limit users to specific organizational units, use the following command in the
ADC.config file, with semicolons ad a delimiter between the organizational units
that you want to use. In the following example, two organizational units are
used, separated by a semicolon.

<OUList>OU=NorthAmericaUsers;OU=SouthAmericaUsers</OUList>

Special Filtering Requirements

There are optional filters that may be specified in the ADC.config file. These
filters may be used to limit the scope and reduce the number of objects returned.
For example, a filter could be added to only include users whose names start
with the letter "A". The filters are LDAP search style strings and are logically
"and-ed" to the built-in search filters.

• FindDeletedUsersFilter
• FindGroupsFilter
• FindUsersFilter
• FindMailStoresFilter
• FindStorageGroupsFilter
• FindUserForestMailBoxFilter
• FindResourceForestMailBoxFilter

If you have a requirement to add to your Archive Manager database only users,
groups, mail stores, or storage groups that meet special search criteria, you can
use the extra filter definitions defined in the Filters section. In order to use the
filter, you will need to create an ADC.config file and add the <Server> and
<UserNamingContext> sections. You can now add any of the configurable filters,
the filter configuration is logically "ANDed" with the base filter.

As you define your filter you can verify that it is working by using LDIFDE
(http://support.microsoft.com/kb/237677) and your filter definition along with
the ADC's base definition. You can logically AND two filter definitions using
parentheses and the ampersand as follows (more LDAP syntax help can be found
at http://technet.microsoft.com/en-us/library/aa996205(EXCHG.65).aspx):

(& (FILTER1) (FILTER2) )

68

Post-Installation Tasks

When editing the ADC.config file, it can be easy to miss a tag. For every opening
tag <tag>, there must be a matching closing tag </tag>. All tags are
case-sensitive, e.g., using UseResourceURL is not the same as UseResourceUrl.
Opening the ADC.config file with Internet Explorer can help you find tag errors.

<?xml version="1.0" ?>
<ArrayOfAfterMailInstance>
<AfterMailInstance>
<Server>server.example.com</Server>
<UserNamingContext>DC=example,DC=com</UserNamingContext>
<!-- Only export users with surnames that start with A -->
<FindUsersFilter>(sn=A*)</FindUsersFilter>
</AfterMailInstance>
</ArrayOfAfterMailInstance>

Configure ADC Import Behavior

Two program parameters that control ADC import behavior are set in the Archive
Manager Configuration Editor:

• Directory Connector Import Mailbox Permissions: Determines
whether group and user permissions are imported into Archive
Manager. (This feature applies to customer-defined groups, not the
pre-built ones.) Set this parameter to True if you want to import
group and user permissions, and each user having full mailbox access
permissions in Active Directory will be assigned the corresponding
mailbox in Archive Manager. Note that an account with an unresolved
SID in its ACL will not be imported by ADC, nor will the log identify
the account that contains the unresolved SID. Set the value to False
to disable this feature.

• Directory Connector Import Users Without Mailboxes:
Determines whether ADC will import users without corresponding
mailboxes. Set the parameter value to True to enable this feature, or
False to disable it.

69

Quest Archive Manager

Configure and Deploy the Offline
Client (Optional)

If you are using the Offline Client, the Administrator configures offline access and
typically deploys the client through group policies. For information on configuring
an deploying the offline client, see the Download Tools chapter of the
Administration Guide.

Performance Tip: If the volume of users will make the Offline Client load
heavy, you can improve performance by deploying a separate dedicated IIS
server for web services. That is, deploy a second, duplicate IIS Archive Manager
server, then point users' Offline Clients to the web services component of the
second, but leave the primary website URL set to the first, original server.

Deploying the Outlook Form

The Outlook Form is automatically deployed by the Archive Manager installer
when public folders are enabled on the specified Exchange server, and the
Install Outlook form into Exchange checkbox was selected during
installation. See the next section to deploy the Outlook Form when public folders
are not enabled.

The Archive Manager Outlook Components
Tool

The Archive Manager Outlook Components tool provides a method to install the
Outlook Form on users' computers when public folders are not enabled on the
specified Exchange server.

This tool installs an Outlook Add-in on local computers that will automatically
install a copy of the form when a user launches Outlook. Therefore, it is only
necessary to run this tool once per computer. It can be managed by Group
Policy.

Prerequisites

The Archive Manager Outlook Components tool can only be installed with
supported versions of Archive Manager up to version 4.4.2.

• Microsoft .Net 2.0 or later

70

Post-Installation Tasks

Client Workstation for Exchange Mail Systems

• Stripped message reconstruction using the Outlook Form requires the
following:

• Microsoft Outlook 2010 (32-bit), running on Windows 7, or
• Microsoft Outlook 2007, 2003 or (32-bit), running on Vista (RTM, SP1,

or SP2), or
• Microsoft Outlook 2007, 2003 or (32-bit), running on Windows XP

(SP2 or SP3).

Installing the Outlook Add-in Using a Group
Policy

To install the Outlook Add-in on computers that are running Windows XP
Professional, Windows Server 2003, or Windows 2000, please see the Assign a
Package section of the following Microsoft support article:

http://support.microsoft.com/kb/816102

The Outlook Add-in will be installed at the first reboot of the computer after the
group policy has been applied. The Outlook Form will be installed automatically
the next time a user logs in to Outlook after the Outlook Add-in has been
installed. By default, the Outlook Form is installed with standard mail icons. If
you wish to install the Outlook Form with Archive Manager icons, see the
additional instructions below.

A reboot may be required after to install the Outlook Form after installation of
the Archive Manager Outlook Components tool with older versions of Outlook, or
if the form has been manually removed from Outlook prior to reinstalling the
tool. If you are reinstalling this tool on a client computer that is running Outlook
2003, you must delete the following file in order for the Outlook Form to be
installed again:

C:\Program Files\Quest Software\Archive Manager\Outlook
Components\OutlookAddIn.default.config

Installing the Outlook Add-in to Deploy the Form With
Archive Manager Icons Using a Group Policy

1. When installing the Archive Manager Outlook Components tool, on
the Deploy Software screen, click Advanced, then OK.

2. Under the Modifications tab, click Add.

71

Quest Archive Manager

3. Select UseAMIcons.mst.

Installing the Outl ook Add-in Manually

1. Log in to a computer with Administrator credentials.
2. Launch Archive Manager Outlook Components.msi.
3. Follow the prompts in the Windows installer.

The Outlook Form will be installed automatically the next time a user logs in to
Outlook after the Outlook Add-in has been installed. By default, the Outlook
Form is installed with standard mail icons. If you wish to install the Outlook Form
with Archive Manager icons, see the additional instructions below.

Installing the Outlook Add-in Manually to Deploy the
Form With Archive Manager Icons

1. Log in to a computer with Administrator credentials.
2. From a command prompt, navigate to the directory where you have

placed the Archive Manager Outlook Components.msi file.
3. Use the following command to install the package with Archive

Manager icons:
"Archive Manager Outlook Components.msi" FORMAMICONS="1"
4. Follow the prompts in the Windows installer.

Installation Options

For manual installation, the Archive Manager Outlook Components.msi package
can be run in a "silent" mode. In silent mode, no user interface is displayed. To
install with silent mode enabled, run the following command at a command
prompt:

"Archive Manager Outlook Components.msi" /quiet

Relocate FTI Temp Location (If
Necessary)

If the Archive Manager services are on a separate workstation from the
SQL Server: Move the Full-Text Index temp location from the Archive Manager
server to the SQL Server.

72

Post-Installation Tasks

Add MAPI Data Loaders for
Exchange Journal Mailboxes

Microsoft Exchange 2007 includes optional journaling features that can help an
organization meet compliance standards, but that are not installed by default.
Archive Manager lets you configure MAPI data loaders to offload messages from
Exchange Journal mailbox(es) into Archive Manager.
The Pre-Installation Preparations chapter in this Guide suggests that you enable
Exchange Journaling, and the installation procedures include steps to configure
MAPI data loaders to offload messages from Exchange Journal mailbox(es) into
Archive Manager.
If you did not enable Exchange Journaling during installation, you can refer to
your Microsoft documentation to install and configure it now. If you did not
configure MAPI data loaders in the original installation, you can refer to the Data
Loaders chapter of the Archive Manager Administration Guide for the procedure.

73

Quest Archive Manager
74

A

Attachment Store Types

• Attachment Store Types Overview
• Changing the Storage Location After

Installation
• Adding a New Storage Location
• Common Scenarios for Editing the

Configuration

Quest Archive Manager

Attachment Store Types Overview

Archive Manager supports four different storage types for storing attachments
and compliance messages. Details on using each of the storage types are
provided below. The storage types supported by Archive Manager include:

• NTFS / Windows File System: This is the default option, and stores
files on standard disk.

• NetApp SnapLock: SnapLock provides fast WORM (Write Once Read
Many) storage on magnetic disk. It uses non-rewritable, non-erasable
disk storage protects data until a specified retention date.

• EMC Centera: This option uses an external EMC Centera server or
cluster to store the attachments.

• Bridgehead HDR: This option uses an external Bridgehead HDR
server to store attachments.

• IBM DR550: This option uses an IBM DR550 running IBM System
Storage Archive Manager (SSAM) to store attachments.

Archive Manager allows more than one type of storage to be used on a running
system. However, only one storage location can be considered the default
storage location at a time.
When installing Archive Manager, you set the attachment store type on the
Attachment Store Type screen. Once the product is installed, additional
attachment stores can be added. This process is described below in the section
Changing the Storage Location After Installation.
In all cases, Archive Manager stores each unique attachment as a single file or
the equivalent unit. Archive Manager performs no compression or encryption.
This is left to the underlying storage system.

76

Attachment Store Types

Some attachment store types are deprecated in Archive Manager for
new installations. Existing customers on deprecated file storage types
are fully supported and will continue to be supported until a migration
plan is in place and migration tool is available to move to a new storage
type

EXTERNAL STORAGE TYPE ARCHIVE MANAGER VERSION FOR
DEPRECATION

File System Supported.

NetApp SnapLock 7.2.4 Supported.

EMC Centera 4.1.1, 4.1, 4.0, Supported.
or 3.1.4

BridgeHead HT FileStore with Deprecated. Only upgrades supported.
HDR 2.2-20, build 23007

IBM DR-550 version 5.4.1 Deprecated. Only upgrades supported.

(Version 5, Release 4, Level 1)

NTFS/Windows File System

The file system is the default storage mechanism for Archive Manager. This is a
directory structure, usually in C:\ArchiveManager\Data, with each file stored
represented by its database id and file type. For example: 34.gif

These files are stored in blocks of 1000 files per directory. Each database ID has
up to twelve 0’s added to the front. For example, 34 becomes 000 000 000 034,
and this is converted in a directory name:

c:\archivemanager\data\000\000\000\000\34.gif

By default, the entire tree, from c:\archivemanager\data down, is set to be
compressed using NTFS compression. These files will not be rewritten, so any
backup scheme can be used. Quest recommends an incremental backup.

Manual Configuration Options

The File System has these configuration options in the StorageLocation table:

• Storage Type: 1
• ConnectionString: DATA=C:\ArchiveManager\Data\

77

Quest Archive Manager

NetApp SnapLock

The NetApp SnapLock Setup Wizard allows you to create volumes or WORMS on
which Archive Manager can put attachment stores. The volumes containing
attachment stores are an effective tool for compliance.

The NetApp SnapLock Wizard is run from the Archive Manager Installer. Run the
installer during the installation process, unless you already have all the
necessary volumes created.

If a CIFS share is already in place, you can upgrade from a Windows file
system attachment store to NetApp SnapLock by these two steps:

1. Copy the filesystem data folder (containing the archived
attachments) to the NetApp CIFS share.

2. In the Archive Manager SQL database, StorageLocation Table:
Change the connection string (originally in the form
"DATA=\\archivemanagerserver\filesystemlocation") to point to the
new CIFS share location (for example, "DATA=\\NetApp\data").

Manual Configuration Options

The File System has these configuration options in the StorageLocation table:

• Storage Type: 5
• ConnectionString: DATA=\\SnapLock\Data\

Prerequisites

• Install all of the necessary licenses for the NetApp Data ONTAP
operating system.

• In DataONTAP, run the CIFS (Common Internet File System) setup.
The CIFS shows the volume to the Windows system as a drive.

Running the NetApp SnapLock Setup Wizard

The NetApp SnapLock Setup Wizard is run from the Archive Manager Installer.
The NetApp SnapLock Configuration screen contains a Launch SnapLock Setup
Wizard button. When you launch the wizard, fill in the information on the
following screens:

Login Page
• Create New SnapLock Volume: Select this option to create a new
volume.
• Change Retention Times: Select this option to change the default
retention times. The settings here apply only if you select SnapLock
Default as the retention mode in the Archive Manager Installer.

78

Attachment Store Types

• Filer Address: IP name or address of the machine running Data
ONTAP.

• User Name: Account name you want to use to access the machine
running Data ONTAP. This account must be an Administrator account,
preferably root.

• Password: Password for the account used to access the machine
running Data ONTAP.

• Volume Name: Name of the volume you want to create on the
machine running Data ONTAP. Or the name of the volume for which
you want to change retention times. This name is case sensitive.

Volume Properties
• New Volume Name: Enter the name of the volume you wish to
create.
• Number of Disks to Use: Enter the number of disks to use on the
volume. Because it is a RAID configuration, this must be an even
number.
• Create Data Loader User: Select this box if you are not using Active
Directory and need to set up a Journal User for the data loader.
• Data Loader Log-In User Name: Enter the name for the Journal
User that you are creating.
• Data Loader Log-In User Password: Enter the password you want
to create for the Journal User.
• Verify Password: Retype the password.

Click Next to create the volume If this is a new setup, the volume will be created
instantly. If this is an existing setup, the wizard will take some time to prepare
the volume for use.

Retention Time
Current Retention Times: Shows the current settings for the minimum time,
default time, and maximum time.
Set Retention Time: Enter a number for the minimum time, default time, and
maximum time. Select days, months, or years from the drop-down list.

79

Quest Archive Manager

EMC Centera

The EMC Centera is supported for the storage of attachments and compliance
messages. The native Centera API is used to store attachments in the Centera
cluster. Archive Manager considers the Centera to be an "always-online blind
storage system." Archive Manager presents an attachment, and then receives a
“ticket”. To get the attachment back, Archive Manager presents the ticket and
gets the attachment.

Archive Manager does not set any retention policies on the Centera. This is left
to the Centera administrator.

Archive Manager supports any centera settings which can be set on the Centera
connection string or in a PEA file.

Manual Configuration Options

The Centera configuration has the following configuration options in the
StorageLocation table:

• Storage Type: 2 (Non-isolated storage type: 6. Please contact Quest
support before using a non-isolated storage type.)

• ConnectionString: The Centera connection string. Please see the
EMC Centera documentation for examples. The string will look similar
to: 10.1.1.1,10.1.1.2;user=am_user;password=password

Using a PEA File

When utilizing a PEA file with a Centera Configuration, it is important that the
PEA file is accessible by each component that requires access to it. The Archive
Manager components that will access the Centera, and therefore require access
to the PEA file, are:

• Archive Data Load Service
• Archive Full-Text Index Service
• Website

As a result, the group ArchiveManagerServiceUsers should have permissions to
access the PEA file location. The PEA file should also be present on all servers
with the above Archive Manager components. (This is important if you have NLB
WebServers, and/or a clustered Archive Manager installation).

If the machines are separate, then the PEA file must be either configured with a
UNC path, or placed in the same local path as all machines that use the PEA file.

80

Attachment Store Types

Bridgehead HDR

The Bridgehead HDR system is supported for the storage of attachments and
compliance messages. The native HDR API’s are used to store attachments in a
HDR system. Archive Manager considers the HDR to be a "usually-online blind
storage system." Archive Manager presents an attachment, and then receives a
“ticket”. To get the attachment back, Archive Manager presents the ticket and
gets the attachment. If the HDR tells Archive Manager that the attachment is to
be retrieved from slow storage (tape, DVD etc.), Archive Manager presents this
to the user or handles it in the appropriate way.

Note that performing a full text index or reindex can cause the Bridgehead
system to become overloaded with restore requests. Please consult with Quest
before performing this action.

Using BridgeHead configured with transform methods is not supported. It
causes Dataloader exceptions when processing messages.

Manual Configuration Options

The HDR configuration has the following configuration options in the
StorageLocation table:

• Storage Type: 3 (Non-isolated storage type: 7. Please contact Quest
support before using a non-isolated storage type.)

• ConnectionString: The connection string contains the following
items, in the format:
HDRHOME=\\server\hdr;REPID=2
• HDRHOME=path: The UNC path to the Bridgehead HDR system’s
home folder. This is the same as the HDRHOME environment variable.
• LIBPATH=path: The local path to the HDR libraries. This is usually
C:\Program Files\ArchiveManager
• REPID=number: The repository ID to use in the HDR. Default is 1.
• APPLICATIONNAME=name: The application name to use in the
HDR. Default is AFTERMAIL

IBM DR550

The IBM DR550 is supported for the storage of attachments and compliance
messages. The native TSM API is used to store attachments in the system.

81

Quest Archive Manager

Archive Manager considers the IBM DR550 to be a usually-online blind storage
system; we present an attachment, and receive a “ticket”. To get the attachment
back, we present the ticket and get the attachment. If the IBM DR550 tells us
the attachment is to be retrieved from slow storage (tape, DVD etc.), we present
this to the user or handle it in an appropriate way.

Note that performing a full text index reindex can overload the IBM DR550 with
restore requests. Please consult Quest before doing this.

Manual Configuration Options

The HDR configuration has the following configuration options in the
StorageLocation table:

• Storage Type: 4
• ConnectionString: The connection string contains the following

items, in the format:
NODE=tsm;HOST=tsmbox.domain.local;PORT=1500
NODE=(name of SSAM node) – the name of the SSAM node to use

• HOST=(host name / IP of the TSM server): The IP/hostname of
the IBM DR550 server.

• PORT=(port number of the TSM server): The TCP port number.
This defaults to 1500.

• USERNAME=(username): The username to use to connect to the
DR550.

• PWD=(password): The password to use to connect to the IBM
DR550 server. This is encrypted.

• OPMODE=(archive or backup): The operation mode to use. Only
archive is recommended.

• MSGFILESPACE=(filespace): The name of the file space to use for
messages.

• MSGFILEPATH=(path): The path of the filespace to use for
messages.

• ATTFILESPACE=(filespace): The name of the file space to use for
attachments.

• ATTFILEPATH=(path): The path of the filespace to use for
attachments.

• STORECOMPLIANCE=(true, false): Whether or not to store
messages for compliance.

82

Attachment Store Types

Changing the Storage Location
After Installation

The Archive Manager installer will only set up a default storage location if one
does not already exist. To add or change the storage location, follow these steps:

1. Stop the Archive Manager Website and the following Archive
Manager services:
• Data Load
• Exchange Store Manager
• Full Text Index
• Message Retention Policy

2. Make the necessary changes to the StorageLocation table. (See the
table below).

3. Start the services.

Adding a New Storage Location

To do this, create a new row in the StorageLocation table, and set the
StorageType to the appropriate type (1= file system, etc.). Set the connection
string to the format documented for that type earlier in this Appendix, and verify
(or update) the Default column settings. The Default column value for the
default storage location should be set to 1. There can be only one default, so the
Default column value for all other rows must be set to 0.

In this example, a new File System has been added as a storage type, but it is
not yet set it to be the default.
Once the new default is set and the services started, any new attachments will
go into the new location. Any old attachments will remain where they were, and
if a request comes for them, it will be served from that location.
It is possible to have any number of storage locations, of any mix of types. The
only constraint is that they must be present if an attachment is requested, and
only one can be default at a time.

83

Quest Archive Manager

Common Scenarios for Editing the
Configuration

Using a NAS Box

Archive Manager’s installer does not support storing attachments on a NAS box,
as software is installed on the box, which is most likely not running windows.

If you want to store attachments on a NAS box, use the following workaround:

1. When installing Archive Manager, set the services to NOT start after
installation. Install using a normal filesystem storage location.

2. Once Archive Manager is installed, edit the StorageLocation table and
change the default storage location to point to the UNC of the NAS
box. For example: DATA=\\nasbox\archivemanagerstore

3. You must ensure that all Archive Manager users,
ArchiveMgr_Service, ArchiveMgr_ESM, ArchiveMgr_Journal, have full
access to that folder.

4. Start the services. They will now load and retrieve attachments from
the NAS box.

Moving a Store to a New Location

You may need to move your store to a new location, for example, when your SAN
fills up or you need to move the attachment store to a new SAN or machine. This
is usually preferable to having two filesystem stores. However, either option is
valid.

1. Stop all Archive Manager services on the Archive Manager server.
2. Move the attachment store to the desired location.
3. Set compression as needed, and set permissions to match the old

location.
4. Sign in to the SQL server and run Enterprise Manager.
5. Browse to your Archive Manager database.
6. Open the StorageLocations table located under the Tables node.
7. Specify the new location of the store in the connection string.
8. Restart the previously stopped services on the Archive Manager

server.

84

Attachment Store Types

Deleting Attachments from a SnapLock
Volume

The Archive Manager Retention Engine cannot delete attachments from a Data
ONTAP device unless the retention settings in SnapLock contain a retention time
that precedes or is the same as the one set in the Retention Engine. The
Retention Engine generates errors when the retention settings in SnapLock for
attachments on a Data ONTAP device are set at a later time than the Archive
Manager retention delete policy.

85

Quest Archive Manager
86

B

Process Overview
Checklist

• Pre-Installation Checklist
• Install Archive Manager for Exchange
• Post-Installation Checklist

Quest Archive Manager

This checklist provides a high-level overview of the process for installing
Archive Manager for Exchange. Full details for these steps are documented in
earlier chapters of this Guide, as cited below.

Pre-Installation Checklist

For details, see: Pre-Installation Preparations. CHECK

1. Review your system requirements.

2. Configure your Archive Manager Services Server.
1. Install the required software.
2. Configure your antivirus software.
3. Create a DNS entry. (optional)
4. Install Filters (optional)

3. Configure the Archive Manager Database Server.
1. Check your system requirements.
2. Check the database folder.
3. Configure the SQL Agent Service.
4. Configure the SQL Server Data and Log Directories
(optional).

4. Create Accounts and Grant Permissions.
1. Create the Archive Manager accounts and group.
2. Grant permissions to the Exchange Admin Group.
3. Grant permissions to the Archive Manager Service Account.
4. Grant Permissions in a Windows 2000 domain.

5. Configure Journaling on Your Exchange Server
(Optional)

1. Turn on Envelope Journaling.

2. Enable Journaling for a Mailbox Store.

88

Process Overview Checklist

Install Archive Manager for
Exchange

Install Archive Manager using the instructions provided in the Installing Archive
Manager with Exchange chapter of this guide.

Post-Installation Checklist

For details, see: Post-Installation Tasks. CHECK

1. Install the Archive Manager Offline Client. (Optional)
1. Install using Group Policy, or
2. Install at Next User Logon

2. Perform an application functionality check for Login and
Display.

3. Perform an application functionality check for Searching.

4. Perform an application functionality check for Messages.

5. Perform an application functionality check for
Attachments.

5. Perform an application functionality check for Online
Help.

6. Perform an application functionality check for Mailboxes.

7. Perform an application functionality check for
Administrator Features.

89

Quest Archive Manager
90

About Quest Software

Quest Software simplifies and reduces the cost of managing IT for more than
100,000 customers worldwide. Our innovative solutions make solving the
toughest IT management problems easier, enabling customers to save time and
money across physical, virtual and cloud environments. For more information
about Quest go to www.quest.com.

Contacting Quest Software

Email [email protected] Mail Quest Software, Inc.
World Headquarters
Website www.quest.com 5 Polaris Way
Aliso Viejo, CA 92656
USA

Please refer to our Web site for regional and international office information.

Contacting Quest Support

Quest Support is available to customers who have a trial version of a Quest
product or who have purchased a Quest product and have a valid maintenance
contract. Quest Support provides unlimited 24x7 access to our support portal.
Visit our support portal at: http://support.quest.com.

From our support portal, you can do the following:

• Retrieve thousands of solutions from our online Knowledge Base
• Download the latest releases and service packs
• Create, update and review Support cases

View the Global Support Guide for a detailed explanation of support programs,
online services, contact information, policies and procedures. The guide is
available at: http://quest.com/support.

91

Quest Archive Manager

Product Information and
Documentation

Visit the following page to view our most recent product solutions, downloads,
documentation, notifications and product lifecycle table (login to SupportLink is
required): https://support.quest.com/Search/ProductInformation.aspx

Visiting Our Archive Manager
Online Community

The Quest Archive Manager community is an interactive community dedicated to
issues related to email data management, including storage, compliance, and
knowledge management. The community is designed to foster collaboration
between Quest Archive Manager experts and users. This community is a place
where you can:

• Learn about product releases and betas before anyone else.
• Get access to Quest product leaders and subject matter experts

related to archiving.
• Gain additional knowledge from discussion forums and get common

questions answered.
• Ask questions. Share knowledge. Exchange ideas regarding your use

of archiving products, as well as on general archiving topics.

You can browse around the forums and the library, but to take full advantage of
the community, post new threads, respond to messages from others, rate our
documents and downloads, you need to become a registered member. And if you
already have a Quest account or are a member of another Quest community,
simply log in.

Join the community at Quest Archive Manager Community.

Other Quest Communities

Quest.com has a large and growing number of communities dedicated to specific
products and technologies.

92

Visit these communities to get access to the expertise at Quest Software and
take part in product development through discussion forums, polls, and product
betas. Also find the latest product news and announcements, and browse a
knowledge base of general documentation, tips and tricks, product videos and
tutorials.
http://www.quest.com/communities/

93

Quest Archive Manager
94


Click to View FlipBook Version