Daylight Saving Time Correction for Microsoft Office Outlook Calendars – Help desk guidelines


This document provides recommendations and prescriptive guidance for updating Outlook calendars to comply with the Daylight Saving Time (DST) 2007 rule changes. The goal is to provide an Outlook user with a "personal touch" experience to help them understand what is happening with their calendar. You might find this helpful when dealing with end user questions or answering their helpdesk calls on the subject.


This document assumes that the Outlook user:

  • Is running Windows XP
  • Has permissions to open Outlook and update their calendar
  • Has the ability to modify the operating systems Date and Time Properties
  • Has the Outlook Time Zone Data Update tool installed on their computer

General References

Tools Availability


We recommend using the following process for updating Outlook calendars.

I - Verify Operating System Update Has Been Installed

Start by verifying that the Outlook user's operating system has been updated with the DST 2007 update. An easy way to verify that the update has been installed is to examine the list of available time zones in the Date and Time Control Panel applet. To do this, have the Outlook user:

  1. Click on Start, and then select Run.
  2. In the Run area, type timedate.cpl. The Date and Time Properties dialog will appear.
  3. Select the Time Zone tab.
  4. Click the Time Zone drop–down box.
  5. Look for these two time zones:
    (GMT-06:00) Guadalajara, Mexico City, Monterrey -New
    (GMT-06:00) Guadalajara, Mexico City, Monterrey –Old
    as shown in Figure 1 below:

Figure 1 - Windows XP Time Zones After DST 2007 Update is Applied

If both of these time zones are not present, Windows XP is not updated with the DST 2007 update, and must be before proceeding. See for details on the update and to download the update.

If both of these time zones are present in the list, then Windows XP is correctly updated with the DST 2007 update, and you can proceed.

II - Review Outlook Calendar

Once you have confirmed that Windows XP is updated, you can help the Outlook user review their 2007 calendar for any issues present during the date range of March 11 - April 1, 2007 and October 28 – November 4, 2007. You should not move any items unless it is determined that moving them is needed to correct them. If the Outlook user indicates that everything is correct, then there is no need to proceed with rebasing or moving items.

If the Outlook user is a Delegate, ask them to request that their manager review any personal appointments to ensure that there are no problems with those items.

If the Outlook user indicates that meeting times are not correct, then proceed with rebasing by running the Outlook Time Zone Data Update tool (TZMove.exe).

III - Run the Outlook Time Zone Data Update tool

The process for running the Outlook Time Zone Data Update tool begins with creating a new online profile. Using a new, online profile is optional, but recommended as a best practice. The Outlook Time Zone Data Update tool can also be run using the Outlook user's existing profile.

Creating a New Online Profile
Use the following steps to create a new profile on the Outlook user's workstation. These instructions can be read to the Outlook user over the phone, or performed by the Help Desk technician that is remotely connected to the Outlook user's computer using Remote Assistance or similar remote control software.

  1. Double-click the Mail icon in the Control Panel.
  2. Click Show Profiles.
  3. Click Add.
  4. Add a new profile, and in the Profile Name field, type the name of the user you are assisting.
  5. Click OK.
  6. Make sure the option "Add a new email account" is selected and click Next.
  7. Select "Microsoft Exchange Server" and click Next.
  8. For the Exchange Server Name enter the name of the Outlook user's Exchange server.
  9. Enter the user's display name and click Check Name.
  10. You may need to select the users name from a drop–down box.
  11. The name should appear with an underline under it.
  12. Uncheck the checkbox for "Use Cached Exchange Mode"
  13. Click Next and the click Finish.
  14.  Verify that the option in the Mail applet is set to "Prompt for a profile to be used" and click OK.

Once the profile has been created, or after deciding to use the Outlook user's existing profile, proceed with running the Outlook Time Zone Data Update tool.

Run the Outlook Time Zone Data Update tool using the New Profile or the User's Profile

Use the following steps to run the Outlook Time Zone Data Update tool using either the newly created profile, or the Outlook user's existing profile.

1. Launch the Outlook Time Zone Data Update tool by double-clicking the Mail icon on the Outlook user's desktop.

2. Select the Mailbox for this user as the "Data File".

3. Make sure that the Outlook user's correct time zone is selected in the Original Time Zone field.

4. Make sure that the Update to reflect changes to the Windows time zones option is selected, as shown in Figure 2 below:

Figure 2 - Outlook Time Zone Data Update tool

5. The tool will report the number of items to possibly rebase, as shown in Figure 3 below:

Figure 3 - Number of Items that Need Rebasing

6. Click the Details button to get a list of items to be updated, as shown in Figure 4 below.

Figure 4 - Details on Items to Be Updated

7. Ask the Outlook user if any appointments on this list appear to be incorrect (e.g., appear one hour ahead). Any appointments that appear to be one hour ahead will need to be moved.

8. Uncheck any appointments that are indicated as correct (e.g., not 1 hour ahead).

9. Click OK.

After the Outlook Time Zone Data Update tool has updated the checked items, meeting updates will be sent automatically and the Outlook user can expect to receive meeting acceptances. Let the Outlook user know that anyone who receives meeting updates from them should accept them.

Then, review the calendar with the Outlook user and ask them to verify their appointments from March 11 – April 1, 2007. If any appointments appear at the wrong time, instruct the Outlook user to move the appointments by clicking and dragging them to the correct time.

If all of the appointments are not correct proceed with checking for incorrect or missing appointments. If all of the appointments are correct proceed to the discussion of other clients that might access the calendar items.

Confirm the accuracy of items

Only proceed with these steps if the Outlook user has indicated that they are having problems or that items do not appear to be correct. Assist the Outlook user by reviewing appointments between March 11 and April 1 to make sure they are all correct.

Help the Outlook user correct items by instructing them on what actions to take. Ask them to click and drag any appointments that they have organized to the correct time. They should also send out meeting updates if prompted during the move operation. If they want you to move then items, you can, but the ideally it should be the Outlook user that makes the updates.

Check for missing items

If the Outlook user reports missing appointment items during the period from March 11 to April 1, those items might be recoverable using Outlook's Recover Deleted Item feature. You can use the following steps to try to recover these deleted items:

1. Open Outlook.

2. Select the user's profile.

3. When the mailbox is opened, select the Deleted Items folder, and look for any deleted items that need to be recovered.

4. Then, select the Inbox.

5. On the menu bar, click Tools, and then choose Recover Deleted Items. The Recover Deleted Items window will be displayed, as shown in Figure 5 below.

Figure 5 - Recover Deleted Items Window

6. Check the Recover Deleted Items window for any items that need to be recovered.

7. Repeat steps 3-5 for the Deleted Items folder and the Calendar folder until all items are recovered.

If missing items are not recoverable then let the Outlook user know that they should contact each meeting organizer and request that they re-send the meeting invitation.

IV - Discuss Other Clients that Access the Outlook User's Calendar

Once the calendar is updated to the user's satisfaction, next ask if any other clients or users are accessing their calendar.

  • Ask if the Outlook user has a delegate, or if anyone else has permissions to modify their calendar.
  • Ask if the Outlook user has multiple machines or a mobile device that they use to access their calendar. It is critical that all clients and mobile devices used to access the calendar be updated with the appropriate DST 2007 update(s).

If the Outlook user mentions that appointments from other users appear incorrect, ask for the names of the meeting organizers and the Help Desk will proactively follow-up with an offer of a calendar review for that Outlook user.

Instruct the Outlook user that they can continue to accept meetings from everyone. If the Outlook user sees future meeting updates, they must accept or decline the updates, and not just delete them.

Appendix A

Scenario 1

Calendar items are created under DST 2006 rules and then viewed under DST 2006 rules


The operating system is not updated to accommodate the new DST rules. This issue may occur if users are not receiving updates from Microsoft Updates and have not taken action to address DST.


Appointments are created that occur during the extended DST periods in March and October 2007 on computers that are not updated to reflect DST 2007. Additionally, meetings and appointments are viewed in Outlook on computers that have been updated to reflect DST 2007.


The calendar items are displayed at the correct time. However, the system time on the computer is off by one hour during the extended DST period.


Update Windows to reflect DST 2007. After the Windows update is installed, users must run the Time Zone Data Update Tool.

For more information about this update, visit the following Microsoft Update Web site: (

For more information, click the following article number to view the article in the Microsoft Knowledge Base:

931836 ( February 2007 cumulative time zone update for Microsoft Windows operating systems

Scenario 2

Calendar items are created under DST 2006 rules and then viewed under DST 2007 rules


The operating system is updated for DST 2007. However, the Time Zone Data Update Tool was not yet run to address appointments that were created under DST 2006 rules.

In this scenario, new calendar items may continue to be created by using mobile devices or other computers that have not been updated for DST 2007. However, the calendar items are viewed on a computer that has been updated.


Calendar items that fall within the extended DST period were previously created on devices under DST 2006 rules. However, these items are then viewed on devices that have been updated to reflect DST 2007 rules.


Calendar items that you organize are off by one hour during extended DST periods. Meetings for which you are an attendee may not be set at the correct local time in Outlook.


Run the Time Zone Data Update Tool to update appointments and meetings that are organized by the user to reflect the new DST rule. Meeting updates are automatically sent to the other attendees.

Avoid creating new calendar items during the extended DST period from other computers or from devices such as mobile devices until the computers or devices have been updated to reflect new DST rules.

There may be meetings for which you are an attendee that occur during the extended DST period and that have not been updated by the meeting organizer. In this case, contact the organizer directly to confirm the time.

Scenario 3

Calendar items are created or updated under DST 2007 rules and then viewed under DST 2006 rules


Other users have updated the computer that they use to reflect DST 2007 rules, and have sent you meeting invitations that occur during the extended DST period. However, you have not updated the computer that you use to accommodate the new DST rules.

Alternatively, you have updated the computer to reflect the DST 2007 rules and have run the Time Zone Data Update Tool. However, you are now viewing your meetings and appointments from another computer or from a mobile device that has not been updated to reflect the DST 2007 rules.


Appointments and meetings are created on a computer that is updated to use DST 2007 rules. However, appointments and meetings are viewed on a computer that is not updated to use DST 2007 rules.


Appointments and meetings that you organized are off by one hour during extended DST periods. Meetings for which you are an attendee may not be set at the correct local time in Outlook.


Apply the Windows DST update to computers and mobile devices.

Scenario 4

Calendar items are created or updated under DST 2007 rules and then are viewed under DST 2007 rules


Windows is updated on the computer to reflect DST 2007 rules, and the Time Zone Data Update Tool has been run to update the previously created calendar items.


Other computers and mobile devices that are used to view and create calendar items are updated to reflect DST 2007 rules.

Meetings for which the user is an attendee have been updated by meeting organizers who have updated their systems to reflect DST 2007 rules.


Calendar items were created by the user under DST 2006 rules and were updated by using the Time Zone Data Update Tool. Alternatively, appointments were created after Windows was updated to reflect the new DST rules and are viewed on computers that are updated for DST 2007 rules.


Calendar items display correct times during all time periods.


No action is required.

- Steve Justice

Comments (49)
  1. Rod Payne says:

    Note that Outlook 2003 and earlier clients need a DumpsterAlwaysOn registry setting to use Deleted Items Recovery for anything other than the Deleted Items folder.  (Outlook 2007 wasn’t listed in the assumptions.)

  2. TNATnT says:

    I have a quick question….

    I am preparing to do the DST update to my exchange but when I unzip the MsExTMZ.msi, I am missing the daylight.prf. Am I downloading the correct version?

    Any Help you can give is appreciated!



  3. Richard Read says:

    I wonder if you could confirm my understanding of how the issue affects UK/Europe, and whether my approach is correct?

    I work in the UK, part of a global organisation. I am planning to update client and server OS’s with the DST update; then update the Exchange server OS’s and finally apply the Exchange server DST update.

    I do not think that I need to run the rebase tools for my UK user’s calendars. My colleagues in the US are going to be running rebase for their users. The reason I don’t think I need to run rebase is that I think that any meetings organised by US/Canada colleagues, that UK people are attendees for, will result in meeting Updates being sent to UK people (generated by rebase), which when the UK people accept will then show the correct local and remote time; and any meetings that UK people have organised, and invited US/Canada people to, will also "just work" because the originating time zone (GMT) is unaffected. Do you think this is correct? I am reluctant to run the rebase tool if I can avoid it.

    Thanks in advance for any help.


    Richard Read

  4. Chris says:

    Thanks for this article, which is very helpful.  I am a little confused in the part that says:

    7. Ask the Outlook user if any appointments on this list appear to be incorrect (e.g., appear one hour ahead). Any appointments that appear to be one hour ahead will need to be moved.

    8. Uncheck any appointments that are indicated as correct (e.g., not 1 hour ahead).

    In step 7, by incorrect, do you mean that the "new time" displayed is an hour ahead of the desired time?  Which would mean that the meeting is already at the correct time and would therefore get unchecked in step 8?  So why would they need to be moved?

  5. Anonymous says:

    The Exchange team has posted a helpdesk oriented document that provides recommendations and prescriptive

  6. Anonymous says:

    The Exchange team has posted a helpdesk-oriented document that provides recommendations and prescriptive

  7. Anonymous says:

    I’m sure that’s the source of heartburn for IT Administrators all over the country right now. I just

  8. Another IT Manager left out in the cold with no hotfixes says:

    I used to be a dedicated supporter of Microsoft for years but I can’t respect that they are hiding behind technicalities in order to charge $4000 instead of releasing the Exchange 2000 patches.  What Microsoft is doing may be legal but it is not ethical and it does not engender goodwill.  I predict that this little DST 2007 technicality is going to fall out in the end to be a huge hit for Microsoft’s public image among formerly supportive IT specialists and business owners.  I never thought I would say it….but time for me to take a Linux class.

  9. ramsam says:

    I have a situation.

    At one organization the Exchange servers were patched for the new time zone updates which starts on march 11th.

    On the desktops we ran the Time Zone Patches for XP OS.

    Running the OS patch moved the timings of the meetings between 10individuals to 9:30 to 11:30 instead of being 8:30 to 10:30

    The people for whom the OS patch was not added shows the correct time which is 8:30 to 10:30

    Is there any known method to fix this?

    NOTE:This is a reccuring meeting and these people have set up many other meetings till the year end.

  10. Atif Shaikh says:

    We applied Server OS , and Workstation OS patch, We ran the Exchange Mailbox tool to fix the appointments, however we did not install the Exchange DST patch. What will happen and can we install the Exchange DST Patch now even if we ran the mailbox fix tool.

    Please email me back Thank you.

  11. ramsam says:

    Hey Atif,

    I would recommend you do not run the DST patch on the Exchange if

    all the time schedules are fine for the Users.

    We did it the other way applied patched to the Server first and them applied patches to the individual OS which messed it up.

    But could any one tell me a way to undo my issue mentioned above?

  12. Steve says:

    Man this is complicated.  The fact that the hold time for Exchange DST support is over two hours shows that I’m not the only one who feels that way.  The sad part is that we may have to do this again if Congress decides it’s not saving enough money and reverses the change.  Hopefully MS will simplify the process by then (but I doubt it).  Being caught between MS and Congress is killing me.

  13. tom says:

    This is all MUCH TOO COMPLICATED!! :) :)

  14. Leif says:

    So far our entire office has had their appointments move an hour ahead.  Has anyone had any luck with talking with Microsoft?  We are currently on hold with them and am wondering if we should stay on hold or not.  BTW congress did this to save money for WHO? it is costing our businees a ton in IT support and I bet cost Microsoft a butt load to release a bum patch.

  15. Steve says:

    Just got this e-mail from zdnet:

    Microsoft Meltdown over daylight savings patches

    Microsoft’s online DST chat room is full of customers who can’t get their patches to work. Plus, Microsoft support phone lines are jammed with users with DST problems.

  16. Jason says:

    We’re telling our clients to print-out their calendars now and not trust any time entries in their Outlooks for the next three weeks.  Once the dust settles and there seems to be some sort of semblance of a consistent strategy, we’ll look at the tool approach again then.

  17. Leif says:

    So, after spending the 3 hours on hold with MS we still have a messy problem on our hands.  If we roll back to before the 666 patch will the appointments that MS changed go back to the regularly scheduled times?  Will our systems break on Sunday or will OWA show the wrong time for some appointments for the next 3 weeks?  What I am thinking is that we were fine before we tried to update our exchange server and the tool approach is worthless.  Our OWA is under utilized within our firm so if one place is broken it is better than every place being broken.

  18. Brent says:

    Why is there a fix to the Outlook TZMove on March 7th, 2007 just a few days from Black Sabbath? Why weren’t all these things worked out starting in 2005 when Congress passed the law? Are we required to watch the MS Website for new fixes until 2 AM. Or is this just typical Microsoft software testing: 1) write the code. 2) release the software 3) let the customer test it. 4) post a patch. 5) post a patch. 6) post a patch…. 7) Talk about converting to Linux again…

  19. Fed Up says:

    Is anyone at Microsoft going to be fired b/c of this or is there no accountablity there?

  20. Contact my IT department... right! says:

    have windows Vista… so I have nothing to do?

    but I have Outlook 2003… so I should do something, correct???

    does’nt work!


    My IT department is…. mmmm let’s see, R they in my kitchen?

    Nope, not there…

  21. Tzmove Don't Work says:

    Every time I run tzmove.exe it says "The Operation Failed" and that’s it.

  22. Veera says:

    ESM Message tracking shows the default end time by one hour ahead of system time after applying DST patch. Did any one notice this?

    Any comments on this?

  23. Leif says:

    We have gone through all of the steps that Microsoft provided plus we have gone to individual machines and run all of the patches and tools MS provided and told us to use and we are in the exact same place we were before the last 14 hours of work every calendar appointment is one hour ahead for the next 3 weeks.  So I wanted to say THANK YOU for screwing up every single calendar in our office (sarcastic of course).  I still cannot understand why anything in outlook needed to be changed, the entire calendar feature just needs a time to tell you when you have an appointment it shouldn’t care if it is 9 PM DST or 9 PM STD time it only needs to know 9 PM period.  I hope the Exchange Team test their patch and then test it again and again and again next time before releasing it.

  24. paul j. camp says:

    Your timezone update tool doesn’t work. It complains that Outlook is not the default email client and refuses to run. Making Outlook the default email client does not alter this behavior. It still crashes. This is useless.

  25. JaredCEG says:

    i have installed the patch kb926666 and now some of the permissions to shared mailboxes and calendars are broken….how i get this fixed…i’ve on hold with MS for 2.5 days…need a resolution fast… should i just uninstall kb926666…?

  26. Arron says:


    Is your issue possibly related to either of these? They were mentioned in the KB926666 documentation.



    Hope you get things worked out.

  27. osric says:

    All I can say is, it’s time to get a Mac and move to open source server software.

  28. ChrisA says:

    The bad think is that Outlook uses the system DST table to write the Calendar time correctly in UMT time + or – for the timezone your in. The bad thing is if you haven’t patched all your desktop OS systems in one fell swoop and then run the TZmove utility immediately you have that wonderfully screwed up grey area that should be spelled out at the top of KB articles. You have to know whether the items were created in Outlook prior to or after the DST patch was applied to OS, because if you don’t the items created after the OS patch will be changed to be incorrect with the same TZmove utility tool designed to fix the prior patch appointments. This is one hell of a mess from my point of view. Microsoft should have wrote a smarter utility to deal with this mess. Even if they had that wouldn’t necassarily take into account the users that may have machines at different patch states and both have been used to schedule appoinmtents.

    One solution that enables to pick the items to correct is change the calendar to Event view and add the created field to the view before running TZmove and compare the install date and time for the OS patch and modify only the re-occuring and calendar items that fall into the Extended DST period created before you applied the OS patch and uncheck all that were created after the OS patch.

  29. JaredCEG says:

    i removed kb926666…. reverted back to the old permissions… only folks affected are owa users… small percentage… so i dont mind..

    but i cant believe i didnt do that earlier…waited 2.5 days for msft to say that…

  30. Nathan says:

    I can’t believe this.  Tzmove tells me "No appointments, meetings, or reminders were found that need to be moved to the new time zone" even though I am looking at my appointments and they are all scheduled for an hour behind what they should be scheduled.  I’m getting my reminders an hour after the fact.

    Way to go again Microsoft.

  31. L663 says:

    When it Hotmail going to be update for the DST 2007?

  32. IT GUY John says:

    Spent a long time Saturday and Sunday running updates on the XP PCs and running TZmove.exe.  Now I have most computers that are an hour ahead!  They changed 2 hours, not one.  I set the time correctly and they change back!  I tried turning off "Automatic DST change" to keep the correct time but now Outlook appointments for the rest of the year are incorrect.  Any all day events now span an extra day.  I just forgot the 30 Win 2000 machines and changed them manually.  

    I’m sure saving a lot of energy on this fiasco.  Wish I had never touched our PCs.  Can uninstalling the KB-931836 patch fix the Outlook problem??  Sure glad I didn’t touch our servers….

  33. Nothing Works says:

    Just found this out:

    Microsoft’s DST patch for Windows 2000 does not work as advertised

    If you manually updated Windows 2000 machines with the tool MS provided, guess what?  It doesn’t work!

  34. wg says:

    Ran TZMOVE on public calendar and it showed 7 items required update. This calendar has dozens of All Day events. These were not listed so ran the tool.

    All the All Day events now run 1am to 1am. Niiiice. OS is properly updated

  35. Ray Avila says:

    After nearly 36 hours of wrestling with DST problems in my Outlook calendar I am about to give up and have lost a great deal of respect for Microsoft in the process. The tzmove tool will not install on my system saying I have not set up outlook as default mail program even when I did. Likely the real problem is I don’t have a MS mail account and do not intend to get one. Because of that, the instructions above also are not workable for me as they require a MS exchange account. I was only using the calendar function of outlook and that was all I wanted. This whole thing has been made too complicated to users.

    If that is not bad enough, I now also have a corrupted SQL server as a resullt of attempts to install microsoft updates last night. Boot message says it is corrupt and I should uninstall SQL server and rerun setup to fix it. It gives no direction on how. I can find no help on how to even tell which version of SQL server I have. I did find instructions on web to manually uninstall but that requires using a Microsoft SQL Server compact disc which did not come with my system and its bundled software. I don’t really want to buy one and I don’t know what version to get if I do nor if it will work to remove the one on my system… I am more than a little frustrated by all this.

    I wish someone could show me an easy way out of the mess.

  36. IT GUY John says:

    Update: I have the correct time but I had to uncheck the "automatically adjust for DST" box.  Regarding all day events in Outlook spanning 2 days, I was able to run TZmove.exe again (and again) check the 2nd option and pick different time zones for  "Original" and "New" time zones.  All day events now run midnight to midnight as they should instead of 11pm to 11pm.  Not as advertised, but it gives the proper end result.

  37. DevilDog44 says:

    This "simple" process has proven to be anything but. We are still combating issues related to the many patches and repatches. With Microsoft having 2 years of knowledge of this issue I would have expected more time for testing the patches that were issued. This has been very disappointing.

  38. I in IT... says:

    Think this is complicated…wait till Congress decides we need to stick the the original DST zones and we have to undo all this mess…

    We have had little or no issues (knock on wood) but we just migrated from Sendmail to Exchange so folks don’t have many affected appointments.  And we’re just now setting up shared calendars and resources.

    However…some old co-workers of mine have applied all patches and run the Update tool only to find it does not send meeting updates to attendees even though it fixes the organizer’s meeting item.

  39. Marc says:

    Nice of Microsoft to leave us out in the cold until the last minute.  I take it that the teams had more important things to work on like Vista, Office 2007 and Exchange 2007. Will Microsoft hold a postmortem on this so that we don’t have another mess next time?

  40. Anonymous says:

    EHLO has published a helpdesk guidelines document for the application of the Outlook Time Zone Update

  41. alex says:

    I found the tool, but it would be nice if there was a link to it here. All of my Reminders are an hour late, even though the Calendar entry shows the correct time and date. We’ll see how it works out.

  42. Kevin Hastie says:

    This is an absolute NIGHTMARE. Way to go, Microsoft. Unbelievable.  Back to OpenOffice I go!

  43. alex says:

    Well, It updated some of the Calendar entries, but not all. My recurring entries still pop up an hour late. The Calendar entry itself has the correct time. Hmmm.

  44. Outlook Tips says:

    Outlook have great calendar and I do not have any problem with him

  45. Keith says:

    Once we applied the DST patches it has messed up security between our exchange server and dc.  We have been having to reboot the exchange server.  And our users are having to delete their outlook profiles and recreate them to get into outlook.  Has anyone else experienced this?  We are exchange 2003 and Windows server 2003 on both systems.  

  46. alex says:

    After loading the patch for the tool, I ran it again. It did not indicate any new findings, but after running it my recurring calendar entries are working correctly. Not sure what the magic was, but all is well.

  47. Shahzad says:

    Need help with small issue.  I actually wound up calling MS to get help on DST updating and got everything up-to-date and working OK.  There is one small issue though, which I’m guessing all of you will have as well.  When using the Web interface for Outlook, if you set an all day recurring appointment on one of the DST change days, like the 2nd Sunday of March, it will span 2 days.  All other days work fine, and this is only an issue on Outlook Web.

    MS has a different order to follow for the steps for updating the exhange server, if users rely heavily on Outlook Web for scheduling appointments or not.  I’ve tried both of these orders, and this problem remains.

    Occurring on MS Exchange 2003 Servic Pack 2, using WinXP Pro SP2, with IE 6.0 on the client side.

Comments are closed.

Skip to main content