03-12-2007 01:06 PM - edited 03-18-2019 07:04 PM
As you might imagine, lots of calls and questions about DST issues are coming in across many different products. There are a couple of field notices that may be helpful if you?re having problems.
For Unity Connection, start here:
http://www.cisco.com/warp/public/770/fn62668.shtml
For Unity, start here:
http://www.cisco.com/en/US/products/sw/voicesw/ps2237/products_field_notice09186a00807dcf40.shtml
links to patches for the Unity and Connection products as well as recommendations for Windows and JRE updates can be found off those links.
03-12-2007 02:47 PM
Unity 4.21 - failover pair with exchange message store server as DC.
I applied the patches to the servers earlier this week...the following occurred after 2am Sunday:
Time on the message store server was ok
Time on the primary and failover was not changed.
When time was manually set on the servers, the Primary and Failover would go out of sync by 1 hour repeatedly.
I stopped the unity services on the Failover server, rebooted and waited for time sync with the DC. I then started failover mode and then did the same to the Primary. After few hours with no time problems I failed back to the Primary.
I had no issue with single server sites. I suspect this had to do with the SQL replication.
P.S.
I did not change the check on the auto DST checkbox, it was on in all servers.
I would like to know what will occur in November: I anticipate I will have to manually change time on the Exchange box and reboot the Unity servers, and forget about automatic DST changes.
03-12-2007 03:01 PM
This could be the following microsoft bug posted in the earlier thread:
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: