03-11-2008 07:24 AM - edited 03-15-2019 09:22 AM
Very strange behaviour after the work around was applied to Unity in a UM configuration.
From Outlook, users receive the correct time for VM's (patched exchange) but when they access the same VM from the phone it's 1 hr behind.
Both Unity & CCM are in synch (time in the system tray) and VM ports register without issue although the timestamp is still behind. Time on the phones is correct.
Any idea how this can be resolved? A reboot didn't produce a positive change.
03-11-2008 01:51 PM
The date\time properties window shows that the "'automatically adjust clock for daylight savings" is unchecked currently.
The time zone is Eastern Standard Time.
03-11-2008 02:06 PM
Right so you need to LOAD THE PATCH. It will not reboot the server, you can do this during business hours. It's a Microsoft patch for windows 2000 server that addresses this fix.
03-11-2008 02:44 PM
Can you provide a link to the related patch?
I've read that the patches are bundled together into 1 .exe that will address DST although at this time all that is needed is the reccomended patch to address the TUI timestamp issue and not patch the server fully in regards to DST.
03-11-2008 03:02 PM
Please see my early post in this thread.
When you download the Cisco Unity DST fix, it will have the Windows KB patch for daylight savings.
also here is the bug.
http://www.ciscotaccc.com/kaidara-advisor/voice/showcase?case=K90543054
03-11-2008 02:02 PM
Here's how I fixed my system.
Unchecked "automatically adjust clock for daylight saving changes" from date and time properties on all servers (exchange, unity) and set the times to correct time.
Timestamps seem to indicate correct time now.
Hope this helps others.
Regards,
metuzuner
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide