Can Unity support Exchange 2003 with more than 250 Information stores

[allcom]

Currently our Microsoft Exchange 2003 environment has increased to 320 odd Information Stores. According to the design documentation for Cisco Unity release 5.x (covering 7.x) "Cisco unity supports a maximum of 250 Exchange stores". We have currently an issue where by users out of the 'lucky dip' that unity monitors, have issues retrieving voicemail through the phone, affecting multiple agencies.

It is unlikely we can reduce the number of informatuion stores easily and the Exchange team has plans to expannd these further.... so.....

1. Is there either a way on the current version of unity to increase the limit from 250?

2. Are there any considerations in newer version to increase this limit?

3. Are there any known workarounds?

4. Will unticking some of the permissions applied to mail stores in permissions wizard and limiting this down to 250 be a feasible workaround?

5. Are there any recommendations that Cisco can make?

Any assistance is greatly appreciated.

Any assistance is greatly appreciated.

[Scott Hills · Accepted solution]

This would be fixed by CSCsu03848 -

More info can be found at the following link:

http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&bugId=CSCsu03848

Symptom:
Cisco Unity 5.0 and 7.0 support up to 250 Exchange mail  stores. This is the enhancement request to change this limitation from 250 to  over 500 or hopefully unlimited.

Conditions:
Cisco Unity  5.0 and 7.0.

Workaround:
Customers who need to change the  number of Microsoft Exchange mail stores that Cisco Unity supports can install  the following Engineering Specials (ESes):
-- Cisco Unity 5.0 ES 61 or  later
-- Cisco Unity 7.0 ES 25 or later

After the ES has been  installed, modify the registry key found here:

[HKLM\Software\Active  Voice\AvWm\1.00]

Registry Key Name: Max Stores
Registry Key Type:  DWORD
Registry Key Default Value: 250

Additional Information: 
After changing the number of mailstores to support, stop Cisco Unity and the  CuMdbStoreMonitor service and then re-start Cisco Unity. If Cisco Unity failover  is configured, make the registry change on both the primary and the secondary  servers because registry settings are not replicated.

[allcom]

Thanks Scott,

We tried the ES earlier today with some mixed results - but we are not so sure the issue isn't complicated by our exchange configuration so some more diagnostic works are in progress.

Interestingly enough we decided to back out the ES but were able to maintain the new Reg Key value.... we backed out due to "broken" browser behaviours but will take these up directly with the TAC...

I have marked this as answered for now as it did address the question I put even if there are some negative outcomes experience in our envirionement. It is likely the right answer for most

Thanks Again.

Andrew