Paul - I understand your frustration very well because I'm living it, too. I've been on MS web pages that have literally updated *while I was reading them*! In any event, either workaround will work (turn off AAA or modify the config file). Whatever
you do, there's going to be double-bookings and, worse, holes in the calendar where meetings should be until the meeting organizer runs TZMove.
Brian - AAA is an add-on for Exchange 2000. It's available here: http://www.microsoft.com/downloads/details.aspx?FamilyID=3D0884E6-C603-491D-BF57-ACF03E046BFE&displaylang=en
http://www.microsoft.com/downloads/details.aspx?FamilyID=3D0884E6-C603-491D-BF57-ACF03E046BFE&displaylang=en.
My testing and experience shows that if you use direct booking, a resource mailbox will accept a double-booking, or conflict, even if the resource mailbox is configured to decline conflicts. I believe this is because the updates that are generated are not
normal updates. Did anyone notice that the updates that TZMove or the MSExTMZCFG tools generate don't show as "Update: our meeting", like a regular update does?
PS - Just to be clear, I don't work for MS. I'm an MCSE:Messaging consultant working for a MS Gold Partner. I've been working on DST solutions for customers from 100-10,000 users.