Additional information about Exchange and Daylight Saving Time 2007 is now available

As a followup to Elizabeth's previous post I wanted to let you know that the "Preparing for daylight saving time changes in 2007" page has been updated with more information related to Exchange, Outlook, Windows and other products. Please keep checking that page for more information:

- Nino Bilic

Comments (132)
  1. Larry Heier says:


    So if I am to read this correctly, all Exchange installations will have to patch the Server’s operating system, Exchange itself (also to cover Entourage) and probably all workstation’s operating systems and Outlook (if not 2007) to resolve this issue?



  2. J-P says:

    So, what do we do if we are still running Exchange 2000 and don’t have Extended support?

  3. Exchange2003 says:

    We are waiting for the Outlook Data Update Tool since none of our workstations have Outlook 2007.  

    We wish it had been released before now since we have release management requirements … some sites which only allow changes once per month.

    We will be hard pressed to get the patches out for our users since the tool has not been released.



  4. Joe DuPree says:

    We wish it had been released before now too.  We schedule meetings months in advance and our calendars are all off during those initial 3 weeks.  Geez, this change has been known for a year and a half.  And no, we can’t upgrade from E2K before March 11.  Thanks, Microsoft.

  5. Shlomi says:

    if appointments are already scheduled for those dates, and the OS and Exchange are not yet updated, will updating the Exchange and OS be enough? or should be update outlook as well ?

    btw, we have been having DST issues for 5 years in israel , since DST is change every year.. join the club :)

  6. Jeff Taylor says:

    The new information posted at the "Preparing for Daylights Savings Time changes for 2007" has rasied more questions than answers.  In a large corporation, there is a great possibility that there will be calendar entries made that will incorrect after all the patching and tools have been applied.

    Before the OS is patched on the workstation, Outlook will store appointments in the Exchange database without he new GMT offset.  When the workstation OS is patched, Outlook will begin to store the appointments in the Exchange database in GMT using the corrected offset for the new DST.   This means that all workstations need to be patched before the Exchange tool can be re to "fix" the old appointmnets.  Even with SMS, it takes about 5 days for the patch to be applied.  That means there will be some appoints stored correctly while others will be incorrect.  If you then run the Exchange tool, it will change the time on all appointments from 3/11 – 4/1, thus incorrectly changing those that had the corrected time.  This gets worse when you include, Blackberry devices, Mobile devices, home workstations and Public Folders and applications that use CDO. What solution does MS offer to reduce the risk of incorrectly changing appointments?


  7. BK says:

    I think there’s a lot of confusion going on overall.  I was in a conference call with Microsoft TAM and he thinks that there’ll be a webcast to go over Exchange and Outlook to get the DST changes.  Just to be clear, there are no patches for Outlook client, but there’ll be tools to fix appointments, Outlook Data Tool, against calendars in mailboxes.  This tool will be available in standalone and enterprise.

    Go to below link to read more about "Prepare Outlook calendar items for daylight saving time changes in 2007"

    Addressing daylight saving time using the Outlook Time Zone Data Update Tool

  8. JackC says:

    Here’s what I’m contemplating with my Exchange 2000/Outlook 2002 environment:

    – Update Exchange server OS time zone data via TZEdit.exe

    – Apply timezone update to all client OSs (XP SP2) via WSUS

    – Run Exchange Timezone update tool against all Exchange mailboxes

    My questions are:

    -Will the soon-to-be released Exchange Timezone update tool work with Exchange 2000?

    -Given that I will not have updated CDO on the Exchange 2000 server, I expect OWA (running on that same Exchange 2000 server) to have DST issues, but what about patched Outlook 2002 clients? Will they be OK?


  9. Elizabeth Scott says:

      Your plan above will work.  There will be OWA issues during the delta period where appointments made with OWA and viewed with OWA will be one hour off.  the Exchange tool will work against all versions of Exchange.  it does require Outlook 2003 our Outlook
    2007 to run.  if you don’t have Outlook 2003 or Outlook 2007 you can use the trial version that is located here:

    There will be a webcast on Feb 2.  I don’t have all the details at the moment but will post them when i do.  this webcast is externally facing and is intended for customers and partners.

  10. ryan says:

    FYI – The Exchange DST Daylight Savings Time patch killed one of our database servers.  Kept giving us an error, so I had to go in and find the patch folder under C:Windows – and run the spuninst.exe file located in there to remove the patch.  Reboot and your databases will mount again.  I guess until March, I just have to keep my eyes out to see what MS says about it.  Hopefully try that patch again later.  


  11. LHargrove says:

       Two questions for Elizabeth Scott.

       1. Do you have an additional info regarding the webcast on 02-02-07?

       2. You mentioned that the Exchange server tool will work on all Exchange servers. When I checked the KB96666 (for Exchange 2003) I noticed that the list of files being changed includes Store.Exe .  Can you please clarify the information for the Exchange server tool as it relates to Exchange 2000?

       Thank you

  12. compguy030471 says:

    Why would we need Outlook 2003 – Outlook 2007 if running the Exchange Timezone update tool against the mailboxes on the exchange server? Our setup is:

    – Exchange 2000 Enterprise

    – Outlook 2003/2002 (Citrix)

  13. compguy030471 says:

    What happened to the release of Exchange Time Zone Update tool (available February 1) KB article 930879? I have heard no update on it’s release.

  14. Elizabeth Scott says:

    We decided that we needed to dogfood this for a pilot in our Exchange Environment so that we could provide comprehensive guidance to our users

  15. Jason Giambrone says:

    Any update on the Exchange Time Zone Update Tool? It was to be out 2/1/07 but I hear it has been delayed. Can you guys shed some light?

  16. Chantal Bélanger says:

    Please let us know when we can expect the Exchange Time Zone Update Tool to come out !  We need to plan ahead for our update schedule needs lots of approvals …

  17. guy says:

    Does anyone know if the Outlook Time Zone Data Update Tool works in cases of non America DST changes, for example Israel Time Zone?

  18. Milan says:

    We have purchased the DST 2007 bundle update for Windows2000/Exchange 2000 and have a few questions. Does the Exchange 2000 executable update contain the CDO file only? If that is the case then we have to wait for the Exchange Time Zone Update Tool. Is this assumption correct?

  19. applesmash says:

    Exchange timezone tool was released earlier today:

  20. Milan says:

    I noticed in the applies to section that Exchange 2000 Enterprise was missing. An error or true?

  21. Exchange says:


    That was an error, thanks for pointing that out! The body of the KB says:

    Versions of Exchange Server that are compatible with the Exchange tool

    The Exchange tool can update mailboxes on the following versions of Exchange Server:

    • Microsoft Exchange Server 2007

    • Microsoft Exchange Server 2003

    • Microsoft Exchange 2000 Server

    • Microsoft Exchange Server 5.5

  22. XchangeRipoff says:

    So J-P asked what users of Xchange2K do if they are off extended support. Here’s the scoop. MS is charging $4000 per Xchange server for the patch for daylight savings.

    Apply that charge to the 200,000 customer of MS still using Xchange2K off extended support and you’re looking at a $800,000,000 cash grab for Microsoft.

    Count those zeros again folks… that’s eight hundred million possible dollars in the space of a month. And people whine when Apple tries to charge $2-$5 for wireless-n support on their new intel macs… sheesh.

    I’m surprised this isn’t more widely known and a much bigger issue.

  23. LHargrove says:

       It appears as if the tools for Exchange 2000 servers has been released as per the information provided by "Applesmash" and "Exchange".

       I am now wondering if there is something else that Exchange 2000 server users need to purchase based on info from "Milan" and "XchangeRipoff".

        Can someone from Microsoft please clarify once and for all which tools that have been released  will work with which versions of Exchange, and do the Exchange 2000 people really need to buy a $4k fix?

         I have checked the provided links for information, but there still seems to be a lot of confusion and misinformation floating around.

  24. Milan says:

    I noticed a revised KB930879 today and a welcome revision at that! Thank you for the example process on how to update the Exchange server.

  25. dontpayMS says:

    don’t pay $4K for the Ex2K patch.  call microsoft and bitch to them.  we got it for free.

  26. Leaving MS Behind says:

    We were looking at upgrading our messaging infrastructure to Exchange 2007 (from Win2K/Exchange 2k). The issues with obtaining a patch for DST2007 are making us seriously reconsider our messaging infrastructure, and we’re now looking at other products. Before, it was pretty much a shoe-in upgrade, but there is concern from management about being placed in the same situation that we are currently in, again.

  27. Richv says:

    I’m trying to use the Exhange Calendar update tool.  Besides finding it confusing, it’s failing every time I try.  Is anyone familiar with the following messages from the msextmz.log?

    Success Event not found in Application log, treating as a failure.

    Unable to process mailbox…………. 0x80004005


  28. Elizabeth Scott says:

    After applying a version of Store.exe that is later than 06.05.7651.26 (This applies to KB 926666 – Update for DST 2007 transition for Exchange 2003 SP2) on a computer that is running Microsoft Exchange Server 2003, the Exchange databases may fail to mount if the security descriptor of the database object has been modified to include a well-known user or group and more than one domain exists in the forest. This problem may also occur if a security identifier (SID) present in the database object has conflicting values with another object in the Active Directory for one of the following attributes:

    • objectSID

    • msExchMasterAccountSid

    • sIDHistory

    The above three attributes must be unique within the forest.

    In the above conditions the Microsoft Exchange Information Store service will experience an ecAmbiguousAlias error when enumerating the groups and users that are assigned permissions to the store databases objects in Active Directory. This error prevents the affected database from mounting.

    Exchange SE will release an update which will allow the database object to be mounted by ignoring the well-known group objects and logging an error message when two objects are returned by for a single SID. This update will be available via the download center sometime next week.

    For more information please refer to


  29. Milan says:


    We are preparing to run the exchange Tool tomorrow morning. I will inform you if we run into the same type of error.

  30. Elizabeth Scott says:

    Within the next week Microsoft will be releasing an update to CDO for E2k3 sp2 which will include support for the Newfoundland Timezone.  This update will be similar to the update that was released last week for CDO for E2k3 sp1

  31. Wayne says:

    While the tool looks like it’ll be helpful, I agree with Rich that it’s confusing.  Personally I think the directions are only useful if you’ve already done it before and use it as a reminder.

    The error I’m getting is

    Unable find mailbox timezone:Error 0x80004005.

  32. hohokus says:

    dontpayMS: mind sharing? :)

  33. dneisler says:

    I’ve been trying to get this "new" patch to work for hours. I’m getting the same error messages as Wayne.

    Why can’t those of us with Exchange 2000 get the same easy to install hotfix as those with Exchange 2003?

  34. EX2K_User says:

    So let me get this straight:

    The Exchange Calendar Update tool referenced in the above KB article will change the mailbox calendars to reflect the time change, but only AFTER you run the Windows DST patch AND the E2K CDO DST patch?

    The E2K CDO DST patch is still only available from MS under the $4,000 "E2K Out of Support So You’re Screwed" purchase plan, correct?

    This seems tailor made to force small shops like mine to search for an alternative to Exchange.  WTG Microsoft.  They knew this was coming in August of 2005, when E2K was still under Standard Support, this patch should be FREE.

  35. LHargrove says:

       After visiting this site for the last several weeks, I am really beginning to wonder if anyone from Microsoft is actually reading this blog.

        I see entries about this update or that scheduled webcast, but nothing substantive that answers the numerous questions and complaints.

        Reading the released KB articles only serves to add more confusion and speculation to an already troubling situation.

        Time is growing short, someone that really knows what is going on needs to step up to the plate and start answering questions.

  36. chatou7 says:

    Now after spending a few hours trying to figure this Exchange Update tool, I am a bit confused.  Can someone confirm something for me ?  

    The difference between MsExTmz.exe and msextmzcfg.exe is that one is to be be configured manually and the other configures itself thru GUIs.  Is that right ??

    I also get error messages in my .ini file, after extraction. It goes: Error in reading Time Zone.  What could that mean ??

    Also, this is realy weird but I thought that MS would come up with an easy tool to run on each Exchange server to update the database directly and that would be it. Instead, we have to run a weird xp tool that actually runs Outlook onto every mailbox !!!  How slow can that be ???!!!!

  37. dneisler says:

    I’m going to ditch the Exchange Calendar update tool and try the VM for Exchange:

  38. nicatnite303 says:

    I cannot find any documentation that addresses the following scenario. Can anyone provide any guidance?

    Single Instance or Recurring Meetings where the organizer is in a non-affected time zone but attendee(s) are in an affected time zone.  

    It appears from the documentation that since the organizer is not affected even if the Exchange or Outlook tool is run against their mailbox it would not update the item (since they are in an unaffected time zone).  

    So what will be the impact to the attendees of such a meeting. Would a meeting in this scenario have to be recreated?

  39. m2 says:

    Nicatnite303 – I have the same scenario. From what I have read (someone please correct me if I’m wrong), the tool will skip these user’s calendar items. That being said, the participants will see the meeting 1 hour ahead after they apply the DST OS patch on their workstations. If the participants have meetings in adjacent time slots and are updated by the Data update tool on their end, there will be a conflict on their calendars. The same is also possible in the reverse scenario where a user affected by DST adjusts a meeting with a user in a non-dst timezone.

  40. m2 says:

    For anyone who has run the exchange data update tool, do participants of updated calendar items receive the update email and have to manually accept each updated meeting again?

  41. nicatnite303 says:


    Thanks for your response. Your last question is also a good one because the Exchange update tool is supposed to just be a way to run the Outlook tool in a batch form from the server.  The Outlook tool is supposed to give you the option to update attendees or not, but I haven’t seen this mentioned in documentation for the Exchange update tool. I am hopeful it will notify attendees of the change by default. Hopefully someone who has already run the updates and tools can chime in…

  42. Milan says:

    On a PC (Windows XP SP2) we installed Outlook 2003, Outlook Update Tool, and Exchange Update Tool. We ran the process and the mailbox_1.ini file was created with 5 users. A nonexistent.txt file was also created with the rest of the users. What is this file? Single instance appointments? Another problem is that when we try to run the batch file that gets created, it works on the first 2 profiles then stops and corrupts the profile we are using to logon to the mailboxes. Has anyone here encountered same type of problem?

  43. chatou7 says:


    Yes I ran into the same situation, up to the point where you try to run the update process.  Mine stopped for I had forgotten to run the "Grant Mailbox Permission" script.  I’m at that point …

    Like you say, most of my mailboxes ended up in the nonexistent.txt file … go figure !!  Seems to me I read that a mailbox that had never been accessed by/with Outlook would be considered as not having a time zone …

    Will be doing some more tests.

  44. Exchange says:

    Milan and chatou7,

    You are right – the nonexistent.txt will show mailboxes that do not have time zone information defined. By default this will be any mailboxes that have not been logged into as well as mailboxes such as System Mailbox, SMTP, System Attendant etc.

    We are working on a new blog entry that will be kind of a walkthrough of how to run the Exchange side tool with some goatchas that we in Support Services have seen.

  45. Milan says:


    Thank you. That helps. Another question that some of us on the team worry about is "Will appointments that are updated, be resent to users to accept again?"

  46. Milan says:

    I forgot to add another question. Does the exchange tool only look for appointments during the delta period (March 11th – April 1st) and (October 28 – November 4th).

  47. Ben Winzenz says:


    I don’t have a concrete answer on whether it will only look for appointments during the delta period.  Our initial thoughts were yes, but it looks like some additional research may be required.  I do know that the only appointments/meetings that will be updated will be those during the delta period.  If I find any other information out about whether it only searches for meetings during the delta period, I will post another comment response for you.

    The answer to your other question about meeting requests is yes.  When the meetings are updated on the organizers calendar, an update will be sent out to all attendees that they will have to accept before it is updated on their calendar.

  48. E2k problems. says:

    I am trying to run the msextmz.exe and I am very confused. Is there anyone out there who has run this with success and is there anyone that can document the step by step proccess so that all of us have a guide line to go by. I have read through Microsofts KB information pertaining to the Exchange tool and I have got nothing but confused. please help


  49. JackC says:

    Just a couple of notes as to my experience running the Exchange rebasing tool in my lab environment.

    -Forget manually editing the ini, what a pain.. run the msextmzcfg.exe util instead.

    -Got many mailboxes showing up in the errors.txt file. Had to open up mailboxes_1.txt in Excel, and add all mailboxes from errors.txt (with the correct time zone values).

    -Full mailboxes caused issues with the meeting updates not getting to all the invitees. Need to check user mailbox limits and adjust beforehand, at least for VP calendars..

    -In the case of a delegate PC that handles meeting invites to confernce room calendars, it declined many meeting updates due to meeting conflicts. Need to set the conference room calendars to accept conflicting meetings before kicking off the rebasing, then turn it back off when done.

    – As for "send as" permissions, we opted to set AD "send as" perms to  user objects at the OU level for the user running the Exchange rebasing tool, and that seemed to work just fine. Can always remove the perm after we’re done if desired.

    Time to restore the lab Exchange server and run another rebasing test…

    Also, what’s this I hear about MS giving out the E2K DST fixes for free if one complains loud enough??  Must just be rumor, although it would be the right thing for MS to do…. and no loud complaining should be needed either… If they are going to do it, they’d better do it soon else they’ll have that many more refunds to hand out to those who ponied up the $4K.

  50. dontpayMS says:

    no rumor.  we were outraged by the $4K fee just as all of you are.  we contacted our MS account manager and ascertained that we have been a loyal enterprise MS customer for years and use many of their products.  up until this $4K patch, we were planning to upgrade to Exchange 2007 mid-year.  we told our account manager that if we had to pay that we would consider another product for our electronic messaging needs.  a few days later MS agreed to waive the fee.  

  51. compguy030471 says:

    We are working on an implemention plan to apply the patches in one swoop.

    1. Windows DST Update on servers (Windows 2000/Windows 2003 patch)

    2. Windows DST updates Clients (Push out with SMS)

    3. Exchange DST Patch (Exchange 2000 in our case)

    4. Blackberry Server

    5. Exchange/Outlook Rebasing tool.

    My question is, if the process above is done right before the deadline, March 11, 2007. And handfuls of Windows clients are not turned on when the patch sent to them, will they be locked out of logging on to Active directory because the clocks on the unpatched clients will be off by 1 hour? I know that if clients are off by 5 minutes compared to the Domain controller they will not get access. Also is the time info passed from server to client in UTC or does it have Time Zone information?

  52. Milan says:

    Can I use the Exchange Server Profile Analyzer against my Exchange 2000 server to get a rough estimate on how many calendar items I have?

  53. robrandon says:

    Of course outraged and needing to pay $4,000 for a patch that should have been released while support was NOT in the extended phase.  This is really shady of MS to release the patch AFTER they expired support.  Anyway…

    We are running Exchange 2000 Enterprise as a cluster on 2 Windows 2000 Enterprise servers.  If we run the server OS patches, the client OS patches, and an appropriate TimeZonewhateverEXE to move the appointments, BUT DO NOT apply the MS Exchange patch, what happens under different scenarious, such as

    1. creating an appointment for myself in my own timezone, a different time zone (US), or a different time zone (NOT US) – that are all on my server

    2. the same as above, but where we forward the appointment to someone outside of our exchange environment.

    The reason I ask is because in some sitiuations, it may not be necessary to apply that patch….


    Very confused…..


  54. Paul Holmgren says:

    Hey, compguy030471, I’m not sure of a DC locking out a user or computer because the time is off.  We have users in a separate time zone from out DC and have not had issues of the sort

  55. Milan says:

    DC uses UTC to time synch so Time zone data should not affect. But I am pretty sure of client clock is off more than 5 minutes it will not be able to logon.

  56. Milan says:

    Question for anybody out there that might know, If the Exchange Rebasing tool is run a 2nd time on store to correct some appointments, is the tool smart enough to leave appointments that are correct alone and update just the wrong ones or does it adjust any appointment in the delta period regardless of where they are at? If yes then very important to get it run on the first run.

  57. Exchange says:


    There should be no issues with running the tool multiple times. It will not just blindly move stuff over for 1 more hour at every run.

  58. Milan says:

    Thank you Exchange, we were a bit worried.

  59. kaje74 says:

    OK, since this is so painful, what happens if we run the OS fix for WIN2k on the server, but don’t run it on Exchange?  Meetings will be off by an hour for a couple of weeks, even though the server has the right time?  Because I don’t fancy corrupting or otherwise damaging my main mail server with a patching scheme that looks like something from the Linux arena.

  60. JackC says:

    To dontpayMS:

    Thanks for confirming. I would assume you’re running a decent sized Exchange 2000 shop for MS to make an exception.

    Its unbelievable that this game is still being played.. I for one am lucky enough to not require OWA all that much, and my Blackberry system can be remedied by upgrading the Exchange system manager on it to E2K3, so I will not pay $4k for just CDO. However, my earlier plans to go to Exchange 2007 later this year are now already being questioned by management.. Very disappointing.

  61. John says:

    Can anyone shed some light on the Public folders issue? I have E2K3 SP2 with several PF’s as calendars, am I going to have to run the Outlook tool (I have rights to them all) to fix them?

  62. Andrew says:

    I’m 99% certain that the DST patch took down all 6 of my agency’s production Exchange 2003 servers.  MS support was no help at all.  They kept trying to pin it on DNS and AD replication.  Both of which turned out to be fine when they got an AD Engineer involved.  I am just sick from all this.

  63. chatou7 says:

    Hi everyone,

    running the MSEXTMZ.EXE

  64. chatou7 says:

    Hello all take 2 !!

    Running the MSEXTMZ.EXE and getting the fol error for all my input mailbox:

    Error 0x80070002 – Unable to Read timezone ERROR IN READING TIME ZONE

    Did anyone run into the same ??

  65. technochi says:

    Here’s another consideration…

    We have conference rooms that are set up as resource mailboxes that people use to book meetings. How will those get updated?

  66. MDurkin says:

    Help – I must be an idiot…  I can’t find the Exchange Time Zone Update tool (MSEXTMZ.EXE)  Every time I go download it I am getting a 404 from MS.  Does MS just hate me?

  67. BCochran says:

    Has anyone successfully used the Exchange Update Tool?  Time is running thin, and I would like to hear from someone who has blazed this trail.

  68. chatou7 says:

    Just another question  … When all the patches and fixes are installed, how do you make sure that it will work when the time comes ??

    Would changing the date on the DC in my test environment be a good simulation ?

  69. Milan says:


    Exactly, change the dc time to 1:58am March 11th.

  70. Rich Turner says:

    I applied the updates to my computer, and all of a sudden these appointments are an hour late.  So then I run tzone.exe, it fixes some issues, but not all.  But when I changed my time zone, then chnaged it back, all of my appointments were properly scheduled.

  71. thull says:

    Of my roughly 1500 Exchange 2003 users, I have maybe 200-300 who actively use their calendars and will be affected by the DST fiasco. I have run the MSExTMZCFG.EXE tool several times and each time it finds only about 450 "affected users".  All others return an error " Unable Find Mailbox Timezone: Error 0x80004005" – unfortunatley, when I check the input file, the users I know to be the heaviest calendar users are not in that list of 450 "affect users". The only thing I have been able to find about this error is in this forum – and it states this error occurs on mailboxes that have not been access – WRONG!!!  These are my heaviest users.There seems to be a lot of people with the same problem.  Where’s the solution, Microsoft??? I so wish we were still on GroupWise!!!

  72. BobbyLyon says:

    I’ve attempted to run the V2 tool several times in a lab and I am also getting this error message of "Unable find mailbox timezone: error 0x80004005" and "0x8004010F".  All users have accessed their mailboxes and accessed through OWA.  This is CRAP!  Has anyone gotten this tool to work?

  73. MCSE2002 says:

    Richv said:

    I’m trying to use the Exhange Calendar update tool.  Besides finding it confusing, it’s failing every time I try.  Is anyone familiar with the following messages from the msextmz.log?

    Success Event not found in Application log, treating as a failure.

    Unable to process mailbox…………. 0x80004005

    Rich, had the same issue, even in the VM provdided.  I was using the wrong TZMOVE.exe.  Copy the one from C:Program FilesMicrosoft OfficeOffice12Office Outlook Time Zone Data Update Tool into the path for your ini file and try again.

  74. Eagle117 says:

    I am having the same problem with the error: "Unable find mailbox timezone:Error 0x80004005" on about half of my mailboxes.  I can’t seem to find anything common between them.  Some people in the list have no appointments, some have some but none in the affected window, and some of them have a birthday appointment right in the middle of the window in question.  

    The good part is that none of them are high profile users, but what does this error mean? I don’t have to have to run the tool multiple times and screw things up more.

  75. JackC says:

    Just succefully ran MSExTMZCfg.exe against my production mailboxes.

    -assigned "sendas" permissions for the account running the rebasing process to user objects(at the OU level). Did not bother with the "send as" VB script.

    -Ran MSexTMZCfg.exe to extract mailboxes list.

    -Took contents of mailboxes_.txt, and nonexsistent.txt and merged them inot a new mailboxes_1.txt being sure to add any missing timezone values (via Excel).

    -ran the batch file that the MSexTMZCfg.exe had created.

    -400 mailboxes took about 2.5 hours.

    Note: I had enabled conflicting meetings in all my resource calendars (conference rooms) beforehand.

    One thing I hadn’t considered is that users would be re-invited to meeting they had previously declined if the organizer never took them off the invitees list. We just opted to have our users accept all meeting updates, and then blast any meeting they did not want after the fact.

  76. SteveJHU says:

    We just ran the debasing tool, but it doesn’t appear that any appointments in the DST change period were effected.  There were no errors, but the appointments still appear 1 hour later.  Here’s a logfile from a run on one mailbox where the appointment times were not corrected:

    Logfile opened as:msextmz.log
    Reading Configuration.
    Command Line:C:Program FilesMicrosoft OfficeOffice12Office Outlook Time Zone Data Update ToolTZMOVE.EXE /q
    ServerDN:/o=My Organization/ou=Organization/cn=Configuration/cn=Servers/cn=MyServer
    OutputputFile opened as:Output.txt
    InputFile opened as:C:msextmzMyServerMailboxes_1.txt
    Error opened as:Errors.txt
    Default Timezone is not set.
    Per-Mailbox time limit:15 minutes.
    Master PRF FIle set to:C:msextmzdaylight.prf
    Outlook command line set to:C:Program FilesMicrosoft OfficeOffice12OUTLOOK.EXE /noextensions
    Outlook Registry key set to:SoftwareMicrosoftOffice12.0Outlook
    Profile Creation Time Limit:15 seconds
    Processing Mailbox:/O=My Organization/OU=Organization/CN=RECIPIENTS/CN=MyUsername
    PRFFile set to C:msextmzMSExTmz-MyUsername-0x18E0F678.PRF.
    Spawned outlook process as pid – 2488.
    Timezone set to EASTERN STANDARD TIME.
    Spawned worker process as pid – 2408.
    Saved Log set to C:msextmzMSExTmz-MyUsername-0x18E0F678.LOG.
    No log file written for user.
    Any ideas?  Thanks!

  77. DIlly says:

    I am getting the 0x80070002 – Unable to Read timezone on half of my mailboxes!!

  78. Demelich says:

    So, let me get this straight.  If we have an Exchange 2000 environment, but do not use OWA, we do not need to $4000 patch?

  79. Exchange says:

    "Unable find mailbox timezone:Error 0x800004005" during time zone extraction process is not a big deal, you do not have to worry about this much.

    Simply add those users into mailboxes_1.txt, tab separated, in the format of "user <tab> server <tab> timezone". You can use Excel to make this easy (Excel is on the virtual machine that you can download from us with tools), hopefully most of your users are in the same timezone – then it becomes REALLY easy.

  80. chatou7 says:

    Please Exchange, what about the "0x80070002 – Unable to Read timezone ERROR IN READING TIME ZONE" error ???

    Anything on that one ?  It has to do with reading the Time Zone info from the registry.  Could it have anything to do with my pc’s XP being the French version ?

  81. Exchange says:


    We have seen this error in 2 cases primarily:

    1. if there is no profile defined on the machine

    2. try to edit the msextmz.ini to define the explicit path to tzmove.exe

    So FOR EXAMPLE if the entry in the .ini file is as follows:

    CommandLine=tzmove.exe /q /onlyrecurring

    Would now be entered as:

    CommandLine= C:Program FilesMicrosoft OfficeOffice12Office Outlook Time Zone

    Data Update Tooltzmove.exe /q /onlyrecurring

  82. chatou7 says:


    thank you for your suggestions, but unfortunately:

    1- I have a Outlook profile defined

    2- I have tried changing the path in the MSExTmz_1.ini file but with no luck.

    The complete error msg is:

    HrReadTimezoneFromRegistry:Failed opening timezone registry key ‘SoftwareMicrosoftWindows NTCurrentVersionTime ZonesERROR IN READING TIME ZONE’ – Error 0x80070002.

  83. Exchange says:

    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. This IS what has been called a "V2" of Outlook tool, but it is not a new standalone version but is rather a hotfix for the original tool.

  84. BtheMan says:

    I think it is hillarious that someone at the Department of Energy actually thought this would save money.  Since they couldn’t come up with a real plan and wouldn’t want to put any pressure on Automaker’s to meet higher CAFE standards.  Hey, I’ve got a bright idea…

    When execs start showing up an hour early for meetings I’ll be quietly laughing my ass off.

  85. chatou7 says:

    Hello again,

    Running the hotfix for the Outlook tool, I get the fol error msg:

    The installation of this package failed.

    I’m telling you, this is twice as worse as year 2000 !!!!

  86. BryanG says:

    This is crazy.  Getting the Error 0x80070002 also.  Anyone making any headway?  BtheMan, hit it on the head brotha.

  87. chatou7 says:

    Re: probleme installing Outlook tool hotfix, it now works …. sorry did’nt do my Homework.

    Upgrading MSIExec solved this problem.

  88. Igor says:

    Downloaded the DST VM.  Running MSExTmz.exe versus my own mailbox and it shows that it completes just fine but my meetings are still 1 hour later.

  89. Alan Gordon says:

    I am getting the following error after running the msextmz_1 batch file:

    HrProcessMailbox:Unable to process Mailbox…..-0x800004005

    I have tried both tzmove files (the 8.3MB file and the 320K file).

    Any help would be greatly appreciated!

  90. chatou7 says:

    Found it !

    Found solution for error "0x80070002 – Unable to Read timezone ERROR IN READING TIME ZONE".

    Look at your Mailbox_1.txt file and make sure the time zone is correct.   My read something like "UNABLE TO READ TIMEZONE"

  91. tcdrake says:

    I am in the same boat as Igor. Ran the tool and clients with meetings in the future are off an hour. So a 5PM meeting is now at 4PM. I looked at the log files created for each user and it confirms what I see. Why is it off an hour?

  92. lgak says:

    same problem as igor and tcdrake.  it looks like almost all single instance appointements are off by 1 hour.  3 instead of 4, 4 instead of 5.  wonderful.

  93. Paul Holmgren says:

    I believe that’s how it is supposed to be.  Outlook’s time will be wrong for these upcoming 3 weeks so showing the appointment is at 3 (when it is actually at 4) the user will be prompted 15 minutes before what outlook thinks is 3 (Outlook thinks 2:45, remind of meeting, time is really 3:45).  Unfortunately, I ran the tool (Exchange 2000, Outlook XP & 2003 mixed) and the appointments are showing an hour LATER so I think we’ll be 2 hours off

  94. chatou7 says:

    hello all,

    Now that I’ve got it working on my test environmnent, I need to make in work in prod.

    I’m trying to uninstall Exchange System Manager form my XP workstation and it wont dissapear from the Add/Remove Program List.

    Of course, the Exchange tool wont install …

    Anybody know how to completely uninstall the ESM from a workstation ?

  95. Milehijones says:

    You know what is odd is the DST 2007 patch, when downloaded via WSUS, doesn’t get categorized as a Critical update – it is Non-Critical.  I wasn’t even looking for it under there.  Given the impact this could have on folks it’s hardly Non-Critical, Microsoft.

  96. Roman says:

    I am trying to run the permissions script but keep geting the syntax message.  Any thoughts?  I checked everything.

    E:DST2007>CScript GrantMailboxPermission.vbs -add ABCROMAN Input_GrantPerm.txt

    Microsoft (R) Windows Script Host Version 5.6

    Copyright (C) Microsoft Corporation 1996-2001. All rights reserved.


    Grant Full mailbox access and SendAs permission to USER based on IMPORT_FILE:

       CSCRIPT GrantMailboxPermission.vbs -Add DOMAINUSER IMPORT_FILE

       NOTE: "GrantMailboxPermission.log" will be created for -Remove option

    Remove Full mailbox access and SendAs permission based on GrantMailboxPermission


       CSCRIPT "GrantMailboxPermission.vbs" -Remove

    For all modes, errors are saved to GrantMailboxPermission.err

  97. Baracus says:

    Do you have your import file in the same directory as the GrantMailboxPermission file?

    > I am trying to run the permissions script but keep geting the syntax message.  Any thoughts?  I checked everything.

  98. Baracus says:

    Is the Exchange tool smart enough to know to only bump calendar times that were created prior to the OS/Exchange DST patches??


    1. schedule appointment ABC in delta period

    2. apply OS/Exchange patches.

    3. schedule appointment XYZ in delta period

    4. Run Msextmz.exe on mailboxes.

    Does it bump only ABC as it should or does it also bump XYZ?

  99. DavidF says:


    "Unable find mailbox timezone:Error 0x800004005" during time zone extraction process is not a big deal, you do not have to worry about this much.

    Simply add those users into mailboxes_1.txt, tab separated, in the format of "user <tab> server <tab> timezone". You can use Excel to make this easy (Excel is on the virtual machine that you can download from us with tools), hopefully most of your users are in the same timezone – then it becomes REALLY easy.

    Not good enough. We’re an ASP with thousands of users spread across a dozen mail servers, in every time zone. Getting 0x800004005 on almost every single mailbox. Vague error messages with third-grade English and the clock is ticking – yeah, our bad for expecting this tool to "just work" and not testing it sooner.

    Time to call MS support I guess. I sure hope this tool is supported.

  100. Exchange says:


    No – both will get moved. Unless they were created using Outlook 2007. That is because the appointments do not have timezone information embedded into them until the tool is run

  101. Baracus says:


    What about this,


    1. schedule appointment ABC in delta period

    2. apply OS reg/patch update on client.

    3. schedule appointment HIJ in delta period

    4. apply OS/Exchange server patches.

    5. schedule appointment XYZ in delta period

    6. Run Msextmz.exe on mailboxes.


    1. schedule appointment ABC in delta period

    2. apply OS/Exchange server patches.

    3. schedule appointment HIJ in delta period

    4. apply apply OS reg/patch update on client.

    5. schedule appointment XYZ in delta period

    6. Run Msextmz.exe on mailboxes.

    Still OK??

    Thanks again for the help,

  102. Exchange says:


    In both scenarios, it is all getting moved. The difference here is that in scenario #2 – you will have to "fix up" only the XYZ stuff as ABC and HIJ should be OK after rebase (assuming that you are using Outlook to create appointments – as if you used OWA, you will have to check/fix also HIJ).

  103. Exchange3 says:

    In reply to the question regarding "0x80070002 – Unable to Read timezone ERROR IN READING TIME ZONE" error.  We had the same problem.  It ended up being that we had trailing spaces in our input file (mailboxes_1.txt).  Once we removed them, everything ran fine.

  104. says:

    Can someone with access to the DST update for Exchange 200 please email me it?

  105. civiwilly says:

    Running tools from the Exchange DST VM.

    I need help getting the input file created and formatted.  When I run the extraction process, it creates the output file and lists the full cn of each mailbox, but no timezone and each mailbox errors with 0x80004005.  

    I’ve ran the permissions script successfully but cannot get beyond the extraction process.

  106. Jeff25 says:

    I am attempting to run the exchange mailbox update tool on my E2K3 mailboxes.  But like others I am getting the 0x80004005 errors.  Of my 600+ mailboxes I get timezones from 130.  All the rest I do not get time zone info from.  They are placed in the nonexistent text file.  What causes this? Does it mean that the windows update has not been applied to the PC? Is there a workaround for this issue?

  107. Brian says:

    I have run msextmzcfg.exe and reviewed the nonexistent.txt and mailboxes_1.txt files.  I do not quite understand *what* differentiates the users that were listed in the nonexistent.txt file from the users in mailboxes_1.txt.  Of the 100 or so users on a single EX2003 box, about 25 of them ended up on the nonexistent.txt list.  I confirmed that these users are active calendar users and do, in fact, have appointments scheduled during the 4 weeks in question.  I am waiting to learn what, if anything, I need to do to ensure that after I manually add these folks to the mailboxes_1.txt file, that these folks will be updated like everyone else.

    I have only ONE Time Zone for all users — EST.

    Any help is greatly appreciated.

  108. ninob says:


    You do not have to do anything else special. If the tool failed to find the users timezone but they are all in the EST, just mark them all as EST and run with it. The results will be exactly the same for the ones that were detected automatically and the ones that were not.


    Please see what Brian did (a comment after yours) – that is what you can do if mailboxes were not detected for the timezone.

  109. Brian says:

    nonob — thanks very much.

    I added the applicable users from the nonexistent.txt file to the mailboxes_1.txt file.  I copied the tzmove.exe to the same directory as my .ini file and ran the MSExTmz_1.bat file.  For each user, I receive the same error that a few other folks referenced in this thread:

    Success Event not found in application log, treating as failure.

    Unable to process mailbox …

    Error processing mailbox …

    Then, it repeats for each user in the mailboxes_1.txt file.  It appears to be setting the timezone correctly in the log file though.

    Any thoughts?  Any assistance is appreciated.



  110. Erik says:

    Regarding the 0x80004005 error.  Make sure that you place the TZMove.exe file in the same directory that your MsExTMZ.ini file is located and run the installation from there.  Once I did that, it yielded different results.  The error was still there, but I finally got all of my mailboxes to show up in the output.txt file and the nonexistant,txt files.  Initially I could only see 74.  Afterwards I saw all 183.  I simply combined the two using text files using excel and exported to a new tab delimited file.  Everything worked at that point once I started the update process.

  111. Brian says:

    Does anyone have any suggestions for the errors:

    Success Event not found in application log, treating as failure.

    Unable to process mailbox …

    Error processing mailbox …

    Many thanks,


  112. Bob Hyatt says:

    couple of questions:

    I’m getting that 0x80004005 as well running the tzmove, it does not write to the application event log. it says it updated the timezone but unable to process the mailbox. did it update the calendars? we’re running a cluster with virtual servers, is that a problem with the legacy dn that was extracted causing the error?

    when running the grant permissions on the ex server the log has to fields of false/true. anybody know what that stands for?

    after running that program should you be able to see the user granted the permission using adsi edit on a mailbox?

    Thanks for any insight, Bob

  113. Jeff25 says:

    When running the Exchange tool in extract mode our mailboxes_1.txt file contains many mailbox names in the form if a GUID:


    Why is this happening?  And I’m guessing this is NOT a problem?



  114. Bob Hyatt says:

    anybody else getting these errors -Success Event not found in application log, treating as failure.

    Unable to process mailbox …

    Error processing mailbox …

    search out the tzmover.dll and copy it to the folder txmover.exe (316kb version) is running from. got that ms chat

  115. Here is what worked for me ... says:

    When using myself (domain admin, etc.) and my Outlook profile, I was receiving the errors I mentioned above (unable to process, etc.)

    Here is what I did to obtain a successful exchange outlook tool run:

    1.  Create a new user (daylight_savings) with mailbox

    2.  Create a new Security Group (stuff) and added daylight_savings user

    3.  In Exchange System Manager, go to Properties of the Mailbox folder (under mailbox store name), Security Tab, Add the stuff Security Group and give, at a minimum, Send As and Receive As permissions.

    4.  On a workstation NOT running Exchange or the Exchange System Tools (with .net 2.0 framework installed and Outlook 2003 or Outlook 2007), login as daylight_savings user (be sure the user is local admin).

    5.  Setup Outlook profile for daylight_savings user

    6.  Follow the instructions in MS KB article 930879 … I used  Msextmzcfg.exe.

    And, it WORKED !!!!!  Finally!  What a PITA this entire process was!  Now, I have 5 other customers to FIX ASAP!

    Good luck!


  116. EdGonz says:

    Wow, Microsoft REALLY dropped the ball on this update. It appears that all these tools were written by junior developers – instead of the great developers MS has hired.

    Not only is this a patched up tool, but also unreliable and not well documented.

    Way to go MS!

  117. Ryan_S says:

    This was the key for me… I was using the wrong TZMOVE.exe file

    "Rich, had the same issue, even in the VM provdided.  I was using the wrong TZMOVE.exe.  Copy the one from C:Program FilesMicrosoft OfficeOffice12Office Outlook Time Zone Data Update Tool into the path for your ini file and try again."

    This was also very helpful…

    Here is what worked for me … said:

    When using myself (domain admin, etc.) and my Outlook profile, I was receiving the errors I mentioned above (unable to process, etc.)

    Here is what I did to obtain a successful exchange outlook tool run:

    1.  Create a new user (daylight_savings) with mailbox

    2.  Create a new Security Group (stuff) and added daylight_savings user

    3.  In Exchange System Manager, go to Properties of the Mailbox folder (under mailbox store name), Security Tab, Add the stuff Security Group and give, at a minimum, Send As and Receive As permissions.

    4.  On a workstation NOT running Exchange or the Exchange System Tools (with .net 2.0 framework installed and Outlook 2003 or Outlook 2007), login as daylight_savings user (be sure the user is local admin).

    5.  Setup Outlook profile for daylight_savings user

    6.  Follow the instructions in MS KB article 930879 … I used  Msextmzcfg.exe.

    And, it WORKED !!!!!  Finally!  What a PITA this entire process was!  Now, I have 5 other customers to FIX ASAP!

    Good luck!


  118. GR says:

    I’ve got a lot of users showing up in the Nonexistant.txt file.  Even though I can put them in the mailbox file with a timezone, I am not 100% sure of each user’s default timezone.  So, my question is…what if you put in the wrong timezone?  How does that affect then during the DST time period?  Does it have to be corrected manually by each user?

    Thanks for any help

  119. Cliffstar says:

    For every user I get No Log file Written for user

    And the Saved Log Set to c:DSTMSEXTMX – username-0x0030F6E6.log is never written. I cannto tell if this tool is working or not.

    Any thoughts?

  120. jmorris says:

    I do not have many users so I am just running the outlook tool on each individual mailbox, but the Company Calendar is not being updated.  It is edited by one individual and I ran the tool on his computer and it just fixed his personal calendar.  Is there a way to use the Outlook tool for the Company Calendar on Outlook without using the Exchange Tool?

  121. jmorris says:

    I do not have many users so I am just using the outlook tool on each individual mailbox.  It successfully updated all personal calendars, but the shared company calendar is not being updated.  Is there any way to update that using the Outlook  tool, or must I use the exchange tool for the company calendar.


  122. Shiraz says:

    OK. Here is what the problem and solution is , to cut things short for those of you having this issue : while updating

    Success Event not found in application log, treating as failure.

    Unable to process mailbox …

    Error processing mailbox …


    you need to copy the tzmove.exe (The installer) to the Exchnage tool installiation directory , then from there run it , it will copy TZMOVE.exe to /Programe Files/Microsoft Office/Office12/Office Outlook Time Zone Data Update Tool .

    browse to the path above mentioned to select the tzmove.exe when asked ( update process) , if you copy this file anywhere else and give that path , it come out and give you the error mentioned above…. plz make sure that extend.dat file is not there before you start the update process..dont delete it , rename it ..

  123. paul says:

    Has anybody figured out what the Distinguished Name format is supposed to be for Exchange 5.5, since it is not integrated with Active Directory?  

    I have two remaining networks that I still need to update: one has Exchange 5.5 running under 2000 Server, the other under NT 4.0.  The tool ran fine against E2K3 under W2K3 Server, once I got the DN format correct — I just need whatever will make MSEXTMZCFG.EXE happy in these non-AD environments.

  124. phil@bcra says:

    The efforts to answer  "UNable to…" or "Error Processing mailbox …0x80004005"

    are very repetitive.  Nobody is saying anything new.

    >renamed extend.dat

    >permissions are correct

    >process worked against user boxes, but these are resource boxes, and I’m using the /forcesuppressallupdates switch

    >so tzmove is in the right place, tried every location of it….

    >started with a fresh folder from MsExTmzCfg.exe

    and I still get these blasted 80004005 errors.

  125. phil@bcra says:

    app log says:  The Time Zone Data Update tool for Microsoft Office Outlook encountered the error: Could not complete the operation. One or more parameter values are not valid.  Additional error information: 80070057 (, , 00000000, 00000000).

  126. ScottB says:

    Does anyone know if there is patching or updates required for the Exchange System Manager that is installed on a windows xp workstation?  I would like to know if there is anything on a management workstation that needs updating other than the OS?

  127. Brian says:

    I work for a IT Outsourcing company.  Each and everyone one of us, all engineers, performed all the patches as described by MS Articles and all showed as successful.  However, we have confirmed by remoting in to several of our customers that the Exch Calendar Tool did NOT work as it should have.  Running the tzmove.exe on a single workstation after the fact does work.  Go Figure!!  Going to be a fun week!

  128. Raffi says:

    I have a small environment. I tried the exchange tool (which just seems to batch tzmove anyway). it runs through, no errors

    However, I do have clients that are saying that the time is wrong on contacts.  looksl ike some manual updates will have to be done after all.

  129. Bob Hyatt says:

    fyi on the 80004005, 2 things I ran accross – make sure the tzmover.dll is in the directory you run tzmover.exe from(search if you don’t know the folder it installed to) also had to call MS to get the hot fix from kb932962. that allows the tool to update other mailboxes instead of continually running against the default profile configure in the ini file

  130. wholiao says:

    I have download and install (run) Exchange data DAT update. And some user’s calendar shows one hour ahead (org: 03:00pm, now: 02:00pm). I run TZMove.exe on user desktop, and it shows no appointments found. The Tool provide by MS only fix some user’s Calendar issue.

  131. BrianBuda says:

    I’m having the same problems as wholiao is having.  After running the MxExTmz file and getting it to successfully run on all users mailboxes, it fixed some appointments but also moved some appointments an hour earlier.  When I run the standalone TZMove on that user’s computer, it says no appointments found, but there’s many that are now an hour earlier.  Is there a way to fix this for all appointments?

Comments are closed.

Skip to main content