This is a weird one. I know that a native mode Exchange 2003 system should set all newly created public folders to mail disabled. However we have here a clustered Exchange 2003 system that does just that. I have checked across the web for any indication of a config that can possibly cause this, but have been unsuccessful so have come here to ask. Any public folders that are created by either the admin or by a normal user using outlook or the ESM are always automatically mail enabled. According to the ESM the Exchange org is set to Native mode. Does anyone have any clues to where i might be able to get Exchange to work properly and actually NOT mail enable a new folder. Any help is good as i've run out of ideas. Thanks

Has server rebooted anytime after changing the mode of Exchange organization?Amit Tank | MVP Exchange Server | MCITP: EMA | MCSA: M | http://ExchangeShare.WordPress.com

I would imagine so. Its been on Native mode for as long as i can remember so i would guess its been rebooted. Being a Windows system i doubt is been up for 2 years. Would being in a cluster have affected the migration from mixed to native mode? Is there any way to confirm if it truly is in native mode or it just thinks it is. Perhaps when the mode change was done some changes may not have been processed correctly??

Well, you can check an attribute "msExchMixedMode" of Exchange Organization container with ADSIEdit.msc Configuration Container -> Services -> Microsoft Exchange -> Exchange Organization It should be set to false to be in native mode.Amit Tank | MVP Exchange Server | MCITP: EMA | MCSA: M | http://ExchangeShare.WordPress.com

Hi, The msExchMixedMode attribute is set to False as expected. Is there a list of changes or commands that get processed during the mode change that we may be able to run to force the server to recheck/rerun its mode status. Or a value somewhere in adsiedit that we can change the default behaviour of created public folders? Thanks

Is it a pure exchange 2003 environment? Please describe the exchange topology Do you mean that the newly created public folder will have mail address attached by default and got all exchange tab in the EMS? Is there any related event in the application log if the issue occurs? Does the issue occur to the public folders on all public stores? Which option is available for newly created public folder under All Tasks via EMS, Mail Enable or Mail Disable? Have you seen KB 327779?

Hi, Yes pure Exchange 2003. Single exchange org with 2 exchange servers in a clustered setup giving us on single exchange virtual instance. Correct and newly created public folder will have an email address associated and also the exchange tabs enabled. In the context menu on the public folder it lists the option to mail disable only. I have just now created a new public folder structure and mounted the store. This works correctly and as expected new folders are created mail disabled. The only difference i can see between the new test PF tree and the production PF tree is that the Folder tree type on the production one is set to MAPI Clients, where as the new test store is set to General Purpose. Do you know what the difference in these folder types is? if so is it possible to change the type and would it be safe to do so? Thanks

OK Scratch the last bit. I have just had a little read online and now i understand the difference in tree types. This should not have an effect on mail enabling folders by default. And changing the default to non mapi would not be a great idea, if its even possible. So im still stuck then with a new folder structure that works perfectly, and the default public folder tree that automatically mail enables new folders. As the new one works fine im guessing its something particular with the default tree. Any other suggestions i can try? Thanks

Hi all, Just thought id let you know i have fixed this problem. It appears that exchange keeps all folders mail enabled after a exchange 5.5 > 2003 upgrade. This basically meant that all previously created folders were mail enabled including the "schema-root\default" folder. I have manually mail disabled this"schema-root\default" folder. This now stops all new folders being automatically email enabled within the 2003 environment. Thanks for all the help with varoius suggestions and troubleshooting.

J Glad you solved the issue, and thanks for sharing the resolution at here!