I just read an article about configuring legacy public folder access for Exchange 2013 users to access Exchange 2007 Public Folders
     http://www.exchange2013.es/on-premises-legacy-public-folder-coexistence-for-exchange-2013-cumulative-update-7-and-beyond/

I currently have the "PublicFolderDatabase" field set on my 2013 databases, but going to change one of them today, I get the message that this field has been deprecated.

So, it looks like I need to make changes using set-organizationconfig to configure user access to legacy publicfolders.
Looking at settings that should be made, I am looking at configuring using.....
     - PublicFoldersEnabled Local
My legacy 2007 and 2013 Exchagne systems are in the same organization.
     - RemotePublicFolderMailboxes pfmb01,pfmb02,pfmb03
But wait, the write up on technet says that the remote mailboxes are only used if the public folder is deployed in a remote forest!!!!

If thess fields refer to remote forests, and the publicfolderdatabase field is being deprecated, how am i supposed to refer my 2013 users to legacy, same org, public folders???

Tom

Does this help you?

http://blogs.technet.com/b/exchange/archive/2014/11/07/on-premises-legacy-public-folder-coexistence-for-exchange-2013-cumulative-update-7-and-beyond.aspx

heh, if you look, your link is the same as mine.

They tell us to...

• From a CU5 or later Exchange 2013 Server: Use the Set-OrganizationConfig cmdlet to assign the legacy public folder discovery mailbox(es) to the RemotePublicFolderMailboxes value of the organization. 
• From a CU5 or later Exchange 2013 Server: Use the Set-OrganizationConfig cmdlet to set the PublicFoldersEnabled attribute of your Exchange organization from Local to Remote.

However, reading the TechNet page on the set-organizationconfig command, the parameter for PublicFoldersEnabled, if you set it to REMOTE, you are telling the system that the public folders are in a remote forest. My public folders however, are in the same organization.

Will telling Exch 2013 that the folders are remote, will that confuse my system? Or has the function of the command and intent of the parameter changed with CU7 ?

Tom

It looks like you have a valid point.  I have submitted feedback via a couple of channels.  Please consider adding your own feedback at the bottom of the cmdlets documentation page.

in the meantime, while the set-database command has the -publicfolderdatabase parameter, CU7 give the error that this parameter is deprecated. ( parameter may be a little mistyped here, its something like that. )

Is the parameter meaningless now? or just on its way out in later releases?

Tom

That's what the documentation says, and it's probably related to the Set-OrganizationConfig settings.

Hi,

If the public folder remain in Exchange 2007, please set PublicFolderEnabled parameter to remote in Exchange 2013 server. Once, you migrate public folder to Exchange 2013, you have to change it to local. Otherwise, your Exchange Organization still thinks it should direct Public Folder traffic to a legacy server.

It also de described when migrating public folders to Exchange 2013 from previous versions, for your reference:
https://technet.microsoft.com/en-us/library/jj150486(v=exchg.150).aspx

I have received confirmation that the Set-OrganizationConfig documentation will be updated to reflect that "Remote" also means intra-organization cross-version application as described in the blog post.  Thanks for bringing this to our attention, you have helped make things better.

Thank you Ed for working on this with me.

I appreciate you reference to "Migrating PF to Exchange 2013", but we are going to try to avoid adding our conglomeration of PF to 2013. We will be migrating ours to 2010 so we can get off of 2007 though.

Thasnk1 again!!!

Tom

You're welcome.  Happy to have helped.