James, Yes, it helps a lot! We don't have that many PB's, so I'm going to disable/enable per your suggestion.
This is one of those "unknowns" that was bugging me. Now I know why it's happening! Thank you very much!!! Larry From: Knoch, James W [mailto:james.kn...@intergraph.com] Sent: Monday, May 23, 2011 5:24 PM To: MS-Exchange Admin Issues Subject: RE: Public Folders losing email address Yes, I figured out one way to fix it on my support call with Microsoft when we first started migrating to Exchange 2010. For us, the issue stemmed from a particular MAPI attribute that was not stamped in Exchange 5.5. For us it was the MAPI attribute: PR_PF_PROXY_REQUIRED First, get PFDAVAdmin and run it against your Exchange 2003 or 2007 server. Or you can also use ExFolders against your Exchange 2007. Find one of the problem public folders and look at the Property Editor for that particular folder. If you look for the aforementioned MAPI attribute, it will probably not be defined (blank). The default for this attribute is True when mail-enabled from Exchange 2003+. You can also double-check PR_PF_PROXY is assigned some value while you're there as well. If it is just a few you can mail disable and then mail-enable those public folders from Exchange 2007 (probably the best way). If you had a lot like we did, then you can use PFDAVAdmin or ExFolders, to set this attribute to True. Please note that if you do use PFDAVAdmin or ExFolders, sometimes it will create a new AD directory object as representative when it gets stamped with the e-mail address policy that applies to it (doesn't always happen!). If it does happen, it will more than likely say that the e-mail address is already in use when you then go to assign the old address. So unless you can find that original AD object and delete it (in Exchange System Objects in AD) you won't be able to reuse the e-mail address. For us, however, the e-mail is still routed to the folder WITHOUT bouncing (at least while there is an Exchange 2003 object still so far). That is why I recommended just disabling/re-enabling, unless you have to deal with several thousand public folders like we did. I found a loose reference to this issue in regards to Exchange 2007 when I originally came across this problem (at the bottom of the page): http://blogs.msdn.com/b/webdav_101/archive/2009/08/14/howto-mail-enable-mail-disable-and-view-mail-settings-for-a-public-folder-with-cdoex-and-cdoexm.aspx If the public folder was migrated from Exchange 5.5 and will not mail enable or disable, then the pf_proxy_required may not be set. You may receive a c1038a21 error message when you try to use Exchange System Manager to look at the properties of a public folder http://support.microsoft.com/?id=328740 Microsoft Exchange Server Public Folder DAV-based Administration Tool http://www.microsoft.com/downloads/details.aspx?FamilyId=635BE792-D8AD-49E3-ADA4-E2422C0AB424&displaylang=en PFDAVADMIN->connect to Server->Select Root public Folders->Click Tools->Custom Bulk Operations 2- Type (DS:proxyaddresses=*) in the filter box 3- Click on ADD->Select other folder properties->ok 4- under the property box select PR_PF_PROXY_REQUIRED-> under value type 1 and click on add-> click ok and again click ok Hope this helps.. James From: Brown, Larry [mailto:lc.br...@dplinc.com] Sent: Monday, May 23, 2011 3:42 PM To: MS-Exchange Admin Issues Cc: McCready, Rob Subject: Public Folders losing email address We are testing the procedure for shutting down Exchange 2003 in an Exchange 2007 environment. We had to keep E03 for a while due to a software connector pointing to the Public Folders that wasn't compatible with E07 for a long time. That has been resolved, so we're ready to move the PF's to E07 and be done with the old boat anchor server that E03 is on. But during testing we noticed that old Public folders that were originally created on the Exchange 5.5 server, then moved to Exchange 2003, do not have their email attributes when moved to Exchange 2007 servers as seen in the Public Folder Management Console. Trying to send an email to the PF fails. In production, the Public Folder Management Console also doesn't see the email attributes, but the PF's are still receiving email because they are on E03 and only replicated to the Hub Transports. This is not the end of the world, as there aren't that many old PF's involved. After the move it would only take us an hour or less to generate new email attributes. Just wanted to know if anyone has run in to this before? Larry C. Brown LAN/WAN CS Support Dayton Power & Light (937)-331-4922 --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com<mailto:listmana...@lyris.sunbeltsoftware.com> with the body: unsubscribe exchangelist --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com<mailto:listmana...@lyris.sunbeltsoftware.com> with the body: unsubscribe exchangelist --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist
