Export (0) Print
Expand All
2 out of 4 rated this helpful - Rate this topic

Configuring Auto Accept Agent

 

Topic Last Modified: 2006-07-18

This topic contains information about how to configure Auto Accept Agent settings in the XML configuration file (AutoAccept.config.xml). The topic also covers parameters that trace event logging for Auto Accept Agent.

After Auto Accept Agent has been installed on an Exchange server, you can configure the default processing policy applied on the server by editing the XML configuration file, AutoAccept.config.xml, which is in the install folder. The default install folder is \Exchsrvr\Agents\AutoAccept.

You can also specify processing for individual mailboxes in this XML configuration file. Because no configuration data is stored in the Active Directory® directory service, the configuration settings are unique to each server. The following table contains the configuration settings that you can modify in the XML configuration file. The DeleteAttachments, DeleteComments, RemovePrivateProperty, DisableReminders, and DeleteNonCalendarItems settings allow modifications only to resource mailbox items, not to items in the organizer's mailbox.

Configuration settings in AutoAccept.config.xml

Parameter Description Possible values Default value Scope

DeleteAttachments

Determines whether to delete attachments in an accepted meeting.

True, False

True

Global, mailbox

DeleteComments

Determines whether to delete comments in an accepted meeting.

True, False

True

Global, mailbox

RemovePrivateProperty

Determines whether to remove the private designation on an accepted meeting.

True, False

True

Global

DisableReminders

Determines whether to disable reminders on an accepted meeting.

True, False

True

Global, mailbox

DeleteNonCalendarItems

Determines whether to delete items in the Inbox that are not meetings.

True, False

True

Global, mailbox

EnforceRecurringMeetingEndDate

Determines whether to enforce an end date for recurring meetings. If set to True, recurring meetings with an end date beyond the end of the booking window are declined.

True, False

True

Global, mailbox

BookingWindowInMonths

The number of months ahead that a meeting can be booked. Requests beyond this limit are denied if EnforceRecurringMeetingEndDate is set to True. If EnforceRecurringMeetingEndDate is set to False, requests will be truncated to the limit set by this parameter.

0 - 36

12

Global, mailbox

RecurringMeetingConflictPercentageAllowed

The percentage of conflicts allowed when accepting a recurring meeting. Requests greater than this limit are denied.

0 – 100

0

Global, mailbox

RecurringMeetingMaximumConflictInstances

The number of conflicts allowed when accepting a recurring meeting. Requests greater than this limit are denied.

0 – n

(no maximum is enforced)

0

Global, mailbox

TraceLevel

Determines the diagnostic tracing. For more information about tracing, see "Tracing Parameters" later in this guide.

0 – 4

0

Global, mailbox

TraceToEventLog

Determines whether tracing information is logged in the Application log. For more information about tracing, see "Tracing Parameters" later in this topic.

True, False

False

Global

TraceListenerFile

The file to which tracing information is logged. For more information about tracing, see "Tracing Parameters" later in this topic.

String

<system drive>:\temp\log.txt

Global

EnableResponseDetails

Includes a description of why a meeting was accepted or declined in the e-mail response. The response may also include additional conflict information.

True, False

True

Global

IncludeDebugInResponse

Includes the response code and agent information in the e-mail response. Regardless of this setting, debugging information is always returned in the category of the e-mail response.

True, False

True

Global

CustomResponseText

A customizable text string that is included in the e-mail response. This text displays after the response details, but before the debug information in the e-mail response. A new line will display in the e-mail response. If the text string is longer than 512 characters, the text is truncated in the e-mail response.

0 to 512 characters

None

Global

The following is an example of an AutoAccept.config.xml file.

<?xml version="1.0" encoding="utf-8" ?> 
<Configuration 
   xmlns:xsd="http://www.w3.org/2001/XMLSchema"    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"    xmlns="urn:microsoft.exchange.agents.autoaccept.config"    xsi:schemaLocation="urn:microsoft.exchange.agents.autoaccept.config AutoAccept.config.xsd">
 <GlobalSettings>
 <BookingWindowInMonths>12</BookingWindowInMonths> 
   <DeleteAttachments>true</DeleteAttachments> 
   <DeleteComments>true</DeleteComments> 
   <DeleteNonCalendarItems>true</DeleteNonCalendarItems> 
   <DisableReminders>true</DisableReminders> 
   <EnforceRecurringMeetingEndDate>true</EnforceRecurringMeetingEndDate> 
  <RecurringMeetingConflictPercentageAllowed>0</RecurringMeetingConflictPercentageAllowed> 
<RecurringMeetingMaximumConflictInstances>0</RecurringMeetingMaximumConflictInstances> 
   <RemovePrivateProperty>true</RemovePrivateProperty> 
   <TraceLevel>0</TraceLevel> 
   <TraceListenerFile>c:\temp\log.txt</TraceListenerFile> 
   <TraceToEventLog>false</TraceToEventLog> 
   <EnableResponseDetails>true</EnableResponseDetails> 
   <IncludeDebugInResponse>true</IncludeDebugInResponse> 
   <CustomResponseText /> 
  </GlobalSettings>
  <Mailbox EMailAddress="conf-room1@example.com">
   <Settings>
    <BookingWindowInMonths>12</BookingWindowInMonths> 
    <DeleteAttachments>true</DeleteAttachments> 
    <DeleteNonCalendarItems>true</DeleteNonCalendarItems> 
    <DisableReminders>true</DisableReminders> 
  <RecurringMeetingConflictPercentageAllowed>25</RecurringMeetingConflictPercentageAllowed> 
<RecurringMeetingMaximumConflictInstances>4</RecurringMeetingMaximumConflictInstances> 
    <TraceLevel>0</TraceLevel> 
   </Settings>
  </Mailbox>
  <Mailbox EMailAddress="conf-room2@example.com">
   <Settings>
    <BookingWindowInMonths>8</BookingWindowInMonths> 
    <DeleteAttachments>true</DeleteAttachments> 
    <TraceLevel>4</TraceLevel> 
 </Settings>
 </Mailbox>
</Configuration>

In the XML configuration file, you can configure settings that affect either all registered mailboxes on a server or individual mailboxes.

When you install Auto Accept Agent, default parameter settings are enforced regardless of whether configuration information is available from the XML configuration file.

The global settings that you specify in the XML configuration file are server-wide settings that affect each registered mailbox, regardless of which mailbox database the mailbox belongs to. Global settings override default configuration settings.

The mailbox settings that you specify in the XML configuration file affect only the resource mailbox for which the settings are specified. When you specify mailbox settings in the XML configuration file, you must identify the mailbox by using its primary Simple Mail Transfer Protocol (SMTP) address. If you change the primary SMTP address of a registered resource mailbox, you must reregister the mailbox. Mailbox configuration settings override both default and global configuration settings.

If a mailbox configuration setting is absent or invalid for a parameter, Auto Accept Agent uses the global setting for that parameter. If a global setting is also absent or invalid, Auto Accept Agent uses the default setting for that parameter.

If you save an invalid XML configuration file, an event is written to the application event log. No custom global or mailbox configuration settings will be enforced until the file is edited and saved. For example, an XML configuration would become invalid if an XML tag was omitted or misspelled. If a value outside the allowed parameter range is specified, the default value is used instead. One method that you can use to ensure that the changes you make to your configuration file are valid is to edit and validate the configuration file in Microsoft Office Word 2003.

To edit and validate an XML file in Word 2003
  1. Open AutoAccept.config.xml in Word 2003.

  2. On the Tools menu, click Templates and Add-Ins.

  3. On the XML Schema tab, click Add Schema. Navigate to the AutoAccept install folder. By default, this is \Exchsrvr\Agents\AutoAccept.

  4. Click AutoAccept.config.xsd, and then click Open.

  5. In the Schema Settings dialog box, click OK.

  6. Ensure that the Validate document against attached schemas check box is selected.

  7. Ensure that the Allow saving as XML even if not valid check box is clear, and then click OK.

As you are working in the configuration file, the XML Structure task pane displays icons that alert you to edits that invalidate the file. Additionally, when you are working in Normal view, Word marks schema violations with a purple wavy line in the body of the document. You can hide schema violations by selecting the Hide schema violations in this document check box in the XML Options dialog box. For more information about how to use the XML validation features of Word 2003, see the Word 2003 Help.

Auto Accept Agent logs significant errors, warnings, and informational messages to the Application event log using the event source name "Auto Accept Agent". When exception information accompanies a message, the following items are included: error message string, HRESULT, and call stack. For more information about the messages logged by Auto Accept Agent, see Troubleshooting Auto Accept Agent.

Three parameters in the XML configuration file control tracing to the application event log and a listener file. By default, these parameters are not enabled. It is recommended that you enable these parameters only when troubleshooting. For more information about how to troubleshoot, see Troubleshooting Auto Accept Agent.

  • TraceLevel   The TraceLevel parameter determines the diagnostic tracing for Auto Accept Agent. TraceLevel is the only parameter that can be set either globally or for an individual mailbox. The following table contains the available values for the TraceLevel parameter. The default value is 0.

TraceLevel parameter values

Value Type of message

0

None (no tracing); the default value

1

Only error

2

Warning and error

3

Informational, warning, and error

4

Verbose, informational, warning, and error

  • TraceToEventLog   The TraceToEventLog parameter determines whether tracing information for Auto Accept Agent is logged in the Application event log. True enables tracing information to be logged in the application event log. False disables this action. The default value is False. When set to False, errors will still be logged in the application event log.
  • TraceListenerFile   The TraceListenerFile parameter contains the name of the file to which the tracing information is logged. The default file is "<system drive>:\temp\log.txt".
    noteNote:
    If the specified folder path does not exist, Auto Accept Agent does not log tracing information. If the folder path exists, but the file does not exist, Auto Accept Agent creates the file and then starts logging.
 
Did you find this helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

ADD
Show:
© 2014 Microsoft. All rights reserved.