Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 245
  • Last Modified:

Named Properties in Exchange 2003

So we have 2 Exchange environments.  We are moving over to Exchange 2007 and should be completed by early next year.  We just had some errors in the event log that state our named properties have reached the quota limit on one of our 2003 mailbox clusters.  I have enclosed the screenshot.  There are quite a few things trying to create a named property like BES and our Enterprise Vault system.  Here is the KB article on this below.  My question is I would rather not make changes unless it is absolutley imperative.  I can not find out if this is harming the environment or not and I would like to know if I should put in a change control to make the changes or just let it ride out.  Any opinons would be appreciated as it is either this or call MS on it.

http://support.microsoft.com/kb/820379

exerror.jpg
0
JeffWilliams
Asked:
JeffWilliams
  • 2
1 Solution
 
eldiosCommented:
This solution is probably your best bet.  Microsoft supported and it's a simple registry entry.  Of course always make sure you have a backup, but there's no reason to think that this would cause any problems on your information stores.  I would go ahead with the fix.
0
 
JeffWilliamsAuthor Commented:
Thanks I will do the CC today.
0
 
JeffWilliamsAuthor Commented:
Was not really a tech question so the score should not be really high.
0

Featured Post

VIDEO: THE CONCERTO CLOUD FOR HEALTHCARE

Modern healthcare requires a modern cloud. View this brief video to understand how the Concerto Cloud for Healthcare can help your organization.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now