RemotePublicFolder set to deleted object

[Stefano Colombo]

We are finalizing the exchange migration from 2010 to 2016.

After following the steps in https://learn.microsoft.com/en-us/exchange/collaboration/public-folders/batch-migration-from-previou... we started deleting the proxy mailbox on exchange 2010 and its mailbox DB to be able to remove the exchange 2010 server.

However checking the organization we found that the  RemotePublicFolderMailboxes :  still points to the "deleted" object

PS] C:\Windows\system32>Get-OrganizationConfig | fl *publicfolder*

DefaultPublicFolderAgeLimit :
DefaultPublicFolderIssueWarningQuota : Unlimited
DefaultPublicFolderProhibitPostQuota : Unlimited
DefaultPublicFolderMaxItemSize : Unlimited
DefaultPublicFolderDeletedItemRetention : 30.00:00:00
DefaultPublicFolderMovedItemRetention : 7.00:00:00
PublicFoldersLockedForMigration : True
PublicFolderMigrationComplete : True
PublicFolderMailboxesLockedForNewConnections : False
PublicFolderMailboxesMigrationComplete : False
PublicFolderShowClientControl : False
PublicFoldersEnabled : Local
RootPublicFolderMailbox : 58b5e8ab-9d2e-4ce5-9ca1-e40faca1a5d1
RemotePublicFolderMailboxes : {xxxx.xxx/Deleted Objects/PF2016PROXY
DEL:be1f7e08-9f60-4569-b8be-1efb7e487eee}

and the event 2937 is logged.
Log Name: Application
Source: MSExchange ADAccess
Date: 12/1/2022 4:05:48 PM
Event ID: 2937
Task Category: Validation
Level: Warning
Keywords: Classic
User: N/A
Computer: xxxx.xxxx.xxx
Description:
Process MSExchangeFrontendTransport.exe (PID=12812). Object [CN=xxxxxx,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=xxxxx,DC=xx]. Property [RemotePublicFolderMailboxes] is set to value [xxxxx.xx/Deleted Objects/PF2016PROXY
DEL:be1f7e08-9f60-4569-b8be-1efb7e487eee], it is pointing to the Deleted Objects container in Active Directory. This property should be fixed as soon as possible.

How this should be fixed ? Which impact can it have ?

[#2]

@Stefano Colombo 

I know this is very old, but we had the same issue and I discovered the solution here and I wanted others to maybe be able to find this solution a little easier: https://www.blackmanticore.com/deb16162d44ad508ca715642595deebd 

With the removal of the public folders database, not all objects referencing the database have been adjusted. You can manually fix the issue by clearing the reference to the deleted public folders database, using ADSI Edit.

1.) As a domain admin, open ADSI Edit (adsiedit.msc).

2.) Connect to the Configuration well-known naming context of the domain in which Exchange operates.

3.) Navigate to the object mentioned in the warning event (in this case: CN=Contoso,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=contoso,DC=com).

4.) Right-click the object itself (not any of the subordinates) and click Properties.

5.) Browse the attributes of the object. One of the attributes should mention the deleted public folder database and clear the value.

If more than one public folder database was used, clear all of them, unless you still have a public folder database in use, in which case you should leave the references to the existing databases as is.

Note that the Property mentioned in the event does not always match the name of the attribute in AD. In our example, the property RemotePublicFolderMailboxes (retrievable through EMS: Get-OrganizationConfig | Select RemotePublicFolderMailboxes) is in fact the attribute named pFContacts).

6. ) After clearing the incorrect values, the event should no longer be triggered. Note that multiple references may exist. Clear the invalid references of all the objects to get rid of the events.

As the change is in AD, clearing the values should only be done on one DC. The change will be replicated to all DCs and all Exchange servers will pick this up.