DST and resource mailboxes – Auto Accept Agent and Direct Booking

When running the Exchange Time Zone Update tool, or the Outlook Time Zone update tool, issues may arise with Resource mailboxes. There are two methods of managing Resource mailboxes. The first method is using the Auto Accept Agent. The second method is by implementing Direct Booking using Outlook's Resource booking functionality.

The Auto Accept Agent is installed and configured on the Exchange Server where the resource mailbox resides. The following workarounds can be used to mitigate problems with the Time Zone Update tools.

UPDATE 3/1: We have consolidated the listed workarounds below to the list of workarounds that will give you the best results only. 

Auto Accept Agent

Workarounds are listed from easier to harder.

Auto Accept Agent Workaround #1

The hotfix for the Outlook tool is now available. Please see the following KB article:


Please note that the original Outlook tool has to be installed before the hotfix is applied. The article contains information about new switches available in the tool.

Auto Accept Agent Workaround #2

1. Disable the Auto Accept Agents by unregistering the mailboxes.

2. Run the Exchange Time Zone Update Tool.

3. Log in to each Resource mailbox, and manually process all updated meeting requests.

Auto Accept Agent Workaround #3

1. Install the Windows and Exchange DST patches.

2. Do not run either the Exchange Time Zone Update Tool, or the Outlook Time Zone Update Tool. Have meeting organizers update the Subject of the meetings only to reflect the correct time and time zone.

Direct Booking

The hotfix for the Outlook tool is now available, this is your best way of dealing with Direct Booking resources. Please see the following KB article:


Please note that the original Outlook tool has to be installed before the hotfix is applied. The article contains information about new switches available in the tool.

- Ben Winzenz, thanks also to Richard Roddy

Comments (60)
  1. John says:

    For resource MB what if you just stop and disable the Microsoft Event Service, open each MB after rebasing is completed and accept all requests that are sent? Will there be any issues with this approach?

  2. Eric says:

    Do you have to actually rebase the Resource MB?

  3. kimono says:

    The 2003 Autoaccept agent is sink based and so doesn’t need the Event service to be running. Event service is 5.5 technology..

  4. Keith says:

    Thanks for all the work.  Personally, I’ll be watching for a new version of the tool.

  5. BK says:

    Do you have any ETA for a new version of the tool?  


  6. Alison Bray says:

    We would like to know an ETA so we can better plan for our deployment schedule.  We hope it is posted early this week than next:)

  7. Craig says:

    What happens if a user that got declined in the past because the resource was taken has the resource in the "resource" invitee list still.  Then the person that had the room originally has the time zone update tool ran after this mailbox.  Sounds like the original meeting will get booted from it’s time slot because of this.

  8. Anonymous says:

    Updated DST Home Page Microsoft’s DST Home Page at http://www.microsoft.com/dst2007 has been updated

  9. Anonymous says:

    If you have been checking our DST Webcast page, you could see the following Webcast is coming up shortly:…

  10. JeffBe says:

    How did you get Exmrege to archive the meeting information from the calendar?  Exmerge only gives the option to archive a date range based on Message Delivery or last Modification Time.  The calendar entries do not fall into either category.

  11. SteveS says:

    How long do we need to wait for the AAA update tool? Microsoft made the Windows update critical last week. Computers are starting to get the Windows DST patch installed and are starting to see issues when creating meeting requests during March 11th and April 8th. The sooner the better for everyone! Thanks.

  12. Anonymous says:

    I’m copying an entire blog post because the info is really good…. for those who have Public folder

  13. Steve says:

    Is the "Automatically decline conflicting meeting requests" setting exposed to CDO or Outlook APIs?

    We have 1900 resource mailboxes to update this weekend, and the process or clearing and then resetting this option on each one is going to take a long time. I could easily code something if this option can be accessed via an API.


  14. Scott says:

    We have a lot of direct booking, where is thst new tool?

    Or if anyone has a script to adjust the "decline conflicting"…

    In the time it’s going to take me to change all of these both ways manually I see a lot of new conflicting meetings booked.

  15. Jon says:

    This is really getting old.  How can we decide on whether or not "we can wait" when you won’t tell us how long we have to wait?  GIVE US A DATE, PLEASE!!!!  I understand MS is trying to help by updating these tools, but in reality you’re hurting us by not making any commitments.  So instead we are forced to move forward with our existing plans based on existing tools (because this is so time critical), only to what — find out a day or two later that you’ve released something new that makes more sense in our environment and we have to change our plans all over again?  Can someone over there please stand up and flippin’ start communicating dates?  Even if you say "this is the target date and it may slip", that’s better then this open-ended FUD you keep flinging around.  While you’re at it, get the Outlook team to frickin’ communicate some dates for the client CDO updates!  Your products rock, but your ability to truthfully help your customers through this situation is pathetic.

  16. Exchange says:


    I am sorry there is no better date that I can give you other than say it will be the week of 2/26 when the new OL tool will be out.

  17. Steve says:

    Scott – please send me an email and I’ll send you an app that I cobbled together today.


  18. Kristin says:

    All – FYI: the Exmerge Archive option to clear out the meeting room calendars between a certain date range does NOT work.  

    Don’t expect to use that workaround!  In testing, setting the Archive option in Exmerge only worked if you did not specify a date range.  If you specify a date range it doesn’t work.

    Kind of a pain for large companies that have lots of meeting rooms to manually clear out the meetings or write a script.  If anyone has written a script, please post!



  19. jc9394 says:


    I’m interested in the you have that address the "decline conflicting", I will email you..



  20. Mears says:


    That’s odd that you mention the Archive option doesn’t work for you.  I was able to archive calendar entries for 1 of our resources successfully and then send an update and the room accepted the request.  

    I specified the date range from the 11th to 1st as well.  

  21. mlgomez says:

    I’m with Jon. We are still bantering back-n-forth between running the Exchange took, Outlook tool or having the users work their own calendars manually. We are a small-medium shop with 3 Exchange servers on Exch 2003, about 1000 mailboxes, users running Outlook 2002. We have 1 critical app that is a Pop3 account and would be devastating if we "lost" our server. I wanna final fix because we’re running out of time. We have to have a decision  made by tomorrow because whatever we do, we have to do by Mar 2 weekend.

  22. John Orsini says:

    I have the same question JeffBe had on Feb. 20th.  It does not appear the the most current publicly released version of Exmerge can remove the appointments.  Does MS have a newer, or more powerful version of Exmerge?  If so, how can we obtain it?  If not, please let us know in detailed steps how to use the tool properly.  



  23. guy says:

    I see a new version (2.0) of the tool was released today  – is this the one ?


  24. Mears says:

    Within Exmerge select only the calendar to process and then go to Dates and enter the target dates which would be 3-11-2007 through 4-1-2007.  This will export all the information from the calendar within those target dates.  

    (This worked for me…Not sure why it wouldn’t be working you either)



  25. Exchange says:

    Kristin, John and others that have issues with Exmerge:

    This is unfortunately something that might but also might not work for you depending on when your appointments were created… we had some customers that used this option with success. We do not have a newer version of Exmerge, no.

    Now for the good news: the updated version of the Outlook tool that was mentioned as option #1 in the post above is scheduled to be released next week, should be early in the week. This is the tool that will have additional options that will help with rebasing the resource mailboxes. While realizing it is getting awfully close – I would suggest you wait until the tool is out, as it should help especially if you have a lot of resource mailboxes.

  26. Exchange says:


    The tool you linked to is the updated Exchange tool which brings some good imporovements but is not what will help rebase resource mailboxes. The updated Outlook tool is going to release next week, should be early in the week, and that is the tool that will have new functiinality to address PF calendars and resource mailboxes better.

  27. John Orsini says:

    Thanks for the 2.0 tool.  I am going to advise my clients to start utilizing that to update everything but resource mailboxes.  Just for my own curiosity, where can I find what the 2.0 version of the tool fixes or does differently than the 1.0 version.  I downloaded it and looked for a readme, but there was none.  Please let us know.  

  28. Dean Chen says:

    Following John Orsini’s comments, in 1.0 version, there is a daylight.prf file, while in 2.0 version, the daylight.prf is gone. KB article 930879 was updated yesterday to reflect the change. My question is do we still need the daylight.prf master .prf file?

  29. ninob says:

    John, the http://support.microsoft.com/kb/930879 says:

    Version 2 of the Exchange Calendar Update Tool was released on February 21, 2007. This article refers to version 2 of the Exchange tool. If you are running version 1 of the Exchange tool, uninstall it and install version 2. Version 2 of the Exchange tool includes the following improvements:

    • Performance in version 2 is twice as fast as version 1 when you run the tool in Update mode.

    • User interface is improved.

    • Memory leak is fixed that required client computers to be frequently restarted.

    • Improved algorithm is included for mapping extracted time zones to the operating system time zone.

  30. Keller says:

    I am getting the following message when I try to install version 2 of MSEXTMZ.MSI – Unable to install because previous version of ‘Microsoft Exchange Calendar Update Tool’  and/or ‘Microsoft Exchange Calendar Update Configuration Tool’ was detected. Please uninstall them and run this setup again. I have uninstalled the previous version and rebooted and still get the error and do not know what more to do. Any one have an idea on what to do.

  31. Dean says:

    The previous version of kb930879 article said the DST udpates 931836 and 926666 should be applied before running EXchagne Calendar Update Tool. I did apply the updates on my exchange servers. Today the updated version 11 of kb930879 reversed the order. DST updates should be applied after Exchange tool. This is very frustrated. While I am waiting for the new Exchange tool next week, can someone tell if I don’t uninstall the DST updates, would that be bad? I have 7 exchange servers. That requires a lot of outage work.

  32. guy says:

    when the new Outlook comes out next week – do we simply reinstall the new Outlook tool  that is installed on our server we are running the Exchange tool so that the Exhcnaeg tool points to the new Outlook tool (TZMOVE)?

  33. Anonymous says:

    Exchange 2007 Discontinued Features The 10 most common Exchange Server issues and how to avoid them Exchange

  34. Karol Lynch says:

    has any tried the workaround #3?  i’ve tried #2 and it isn’t working

  35. DaveC4 says:

    The exmerge option doesn’t work. It appears that exmerge looks for when the calendar entry was created and is not looking for the date that the entry is for. In other words if I create a booking for March 26 on Feb 1st, exmerge is looking at the Feb 1st date. Take a look at the resource under the .backofficestorage location and you’ll see what I mean.

  36. Steve says:

    You CANNOT do workaround #2 (step 1).  Exmerge doesn’t have the ability to select dates of meetings to archive, ONLY dates of when emails were generated or modified.  Since many of the meetings may have been generated (and not modified since) last year, they won’t be included in the date range of the DST change period.  I have tested this several times and cannot get only the meetings on those dates to archive.  If there is a hack to make this work, please post it.

  37. President Carter says:

    Our MS TAM just reported that the new outlook tool should be out VERY shortly… waiting for the website to be updated, in fact.

  38. Cameronk says:

    The new tool is out (via a hotfix updating the old tool):


  39. John says:

    Removed the AAA, run the exchange tool , open each resource mb and accept all meetings.

    Make sure your clients do not have full mailboes – increase the limts  this will allow them to send updates

  40. Dennis says:

    Anyone else having trouble installing the hotfix.  Some of my boxes have kicked back with

    DEBUG: Error 2754:  The File ‘C:WINNTInstaller30fe4b0f.msp’ is not a valid patch file.

  41. ma2 says:

    Maybe off-topic, but we are thinking of doing the following to help users process the meeting updates after rebasing:

    1. register all users’ mailboxes with the AAA

    2. run the exchange data update tool to rebase calendar data

    3. unregister all users’ mailboxes from the AAA

    Does anyone see any problems with this?

  42. Dean says:

    After I rebased my resource mailbox calendar (running AAA) by following kb933146, I am still getting the declined message when schedule the calendars within the extended DST The problem is that, if I schedule a meeting (let’s say 2-3 pm) right before another already scheduled meeting (let’s say 3 – 4 pm), I got the declined message from the resource mailbox. I can clearly see 2 -3 pm timeslot is available but the resource mailbox won’t let me schedule the meeting. Our users are very frunstrated about this. Does anyone run into this problem? Is this a different problem than rebasing?

  43. Karol Lynch says:

    To Dean:

    you rebased your AAA mailboxes?

    I’m trying to run the tzmove.exe with the /FORCEREBASESUPPRESSALLUPDATES switch and it doesn’t

    work at all.  Any suggestion is appreciated

  44. Dean says:

    Hi Karol,

    Here is what did:

    1. Run tzmove.exe with the /FORCEREBASESUPPRESSALLUPDATES. The calendars in the resource mailbox were set one hour back.

    2. Run tzmove.exe without /FORCEREBASESUPPRESSALLUPDATES against user mailbox, the calendars were set one hour back.

    This is the order I did. I didn’t do anything special. However,  I did notice one thing. If I run /FORCEREBASESUPPRESSALLUPDATES twice against resource mailbox, my user calendars won’t get moved. Can MS Exchange guys make a comment on this?

    I would like to hear others’ experiences about this new outlook tool hot fix.

    Hope this helps.

  45. Chuck says:

    I ran the new update against my mailbox and I didnt see and declines or updates but the log shows it moved appointments that are not listed in my calendar and belog to other groups??? I am waithing on a call back from MS now to figure this one out. Basically it is moving appointments that are not in my mailbox and do not belong to me, crazy! If anyone can shed some light on this taht would be great..

  46. Scott says:

    I ran Run tzmove.exe with the /FORCEREBASESUPPRESSALLUPDATES. against a resource mailbox, some appointments were set one hour back, but from what I can tell they are not the ones that should have moved, in fact it looks like it moved the ones that were good and not the ones that needed movement.

    Then I ran /FORCEREBASESUPPRESSEXCHANGEUPDATES on a mailbox and at the very least found it moved meetings that it should not have.

    I would use the /onlycreatedprepatch:etc but you can’t use them with the /force options?

    What do we do if we need both?

    Does anyone have a script that will allow conflicts for direct booking?

  47. Scott says:

    I may be misreading the logs, the meetings I didn’t think had been moved from the log have in fact been moved, correctly.

    Unfortunately others have also been moved that should not have.

  48. Anonymous says:

    Q: Will there be an automated fix for updating Resource calendars? A: At this time there is additional

  49. Anonymous says:

    Q: Is there anyway to "Auto-Accept" any changes made by the tool run on the Exchange Server? A: Please

  50. Anonymous says:

    Q: If the rebasing tool is run from the server side, will it update resource calendars, such as conference

  51. Brian says:

    Hi everyone,

    I’m trying to update our Outlook tool to V2 and every time I run it it says "the installation of this packaged failed", and that’s it.  I even tried it on a clean XP system with .Net and outlook 2003 and V1 of the tool.  Any suggestions?

    Thank you,


  52. Chuck says:


    Make sure you first remove the old installation entirely ( after you run add remove programs check for anything left behind files etc.. Also when installing make sure you don’t use the default path "c:program filesMsExTmz" but rather "c:MsExTmz".


  53. Craig says:

    We had a script which was manually patching the registry and then installing the TZMove tool.  I see that there is a hotfix which gives us the /onlycreatedprepatch option.  However we are having a hard time getting the hotfix (.msp) applied from our script.  Is there a reason why there isn’t just another version of the TZMove installer which installs the new tool, instead of having to install TZMove in quiet mode and then running the hotfix immediately after?

  54. Dennis says:

    I found I needed Windows Installer 3.1 to get the Outlook hotfix to apply.

  55. Ben Drawbaugh says:

    I was having trouble re-installing msextmz.msi, it kept saying it was already installed even though it was no longer in Add/remove programs and no longer on the Cprogram files.

    I did a search in the registry and msextmz and deleted a number of keys.

    Now I can install.

  56. Vu says:

    I too am having trouble reinstalling the msextmz.msi ver.2 after uninstalling the previous version.

    A separate question, how do I grant Send As permissions to all mailboxes to a user account on Exchange 2k3?  Do I have to create a new account named "Admin" for the MS script included in KB930879 to work or can it be any account?  Does it have to be an account that is not a member of the domain or Exchange admins, since they are denied these permissions?  

    I can get through everything up until the running of the batch file at the end and for some reason after running it, I get prompted for credentials for Outlook after moving past the first user account, even though I have it set to automatically open the account I setup.  I’m using Office 2007, XP Pro and Exchage 2k3.  Any help would be greatly appreciated.



  57. Anonymous says:

    Here’s some updates for DST. I also have access to premier support information if you have questions

  58. stephen says:

    I just ran the Exchange Time Zone Update tool on my network.  How can I tell if it updated the clients?

  59. calacademy says:

    Our nonprofit is currently using the Direct Booking procedure for our resource scheduling.  In order to accomodate our macintosh Entourage clients, we have to move to the Auto Accept Agent.

    Per msexchangeteam documentation – it is not recommended that both systems are in use.  Can someone point me to some information on a) steps needed to move completely to AAA and b)caveats prior to doing so.

    Thank you in advance!

  60. ...1 says:

    Interesting comments.. :D

Comments are closed.

Skip to main content