![]() ![]() Outlook basically becomes a conduit for Public Folder data between Forests. The setup would look something like this: The would reveal access to both Public Folder trees: Outlook would have two mail accounts on the same profile: If the company were going to Office 365, then we could copy the data from an Exchange 2007 or 2013 to Office 365 target. See my previous article on how to create isolated Public Folders for multi-company accessed Public Folders. The data would be placed in the company specific folder. Once mailboxes were moved from 2007 in Forest 2 to Exchange 2013 in Forest 1, a copy of the Public Folders would be made from Forest 2 (Exchange 2007) to Forest 1 (Exchange 2007). We can make these kinds of transfers with two different forest models: After a bit of research I found that Outlook could connect to both environments and copy the data across…. ![]() There are third-party tools to do this, but there was no budget to perform the task. We were tasked with importing Public Folders from one company to another from a different Forest entirely. However, what is often overlooked is moving Public Folders. Mailbox moves are relatively easy with PowerShell scripts (Prepare-MoveRequest) and cmdlets (New-MoveRequest). Cross forest migrations (Exchange 2013 or Office 365) can be tedious to plan, execute and support. Recently a client of mine wanted to consolidate their Public Folder infrastructure, or at least reorganize the existing 2007 version before upgrading to Exchange 2013 with the possibility of Office 365. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |