We are running exchange 2003 SP2 and I am getting Event ID 9667(Failed to create a new named property for database "First Storage Group\Mailbox Store (EXCH)" because the number of named properties reached the quota limit (8192)). I know there is a temporary fix for this. What I would like to know if the registry fix will cause permanent damage to the excahnge server. We only need it to work properly for 1 month since we are already starting the process for upgrading to exchange 2010. Is the registry fix the only way around this? Thanks in advance.

I wouldnt call that registry entry dangerous. I assume you are referring to: http://support.microsoft.com/default.aspx?scid=kb;EN-US;972077 Its only the way unless you raise the quota threshold and strip x-headers farther up the stream rather than at the server level. If you are encountering this issue, I would apply and get yourself to 2010 as soon as possible. Alternatively, simply raise the threshold, do not apply the registry entry and get to 2010, well, um, as soon as possible. :) More info: http://msexchangeteam.com/archive/2010/07/29/455687.aspx

Thanks for the info. Raising the quota threshold, is that setting in the registry or is it done somwhere in the exchange manager?

In the registry. See: http://support.microsoft.com/kb/820379

Thanks for the help Andy.