Microsoft Daylight Saving Time & Time Zone Blog : Exchange Server

Microsoft Daylight Saving Time and Time Zone update now available (December 2008)

atsim — Fri, 30 Jan 2009 01:22:00 GMT

The most recent cumulative updates to daylight saving time (DST) and world time zones (TZ) are now available for supported versions of the following products. For the latest DST updates on each of these products, please visit the following Microsoft Web site: Microsoft Daylight Saving Time Support page.
The cumulative updates can be downloaded as indicated in the same Web page.

Microsoft product teams follow a semi-annual DST and TZ update schedule, which follows the Windows regular schedule for publishing newly legislated DST rules and time zone updates. These annual "Cumulative Daylight Saving Time and Time Zone Updates" will be released in December for the coming calendar year; a semi-annual update will be released in July/August, as needed. Microsoft products that are affected may also schedule updates to accommodate some of these changes.

For more information about all the DST and TZ updates that have been made to date, visit the following Microsoft Web site:
914387 How to configure daylight saving time for Microsoft Windows operating systems.

More details are available at http://support.microsoft.com/gp/dst_hottopics.

Chile announces an extension on their Daylight Saving Time for 2008

atsim — Sat, 08 Mar 2008 22:26:00 GMT

The government of Chile announced on February 7, 2008, that their current daylight saving time will be extended in order to save energy. The new fall back date for the daylight saving period of 2007-2008 is:

Daylight saving time ends: Last Saturday of March at 11:59:59PM

Information is available via our Chilean web site at http://www.microsoft.com/chile/cambiodehora, "Extension del horario de Verano en Chile". Customers and partners will find additional information on this change and manual remediation at http://blogs.technet.com/latam/archive/tags/DST/default.aspx:

The default configuration for the time zone “(GMT-04:00) Santiago” in Windows Operating Systems does not reflect the new final date for the daylight saving time defined by the government. This bulletin summarizes the actions recommended for customers in Chile to address the extension of daylight saving time and mitigate its impacts.

Tags: Microsoft, Daylight Saving Time, Daylight Savings Time, DST.

Questions Regarding /PHYSICALMOVE

atsim — Wed, 19 Sep 2007 19:57:11 GMT

In preparation for a potential time zone move, customers may use the Outlook Time Zone Data Update Tool with the /PHYSICALMOVE switch, which has promoted some questions as noted here:

Q: Are there negative effects from running the tool multiple times on the same mailbox? (i.e., on the first pass, original time zone = Central & new time zone = Eastern; on the second pass, original time zone = Easter & new time zone = Central)

A: There should be no negative side-effects. In the example here, this would make sense if someone moved from the Central to Eastern time zone and then, some time later, moved back.

Q: Will the tool behave differently if there are appointments created using Blackberry, Live Meeting, OWA, etc…?

A: The intention is that all items are updated correctly.

Q: Can this switch be used when running the Exchange version of the tool?

A: Unfortunately, no. This is functionality that we did not include in the most recent release. Customers may run into issues related to new time zones, as may be the case in Venezuela (which is moving to a newly created time zone, -4:30 GMT - see DST Hot Topics and Latest News for more information). The recommended and supported way to move between time zones is using the client-side tool.

Q: I’ve tried researching internally and haven’t found much documentation on the /PHYSICALMOVE switch. Is there a brief overview of how it works?

A: At a basic level, the /PHYSICALMOVE switch is not that much different than rebasing with the Outlook Time Zone Data Update Tool: identify future items targeted at the source time zone and, if we detect that being in the destination time zone would affect their start or end time, update them such that they correctly reflect local time in the destination time zone.

DST VIDEOS NOW AVAILABLE!

atsim — Fri, 14 Sep 2007 22:08:45 GMT

Steve Justice (Senior Escalation Engineer) and Joel Schaeffer (Escalation Engineer) from Microsoft Product Support have put together some instructional videos to assist your DST planning efforts.

On-Demand (hosted by Channel9.MSDN.com)
These videos can be streamed on-demand for viewing.

DST: Cumulative Time Zone Update for Microsoft Windows
http://channel9.msdn.com/ShowPost.aspx?PostID=341535

DST: Using the Outlook v2.0 Time Zone Data Update Tool
http://channel9.msdn.com/ShowPost.aspx?PostID=341649

DST: How to Address Daylight Saving Time in Exchange Server by Using the Exchange Calendar Update Tool v2.0
http://channel9.msdn.com/ShowPost.aspx?PostID=341747

Microsoft Download Center (table of contents included – use as a reference)
These videos include a web-based table of contents that allow them to be used as an offline reference.

VIDEO: Cumulative Time Zone Update for Microsoft Windows and Windows Mobile
http://www.microsoft.com/downloads/details.aspx?FamilyId=1E55473C-80FF-4E87-A48F-3BC872EF39AA&displaylang=en

VIDEO: Using the Time Zone Data Update Tool for Microsoft Office Outlook v2.0
http://www.microsoft.com/downloads/details.aspx?FamilyId=1A511C92-A45B-46ED-9848-64349EEBD040&displaylang=en

VIDEO: Using the Time Zone Data Update Tool for Microsoft Exchange Server v2.0
http://www.microsoft.com/downloads/details.aspx?FamilyId=A05519EF-B698-4A60-8292-D22D35393E43&displaylang=en

Enjoy!

The Microsoft DST Team

[JS]

Q: Updates to Exchange 2003 SP1 AND BES Blackberry server advice?

atsim — Thu, 13 Sep 2007 07:20:25 GMT

Q: We currently run Exchange 2003 SP1, and also have Blackberry server. Up to now our understanding was that we need to apply the standard DST O/S fix to the Exchange server, but would only need to install the CDO patch if we had applications that use CDO – and Microsoft was only releasing the CDO patch for Exchange 2003 SP2 (KB937653).

We have the Blackberry notice http://www.blackberry.com/btsc/search.do?cmd=displayKC&docType=kc&externalId=KB14176&sliceId=SAL_Public&dialogID=47758087&stateId=0%200%2023172424 about updating CDO.

We have now seen http://support.microsoft.com/kb/940123 which seems to show a CDO DST fix for Exchange 2003 SP1.

Instead of migrating now to Exchange SP2 now, could we use KB940123?

A: This is the correct fix for an Exchange 2003 SP1 installation.

In this case the customer is installing it on on Blackberry Exchange Server (aka BES). We suggest that customers contact RIM to find out what RIM recommends and supports for their products in this scenario.

Otherwise, the customer may update the Exchange 2003 components on the BES computer to SP2 and then apply 937653 (as RIM states in the link).

[JM]

Q: What steps are needed to install the Exchange Calendar Update tool version 2

atsim — Thu, 13 Sep 2007 06:18:00 GMT

Q: I’m attempting to install the new Exchange Calendar Update tool on a system that had the previous version installed – I removed the previous version via Add/Remove Programs, but when I execute the installation for the new version, I get an option to repair or remove and choosing either option results in an error indicating ‘This action is only valid for products that are currently installed’. Can someone advise as to what kind of clean up may be needed to get the new version to install successfully?

A: If you have uninstalled the old Exchange tool, then look for and remove the following key if it exists:

HKLM\Software\Microsoft\Windows\CurrentVersion\Uninstall\{9F73F6F4-F3A0-4B0A-A52B-D3B622DE6024}

Try the install of the updated Exchange tool again. The installation should now work after removal of this key.

Calendar appointments showing 1 hour later on recipients' calendar appointments

atsim — Mon, 12 Mar 2007 22:06:00 GMT

Symptom: Any calendaring client may show 1 hour later on a recipients' calendar appointment (Outlook, OWA, Blackberry or Goode devices etc.). The recipient will appear to not follow DST2007 rules. This is true even with OS patches are successfully applied even with rebasing successfully executed. Warning: If the system is not OS-patched or rebased successfully, the symptoms will appear similar to this issue (and the unpatched OS is much more common).

· Explanation: This is caused due to multiple copies of CDO.dll or CDOEX.dll existing on the Exchange and/or BES/Goode servers , and the copy of CDO.dll or CDOEX.dll is not being updated, but the applications (Outlook, OWA, Blackberry, Goode, etc) are using the older version of the dll. This can be created by several applications (unrelated to messaging potentially) which install or copy CDO.dll or CDOEX.dll to a separate directory, then register that rough dll.

· Solution:

o Determine if you have this specific issue,

§ please verify all patches and rebasing issues are successfully applied (for example is the OS clock correct, are meetings the user organized being rebased successfully). If the systems are not properly patched or rebased, the symptoms may appear similar.

§ Verify that if a user who is patched sends an appointment to another user who is patched, that the recipient user is showing that appointment one hour later than originator’s.

§ Search the Exchange server (and BES server etc) for multiple copies of CDO.dll or CDOEX.dll.

1 - Run this: C:\>dir /s cdo.dll

2 - Repeat for all drives.

3 - If there's more than one cdo.dll, you have a problem

Same for cdoex.dll

o Fix:

Exchange 5.5 (CDO.dll only - 5.5 does not use/ship CDOEX.dll)

(note - path to system32 may vary)

1 - c:\winnt\system32\cdo.dll is the correct CDO.dll. Delete all other copies of CDO.dll.

2 - regsvr32 "c:\winnt\system32\cdo.dll"

Exchange 2000/2003 CDO.dll

(again - paths may vary slightly depending on installation)

1 - c:\program files\exchsrvr\bin\cdo.dll is the correct CDO.dll. Delete all other copies of CDO.dll.

2 - regsvr32 "c:\program files\exchsrvr\bin\cdo.dll"

Exchange 2000/2003 CDOEX.dll

1 - c:\Program Files\Common Files\Microsoft Shared\CDO\CDOEX.dll is the correct CDOEX.dll. Delete all other copies of CDOEX.dll.

2 - regsvr32 "c:\Program Files\Common Files\Microsoft Shared\CDO\CDOEX.dll"

What is an Exchange resource mailbox? How do I find them?

atsim — Sun, 11 Mar 2007 12:48:00 GMT

What is a resource mailbox?

· A resource mailbox is a mailbox that represents conference rooms and company equipment. Resource mailboxes can be included as resources in meeting requests, providing a simple and efficient way to manage the scheduling of resources for your organization. There are two types of resource mailboxes in Microsoft Exchange Server 2007: room and equipment. Room mailboxes are assigned to a meeting location such as a conference room, auditorium, or training room. Equipment mailboxes are assigned to a resource that is not location specific, such as a portable computer projector, microphone, or company car.

· Custom resource properties are features for room or equipment mailboxes. Administrators can indicate that a resource has a specific feature by assigning the corresponding custom resource property to that resource mailbox.

· See http://technet.microsoft.com/en-us/library/aa996338.aspx

For a video demonstration of the exchange rebasing tool please visit http://msexchangeteam.com/archive/2007/02/21/435543.aspx#435553

Script to determine the resource mailboxes in the enterprise: It is attached. please confirm any issues or anything we can assist with.

What does the script (Legdndump) do?

The script interrogates the property named msexchuseraccountcontrol. The value in case of resource mailboxes is 2; for normal mailboxes, the value is 0. It provides the legdn of the resource mailboxes. Then use the legDn in the input file for rebasing.

Script

Const Writable = 2

Set objFSO = CreateObject("Scripting.FileSystemObject")

Set objLog = objFSO.OpenTextFile("c:\legdn.txt", Writable, True)

Set cn = CreateObject("ADODB.Connection")

Set cm = CreateObject("ADODB.Command")

Set rs = CreateObject("ADODB.RecordSet")

With cn

.Provider = "ADsDSOObject"

.Open "Active Directory Provider"

End With

Set cm.ActiveConnection = cn

strDomainDN = InputBox("Please Enter the Servername and Domain DN. " & vbCrLf & " Example: Myserver/DC=test,DC=lab ")

cm.CommandText = "<LDAP://" & strDomainDN & ">;(&(mailNickName=*)(msExchUserAccountControl=2));legacyExchangeDN;subtree"

cm.Properties("Page Size") = 1000

Set rs = cm.Execute

While Not rs.EOF

On Error Resume Next

objLog.Write rs.Fields("legacyExchangeDN")

rs.MoveNext

Wend

objLog.Close

msgbox "Export Complete to c:\legdn.txt"

The KB928225 patch Exchange 2000 CDO update failed and asked me to check the log

atsim — Fri, 09 Mar 2007 20:42:00 GMT

Q: I tried to install the KB928225 patch (Exchange 2000 CDO update). The patch failed and asked me to check the log. "First condition in rollup.andop.section failed" is what I found.

A: Because of file dependencies, this hotfix requires Microsoft Exchange 2000 Server Service Pack 3 (SP3) and the August 2004 Exchange 2000 Server Post-Service Pack 3 Update Rollup.

To get Exchange 2000 SP3, refer to KB 301378 (http://support.microsoft.com/kb/301378 How to obtain the latest Exchange 2000 Server service pack)

To get Exchange 2000 August rollup, refer to KB 870540 (http://support.microsoft.com/kb/870540 Availability of the August 2004 Exchange 2000 Server Post-Service Pack 3 Update Rollup)

We were able to do the rebasing of appts, but now historical appointments are incorrect

atsim — Fri, 09 Mar 2007 17:38:00 GMT

Q: We were able to do the rebasing of appts, but now historical appointments in 1999 are incorrect. What effect does the rebasing tool have on old messages that are restored from archive systems like the vault. What about items that are restored on Exchange? What shoudl we know about appointments that occur in prior years during the 3 week offset... will the times on old emails be 1 hour off?

A: Are you saying appointments going back in time are off and appointments in the DST 2007 time are ok? This expected. Historical time will be changed by 1 hrs in the DST Window.

With respect to Outlook, anything that is stored in UTC (e.g. message delivery times) will be converted to local time using the current time zone rules. This means that looking backwards in time at received messages (whether restored from backup or not) will report incorrect local times for items in the DST delta periods. The UTC times are always correct (and, I would imagine, what can/should be used in sort of legal/compliance situation).

When running the .bat file and it starts creating logs....if it doesn't create a log for a user does that simply mean there was nothing to change?

atsim — Thu, 08 Mar 2007 02:23:00 GMT

Q: When running the .bat file and it starts creating logs....if it doesn't create a log for a user does that simply mean there was nothing to change?
A: Yes, that's correct.

What is the offical name of the Arizona time zone? The tool did not detect the time zone for Arizona users and I want to manually put the time zone into the import document.

atsim — Thu, 08 Mar 2007 02:23:00 GMT

Q: What is the offical name of the Arizona time zone? The tool did not detect the time zone for Arizona users and I want to manually put the time zone into the import document.
A: I believe Arizona time zone is called Mountain Standard Time (MST)

How do i do this ->"To actually perform the rebase you must have an account with send as and full mailbox access to each mailbox."

atsim — Thu, 08 Mar 2007 02:22:00 GMT

Q: How do i do this ->"To actually perform the rebase you must have an account with send as and full mailbox access to each mailbox."
A: The VBScript will give your account FMA & SendAs. For exporting the time zone data you can run it as a regular exchange admin, OR go into ESM and grant your account (which you ran the VB script versus) "Administer Information Store" privileges on each MDB.

I’m logged onto a computer as the domain admin. I’ve tried running msextmzcfg tool using the mail account of the domain admin, but still show "unable to open mailbox" error message in the log file. Do i have to run the vbs permission script

atsim — Thu, 08 Mar 2007 02:22:00 GMT

Q: I’m logged onto a computer as the domain admin. I’ve tried running msextmzcfg tool using the mail account of the domain admin, but still show "unable to open mailbox" error message in the log file. Do i have to run the vbs permission script????
A: Domain user needs Full Mailbox Access and Send As rights to all mailbox. You need to run Grant Mailbox Permission script. Please refer "Configure permissions for Msextmz.exe" section in kb article http://support.microsoft.com/?kbid=930879

After I clean up non-existent and conflict users and add to output.txt what is the next step? Something about skip extraction?

atsim — Thu, 08 Mar 2007 02:22:00 GMT

Q: After I clean up non-existent and conflict users and add to output.txt what is the next step? Something about skip extraction?
A: You can re-run the tool msExTmzCfg.exe and check the "Skip Extraction" option in the first screen and import the new file(output.txt) you just created manually. The wizard will pop up a dialog and asking you to map the user time zones to windows time zones, this way you can resolve the conflict and generate the bat file to run it. It will not pop up if you have manually resolve the users in output.txt with correct time zone. It will directly lead you to create the bat file to run it.