<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Inline, ws.<br>
<br>
<br>
If we choose NOT to do the patch, then on Sunday our clocks update<br>
correctly anyway, and remain correct until November 1st.<br>
<font color="#3333ff">ws: correct.</font><br>
<br>
If we do an upgrade to a supported patched version between now and then,<br>
we're OK anyway and we're not patching our cluster and rebooting all
phones twice, with<br>
the first reboot being within days of a point at which this would fix<br>
itself anyhow?<br>
<font color="#3333ff">ws: correct. that is why the first recommended
workaround is simply to be patient if that is a viable option for you.</font><br>
<br>
<br>
Just trying to provide a benefit/timespan analysis for us to decide<br>
about the phone outage for users<br>
Since we cannot _absolutely_ guarantee that no phones will reboot<br>
whatsoever, we usually declare such things "maintenance windows" anyhow,<br>
even if we expect no major impact.<br>
<font color="#3333ff">ws: applying the patch does not reboot phones.
however, you are required to restart ccm after applying patch. phones
will reset or at least restart.</font><br>
<br>
<br>
Also - I assume that post the 60 second waiting time, the usual rules
apply to restarting CCM services- eg, you would restart the CM service
on the Pub, then after it's back up, restart the CM service on the Sub,
and phones would switch back and forth and update time as needed?<br>
<font color="#3333ff">ws: correct. keep in mind the 'failback' time
may depend on "connection monitor duration"</font><br>
<br>
<br>
</body>
</html>