Documentation on Public Folder Replication doesn't work
When I try to replicate the SCHEDULE+ FREE BUSY folder as the Technet documentation recommends, from Exchange 2007 to Exchange 2010, it errors with: Set-PublicFolder Failed Error: Modification of the '\NON_IPM_SUBTREE\SCHEDULE+ FREE BUSY' folder isn't allowed. Or do I even need to worry with this if I have no clients using anything below Outlook 2007? I am trying to finish up a close out of my Exchange 2007 servers, and Public Folders are the only obstacle I have to overcome.SnoBoy
December 14th, 2010 11:14am

Hi SnoBoy, Regarding your concern, I would link to collect the following information before we go further: 1. Are you in co-existence with Exchange 2007 and Exchange 2010? If so, please confirm the Exchange 2010’s Mailbox Database has associated with own Public Folder store. 2. Please run this command and paste the result in your next post. Get-PublicFolder "\non_ipm_subtree\schedule+ free busy" -recurse |fl 3. Please make sure the account you use have been delegated the following before you run the Set-PublicFolder cmdlet: Exchange Public Folder Administrator role, and local Administrators group for the target server 4. Please check the event log, if there is any other error, please paste in your next post. Here are some related posts, hope it helps: Exchange 2010 Migration - Busy/Free issues http://social.technet.microsoft.com/Forums/en/exchange2010/thread/07112ef0-c3ec-4819-b79c-c90b274832a7 Free/Busy Replication http://social.technet.microsoft.com/Forums/en/exchange2010/thread/2816b38a-2171-405d-aa60-a3c051fadd82 Thanks, EvanPlease remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
Free Windows Admin Tool Kit Click here and download it now
December 17th, 2010 4:38am

Figured out how to make this work. What I am finding is that the detail of *where* the commands need to be run from makes a *big* difference. In this instance, it *must* be run from the Exchange 2010 Public Folder tool, not the 2007 tool! SnoBoy
December 17th, 2010 9:01am

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

Other recent topics Other recent topics