Posts: 481
Joined: 4.Apr.2006
From: USA
Status: offline
Update: Our Exchange Development Team has signed off & released the public hotfix for this issue, and is available for immediate download. Please note that this hotfix requires Exchange 2003 Service Pack 2 to be installed prior to installation of this hotfix.
While the KB article (933902) is not posted to our external KB website, it is in the process of being published, and should be available in the next few days.
Regards,
Scott Oseychik Escalation Engineer (Exchange) Microsoft Corporation
< Message edited by sabel9579 -- 3.Apr.2007 11:53:49 AM >
Posts: 481
Joined: 4.Apr.2006
From: USA
Status: offline
For those who want to know what this hotfix is for...
Overview: An issue has been identified in Exchange 2003 where Exchange System Manager’s MessageTracking functionality incorrectly displays tracked messages by one hour ahead. This issue occurs after installation of the February 2007 cumulative time zone update (KB 931836). It’s important to note that the actual data in the messagetracking logs is correct; it’s merely a presentation issue in ESM’s MessageTracking. Additionally, once we enter into Daylight Savings Time, this issue will no longer manifest itself.
Posts: 481
Joined: 4.Apr.2006
From: USA
Status: offline
I seriously doubt it. Most likely you will need to call MSFT for the hotfix or if you have a premier account you can download it. Let's see when the article is released
Posts: 159
Joined: 31.May2005
From: Toronto
Status: offline
quote:
ORIGINAL: dloweqsc
Will this be released as a regular update through Windows Update / WSUS in the future? We do use message tracking, but only for troubleshooting.
Do what I did. Download, extract and zip it up and use it if you want. It's ridiculous that MS would not offer this as an update and make you call. I also find this line in the overview to be quite misleading "Additionally, once we enter into Daylight Savings Time, this issue will no longer manifest itself." Aren't we already into Daylight Savings Time?
The problem is that we manage a lot of different companies Exchange servers via a single WSUS platform and the cost of approving an update for 50 servers via 2 clicks is a hellavlot cheaper (and relativly safer) than downloading and installing a non-public KB hot fix, that for us, is a non-critical issue.
---
This DST thing has been a complete nightmare / disaster. This is worse than Y2K. At least with Y2K, everybody just took 3 years and bought new stuff. This was alwful. Final, final, final patches being released two to four weeks before the change!!
We labbed every possible senereo and it still went nuts on the day. TZMOVE sucked.
We are expecting more calls on Monday since the old DST date kicks in this weekend.
Don't even get me started on Windows / Exchange 2000.
Posts: 130
Joined: 4.May2004
From: Everett, WA
Status: offline
A bit off topic, but have they fixed DST for OMA? I'm not finding a solution to that one, and my OMA calendars are short an hour. OWA and Outlook are fine, of course.
|
My Subscription |
My Forums |
Address Book |
Member List |
Search |
FAQ |
Ticket List |
Log Out
Printable Version
All Forums >> [Microsoft Exchange 2003] >> General >> DST Message tracking Hotfix released 
DST Message tracking Hotfix released - 
New Messages
No New Messages
Hot Topic w/ New Messages
Hot Topic w/o New Messages
Locked w/ New Messages
Locked w/o New Messages
Post New Thread
