Product Support Article
Article ID: PSA100224 

Using Attachment Executive Server Side in a Clustered Environment

Table of Contents

1. How does AESS work?
2. How do you set up AESS in a clustered environment?
3. What is modified on my server when AESS is installed?
4. What do I need to back up with respect to AESS components?
5. How to restore AESS when a server fails

1. How does AESS work?

Attachment Executive Server Side removes attachments from the exchange databases using MAPI. MADSolutions feels the safety factor built into MAPI ensures the least amount of impact and risk to a corporate messaging environment.  Since AESS uses MAPI to access the information stores, the exact location of the data is not particularly relevant as the AESS service does not require direct access to the database. The mailboxes and public folders are logged into via a MAPI session.

2. How do you set up AESS in a clustered environment?

Run AESS setup on the primary node of your cluster. This should be an active node. In a clustered environment, the service should only be installed on one server within the cluster.

The AESS service mailbox should reside on one of the databases on the same server.

3. What is modified on my server when AESS is installed?

The following items are modified on your server when installing AESS:
- A file folder called "MADSAESS" is created in the root of the hard drive that you select.
- A network share called "MADSAESS" is created that points to the file folder that was created.

<Microsoft Exchange 2000 only>
- A user for "MADSolutions AESS - <server name>" is created in the Active Directory under the "Microsoft Exchange System Objects" container.
- The user that was created is added to the 'Account Operators' and 'Enterprise Admins' security groups.
- An associated Exchange 2000 mailbox is created for the AESS user in the mailbox store that you select.
- The user that was created is given permission to logon as a service on the server.

<Microsoft Exchange 4.0, 5.0 and 5.5 only>
- A mailbox for "MADSolutions AESS - <server name>" is created in the recipients container on the server.
- A service called "MADSolutions AESS" is installed on the server and the proper service files are copied to the share that was created.
- Extra information for the service is installed in the registry in the section for services on the server.
- Configurations, log files and any extra information or data for MADSolutions AESS is stored in the network share that is created on your server.

4. What do I need to back up with respect to AESS components?

The "MADSAESS" folder should be backed up on a regular basis. If a failure should occur, the configuration for the AESS rules can then be restored from backup.

5. How to restore AESS when a server fails

- Create a new file folder called "MADSAESS" on the new server. Share this file folder as "MADSAESS".
- Copy all of the files and folders from the previous "MADSAESS" share to the new share.
- In the MMC Console for AESS, install the "AESS Service" again. You can install or reinstall the service at any time. You do not have to remove the mailbox, user or service first. Your configurations and log files will not be affected by installing or uninstalling the service.
- If you ran the main setup for AESS and you are administrating the software through the MMC Console on the server, you will need to run the main AESS installation again. This will not affect your configurations, log files or operation of the service.