Auto Accept Agent Deployment and Administration Guide
Topic Last Modified: 2006-07-14
This guide explains how to install, configure, and administer Auto Accept Agent, a store event sink that automatically processes meeting requests for resource mailboxes. This guide leads you through the installation process, which installs Auto Accept Agent on your computer and registers Auto Accept Agent as a Component Object Model (COM+) component. After you have installed Auto Accept Agent, you then need to configure it and register the resource mailboxes on which you want this event sink to run. Additionally, this guide provides you with troubleshooting information that is relevant to Auto Accept Agent.
|Download Auto Accept Agent Deployment and Administration Guide to print or read offline. Download Microsoft Exchange Server Auto Accept Agent to get the applicable tool and scripts.|
The guide covers the following topics about Auto Accept Agent:
- Understanding Auto Accept Agent: This section contains an overview of Auto Accept Agent and explains its underlying technologies.
- Planning an Auto Accept Agent Deployment: This section outlines the possible security contexts in which you can run Auto Accept Agent, as well as how to prepare your Microsoft® Exchange server and resource mailboxes.
- Installing Auto Accept Agent: This section explains how to install Auto Accept Agent, and how to verify that it was correctly registered as a COM+ component.
- Configuring Auto Accept Agent: This section discusses how to modify the XML configuration file.
- Registering Mailboxes: This section explains how to register the resource mailboxes for which you want Auto Accept Agent to process meeting requests.
- Managing Resource Mailboxes: This section discusses how to monitor your resource mailboxes and manage mail retention.
- Troubleshooting Auto Accept Agent: This section contains information about messages that Auto Accept Agent writes to the application event log, performance counters, and response codes.
To successfully complete the procedures discussed in this guide, ensure that your computer meets the following software requirements.
Microsoft Windows® 2000 Server Service Pack 4 or a later version, or Windows Server® 2003
Microsoft Exchange Server 2003
Microsoft .NET Framework 1.1
Before you read this guide, become familiar with the following technologies and terms.
- Event sink
Code that gets activated by a defined trigger, such as the receipt of a new message. Exchange store event sinks can be synchronous (code executes as the event is triggered) or asynchronous (code executes sometime after the event).
- Store event
The occurrence of a particular action or the occurrence of a change of state that can be handled by an event sink.
Extensible Markup Language (XML) is a tag language based on Standard Generalized Markup Language (SGML) that is optimized for delivery over the World Wide Web. XML defines data layout for a document, but it does not display characteristics, which are generally defined by using HTML. It allows data to be manipulated using HTTP, WebDAV, and Extensible Style Language (XSL) among different applications on different operating systems. XML is not required to conform to the HTML specification.
Exchange OLE DB (ExOLEDB) is an OLE DB provider that you can use to access Exchange store items. Because ExOLEDB is a server-side component, you can only use ExOLEDB to access mailboxes and public stores that reside on the local server.
CDO for Exchange 2000 Server (CDOEx) provides interfaces and Component Object Model (COM) classes that you can use to manage most types of items in the Exchange store. For example, you can use CDOEx to create, modify, send, and delete messages, as well as to manage appointments in a user's calendar folder.
Before you read this guide, you should understand the following terms:
- Resource mailbox
An Exchange mailbox that represents a resource that can be scheduled, such as a conference room or video conference equipment. Resource mailboxes do not represent people.
- Recurring meeting
A meeting that occurs more than one time and follows a pattern in time. For example, a department meeting on the first Tuesday of each month can be defined as a recurring meeting.
A single Appointment object and one or more RecurrencePattern objects represent a recurring meeting. The Appointment object defines the first meeting (the meeting master), and the RecurrencePattern objects define the pattern for additional meeting instances. You can also specify modifications to the recurring meeting pattern by using one or more Exception objects.