Troubleshooting Exchange 2003 Auto Accept Agent using scripts

re: Troubleshooting Exchange 2003 Auto Accept Agent using scripts

Brian — Mon, 20 Mar 2006 21:44:41 GMT

Thanks for posting more information about AutoAccept Agents.

Microsoft Exchange: Auto Accept Agent

Martin Pavlis - pavlis.net — Tue, 21 Mar 2006 11:52:53 GMT

re: Troubleshooting Exchange 2003 Auto Accept Agent using scripts

Michael Edward Kohlman — Tue, 21 Mar 2006 22:10:11 GMT

Great posts about Auto Accept Agent and Resource Accounts. We are in the process of examing what approach we wish to take in this area and the posts have been very helpful.

re: Troubleshooting Exchange 2003 Auto Accept Agent using scripts

Joel Donaldson — Tue, 21 Mar 2006 23:09:54 GMT

What about when forms authentication is turned on. How should the server be configured to handle that.

re: Troubleshooting Exchange 2003 Auto Accept Agent using scripts

Nagesh — Wed, 22 Mar 2006 15:57:25 GMT

Joel I dont see how FBA would affect AAA. I know of one known issue so far which is documented in http://support.microsoft.com/?kbid=912127 (After you enable Always-Up-To-Date notifications in Exchange Server 2003 SP2, asynchronous event sinks in the mailbox store do not run)
I will have to check to see if FBA causes any issues.

- Nagesh

Weekend reading

subject: exchange — Sun, 02 Apr 2006 16:05:52 GMT

Today this list is longer, since I hadn't the time to post it last week. Sorry...

Exchange on NAS:...

re: Troubleshooting Exchange 2003 Auto Accept Agent using scripts

Dawn — Mon, 03 Apr 2006 21:21:05 GMT

This info is great. I do have an issue that maybe you can help with. We had a few resources deleted before I had the opportunity to unregister them. Now everytime we reboot the server the following gets written to the Application log for each resource that was deleted:
Event Type: Error
Event Source: EXOLEDB
Event Category: Events
Event ID: 103
Date: 4/2/2006
Time: 6:25:21 AM
User: N/A
Computer: US-BV-M22
Description:
Microsoft Exchange OLEDB was unable to initialize the event binding for file://./backofficestorage/exgate.tek.com/MBX/us-bv-eq-ue-jvcbatt2/Inbox/OnSaveForAutoAcceptAgent. BindingID = {36C403FB-74EC-4707-B93F-9983731E0AE7}, HRESULT = 0x80070002.

Is there a way for this to be fixed with out having to create a mailbox for each resource that was deleted?

How do you know which mailboxes are registered with the Auto Accept Agent?

You Had Me At EHLO... — Fri, 14 Apr 2006 20:57:52 GMT

This is my 4th blog post on the subject of Exchange 2003 Auto Accept Agent. If you want to see previous...

re: Troubleshooting Exchange 2003 Auto Accept Agent using scripts

Ben — Tue, 25 Apr 2006 22:28:42 GMT

I'm having trouble registering mailboxes and getting the AAA to work. Here's some output from MailboxStatus.vbs:

<MailboxStatus>
<Summary>

<CurrentTime>4/25/2006 12:24:34 PM</CurrentTime>
<MailboxCount>1</MailboxCount>
</Summary>

<Mailbox EmailAddress="zcol@healthnotes.com">










<Server>EYEBRIGHT</Server>
<RegistrationStatus>2</RegistrationStatus>
<RegistrationTime></RegistrationTime>
</Mailbox>
</MailboxStatus>

When I paste the URL from the "url = http......" line, I get successful login to OWA for the account. Also, I had this test account properly process the request, but I got a text-based e-mail confirmation, rather than the pop-up dialog I got on my previous E2k3 server. Thoughts? Thanks -Ben

re: Troubleshooting Exchange 2003 Auto Accept Agent using scripts

Ben — Tue, 25 Apr 2006 22:40:37 GMT

Follow-up to mailbox registration problem. I have a bunch of deny ACEs for the resource account for the various Admins groups on the Full Mailbox Access permissions. Could this be preventing me from registering the resource accounts? I made sure I logged into the resource accounts using OL.... Thanks -Ben

re: Troubleshooting Exchange 2003 Auto Accept Agent using scripts

Nagesh — Thu, 27 Apr 2006 00:03:28 GMT

In every case that I have seen, permissions on the account being a little wacky can definitely be the cause (not having the correct permissions, etc.). Is this a disabled account by any chance? – If so, have you tried enabling the account and re-registering the room?