For some users only, when there is a new VM, the MWI is not lit. Other times even when there are no new VM, MWI is just lit. If we resynch in UTIM, the problem goes away but again comes after sometime. Same if we dial the MWI off DN, the MWI resynchs and gives correct status for sometime, and problem occurs back.
Seen this error in the Unity applog:
Message: Received message event 2 on NotifyQ for user cn=pb, cn=Receipients, ou=FirstAdministrative Group, o=Demo who is not monitored. No MWI or notifications will occur for this user. To correct, perform a resync of all mailusers with UTIM: go to the Properties tab of your integration and press the Resynchronize button.
I have the exact same configuration as you. Did you get any resolution yet? If so could you please e-mail me at firstname.lastname@example.org. My problem did not begin until I installed the Unity Security Agent.
In my case it was due to bug id CSCeb27709, which aparently is a duplicate of CSCdy86363. My issue was resolved with CCM 3.3.2 es32. TAC said the issue is also fixed in 3.3.3, I donot know if there is a engineering special or service release for that.
I have Unity 4.0.4 and CM 333 SR4 and I too am experiencing random MWI out of sync issues. It just recently started. Its affecting both Centrex and Cisco integrations. I can force a re-sync through SA which corrects the "problem". It only seems to fail with a few users, and doesn't appear to repeat. In the past two weeks I get at least two to three calls per day about "stuck" message waiting lamps. The issue is ALWAYS turning OFF the MWI. I have MWI set to resync everyday for both integrations.
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...
The below trick might come handy when you have to add a new node to a cluster but you don't have or is unsure of the security password for the publisher. This procedure has been around for ages.
1) Login into the CLI of the Publisher.