Multi-Domain Forest & Public Folder Connectivity

Hello. My organisation has one forest with two domains.  The two domains share a common namespace, such as NAME.COM for example.

About one year ago the one domain, which uses public folders, migrated from Exchange 2007 to Exchange 2013.  The other domain, which does not use public folders, is now in the process of migrating from Exchange 2007 to Exchange 2013.  When a user in that domain, whose mailbox has been moved to Exchange 2013, checks their connections status, Outlook 2013 reports that it is connected to a server in the other domain which does use public folders.  How can Outlook users in the one domain that does not use public folders be prevented from trying to connect to an Exchange server in the other domain that does use public folders?

February 4th, 2015 9:56am

The reason why the users in the non PF domain were unable to access it before is because when they were on 2007, they are unable to access "modern" folders hosted on 2013. Legacy mailboxes cannot access modern folders, but now since you moved them to 2013 access has been restored.

I'm not sure if you can disable the referrals, there is always the option of pushing out a reg hack to disable public folders for your other domain users using gpo\script.

How to stop Outlook from using Public Folders.
http://blogs.technet.com/b/johnmak/archive/2012/03/26/how-to-stop-outlook-from-using-public-folders.aspx

Free Windows Admin Tool Kit Click here and download it now
February 4th, 2015 10:14am

Hi James.  Thank you very much for the prompt response.

Unfortunately, the registry hack you identified did not resolve the problem.  If you have any other suggestions, please pass them onto me.  Thanks!!

February 4th, 2015 11:30am

Sure, the registry hack did not resolve the problem or you don't like that solution? I've used it before successfully.
Free Windows Admin Tool Kit Click here and download it now
February 4th, 2015 11:50am

Hi James,

I'm an admin of one of the domains in the question. I would gladly use the registry fix but I'm not having any success with it. I tried it with several test accounts but each time I open Outlook, the connection status still shows a public folder  connection to a server in the other domain.

We run Outlook 2013 and are upgrading to Exchange 2013 CU7.

Thank you for you input.

Tom

February 4th, 2015 12:58pm

Did you reboot after the reg change? I'm having no problem with it, 
Free Windows Admin Tool Kit Click here and download it now
February 4th, 2015 2:31pm

Yes, I just tried again after a reboot and the connection status still shows a connection to "Exchange Public Folders" on a server in the other domain/site.

Thanks again.

February 4th, 2015 4:34pm

Are you sure you're doing this in the hkey current user hive? I just tested on Outlook 2013 with Exchange 2010, no reboot required when toggling the haspublicfolders dword from 1 to 0 or vice versa just a restart of outlook. 

From research it appears to still work for Exchange 2013, although some users seem to be complaining about not working on some builds of Outlook. Let me know what build number of Outlook you are using, I'm currently running 2013 15.0.4667.1000. To find the build number, go to the file, Office Account, About Outlook.

Free Windows Admin Tool Kit Click here and download it now
February 4th, 2015 5:24pm

Yes, I added it to HKCU, checked it several times and tried 0 and 1 with no change. My Outlook version is 15.0.4535.1006. On the original post I saw it worked for some and not others.
February 4th, 2015 6:29pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics