I had to restore our public folders database but now in ESM when using the public folders management console I see no entries for default public folders. I do see public folders under outlook and when using get-publicfolderstatistics. I checked CN=Folder hierarchies CN=public folder msExchOwningPFTreeBL under ADSI and it looks to be pointing to the correct location. What would make public folders visible in outlook but not the public folder management console in exchange 2007?

I had to restore our public folders database but now in ESM when using the public folders management console I see no entries for default public folders. I do see public folders under outlook and when using get-publicfolderstatistics. I checked CN=Folder hierarchies CN=public folder msExchOwningPFTreeBL under ADSI and it looks to be pointing to the correct location. What would make public folders visible in outlook but not the public folder management console in exchange 2007? Reply Quote

Hi, Have you moved PF databse recently from legacy version to Exchange 2007 > One of the causes for this error is that Administrative Group that keep the Public Folders container was deleted without the Public Folders container first being moved to a new Administrative Group. PLease go detail in below thread and refer ames comment to troubleshot this. http://social.technet.microsoft.com/Forums/en/exchangesvradmin/thread/ba367733-3f5c-46d5-9a99-a0a5416a6ae7 Anil

It looks like the DN is different than msExchOwningPFTreeBL. Should I make both entries the same?

You can't modify the msExchOwningPFTreeBL since it's a blacklink AD attribute owned by the system. Instead you update the forward link attribute which is the msExchOwningPFTree on the public folder database. In adsieidt, expand all the way to admin groups, org name, servers, servername, information store, storage group of your PF, database. On the right pane. Right click properties and look for msExchOwningPFTree. This is the forward link attribute that updates the backlink attribute of msExchOwningPFTreeBL. I would also make sure you don't have any orphaned directory objects for public folder stores in adsiedit that may also have the msExchOwningPFTree configured.James Chong MCITP | EA | EMA; MCSE | M+, S+ Security+, Project+, ITIL msexchangetips.blogspot.com

distinguishedName properties on the public folders database are updating msExchOwningPFTreeBL on public folders in folder hierarches.

distinguishedName properties on the public folders database are updating msExchOwningPFTreeBL on public folders in folder hierarches. Folder Hiarchie > Public Folder distinguishedName CN=Public Folder,CN=Folder Hierarchies,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=COMPANY,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=lmc,DC=local msExchOwningPFTreeBL CN=Public Folder Database,CN=Public Folder,CN=InformationStore,CN=EMAIL,CN=Servers,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=Lattimore Materials,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=lmc,DC=local --------- Public folder database distinguishedName CN=Public Folder Database,CN=Public Folder,CN=InformationStore,CN=EMAIL,CN=Servers,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=COMPANY,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=lmc,DC=local msExchOwningPFTree CN=Public Folder,CN=Folder Hierarchies,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=COMPANY,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=lmc,DC=local It's very strange that these settings would be flip flopped but still work out OK.

What do you see in the Exchange Management Shell when you enter: Get-PublicFolder -Identity \ -Recurse ? You've posted in the Migration forum. Does that mean you have more Exchange servers than an Exchange 2007 server?Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

This is my output of the command Get-PublicFolder -Identity \ -Recurse Name Parent Path ---- ----------- IPM_SUBTREE This is the only exchange server we have.

You have no public folders in your hierarchy. If you want to see the system folders, issue this command: Get-PublicFolder -Identity \NON_IPM_SUBTREE -Recurse Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

It's fixed now. I was very close to having this corrected. I don't know if it was restarting the exchange services or just bouncing the server that fixed this issue but I will list my steps to help anyone else having this problem. 1. Use ADSI edit to add/edit entry for Public folders under CN=Folder Hierarchies. Make sure to add correct field values for public folders. Check with public folder database for settings. These two places rely on one another so insure the data is correct. 2. Ran command net stop MSExchangeIS && net start MSExchangeIS. Did not try to access public folders as I was applying patches during this phase. 3. Rebooted server. Hope this help. Good luck!

It's fixed now. I was very close to having this corrected. I don't know if it was restarting the exchange services or just bouncing the server that fixed this issue but I will list my steps to help anyone else having this problem. 1. Use ADSI edit to add/edit entry for Public folders under CN=Folder Hierarchies. Make sure to add correct field values for public folders. Check with public folder database for settings. These two places rely on one another so insure the data is correct. 2. Ran command net stop MSExchangeIS && net start MSExchangeIS. Did not try to access public folders as I was applying patches during this phase.