Hi, The Environment: Exchange Enterprise 2K3 SP1 in Native Mode on W2K3 Enterprise SP1 Was migrated from a Exchange 5.5 environment. All remnants of 5.5 and NT4.0 are long gone. The problem: We would like to mail disable many public folders because we need to do a dump via LDAP or WMI of all the SMTP addresses to give to our external mail forwarder/scanner. Here is the problem: If I am in ESM and right click on a folder and them pick all tasks I am prompted for "mail enable" the public folder. This is what I expect. The folder has not been mail enabled. If I then right click on the folder and choose properties to look at the folder properties the Public Folder get's "Mail Enabled" though no effort of mine. When I then exit the properties window and go to "All Tasks" I am then prompted with the ability to "Mail Disable" the folder because it has been "Mail Enabled" There is now no way to "Mail Disable" the folder either though WMI or ESM if you execute the "Mail Disable" nothing happens. So the question is how do I stop this from happening? I want to programmatically "Mail disable" hundreds of folders. I have seen the post about deleting the object in "AD" but I want to understand why we are doing this? It seems that we are creating a future problem to make this one go away. Aren't you orphaning the public folder entries then? What are the repercussions of this? If you want to Mail Enable this folder in the future will "Mail Enable" repopulate the AD? Thanks in advance! Fred Lobmeyer
Still broken in Exchange Enterprise 2003 SP2.
