Migrate Exchange 2003 Public folders and OAB to Office365?

Hi guys,
I am trying to migrate exchange 2003 public folders to office 365. I have read various documentation however they were either out of date or half-solutions.
The company stored OAB's in each public folder as well, how do I go about migrating these lists into office 365? Will it just "work" if I migrate the public folders across?
Thanks,
Alex

Hi,
If you are migrating from inhouse 2003 to office 365, then the best options for you are-
1. Either you can go for the manaul process. You can create PST files and can upload them to mailboxes through office 365 account.
Kindly refer the below mentioned link for the same
http://blogs.technet.com/b/canitpro/archive/2013/05/31/step-by-step-migration-of-exchange-2003-server-to-office-365.aspx
2. Or you can go for any 3rd party tool using the same you can migrate your public folders to office 365. This is required when you need to avoid the risks associated and need to keep your environment up and running even while migration process. Respond
back for third party tool suggestions.

Similar Messages

Finalising the migration of Exchange 2003 public folders over to an Exchange 2010 environment

After migrating all the user mailboxes, I set up replicas of the Public Folders which I have been running for several weeks.
Once everything had been replicated, using System Manager on the Exchange 2003 server, I removed the source replica server from the list (aka the Exchange 2003 server).
Is this step sufficient to move the replicas over?
Under the First Storage Group -->Public Folder Store do I need to run the
Move All Replicas command? Will this generate a lot of traffic given that I have ran replication for a number of weeks?
I saw somewhere some Exchange 2010 a similar Powershell command .\MoveAllReplicas.psl as well.
I have updated the offline address book, carried out the Address List Conversion and Recipient Polices.
If everything is in order, I am going to run the uninstall on the 2003 server.

After verifying that all the public folders are been replicated, I carried out the following:-
On the Exchange 2003 server under System Mangager > First Storage Group, I issued the command Move All Replicas over the weekend.
When I came back in today I could see the contents of the Public Folders
are now empty.
However, the Public Folder Instances still appears to have content. Is this normal?
On the Exchange 2010 server I have since issued the MoveAllReplicas.ps1 script to see if this will make any difference.
In addition when browsing the Default Public Folders via EMC, if I attempt to Update Content on any of the Public Folders I get the following error:
Cannot start replication against public folder....
MapiExceptionNoReplicaAvailable: StartContentReplication failed.

Migrate Exchange 2010 public folders cross forests

Hi,
Due to some Exchange and Active Directory issues (with remnants of old Ex 2003 server), we are going to migrate Exchange 2010 Mailboxes and public folders to a new Exchange 2010 Sp3 server, which is created in a new AD forest.
One thing we still have to decide, which is how to migrate public folders.
Apparently there are 2 ways:
1. To export PF data to PST and then import using Outlook in destination Exchange server
2. To use interorg replication tool to replicate PFs cross forest in target Exchange Server.
I would really appreciate if someone suggests which one is best. We have around 100GB of PF data.
Also, should we migrate Public Folders first? We think that we should move Mailboxes first.
Thanks in anticipation.
Regards, David Johnson

Hi,
Yes, when we decide to migrate from one Exchange server to another server, we need to move mailbox first.
About migrating public folders, both of these two solutions are available, I think that the first one is simpler.
Here is a similar thread for your reference.
http://social.technet.microsoft.com/Forums/exchange/en-US/e3a23acd-efd2-4e51-bf4d-cb94b4b88a9f/exchange-2010-public-folder-cross-forest-replication-tool?forum=exchange2010
Hope this helps.
Best regards,
Belinda
Belinda Ma
TechNet Community Support

Removing Exchange 2003 Public Folders

I am in the process of removing public folders from the old 2003 environment after upgrading to Exchange 2010. The Exchange 2010 is set as a replica and everything seems to have transferred over. What are my steps from here? I have 5 Exchange
2003 boxes to remove. I have read a few guides and believe my last step is to use the script "MoveAllReplicas"? Is there anything special I have to do to remove the last 2003 PF database? Is there a "master copy" which
needs ported to 2010?
Thank you.

Hi Ian,
As a last step, after you confirmed that all the PF have been replicated to the Exchange 2010, you can move all replicas from Exchange 2003 to Exchange 2010. The "move all replicas" will actually remove the Exchange
2003 replicas.
Move the public folder replicas to another server:
To move all Exchange 2003 replicas to Exchange 2010, which will actually remove the Exchange 2003 replicas:
From the Exchange 2010 server:
.\MoveAllReplicas.ps1 -Server "Exchange 2003 Server" -NewServer "Exchange 2010 Server"
http://blogs.technet.com/b/agobbi/archive/2010/08/04/how-to-move-public-folder-from-exchange-2003-to-exchagne-2010.aspx
http://exchangeserverpro.com/migrate-public-folders-from-exchange-2003-to-exchange-server-2010/
When the public folder instances displays an empty list the operation has completed.
Associate mailbox databases with another public folder database
If any mailbox databases are associated with the public folder database that is to be removed, you must configure another public folder database as their default public folder database.
1. Identify all mailbox databases that use the public folder database that you want to remove as their default public folder database.
2. Use Exchange Management Console to select another public folder database as the default public folder database for the mailbox databases that you identified in Step 1.
3. Repeat Step 2 for all mailbox databases identified in Step 1.
Once moved you can, dismount the PF databases on Ex2003 and verify all are working from 2010.
Remove the PF database and delete the database files manually
1. Now you are ready to remove your Public folder database. To remove a public folder database click on your Public folder database and under Actions select "Remove":
2. You get a prompt to confirm your Action.
3. A warning appears, indicating that the database was removed and reminding you to manually remove the database file.
4. Browse to the folder specified in the Warning message and delete the .edb file from the folder.
Regards,
Satyajit
Please “Vote As Helpful”
if you find my contribution useful or “Mark As Answer” if it does answer your question. That will encourage me - and others - to take time out to help you.

Setup a simple sales funnel with exchange 2013 public folders and outlook 2010 -2013

BCM for Outlook is big and has too many choices. What we want is a combination of contacts and tasks within a public folder so we can see what others are doing. If possible I want
to make a connection between an contact and a task. The task should have some extra fields like branches responsible organization members status etc. Does anyone have a simple solution which is easy to implement in a small organization of 10 people?

Hello,
First of all thank you for your answer. The Outlook version I'm using is 14.0.7113.5005 and the Exchange versuin is CU3. As I'm testing it on XP client it is probably the issue in the PS. I'll try it with Win7 client probably tomorrow. I wonder if there
exists any kind of workaround for XP clients.
Thank you in advance,
Peter

Migrating from Exchange 2007 to Exchange 2013 Public Folders coexistence

Hi all, I'm migrating from Exchange 2007 SP3 to Exchange 2013 SP1.
I have an Exchange 2007 server (Client Access, Hub Transport and Mailbox Server) in Site A, mailboxes and Publics Folders
In another Site in Site B, I have already installed (Client Access and Mailbox Server) Exchange 2013 server.
I am migrating test users, the fact is that users who migrated to Exchange Server 2013 Public folders do not see.
How I can make the migrated users from viewing the Exchange 2007 Public Folders duration coexistence?
Is there a "how to" to migrate Public Folders from Exchange 2007 to Exchange 2013?
thank you very much
Microsoft Certified IT Professional Server Administrator

Hi,
In Exchange 2013, the Public Folder is changed to Public Folder mailbox instead of Public Folder in Exchange 2007 database.
Due to the changes in how public folders are stored, legacy Exchange mailboxes are unable to access the public folder hierarchy on Exchange 2013 servers. However, user mailboxes on Exchange 2013 servers or Exchange Online can connect to legacy
public folders. Exchange 2013 public folders and legacy public folders can’t exist in your Exchange organization simultaneously. This effectively means that
there’s no coexistence between versions.
For this reason, it’s recommended that prior to migrating your public folders, you should
first migrate your all legacy mailboxes to Exchange 2013. For more information about migrating public folder from previous versions, please refer to:
http://technet.microsoft.com/en-us/library/jj150486(v=exchg.150).aspx
(Please note the What do you need to know before you begin part in this link)
Regards,
Winnie Liang
TechNet Community Support

Exchange 2010 Public Folders Cannot Change Permissions Errors from Management Console and Powershell

This problem does not affect new public folders, only old ones that have probably been on Exchange 2000/2003 servers in the past. Migrations I believe did go smoothly but now have errors.
Error Reported is:
Microsoft Exchange Error
The following error(s) occurred while saving changes:
Add-PublicFolderClientPermission
Failed
Error:
Failed to modify the MAPI.NET table property of the object "000000001A447390AA6611CD9BC800AA002FC45A030064004E9CC2F8DD46B5E1E4578DE6D8030000000278E90000" on server "FQDN.Server.Name". See inner exception for more information.
MapiExceptionNonCanonicalACL: Unable to modify table. (hr=0x80004005, ec=2409)
Diagnostic context:
    Lid: 40487   EMSMDBMT.EcDoRpcExt2 called [length=218]
    Lid: 56871   EMSMDBMT.EcDoRpcExt2 returned [ec=0x0][length=356][latency=0]
    Lid: 23226   --- ROP Parse Start ---
    Lid: 27962   ROP: ropModifyACL [64]
    Lid: 17082   ROP Error: 0x969
    Lid: 27745
    Lid: 21921   StoreEc: 0x969
    Lid: 27962   ROP: ropExtendedError [250]
    Lid: 1494    ---- Remote Context Beg ----
    Lid: 26426   ROP: ropModifyACL [64]
    Lid: 22086
    Lid: 27128
    Lid: 27232   StoreEc: 0x8004010F
    Lid: 27128
    Lid: 27232   StoreEc: 0x8004010F
    Lid: 22086
    Lid: 21970   StoreEc: 0x8004010F PropTag: 0x3D210102
    Lid: 19149   Error: 0x0
    Lid: 24509   Error: 0x0
    Lid: 31229   Error: 0x0
    Lid: 21970   StoreEc: 0x8004010F PropTag: 0x668F0040
    Lid: 6671    StoreEc: 0x8004010F
    Lid: 24976
    Lid: 24952
    Lid: 25472
    Lid: 7972    StoreEc: 0x969
    Lid: 26532
    Lid: 4920    StoreEc: 0x969
    Lid: 5119    StoreEc: 0x969
    Lid: 5247    StoreEc: 0x969
    Lid: 17916   StoreEc: 0x969
    Lid: 4814    StoreEc: 0x969
    Lid: 1750    ---- Remote Context End ----
    Lid: 26849
    Lid: 21817   ROP Failure: 0x969
    Lid: 29150
    Lid: 20446   StoreEc: 0x969
OK
From ExFolders we get error "Exception: Object Reference not set to an instance of an object"
Any thought on how to fix permissions, people who already had permission in the past can see and access them OK and all objects, but we cannot change/update or remove permissons
We alos receive similar error from the powershell.

Hi,
Could
you please add a new public folder hierarchies with ADSIEdit as following setups.
For how to use ADSIEdit ,you can access:
http://technet.microsoft.com/en-us/library/cc773354(WS.10).aspx
1.Run ADSIEdit, right click Exchange Administrative Group under “Configuration \ services \ Microsoft
Exchange \ Organization name \ Administrative groups”.
2.Select New Object.
3.Select msExchPublicFolderTreeContainer for the class and click Next.
4.Enter the following for the value:
Folder Hierarchies, click Next.
5.Click Finish.
6.Create
Public Folder Tree Object.
7.Right click CN=Folder Hierarchies -> New Object.
8.Selected msExchPFTree for the class.
9.For the value we entered, "Public Folders" and clicked next.
10.Clicked on the "More Attributes" button, selected msExchPFTreeType .
11.Set the value
to 1.
Note: This is very important that this value is set
to a value of 1 as This tells Exchange that this is a MAPI Tree.
12.Click Ok and then finish.
13.We then went
to the properties of the newly created "Public Folders" Tree object in
ADSIEdit.
14.Copy the distinguished name value
to the clipboard and then click cancel.
15.Navigate
to the Storage group that contains the Public
Folder Store for this server and get properties of the server.
16.Locate the msExchOwningPFTree attribute and paste in the value that was copied
from the Public folders Distinguish name attribute.
17.Restart the Information Store Service.
18.Mounted and dismount the PF store.
19.Open Outlook with administrator,give full permission to default owner.
Hope it can help you!

Need help: Exchange 2003 Public Folder migration to Office365

Been working on this Office365 migration for awhile and down to public folders migration. Its been a VERY difficult experience dealing with India techs, but I am almost done. Here are the details: Migrating from Exchange 2003 to Office365. All users have been migrated. Now we are left with the public folders and shared "Master Calendar". I have exported the public folders to a PST file and I now need to import to Office365. Google results on this topic are not clear to me. Can somebody please walk me through the best way to finish my migration?
Hopefully we can finish the cutover before Friday so we can change the MX record before the weekend.
This topic first appeared in the Spiceworks Community

Hi,
Please check if the links below are helpful:
http://technet.microsoft.com/en-us/library/bb331970(v=EXCHG.141).aspx
http://exchangeserverpro.com/migrate-public-folders-from-exchange-2003-to-exchange-server-2010/
Since this issue is more related to the Exchange side, I'd recommend you post your question to the Exchange forum:
http://social.technet.microsoft.com/Forums/en-US/home?category=exchangeserver
The reason why we recommend posting appropriately is you will get the most qualified pool of respondents,
and other partners who read the forums regularly can either share their knowledge or learn from your interaction with us.
Thank you for your understanding.
Steve Fan
TechNet Community Support
It's recommended to download and install
Configuration Analyzer Tool (OffCAT), which is developed by Microsoft Support teams. Once the tool is installed, you can run it at any time to scan for hundreds of known issues in Office
programs.

Exchange 2003 to Exchange 2010 Public Folders

Hi Gurus, I’m in the process of moving public folders from Exch03 to Exch2010 and I have some clarifications before I proceed with this task. As I have understood the replication process between public folders working in a multi-master environment, I still
need some deep understanding. Okay, the task is to ensure that we don’t lose any PF when I remove the last Exch03 where there’s a lot of PF residing. From my understanding, these PFs found at Exch03 are only replicas from Exch2010. From testing I can verify
that the Outlook clients are looking at Exch2010. The way I tested this is by creating a test PF from Outlook and it did reflected on Exch2010 PF. Looking Exch03 for a couple of days, the test PF never reflected there so I'm just just assuming that there's
no replication happening between Exch2010 and Exch2010.
Please verify on this. Does it mean that Exch2010 is not replicating to Exch03?
If yes, if I remove the PFs from Exch2003 without moving the replicas first to Exch2010, like plainly removing them for decommission, will that delete/remove the PFs on Exch2010?
I have a feeling that it don’t because the PFs I’m creating/deleting at Exch03 are all replicas and I don't see any of the PFs that I deleted at Exch03 to also get deleted at Exch2010. More likely the PFs I'm creating at Exch2010 are not replication across
to Exch03 and therefore removing these PFs at Exch03 should not affect the PFs at Exch2010.
Please confirm on this before I proceed.
Note that I've already taken copy of these Exchange servers because these are all VMs.
Thanks....

Hi,
When you add Exchange 2010 to the replica list on Exchange 2003 server, it will replicate the Exchange 2003 Public Folder hierarchy and content to Exchange 2010, not from Exchange 2010 to Exchange 2003.
You can remove public folders on Exchange 2003 without affecting the public folders which have been replicated to Exchange 2010.
Before you decide to remove Exchange 2003 server, I recommend you put the Exchange 2003 server offline temporarily to check if Exchange 2010 works well.
Best regards,
Belinda
Belinda Ma
TechNet Community Support

Migration; Exchange 2003 SP2 to Exchange 2013 on new Domain and DC

I wasn't prepared for this task, and it was thrown at me to do... Eyes are bleeding from planning reading and planning, would LOVE any input from you guys. First time posting, here and have heard great things about these forums. The Company
I work for obtained a new client and a network that is in a cluster at the moment, so I'm having to dig through everything and restructure..
Scenario:
Old Domain/Server: (To be decommissioned)
Server 2003 Standard SP2 (Domain: cosco.com; NETBIOS name: coscoex)
Exchange 2003 SP2 (6.5.7638.1)
Server is a domain controller and exchange server.
Migrating to:
Server 2012 R2 Datacenter (New Domain ad.cosco.com; NETBIOS name: cosco)
VM #1: Server 2012 R2 Domain Controller at 2012 R2 Functionality
VM #2: Server 2012 R2 with Exchange 2013 Standard (Not Yet Installed) Joined to ad.cosco.com domain
VM #3: Server 2012 R2 with Exchange 2010 (Not Yet Installed) joined to ad.cosco.com domain
These are probably not ideal conditions, but I have to work with what I'm given.
Host server (2012 R2) is in work group mode. Hyper V Installed with a VM of Server 2012 R2 and as a DC at a functionality level of Server 2012 R2. I had intended starting at a lower functionality level and raising
it later, but.... ya I forgot to change it. If needed I can spool up a new DC with a lower functional level.
DNS, AD and group policy is all jacked up on the 2003 DC so that doesn't matter, All user accounts are going to be created under the new domain. The concern is migrating the mailboxes from Exchange 2003 on the old domain to
Exchange 2013 on the new domain. The client is going to provide CSV of the AD accounts that are still valid (a lot of accounts are no longer used or are from people that no longer with the organization.)
I had some ideas, but I'm not sure if they will work. This is something I have never done before (Senior Engineer Quit).
My thoughts:
- Establish a two way trust relationship between the two domains.
- Create two VM's, one with Exchange 2010 and one with Exchange 2013 (They have a 2010 licence that was not used).
- Create the users on the new domain
- Use the double hop method from Exchange 2003 > Exchange 2010 > Exchange 2013
- Link Exchange accounts to the correct user accounts on the new DC.
Can this be done cleanly? Am I going about this the correct way? Any feedback would be GREATLY appreciated.
Note: We are forced to use ad.cosco.com (Obviously not the actual domain name)

Hi,
Base on my experience, your idea is feasible.
However, before getting started, you should note that Exchange 2010 (with any service pack or update rollups) is not (yet) supported to install on Windows 2012 R2. More details refer to the following link:
http://technet.microsoft.com/library/ff728623(v=exchg.150).aspx
After all the preparations complete, you can refer to the following articles to migration exchange 2003 to 2010, then to 2013:
Exchange 2003 to 2010 Cross-Forest Migration Step by Step Guide
Exchange 2010/2007 to 2013 Migration and Co-existence Guide
Best regards,
Niko Cheng
TechNet Community Support

Migrate Exchange 2003-2013 and AD 2000-2012

We are in the process of migrating from Exchange 2003 to Exchange 2013. We currently have 4 Domain Controllers in Windows Server 2000. Two of them host also Exchange Server 2003 in an A-P mode configuration.
The double hop migration to 2010 was not possible as it requiered a minimal functional level of Windows Server 2003. This lead us to consider the double hop migration to 2007 first, even though it is not the recomended path. We have more
than 400 mailboxes with a size than often passes 1TB.
Is this scenario possible and may be the risks? Do you think using a third party tool to pass data to Exchange 2013 would be a safer solution?
Looking forward to your ideas.
Thank you,
Megi

Hi,
As far as I know, same with the Exchange server migration, we cannot also directly migrate AD 2000 to AD 2012. Thus, I recommend you directly upgrade to AD 2008 and then migrate Exchange 2003 to 2007 to 2013.
Here are more references you can refer to :
Exchange 2000/2003 to Exchange 2007 migration guidelines:
http://blogs.technet.com/b/mbaher/archive/2008/06/04/migrating-exchange-2000-2003-to-exchange-2007-guidelines.aspx
Step-by-Step Exchange 2007 to 2013 Migration:
http://blogs.technet.com/b/meamcs/archive/2013/07/25/part-1-step-by-step-exchange-2007-to-2013-migration.aspx
Thanks,
Angela Shi
TechNet Community Support

Exchange 2013 public folders are sending read receipts for items viewed in public folders

We have Exchange 2013 with public folders. These public folders are used for a large amount of shared contacts. When a user goes into the public folders and double clicks on a contact to view it, Exchange dispatches a read receipt to all users
that are configured as publishing editors to notify them that a certain contact was read. How do I disable this option?

hi again dear.. :)
"At first, I would like to say the
read Receipt is not sent out by the device, it is sent out by the Exchange server. This is how it works and what happens:
1.
E-mail with request for send
receipt is received on the Exchange server;
2.
E-mail is synchronized with Windows Mobile based device using Exchange
ActiveSync;
3.
When e-mail is
read on Windows Mobile based device the read status is synchronized back to the Exchange server;
4.
The Exchange server creates and sends out the
Read Receipt when receiving the Read status update from the device;
The above is how this is implemented and there is no functionality which allows preventing this from occurring on the Mobile device.
It seems that there is an alternative method to disable RR using transport rules. However, it will at the risk of the filtering out other messages
with the same subject.
Towards the third party mobile clients that support RR and DR, you might consider using Flexmail 4.11. It’s impossible to deactivate ActiveSync
RRs in Exchange server 2007/2010."
also
One way to stop read receipts being triggered through client side configuration on the mobile is to use the option "Don't Mark Read on server".
I have tested this successfully using this option in the TouchDown mail client on Android.
Not sure if the standard or other mail clients do support this option, TouchDown certainly does and it works.
The side effect obviously is, that the read status isn't synced back to Exchange anymore:"
hope now i r clear... one way or the other... you need to send a feed back or define a transport rule... but that again may create problem with the same subject :)
Regards Shah. MCITP, MCMA, MCTS No claims (try at your own risk)

Exchange 2013 Public Folders Array Dimensions Have Exceeded Supported Range

Hello,
I have another odd issue for public folders on Exchange 2013. I am working with an environment with a bit over 3000 Public Folders and we are having some issues where some users are not able to access the public folder. When I try to change the permissions
to those folders I get the error of:
"Array Dimensions Have Exceeded Supported Range"
The environment is a 2 Node DAG with all components installed on each server. The latest Roll Up has been in stalled on both servers as well.
Thanks in Advance
Joe

Update the thread if you find the resolution...
Cheers,
Gulab Prasad
Technology Consultant
Blog:
http://www.exchangeranger.com    Twitter:
  LinkedIn:
   Check out CodeTwo’s tools for Exchange admins
Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

Migrate Exchange 2003 to Office 365

Dear all,
We are going to migrate Exchange 2003 to Office 365. Because of the large number of mailboxes and mail databases, we decide to build hybrid to support coexistence during the migration period.
According to "Exchange Server Deployment Assistant" I found that we can build more Exchange 2010 for that requirement
http://technet.microsoft.com/en-us/exdeploy2013/Checklist?state=2419-W-BwAIAAAAQAAAAAEAiFIAAAA~
I just wonder that after deploying the Exchange 2010, can we move directly the mailboxes from Exchange 2003 to Office 365 or we need to move to Exchange 2010 first (as a "buffer") before moving to Office 365
Thanks a lot !!!

Hello,
The main goal of a staged migration is to migrate Exchange on-premises servers when:
1. You have more than 2000 mailboxes.
2. You plan to migrate over a few weeks and months rather than in a single batch.
3. You want to migrate to the Cloud completely and remove your on-premises Exchange deployment.
Hybrid scenarios are useful when you do not want to remove your on-premises deployment. In some cases there is no technical possibility, it is not cost-effective etc. to move a whole organization to Office 365. In these situations you may decide that moving
only some mailboxes to Office 365 is a good option and create a hybrid deployment.
You need to consider all pros and cons, especially when Exchange 2003 has gone out of support lifecycle and then choose the better option for your organization.
Hope it helps,
Adam
CodeTwo: Software solutions for Exchange and Office 365
If this post helps resolve your issue, please click the "Mark as Answer" or "Helpful" button at the top of this message. By marking a post as Answered, or Helpful you help others find the answer faster.

Exchange 2003 Public Calendars

I would like to view my Exchange 2003 Public Calendars on my iPad 2 - iOS5. Thanks

When the meeting is added to the exchange calendar, it wants to send the response. One way to solve it (and i think the easiest) is to configure the exchange account to send mail using a smart host. Configure your hosted email address as the default smtp
address - the server will send any mail it receives and the address on it will be your correct internet address.
Diane Poremsky [MVP - Outlook]
Outlook & Exchange Solutions Center
Outlook Tips
Subscribe to Exchange Messaging Outlook weekly newsletter

Migrate Exchange 2003 Public folders and OAB to Office365?

Similar Messages

Maybe you are looking for