when ever we reboot exchange we follow with unity.<div><br></div><div>Unity basically logs into each users email box so it can figure out if it should turn the MWI on or off.</div><div><br></div><div>if Exchange reboots, unity doesn't try to log into the box again. thus is why you get MWI not correct.</div>
<div><br></div><div>I've just given my exchange admins the permissions to reboot unity when they reboot exchange. So long as they don't forget.... works really well.</div><div><br></div><div>Scott<br><br><div class="gmail_quote">
On Thu, Dec 3, 2009 at 12:06 PM, Countryman, Edward <span dir="ltr"><<a href="mailto:Edward.Countryman@provena.org">Edward.Countryman@provena.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
We run unity 7.x and exchange 2003 enterprise cluster.<br>
<br>
Every time we have exchange downtime, I have dozens of users lose their<br>
lamp sync. Running the batch resync fixes most of them but I always end<br>
up with a dozen or so that I have to manually push the unity refresh<br>
button for, sometimes 2 or three different times. This normally takes a<br>
day or two to clear. (and is a PITA)<br>
<br>
TAC says its exchange; my exchange folks say its unity. I was just<br>
wondering if anyone else ran into similar issues when exchange goes<br>
down.<br>
<br>
<br>
_______________________________________________<br>
cisco-voip mailing list<br>
<a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>
<a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
</blockquote></div><br></div>