In Outlook, you can display two separate time zones in the Calendar. This allows you to see your local time zone and the time zone of a city that you often travel to. When you travel to that other time zone, you can use the Swap Time Zones option to change the position of the time bar in the Calendar. Using the Swap Time Zones option in Outlook 2010 results in unexpected behavior.
Consider the following scenario. You are in a time zone that does not observe Daylight Saving Time (DST). You switch Outlook from this DST time zone to a time zone that supports DST and the current date is within the observed DST. You see the times in the Calendar time zone bars are off by one hour. Additionally, the Date and Time Control Panel applet in Windows does not have the Automatically adjust clock for Daylight Saving Time checkbox enabled.
The option to swap time zones in Outlook does not base the DST setting on the new time zone.
This issue is fixed in Microsoft Office 2010 Service Pack 1 (SP1). For more information, click the following article number to view the article in the Microsoft Knowledge Base:
If you are unable to install Microsoft Office 2010 Service Pack 1, you can use the following workaround.
After swapping from a time zone that does not observe DST to one that does, ensure that the Windows setting Automatically adjust clock for Daylight Saving Time checkbox is enabled.
To change your time zone setting, follow these steps:
Double-click the clock in the Windows Notification section of the Taskbar.
Select the Time Zone tab in the Date and Time Properties dialog box.
Enable the Automatically adjust clock for daylight saving changes option and click OK.
Windows Vista and Windows 7
Click the clock in the Windows Notification section of the Taskbar.
Click Change date and time settings
In the Date and Time dialog box, click Change time zone.
In the Time Zone Settings dialog box, enable the Automatically adjust clock for Daylight Saving Time option and click OK.
Click OK again to closethe Date and Time dialog box.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.