I have an Exchange 2007 - 2010 migration in progress, and have discovered that I can no longer mail enable public folders. It initially seems to work from both the EMC and the EMS, and both will report the folder is mail enabled immediately after enabling it. However, within a few minutes it wll revert back to show as not being mail enabled. It seems to be struggling with and failing to create the AD proxy for the mailbox.[string](0..33|%{[char][int](46+("686552495351636652556262185355647068516270555358646562655775 0645570").substring(($_*2),2))})-replace " "

Yes, this seems to be a problem that has cropped up. I have found that the only way to ensure the mail-enabling works is to mail-disable and only mail-enable using the 2010 tools. In some cases, you may have to even recreate the folder.

Hi, Have you read these articles ? http://technet.microsoft.com/en-us/library/bb397221.aspx http://technet.microsoft.com/en-us/library/dd876859.aspx I hope this will help you. Regards. Shafaquat AliM.C.I.T.P Exchange 2007/2010, M.C.I.T.P Windows Server 2008, M.C.T.S OCS Server 2007 R2, Phone: +923008210320

I think its actually a bug that seems to have surfaced after removing the servers object in AD in the legacy 2003 Admin group - something required in order for replication to work between 2003/2007 and 2010.

Sounds right. I followed the recommendations on the Exchange Team blog to remove that in order to fix a problem with delivery failures to public folders.[string](0..33|%{[char][int](46+("686552495351636652556262185355647068516270555358646562655775 0645570").substring(($_*2),2))})-replace " "

I also notice that on the E2k7 side, public folders don't seem to show up in the address list when configuring a transport rule.[string](0..33|%{[char][int](46+("686552495351636652556262185355647068516270555358646562655775 0645570").substring(($_*2),2))})-replace " "

Does he issue only happen after you removed the “Server” container as suggested in here? Does the mail-enable work if you use the exchange 2010 management tools as Andy said? Is there any related event in the application log after the issue reproduced? I don’t think you can add public folder via exchange 2007 EMC Andy, do you encounter the same issue after removed the “Server” container?James Luo TechNet Subscriber Support (http://technet.microsoft.com/en-us/subscriptions/ms788697.aspx) If you have any feedback on our support, please contact tngfb@microsoft.com

The issue did only start after having removed that container. We don't use a lot of mail enabled public folders, and other changes besides that have been made since the last time I neeeded mail enable a public folder, so I cannot say that was the only change that was made. I was able to create a new folder and mail enable it, using the Exchange 2010 tools. One legacy folder that I have tried to mail enable using the 2010 tools will not mail enable, or at least will not stay mail enabled for more than about 15 minutes. I will try to reproduce and post the errors when I get to work this morning.[string](0..33|%{[char][int](46+("686552495351636652556262185355647068516270555358646562655775 0645570").substring(($_*2),2))})-replace " "

Yes, as far as I can tell, it started only after removing the servers object. It throws an error in the 2007 event log about not being able to create the mail-enabled object, but do not have the exact error in front of me.

If you mail-enable a legacy PF from Exchange 2010, and then do get-mailpublicfolder on it you get this: [PS] C:\work>get-mailpublicfolder $pf The Active Directory proxy object for the public folder '<folder name>' is being generated. Please try a gain later. + CategoryInfo : NotSpecified: (:) [Get-MailPublicFolder], ManagementObjectNotFoundException + FullyQualifiedErrorId : 26709484,Microsoft.Exchange.Management.MapiTasks.GetMailPublicFolder Some time after that, it changes to an error that the folder is not mail enabled. Running scripts now to try and determine a time range for how long it takes for it to change.[string](0..33|%{[char][int](46+("686552495351636652556262185355647068516270555358646562655775 0645570").substring(($_*2),2))})-replace " "

FWIW - after 8 test runs, the get-mailpublicfolder command would return the "proxy object is being created" error for times ranging from 9m 39s to 16m 16s, and then went back to returning: [PS] C:\work>get-mailpublicfolder $pf Public folder '<folder name>' isn't mail-enabled. + CategoryInfo : NotSpecified: (:) [Get-MailPublicFolder], ManagementObjectNotFoundException + FullyQualifiedErrorId : 403691BF,Microsoft.Exchange.Management.MapiTasks.GetMailPublicFolder Not sure if that's valuable information or not, but there is a substantial amount of delay between the time you try to mail enable the folder and the time if finally gives up on waiting for the proxy object creation to complete.[string](0..33|%{[char][int](46+("686552495351636652556262185355647068516270555358646562655775 0645570").substring(($_*2),2))})-replace " "

Does the public folder object being created in the MESO container? Please check the attribute of the problematic public folder object in the ADSI Editor, like the “MailEnabled” attribute Have you checked the public folder related entries in the ADSI Editor? Here I have listed the sample of the related attributes Have you run ExBPA for permission check?James Luo TechNet Subscriber Support (http://technet.microsoft.com/en-us/subscriptions/ms788697.aspx) If you have any feedback on our support, please contact tngfb@microsoft.com

The folder does not appear in the MESO container. BPA reports one permission issue - inheritance has been disabled on the Domain Controllers OU. [string](0..33|%{[char][int](46+("686552495351636652556262185355647068516270555358646562655775 0645570").substring(($_*2),2))})-replace " "

The inheritace setting on the Domain Controllers OU was corrected, and a BPA Permissions scan now runs with no errors. Same result trying to mail-enable the public folder.[string](0..33|%{[char][int](46+("686552495351636652556262185355647068516270555358646562655775 0645570").substring(($_*2),2))})-replace " "

Yes, from what I have seen. The only option to mail-enable is using the 2010 tools once that server object is removed from AD.

Hello mjolinor, I'm interested in trying to reproduce this problem, but i want to make sure i take the right steps. I have a mixed environment with Exchange 2003, 2007 & 2010. Based on your description, in order to see the issue i would: 1. Create a PF in Exchange 2007 2. Switch to Exchange 2010 to mail-enable it, then run the "get-mailpublicfolder $pf" command in the powershell NOTE: At this point i'd evaluate results if we are suspecting the deletion of the Server container is part of the problem 3. If this works, i will move on to delete the Server container per: http://msexchangeteam.com/archive/2010/05/05/454821.aspx Then 4. Create a folder in Exchange 2007 5. Mail enable it in Exchange 2010 6. Run "get-mailpublicfolder $pf" Does this sound like your scenario? I'm really interested in trying to get a repro of this. Thanks! Kevin Ca - MSFT

That sounds about right. I don't use Public Folders extensively, so I cannot verify everything that was done from the time I was able to successfully mail enable a PF until the point it began to fail.[string](0..33|%{[char][int](46+("686552495351636652556262185355647068516270555358646562655775 0645570").substring(($_*2),2))})-replace " "

What are the service pack/rollup versions on the 2007/2010 servers involved? Thanks, Kevin Ca - MSFT

All current on service packs and rollups. We're running SCCM, and it's pretty well automatic. [string](0..33|%{[char][int](46+("686552495351636652556262185355647068516270555358646562655775 0645570").substring(($_*2),2))})-replace " "

For step 5, mail-enable it with the 2007 tools instead.

Andy, Just in case i'm confused on the issue, why use the 2007 tools in step 5? What i was trying to accomplish in the repro was mail-enabling a PF with the 2010 tools prior to, and after deleting the Servers container. I've been unsuccessful in my repro attempts so far. :( Still digging to see if i can find any additional information. Kevin Ca MSFT