we have unity um 5.0 with exch 2007/2003.
lately we have many users reporting that their mwi light "stops working". either the light stays on when there is no new msg or the light does not go on when they have a new msg.
each time we have been able to rectify it by doing a status refresh in unity admin.
i opened a tac case and was told " the current unity version is 5.0(1) without any patch installed. With this version of unity the Notifier component, which is responsible for MWI gets overloaded and there are intermitted issues of MWI". recommend we add ES82 to resolve it.
i've been looking for some kind of documentation regarding this but haven't found any. Also ES82 is not on download site so there is no release notes available.
I've asked tac for some doc's but nothing sent yet.
has anyone heard of this and is there doc's available?
Here are a couple of other things to check. I ran into the same issues some time ago and they were resolved by the following.
1. Make sure Unity and Exchange NICS as well as their switchports are hard coded to 100/Full.
2. On the Unity and Exchange NICS > Properties > Advanced - change Checksum Offload to None.
Hope this helps.
Here is the readme.
This Engineering Special (patch) requires Cisco Unity 5.0(1) and needs to be installed on both Primary and Secondary Cisco Unity failover servers in the case of a failover configuration.
A complete list of defects addressed by this Engineering Special can be found in the section titled Resolved Defects. This Engineering Special is a roll-up of the following Engineering Specials and service patches:
ES81, ES80, ES78, ES76, ES75, ES74, ES73, ES72, ES71, ES70, ES69, ES68, ES67, ES66, ES65, ES64, ES63, ES53, ES50, ES49, ES48, ES45, ES44, ES43, ES42, ES41, ES40, ES39, ES38, ES35, ES34, ES33, ES32, ES31, ES30, ES27, ES26, ES25, ES24, ES23, ES22, ES21, ES20, ES19, ES18, ES17, ES16, ES15, ES14, ES13, ES9, ES7, ES4, ES3, ES2, ES1
The following sections detail how to enable new options and features that are supported by this ES. Prior to following these steps, you must first install the ES as per the above Engineering Special Installation Instructions section
|Fixes introduced in CU5.0(1)_ES82|
|CSCsq92171||CSCsq92171 - Conversation traces not enabled using Macro Conversation State Traces|
CSCsz19418 - modify exclusion pattern so . (period) is allowed
|CSCtc24189||CSCtc24189 - HTTP TRAP - CPCA TRaP record does not work|
|CSCta71728||CSCta71728 - Issue with ActiveX controls shipped with Unity PCA|
|CSCsz17586||CSCsz17586 - Unity Inbox timestamp incorrect for some time zones|
|CSCtc11035||CSCtc11035 - DST change for Western Australia|
|CSCsw25257||CSCsw25257 - Unity AD sync - offer setting to disable sync'ing Scope DL's|
thanks for publihing the release notes.
i'm trying to get to the url for the resolved patches but it doesn't display.
do you know anywhere else i can view them
What URL are you trying to get? If you can tell me specifically what you are needing, I can see what I can do to get what you want.
That is because that is an internal link you can't use if you aren't employed with Cisco. You might want to try the Cisco Bug Tookit here..
BTW, this also includes all ES bug fixes for all previous ES releases 1-82. Make sure you do any and all applicable post install instructions. Especially the patch 103.
I have what I think is a very simple question about the MWI sync issue. I am an Exchange Administrator who works with a group of telecom people who manage Cisco Unity. We have clusters for our mailbox servers, and they are telling me that every time a cluster fails over to another node that they have to manually go in and get the MWI lights to sync in Unity. Is this true, is this really how Cisco designed this product, that for every cluster node move you must do a manual process to get the MWI light back up and running?
This ins't how it was designed. This is why there is a patch for this from Microsoft regarding their "failover" and Exchange clustering. You are hitting this specific defect.
CSCsk50809 MWI stops working after Exchange Cluster Failover
No MWI Notifications are received after an Exchange 2007 failover condition
occurs for a clustered mailbox server. This only happens for the Unity
Subscribers whom are located on a *different* clustered mailbox server than the
Unity System Mailbox (Unity_
failed over contains the Unity System Mailbox, MWI will work as expected for
all Unity Subscribers on that clustered mailbox server.
Subscribers whom are not getting MWI are located on an Microsoft Exchange
Server 2007 Single Copy Cluster (SCC) which has recently failed over to a new
physical node, and the Unity System Mailbox (Unity_
on that clustered mailbox server.
Use the BulkLogout Utility to logout the users in question, then perform a resync
Restart the AvMsgStoreMonitorSvr service **NOTE: This will force a system wide
MWI Resync and may cause MWI delays until the Resync process is complete
This is a duplicate of defect CSCsl79289 MWI lengthy after Exchange Cluster Failover
Cisco Unity MWI notification is delayed after an Exchange Cluster Server failover.
Exchange Cluster Server failover.
Stop/Start the Message Store Monitor service.
Ultimatley the case I had that hit this with Unity 5.x and Exchange 2007 clustering was resolved on the Microsoft Side with this hot fix.
I have attached the exe and txt readme regarding this hot fix.
First and foremost I would like to thank you for taking the time to answer my question. It is very much appreciated.
From reading your post, I would have loved to have known about that hot fix from Microsoft when are users were on Exchange 2003. However, all of our users now reside on Exchange 2007 that is configured as a CCR cluster. Do you know of any fix for Exchange 2007 and the MWI lights? Should we have to do a manual sync every time the primary node moves to the other server?
This applies to 2003 and 2007 Exchange so you still need this patch. My case had 2007 Exchange and it fixed the issue. Run the exe on Unity btw.
One more quick question and I promise I will leave you alone. I was reading the KB article associated with the hotfix and was wondering if you created the registry key that they refer to?
I have personally never had to but I have seen other cases where the patch was applied to both Unity and Exchange and had the registry added as well. For the cases I resolved however I did not have to go so far.
I tried to run the patch on our Windows 2008 servers that host our Exchange 2
007 environment, and it won't run. It says there is not enough storage space
, but there is plenty of space.