Public Folders from 2010 on-prem to Office 365 PF database?

Where is the guidance on moving 2010 on-prem public folders to an O365 Public Folder Mailbox. The only thing I have found so far is
this, which is just to configure cloud users to connect to on-prem Public Folder databses. I'm looking for cutover/migration steps to move to a O365 PF database, not Sharepoint Online.
Are people typically using 3rd parties for this, or is their Microsoft Guidance?
http://jaworskiblog.com

Hi Scott,
Did you checked already this:
Use these scripts to migrate public folders from Exchange 2010 or 2007 to Exchange 2013.
In order to migrate Exchange 2010 or 2007 Public Folders to Exchange 2013 on O365, we need to analyze the existing
Public Folder hierarchy for size to figure out the number of Public Folder mailboxes that are required on O365 and the distribution of folders across mailboxes. http://blogs.technet.com/b/catastrophic_failure_joannav/archive/2013/06/12/microsoft-exchange-2013-public-folders-migration-scripts.aspx
Regards, Catastrophic Failure "JV"

Similar Messages

Manually Move Public Folders from Exchange 2010 to 2013

Hi all,
I have a issue to finishing my migration from Exchange 2010 to Exchange 2013, I have been trying to migrate my Public folders but always after a couple hours, the migration state is failed.
The final error is the following:
FailureCode                      : -2146233088
FailureType                      : SourceMailboxAlreadyBeingMovedPermanentException
FailureSide                      :
Message                          : Error: Couldn't switch the mailbox into Sync Source mode.
                                   This could be because of one of the following reasons:
                                     Another administrator is currently moving
the mailbox.
                                     The mailbox is locked.
                                     The Microsoft Exchange Mailbox Replication
service (MRS) doesn't have the correct
                                   permissions.
                                     Network errors are preventing MRS from cleanly
closing its session with the
                                   Mailbox server. If this is the case, MRS may continue
to encounter this error for
                                   up to 2 hours - this duration is controlled by the TCP
KeepAlive settings on the
                                   Mailbox server.
                                   Wait for the mailbox to be released before attempting
to move this mailbox again.
So, after seeing this I started to monitoring all process and I realized that after creating hierarchy the process start to fail and keep in StalledDueMailboxlock status, and the error is:
FailureCode                      :
FailureType                      :
FailureSide                      :
Message                          : Informational: The request has been temporarily postponed because the mailbox is
                                   locked. The Microsoft Exchange Mailbox Replication service
will attempt to continue
                                   processing the request after 2/14/2015 12:38:20 PM.
Finally, digging more into reports of migration I found this:
MapiExceptionNetworkError: MapiExceptionNetworkError: Unable to open entry ID. (hr=0x80040115, ec=6)_x000A_Diagnostic context:_x000A_ Lid: 40487 EMSMDBMT.EcDoRpcExt2 called [length=73]_x000A_ Lid: 44583 EMSMDBMT.EcDoRpcExt2
exception [rpc_status=0x6][latency=0]_x000A_ Lid: 62184 _x000A_ Lid: 16280 dwParam: 0x0 Msg: EEInfo: ComputerName: n/a_x000A_ Lid: 8600 dwParam: 0x0 Msg: EEInfo: ProcessID: 51452_x000A_ Lid: 12696 dwParam: 0x0 Msg: EEInfo: Generation Time: 0415-02-14T14:25:40.9210000Z_x000A_
Lid: 10648 dwParam: 0x0 Msg: EEInfo: Generating component: 2_x000A_ Lid: 14744 dwParam: 0x0 Msg: EEInfo: Status: 6_x000A_ Lid: 9624 dwParam: 0x0 Msg: EEInfo: Detection location: 1741_x000A_ Lid: 13720 dwParam: 0x0 Msg: EEInfo: Flags: 0_x000A_ Lid: 11672 dwParam:
0x0 Msg: EEInfo: NumberOfParameters: 0_x000A_ Lid: 23260 Win32Error: 0x6_x000A_ Lid: 61553 StoreEc: 0x80040115_x000A_ Lid: 52176 ClientVersion: 15.0.1044.25_x000A_ Lid: 50032 ServerVersion: 14.3.181.6_x000A_ Lid: 50128 _x000A_ Lid: 50288 _x000A_ Lid: 23354
StoreEc: 0x80040115_x000A_ Lid: 25913 _x000A_ Lid: 21817 ROP Failure: 0x80040115_x000A_ Lid: 22894 _x000A_ Lid: 24942 StoreEc: 0x80040115
So, would like to know if exist any procedure to migrate/move my Public Folders from Exchange 2010 to 2013 manually, something like Export/Import.
Regards!

What script and process you are running to migrate the Public Folders?
And what do you mean by Manually?
Cheers,
Gulab Prasad
Technology Consultant
Blog:
http://www.exchangeranger.comTwitter:
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.

How to migrate public folders from legacy (exchange 2003 ) to exchange 2010

How to migrate public folders from legacy (exchange 2003 ) to exchange 2010 . Please suggest ?
Aditya Mediratta

Hi Aditya,
please find the answer in
http://blogs.technet.com/b/agobbi/archive/2010/08/04/how-to-move-public-folder-from-exchange-2003-to-exchagne-2010.aspx
Please ensure you have a working mailflow from Exchange 2003 to 2010, vice versa, before you begin.
Basically it's the same procedure as adding some PF Database in E2K3; just
run .\AddReplicaToPFRecursive.ps1 -server "Exchange 2010 Server" -TopPublicFolder "\" -ServerToAdd "Exchange 2010 Server"
Wait until some initial data started to replicate; after that run
Update-PublicFolderHierarchy -Server "Exchange 2010 Server"
After replication has finished you can do a
.\MoveAllReplicas.ps1 -Server "Exchange 2003 Server" -NewServer "Exchange 2010 Server"
Please let me know if it worked.
Kind regards,
Martin

Import Public Folders from pst file

I am trying to import our Exchange 2007 public folders into our managed Exchange 365 account at Microsoft. I created the Primary Hierarchy public folder name, PublicFolders, but don't understand how to use pst import to get the public folders
under this main folder. All I have accomplished thus far is to use Outlook to import the public folders into the administrator Outlook account on the managed Microsoft O365 server. They import into a folder called IPM_SUBTREE in the administrator
mailbox on the server. Do I somehow have to move the public folders from there to the actual public folder location? I really need and appreciate any help.

Hi,
For this issue, I recommend you post to Office 365 forum which is staffed by more experts, you might get a better help there. Thanks for understanding.
http://community.office365.com/en-us/forums/default.aspx
Best regards,
Belinda
Belinda Ma
TechNet Community Support

Move mailboxes and public folders from exchange 2007 to Exchange 2013

1. How do i move mailboxes from exchange 2007 to exchange 2013. I have more than 1000 mailboxes.
What is the correct way to migrate. do i need to move a single mailbox. During migration do the mailboxes get corrupted
2. I want to move public folders from Exchange 2007 to Exchange 2013.
I ran powershell commands and got these results please do guide me how to move to exchange 2013.and what are the shell commands
Get-publicfolder
Name Parent Path
IPM_SUBTREE
Get-publicfolder | select AdminDisplayName,FolderPath
AdminDisplayName FolderPath
Get-PublicFolderStatistics | select AdminDisplayName,FolderPath
AdminDisplayName FolderPath
exchangeV1 schema-root\microsoft\exchangeV1
Internet Newsgroups Internet Newsgroups
Get-PublicFolder -Recurse | fl name,replicas > c:\publicfolder.txt
Name : IPM_SUBTREE
Replicas : {}
Name : Internet Newsgroups
Replicas : {MAIL\Public Folder Storage\Public Folder Database}

I have started moving mailboxes , i have tried moving few individual mailboxes to see how things go
MAIL is my exchange 2007 and MAIL1 is my exchange 2013, please do refer the below result
PS] C:\Windows\system32>Get-MailboxDatabase -server mail
Name                           Server          Recovery
ReplicationType
Mailbox Database               MAIL            False           None
[PS] C:\Windows\system32>Get-MailboxDatabase -server mail1
Name                           Server          Recovery
ReplicationType
Mailbox Database 1460777952    MAIL1           False           None
[PS] C:\Windows\system32>New-MoveRequest -Identity '[email protected]' -TargetDatabase "Mailbox Database 1460777952"
DisplayName               StatusDetail              TotalMailboxSize
TotalArchiveSize         PercentComplete
[email protected]          Queued                    363.6 MB (381,217,115 ...
0

Public folders from exchange 2007 to exchange 2013

HI I am new to exchange, i am planning to do the migration of Exchange 2007SP3 UR10 to Exchange 2013 CU7, I want to move public folders from exchange 2007 to exchange 2013. wht is the procedure to move and wht are the commands to know how many public folders
i have.I just want to be aware before the installation so that later i can avoid issues.please do guide me

Hi Quiett,
please find how to move public folders on ttp://www.msexchange.org/articles-tutorials/exchange-server-2013/migration-deployment/migrating-public-folders-exchange-2013-part1.html
You can replace your servers names and follow exactly the proedure that is shown there. I strongly suggest to read also the 2nd page (replication) before you start. Please be aware of
Set-OrganizationConfig –PublicFoldersLockedForMigration $True , so you cannot change the source side whle migrating.
Regards,
Martin

Error in migrating SharePoint 2010 list fields to Office 365 list [CSOM]

Hi,
I am trying to migrate a SharePoint 2010 list to Office 365. I created a new ListCreationInfo for a new list in O365. But when i am to trying add fields from SP2010 list, its giving me an error after list.update() -
A duplicate field name "fa564e0f-0c70-4ab9-b863-0177e6ddd247" was found.
if (!l.Hidden)
ListCreationInformation creationInfo = new ListCreationInformation();
creationInfo.Title = l.Title;
creationInfo.TemplateType = l.BaseTemplate;
List list = web.Lists.Add(creationInfo);
//Fields in the list
ctxOnPrem.Load(l.Fields);
ctxOnPrem.ExecuteQuery();
foreach (Field f in l.Fields)
list.Fields.AddFieldAsXml(f.SchemaXml, true, AddFieldOptions.DefaultValue); list.Update();
Note- l is the SharePoint 2010 List.

Answer given on StackExchange -
http://sharepoint.stackexchange.com/questions/128875/error-in-migrating-sharepoint-2010-list-fields-to-office-365-list-csom/129015#129015
Thanks,
Thomas

Migrate Notes from Exchange server 2007 to office 365

Hi,
Anyone help me to how to migrate notes from exchange server 2007 to office 365 . My customer having notes on his existing exchange account . We would like to move notes to office 365 .
Please help me or guide me .
Thanks & Regards,
Vinoth

The way you're doing it has two very high hurdles.
First, you have to get the data out of an offline server and into Office 365. That's hardly a trivial task. If the server were online and reachable by the Internet you could use a move request or a third-party tool like MigrationWiz.
Second, if you do get the mail moved, you will want to synchronize the legacyExchangeDN attribute from the old organization into an X500 proxy address in Office 365 for all mailboxes to preserve mail replyability.
Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

Moving public folders from exchange 2003 to exchange 2010 error while moving replicas

Dear All,
i am in the process of migrating from Microsoft Exchange 2003 to Exchange 2010,
i am done with moving all the mailboxes 300 mailbox almost with a 1.5 TB DB with no issues
when i tried all the processes, procedures, instructions and forums to move the public folder or
to use move all replicas from Exchange 2003 to Exchange 2010 i always get errors , now when i try
to open PF Management console from the exchange 2010 server i get it but it is disconnected
then i can choose to coneect to the new server name EXCHANGE2010 with no issues
when i try to expand the default folder and system folder i get the following error.
OAB is set on the new server as default.
when i try to add replica using power shell i get this error:
WARNING: An unexpected error has occurred and a Watson dump is being generated: Object reference not set to an inst
of an object.
Object reference not set to an instance of an object.
+ CategoryInfo : NotSpecified: (:) [Get-PublicFolder], NullReferenceException
+ FullyQualifiedErrorId : System.NullReferenceException,Microsoft.Exchange.Management.MapiTasks.GetPublicFolder
following error when trying to expand PF on EXCHANGE 2010
Microsoft Corporation
Microsoft® Windows® Operating System
6.0.6000.16386
Unexpected error [0x7653450B] while executing command 'get-publicfolder -getchildren -identity '\' -server 'Exchange2010.ptdubai.com''.
Microsoft.Exchange.Configuration.MonadDataProvider.CommandExecutionException: Unexpected error [0x7653450B] while executing command 'get-publicfolder -getchildren -identity '\' -server 'Exchange2010.ptdubai.com''. ---> System.NullReferenceException: Object
reference not set to an instance of an object.
at Microsoft.Exchange.Configuration.Tasks.MapiTaskHelper.GetMapiPublicFolderDatabasesIdentities(ADSystemConfigurationSession configurationSession, ADObjectId serverId, TaskErrorLoggingDelegate errorHandler)
at Microsoft.Exchange.Configuration.Tasks.MapiTaskHelper.ValidateServerContainsPFDatabase(Server server, ADSystemConfigurationSession scSession, TaskErrorLoggingDelegate errorHandler)
at Microsoft.Exchange.Configuration.Tasks.MapiTaskHelper.ResolvePublicFolderServerAndUserLegacyDNs(ADSystemConfigurationSession scSession, ServerIdParameter serverIdParameter, String& serverLegacyDN, String& userLegacyDN, Fqdn& serverFQDN,
TaskErrorLoggingDelegate errorHandler)
at Microsoft.Exchange.Configuration.Tasks.GetMapiObjectTask`2.CreateSession()
at Microsoft.Exchange.Configuration.Tasks.DataAccessTask`1.InternalStateReset()
at Microsoft.Exchange.Configuration.Tasks.GetTaskBase`1.InternalStateReset()
at Microsoft.Exchange.Management.MapiTasks.GetPublicFolder.InternalStateReset()
at Microsoft.Exchange.Configuration.Tasks.Task.ProcessRecord()
at System.Management.Automation.CommandProcessor.ProcessRecord()
--- End of inner exception stack trace ---
at Microsoft.Exchange.Configuration.MonadDataProvider.MonadPipelineProxy.ClosePipeline(MonadAsyncResult asyncResult)
at Microsoft.Exchange.Configuration.MonadDataProvider.MonadPipelineProxy.InternalEndInvoke(IAsyncResult results)
at Microsoft.PowerShell.HostingTools.PipelineProxyBase.EndInvoke(IAsyncResult results)
at Microsoft.Exchange.Configuration.MonadDataProvider.MonadCommand.EndExecute(MonadAsyncResult asyncResult)
at Microsoft.Exchange.Configuration.MonadDataProvider.MonadDataReader.Close()
at Microsoft.Exchange.Configuration.MonadDataProvider.MonadDataReader.Dispose(Boolean disposing)
at System.Data.Common.DbDataAdapter.FillInternal(DataSet dataset, DataTable[] datatables, Int32 startRecord, Int32 maxRecords, String srcTable, IDbCommand command, CommandBehavior behavior)
at System.Data.Common.DbDataAdapter.Fill(DataTable[] dataTables, Int32 startRecord, Int32 maxRecords, IDbCommand command, CommandBehavior behavior)
at System.Data.Common.DbDataAdapter.Fill(DataTable dataTable)
at Microsoft.Exchange.Management.SystemManager.DataTableLoader.Fill(RefreshRequestEventArgs e)
at Microsoft.Exchange.Management.SystemManager.DataTableLoader.OnDoRefreshWork(RefreshRequestEventArgs e)
at Microsoft.Exchange.Management.SystemManager.RefreshableComponent.worker_DoWork(Object sender, DoWorkEventArgs e)
at System.ComponentModel.BackgroundWorker.WorkerThreadStart(Object argument)
mscorlib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
Microsoft.ManagementConsole, Version=3.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
MMCFxCommon, Version=3.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
System.Configuration, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
System.Xml, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
System.Windows.Forms, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
System.Drawing, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
Microsoft.Exchange.Management.PublicFolders, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Management.SystemManager, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
System.Core, Version=3.5.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
Microsoft.ManagementGUI, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Data.Common, Version=14.0.631.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.ManagementGUI, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Configuration.ObjectModel, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
System.Data, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
Microsoft.Exchange.Diagnostics, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
System.Web, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
Microsoft.Exchange.Data.Directory, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.PowerShell.HostingTools, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
System.Drawing.Design, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
Microsoft.Exchange.ManagementGUI.resources, Version=14.0.0.0, Culture=en, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Data, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Management, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Isam.Interop, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Data.Transport, Version=14.0.631.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.PowerShell.HostingTools, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
BPA.Common, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
BPA.UserInterface, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Interop.adsiis, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Interop.Migbase, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.DKM.Proxy, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.AirSync, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Approval.Applications, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.CabUtility, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Cluster.Replay, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Common, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Configuration.RedirectionModule, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Data.ApplicationLogic, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Data.Mapi, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Data.Providers, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Data.Storage, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.EdgeSync.Common, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.EdgeSync.DatacenterProviders, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Extensibility.Internal, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.InfoWorker.Common, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Live.DomainServices, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.MailboxReplicationService.Common, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.MessageSecurity, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.MessagingPolicies.Rules, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Net, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Rpc, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Search.ExSearch, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Search.Native, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Security, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.StoreProvider, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Transport.Agent.AntiSpam.Common, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Transport.Agent.SenderId.Core, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Transport, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Transport.Logging.Search, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Transport.Sync.Common, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Transport.Sync.Worker, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.UM.UMCommon, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.UM.UmDiagnostics.Common, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Rtc.Collaboration, Version=3.1.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Rtc.Media, Version=3.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
MSExchangeLESearchWorker, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
System.Management.Automation, Version=1.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Core.Strings, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Core.Strings.resources, Version=14.0.0.0, Culture=en, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.HelpProvider, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
pspluginwkr, Version=1.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
System.Management, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
System.DirectoryServices, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
System.Design, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
Accessibility, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
MMCEx, Version=3.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Anonymously Hosted DynamicMethods Assembly, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null
Microsoft.Exchange.Data.Directory.resources, Version=14.0.0.0, Culture=en, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Data.resources, Version=14.0.0.0, Culture=en, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Configuration.ObjectModel.resources, Version=14.0.0.0, Culture=en, PublicKeyToken=31bf3856ad364e35
i will be thankful for any assistant.
PF DB is arounf 90 GB with alot of public folders and sub-folders. around 60 mail PF and too many subfolders.

First and the most important thing you need to do is, upgrade exchange 2010 to SP2 and RU5.
Exchange 2010 RTM support is long gone.
http://www.microsoft.com/en-us/download/details.aspx?id=36768
http://www.microsoft.com/en-us/download/details.aspx?id=41480
Your exchange 2010 is still in stogeage ;)
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.

Merging existing 2013 Public Folders and 2010 Public Folders from different organization.

Following recent acquisition of another company we faced the following situation:
Company A has Exchange 2013 Organization up and running and already using new Public Folders migrated from 2010 when we upgraded.
Company B has Exchange 2010 Organization with their own PF infrastructure.
When it comes to migration, there's already public folder mailbox which was created when first migration occured.
I cant figure next steps to merge those PF infrastructures at the moment, as removing public folder mailbox prior migration is not an option, since we already have big amount of data in 2013 Organization.
Have anyone done similiar task and if so, how did you overcome this limitation?

You're looking at a third-party product. MigrationWiz does public folders. There are other cloud-based migration solutions, but I don't know whether they support public folder migrations.
Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

Issue with migration of Public folders from Exchange 2010 to Exchange Online.

We are trying to migratie the Public folders structure of one of our clients and are running in an error during migration.
We are following the steps provided by
https://technet.microsoft.com/en-us/library/jj983799(v=exchg.150).aspx
But after creating the New-PublicFolderMigrationRequest the migration request fails (within 15 minutes) with TooManyBadItemsPermanentException. The following errors are reported.
23-1-2015 20:59:16 [AM2PR02MB0370] A corrupted item was encountered: Folder property ""Denbosch""
23-1-2015 20:59:16 [AM2PR02MB0370] A corrupted item was encountered: Folder property ""Eindhoven""
23-1-2015 20:59:16 [AM2PR02MB0370] A corrupted item was encountered: Folder property ""Enschede""
23-1-2015 20:59:16 [AM2PR02MB0370] A corrupted item was encountered: Folder property ""Groningen""
23-1-2015 20:59:17 [AM2PR02MB0370] A corrupted item was encountered: Folder property ""Hoofddorp""
23-1-2015 20:59:45 [AM2PR02MB0370] Fatal error TooManyBadItemsPermanentException has occurred.
","30-12-2114 20:55:36","New"
With the report logs, we gathered the following information (for every folder that is "corupted")
Timestamp         : 23-1-2015 20:59:17
FailureType       : MapiExceptionPermanentImportFailure
FailureCode       : -2147467259
MapiLowLevelError : 0
FailureSide       : Source
FailureSideInt    : 1
ExceptionTypes    : {Exchange, Mapi, DataProviderPermanent, MapiImportFailure}
ExceptionTypesInt : {1, 30, 102, 43}
Message           : MapiExceptionPermanentImportFailure: Data import failed --> Save on the folder partially succeeded.
                     Result = PartiallySucceeded, Property: [0x3fc90102] , PropertyErrorCode: AccessDenied, PropertyErr
                    orDescription: .. Error code = PartialCompletion (0x00040680)
MessageData       :
DataContext       : --------
                    Operation: ISourceFolder.CopyTo
                    Operation: ISourceFolder.CopyTo
                    OperationSide: Source
                    Outlook Anywhere Public Folders (/o=domain/ou=Exchange Administrative Group (FYDIBOHF23SPDLT
                    )/cn=Recipients/cn=sysadmin)
                    PropTags: [count:23, 0x360f000d(ContainerContents); 0x3610000d(FolderAssociatedContents); 0x360e000
                    d(ContainerHierarchy); 0x61af0102; 0xe080003(MessageSize); 0xe230003(InternetArticleNumber); 0xff40
                    003(Access); 0x360a000b(SubFolders); 0x36170003(AssocContentCount); 0x65e00102(SourceKey); 0x65e101
                    02(ParentSourceKey); 0x65e20102(ChangeKey); 0xe270102(NTSD); 0xf000102(FreeBusyNTSD); 0x3fe00102; 0
                    x3fe0000d(AclTable); 0x3ffe0102; 0x3fe1000d(RulesTable); 0x3fe10102; 0x66980102(ReplicaList); 0x663
                    b0102(AddressBookEntryId); 0x671d0102(PfProxy); 0x671f000b(PfProxyRequired)]
                    Folder: 'Public Root/IPM_SUBTREE/werkbevestigingen', entryId [len=46, data=000000001A44739
                    0AA6611CD9BC800AA002FC45A0300E588060DE94CBC42AA16C57D7D69B8D400000093A2A60000], parentId [len=46, d
                    ata=000000001A447390AA6611CD9BC800AA002FC45A0300E588060DE94CBC42AA16C57D7D69B8D40000000000010000]
DataContextData   :
StackTrace        :    at Microsoft.Mapi.MapiExceptionHelper.ThrowImportFailureException(String message, Exception inne
                    r)
                       at Microsoft.Mapi.MapiProp.ExportObjectHelper(IMapiFxProxy dest, PropTag[] tags, CopyPropertiesF
                    lags copyPropertiesFlags, Boolean useCopyProps)
                       at Microsoft.Exchange.MailboxReplicationService.MapiSourceFolder.Microsoft.Exchange.MailboxRepli
                    cationService.ISourceFolder.CopyTo(IFxProxy destFolderProxy, CopyPropertiesFlags flags, PropTag[] e
                    xcludeTags)
                       at Microsoft.Exchange.MailboxReplicationService.SourceFolderWrapper.<>c__DisplayClass2.<Microsof
                    t.Exchange.MailboxReplicationService.ISourceFolder.CopyTo>b__0()
                       at Microsoft.Exchange.MailboxReplicationService.ExecutionContext.Execute(Action operation)
                       at Microsoft.Exchange.MailboxReplicationService.ExecutionContextWrapper.Execute(Action operation
                    , Boolean measure)
                       at Microsoft.Exchange.MailboxReplicationService.SourceFolderWrapper.Microsoft.Exchange.MailboxRe
                    plicationService.ISourceFolder.CopyTo(IFxProxy destFolder, CopyPropertiesFlags flags, PropTag[] exc
                    ludeTags)
                       at Microsoft.Exchange.MailboxReplicationService.MailboxCopierBase.<>c__DisplayClass12.<CopyFolde
                    rProperties>b__d()
                       at Microsoft.Exchange.MailboxReplicationService.CommonUtils.ProcessKnownExceptionsWithoutTracing
                    (Action actionDelegate, FailureDelegate processFailure)
InnerException    : RopExecutionException: Save on the folder partially succeeded. Result = PartiallySucceeded, Propert
                    y: [0x3fc90102] , PropertyErrorCode: AccessDenied, PropertyErrorDescription: .. Error code = Partia
                    lCompletion (0x00040680)
UnknownElements   :
UnknownAttributes :
Does someone has a tip for further troubleshooting this issue?

Hi,
There are a lot of corrupted items. You can try raising the baditemlimit to 999 to workaround this issue
Get-PublicFolderMigrationRequest | Set-PublicFolderMigrationRequest -baditemlimit 100
To resumed the PublicFolderMigrationRequest
Get-PublicFolderMigrationRequest | Resume-PublicFolderMigrationRequest
Thanks,
Please remember to mark the replies as answers if they help and unmark them if they provide no help.
Simon Wu
TechNet Community Support

Unable to Open Public folders from Windows XP after the upgrade of CU4 to Cu7

We still have few machines running windows Xp, who cannot access Public folders after the upgrade to the latest CU7. Is there any fix for it other than moving them to Windows 7?

Hi DNair,
Hope you are already upto date. But still just putting it through to cross check.
Outlook Versions Supported by Exchange 2013
The following Outlook client versions are fully supported by Exchange server 2013. Please bear in mind there’s a difference between what is supported and what might be compatible with Exchange 2013.All
of the Outlook versions listed below have been thoroughly tested by the Exchange Product group:
Outlook 2013
Outlook 2010 SP1 with November 2012 Cumulative Update ( available from
http://support.microsoft.com/kb/2687623 )
Outlook 2007 SP3 with November 2012 Cumulative Update ( available from
http://support.microsoft.com/kb/2687404 )
Entourage 2008 for Mac, Web Services Edition
Outlook for Mac 2011
Outlook clients earlier than Outlook 2007 are not supported.
Find and Manage
Outlook Updates here.
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.

Migrate only a selection of public folders from 2007 to 2013

Like the subject says- I've been asked to move a small selection only from 2007 to 2013. Essentially out of 4700 public folders they only want to migrate 170. I've always just moved them all and can't think of a way to do this. I can't just delete
the rest of the public folders on 2007- they want to keep them for a short while just in case they've screwed their logic. (They are relying on LastModifiedTime- no access in the last 6 months).
Any Suggestions?
regards
Tony

I agree with Gary that with the MS default process this is true, however if you are open to 3rd party products Lucid8's DigiScope would allow you to open an Offline Copy of the 2007 PF, Filter out what you don't want to copy and then restore the balance
of folders from the offline EDB directly into the 2013 PF.
And of course you could also export the 170 folders to PST and then import to 2013 however that could get a bit ugly...
Search, Recover, & Extract Mailboxes, Folders, & Email Items from Offline Exchange Mailbox and Public Folder EDB's and Live Exchange Servers or Import/Migrate direct from Offline EDB to Any Production Exchange Server, even cross version i.e. 2003
--> 2007 --> 2010 --> 2013 with Lucid8's
DigiScope

Need assistance creating applications with superseedence to uninstall Office 2010, Lync 2010 and then install Office 365 click to run 2013

We are getting ready in a few months to uninstall our locally installed Office 2010 and head to the cloud with Office 365 2013. I have created applications to uninstall Office 2010 and Lync 2010 and then added them to the supersedence tab for Office 365
office 2013 click to run with appv5.
When deploying the office 365 2013 application it does not uninstall office 2010 or lync 2010 with the supersedence. I am able to manually uninstall Office 2010 and Lync 2010 with the command lines I am using in the applications.
The application uninstall for Office 2010 is:
The application uninstall is an exe so I created an application, created a deployment type with the location of our Office 2010 admin point, installation program and uninstall program are set with the same line as I have tried to deploy it separately and
also as a supersedence in the Office 365 application setup.exe /uninstall ProPlus /config "\\sccmserver\share\Office2010\ProPlus.ww\silentuninstallconfig.xml. The silentuninstallconfig.xml was created from the original config.xml file and edited
to these settings:<Configuration Product="ProPlus">
<Display Level="none" CompletionNotice="NO" SuppressModal="yes" AcceptEula="yes" />
<Setting Id="Reboot" Value="Never" />
<Setting Id="SETUP_REBOOT" Value="NEVER" />
<OptionState Id="ProductFiles" State="Local" Children="force" />
</Configuration>
The detection method is the folder path to see that office 14 exists. When I deploy this the machines finish with success showing this exists, but does not uninstall Office 2010.
running the command line manually mapped to this location on a machine uninstalls office 2010 without issue.
Lync 2010 uninstall:
Lync is an exe so I am using the LyncSetup.exe /silent /uninstall. The application is in the supersedence tab for Office 365 2013. This never installs. If I create a softare distribution and deploy it on its own it uninstalls without issue.
We are going to use Lync 2013 with our office 365 2013 installation so we need to uninstall this. The detection method for lync is file system folder and the Microsoft lync folder for detection.
MS Office 15 (Office 365) was created with the click to run tool. I can install this with the application I created using the appv5 package created with the click to run tool. The issue is we need Office 2010 and Lync 2010 uninstalled first.
Having both versions of Office installed in test has caused issues where Office 15 365 will not list in add and remove programs and cannot be uninstalled even with the fix it article to remove office 2013.
I have looked at many articles and so far it is not working for us. Any help appreciated to get us to the cloud.
Thanks,
Brit

The applications I have for uninstall of office 2010 and Lync 2010 for some reason do not uninstall. Manually testing the command lines they do. The detection method seems to be hanging things up. On the lync uninstall detection method I have
the setting type of file system, type folder, path c:\program files\ folder name Microsoft Lync.
I highly recommend using something other than a file/folder "exists" detection method. Installers are constantly leaving things behind due to environmental inconsistencies. It may leave files/folders behind with a schedule to delete files on next reboot.
These things are unpredictable and very hard to use. I just use the "HKLM\Software\Microsoft\Windows\CurrentVersion\Uninstall" Registry location. There you can actually key off the "Product Version" DWORD as well which gives you an even more accurate method
to determine if the application you are trying to deploy (or expect to exist) is truly there. This, of course, being if you are not using an MSI. If you have MSI technology ALWAYS use the product code unless the person writing the MSI chooses to use the same
product code for every version release of their product. In which case, Use the registry method.
As far as getting the supersedence and everything working. You need to start from the basics. Create Applications for all of the apps you want to remove. Make sure they install and uninstall properly (seems like overkill but it isn't that hard). Once you
have working install/uninstall applications then you can easily apply supersedence to your new applications with a setting of Uninstall on the superseded apps you should have no problem getting rid of them. I have done this for numerous things.
For example, I did this with Cisco Jabber to replace older versions of jabber, older versions of cisco unified personal communicator and lync and OSC. All of these replaced versions had to have an Application but once it was in it took two seconds to apply
all the supersedence rules and now I know when I push that software out no matter version is running on any machine it will pull all the old apps off and put the new one on.
Dustin Estes - MCP | www.dustinestes.com

Search SharePoint 2013 On-Prem with Office 365

We're trying to understand federated search in SharePoint 2013, when it comes to Office 365. We have both a SharePoint 2013 on-prem environment, and an Office 365 environment. The 2 are completely separate, and have not been configured to use a hybrid model.
Is it possible to configure a Result Source in either the SharePoint environment or the Office 365 environment to index the other? Reading this
article from Technet, it indicates that you can configure a remote SharePoint farm as a Result Source:
"Remote SharePoint provides
results from the index of a search service in another farm."
But I've read on another
thread on here that this is not possible from O365.
I'm hoping that someone can provide some guidance, or point me in the right direction.
Thanks,
cflbasser

Yes, you can receive search results from an on-premise SharePoint Server 2013 farm within SharePoint Online.
Hybrid search between SharePoint Server and SharePoint online uses federated search results. Neither the on-premise farm nor SPO crawl the other location, they just send a federated search query over the fence and wait for the results.
You can search in either direction (one-way hybrid search) or both ways (bidirectional hybrid search).
The one-way search can either be SharePoint Server sending search queries to SPO or SPO sending queries to SharePoint Server which also needs a reverse proxy for securely publishing your on-premise farm to SPO.
Bi-directional hybrid search just combines both one-way methods together so either location can receive search results from the other location.
Here are some further resources to help you plan and implement hybrid search:
Hybrid for SharePoint Server 2013
Configure hybrid Search for SharePoint Server 2013
Chris O'Brien has an excellent article that describes the actual search experience. Check out Office 365 SharePoint hybrid - what you
DO and DO NOT get
Jason Warren
@jaspnwarren
jasonwarren.ca
habaneroconsulting.com/Insights

Public Folders from 2010 on-prem to Office 365 PF database?

Similar Messages

Maybe you are looking for