Yep, all too well. Here is my scenario from this past time change and you can decide if it will help you.
History: We have a CallPilot 1005r on Release 5. In 2008, this server made it through both time changes problem free. We updated the PEPs on Nov 11, 2008.
Problem: This past time change on March 8, 2009 we were given the report that the time stamp on messages was an hour off. I found a solution on Nortel's Knowledge Base to go to the time zone settings in the Control Panel and check the box to "auto adjust for DST". Then manually correct the time on the server. I performed that action and it fixed the time stamp problem...
BUT: The next morning, I received reports that menus using Time of Day blocks were not playing the correct greetings. I unchecked the "Auto adjust DST" box in the server and that fixed the AppBuilder issue but made the time stamp an hour off again.
As a work around, I checked the box to "auto adjust for DST" again to fix the time stamp and then I went into AppBuilder TOD control blocks and backed them up an hour. For example, one was set to 8am-5pm so I changed it to 7am-4pm.
That work around was fine for a few days while I investigated the cause.
Final Repair: I found that after we updated the PEPs back in November, specifically the Service Pack 2 PEP, that Windows Time Service gets enabled again. I stopped and disabled Windows Time Service and that afternoon the AppBuilder was an hour off again. I corrected the TOD block back to 8am-5pm and it worked properly. The time stamp on messages was also still correct.
Summary: To make this long story short, go into Services on the server and verify Windows Time Service is Stopped and Disabled.
War Eagle!
Lions Baseball '09!
