On the Call Manager Side we have 2 defects opened for this issue. They are as follows ...
CSCsf07541 - MCS-OS Update needed for N America DST changes in 2007
CSCsf07523 - Update needed for N America DST changes in 2007
You can view these defects at the following link below ...
In short we are going to be covered with CallManager versions 3.3(5)ES56 4.1(3)ES89.1 4.2(1)ES38 4.2(3)ES11.1
All the other versions of CallManager will not have this bug fix.
Is the CCM update needed? If you just do OS update and not CCM will be there be any problems in US? Other than maybe date/time groups being off maybe.
How about 4.0(2)? Will those customers have to go 4.1(3) or 4.2 to get the update? Why not a SR and a ES?
win-OS-Upgrade-K9.2000-4-3a-sr8 has the fix from an OS perspective. You can check avability at the following link
On the readme notes you can see that.
I thought we only need to run the tzedit.exe tool from MS to adjust the DST on the Windows OS and that should take care of everything since CallManager is getting its time from the Windows OS. Is this true ?
Noooo!!! that is only for Unity, you can not use any tool that is not on CCO for CallManager. For CCM you need to upgrade both the OS and the CCM version to be fully patched for the DST changes.
This is very important to everyone here, please correct me, I got a little confuse here.
Let me conclude what we know:
You need 2000.4.4sr2 and later for new daytime saving setting.
FOR Unity (messaging only):
Need tzedit.exe tool from MS.
As long as Domain Controller patch, unifed server should get the right daytime saving from Domain, RIGHT???
Thanks a lot!!!
For CCM you need:
2000-4-3a-sr8 or later (for this train) or 2000.4.4sr2 and later (for this train) and any of the following ES's: 3.3(5)ES56 4.1(3)ES89.1 4.2(1)ES38 4.2(3)ES11.1
At this moment only the tzedit.exe tool from MS, not sure if the developers will make a patch for Untiy, we haven't been informed on that matter, you can post that question on the Unified Communicatios forum and ask Jeff Lindborg.
Well, with 4.0(2a) they could update to 4.1(3) or 4.2(3).
Is there an issue that will be noticed on systems that are not updated other then the time not changing/adjusting on it's own correctly?
Would call manager date/time features be effected without the CCM updates? IE: How crucial is it for the CCM updates if they are on earlier versions?
If you are using a NTP server for CCM and IPCC, do you still need the patches. I am assuming yes in the event you lose connectivity to the NTP server.
I also found out that for IPCC Express/CRS, there's going to be a notice from cisco going out in a week or so with details.
In short, TAC had told me that IPCC Express/CRS 3.5(4)SR2 will have fix, and anything lower will need to be upgraded. The 3.5(4) SR2 will have a JRE update also for the DST changes.
IPCC 4.0(1), 4.0(2), 4.0(3), 4.0(4), 4.5(1), 4.5(2) will need the OS update and Sun JRE DST patch.
Cisco Just released this...I'm using this currently as a map for 2007 Energy Policy Act
For all CCM and IPCCX, there is ntp server loaded automatically after Cisco application is installed. The time sync path is, IPCC get sync'ed from CCM, CCM Subsriber gets sunc'ed from publisher, and publisher sync with its' local time.
So for the DST, all servers have to be updated with new DST dates, either tzedit.exe or Windows patches shall work.
With this document (http://www.cisco.com/en/US/customer/tech/tk648/tk362/technologies_tech_note09186a00807ca437.shtml) it is apparent that those customers running 4.0(2a) don't have a solution to this issue.
I'd like to understand why it is necessary to have a CallManager patch in the first place. Why would the OS patch (CSCsf07541) be tied to a version of CallManager? What are the dependencies with respect to DST/Timezones and when they begin and end for CallManager and Windows. Why is 4.0(x) not included?
Any guidance will be appreciated.
A new single patch for the Daylight savings was released the day before yesterday, you can find it on CCO: