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

Similar Messages

Public Folders after 2007 to 2010 Migration

I am unable to move public Folders from 2007 to 2010. Will not replicate nor can I create or use any new Public Folders on the 2010 server. Every other part of the migration has been completed and the system is working well.
Is there anything that I might be missing in order to move Public Folders to 2010?

Hi,
Please check the msExchHomePublicMDB value in ADSI Edit:
1. In Adsiedit, expand Configuration-->CN=Services -> CN=Microsoft Exchange -> CN=domain -> CN=Administrative Groups -> CN=Exchange Administrative Group -> CN=Databases.
2. Right-click the listed database > Properties.
3. Make sure the msExchHomePublicMDB value is pointed to the Public Folder database in Exchange 2010 instead of Exchange 2007.
Additionally, please use the ReplaceReplicaOnPFRecursive.ps1 script to move all the replicas of a public folder subtree from one server to another server. For more information about Public Folder migration from Exchange 2007 to Exchange 2010, please refer
to:
https://technet.microsoft.com/en-us/library/bb331970(v=exchg.141).aspx
Regards,
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
Winnie Liang
TechNet Community Support

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

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 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"

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

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.

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

After migrated to sp2013 library icon still use from 2007.

I've migrated SharePoint from 2007 to 2013 (2007 -> 2010 -> 2013) with database attached method. After upgrade I found that the library and
list application icon are still 2007 image.
How can I change or upgrade all functional to 2013? Please help.

Under Site Settings there is option to Visual Upgrade the site collection to 2013 look and feel. After you complete this upgrade, the site will get the new look and feel.

Mailflow Problem After Migrating Mailbox From 2007 to 2013

I thought I was at the point of migrating our mailboxes from 2007 to 2013. I had created a new test mailbox on the 2013 server and changed all the DNS and virtual directories for the legacy on the 2007 server and was able to successfully send mail
to the test mailbox out and in both internally and externally. Then I migrated my first mailbox from 2007 to 2013 and things went south.
I CAN NOT:
Send e-mail from a mailbox on the 2007 server to the migrated mailbox on the 2013 server.
Send e-mail from migrated mailbox to external e-mail address.
I CAN:
Send e-mail from the migrated mailbox to a 2007 mailbox and the test mailbox on the 2013 server.
Send e-mail from the internet to the migrated mailbox and the 2013 test mailbox.
I unfortunately am running Exchange 2013 with CU6 (I am already aware of the activesync issue and delegation crash issue but saw the info too late).
Suggestions please!!

Hi,
Before going further, I'd like to ask the following questions to troubleshoot the issue:
1. Could you send email from 2007 mailbox to the test mailbox on 2013 server?
2. Did you get any NDR message when sending email to the migrated mailbox failed?
In addition, I recommend you try the following methods to find out the root cause:
1. Try to use message tracking tool in exchange 2007 server ,it will help us to find the email which was sent to the migrated mailbox .
2. Run the following command to check the permission groups of the receive connector:
Get-Receiveconnector |fl Name,PermissionGroups,Exchangeversion
Best regards,
Niko Cheng
TechNet Community Support

Migrated mailbox from 2007 to 2013 now unable to connect to Samsung S4

I'm in the process of migrating from 2007 to 2013.
I have moved successfully a several mailbox's from Ex2007 to Ex2013. Currently, all the EAS policies reside on the 2007 server and I have been successful reconnecting all the smartphones so far.
However, I have a Samsung S4 that is refusing to connect. Any ideas what I need to do?
Penny Miller
PennyM

I checked the phone settings in his OWA account and it is blank. How can I add it in?
Penny
PennyM

DL Migration from 2007 to 2013

Guys,
We need to migrate 150 DL's from 2007 to 2013.
2007 DL's are in .companyname<department> format and in 2013 special characters are not supported
We would like to change the format to DL-companyname....
Is there is script to copy the existing list of DL's including permissions in 2007, recreate new one's in the new format and add the permissions in 2013?
Thanks
D

Hi
Hi Here you go
You can use this one
foreach ($DL in (Get-DistributionGroup -ResultSize Unlimited)) { $owners = Get-ADPermission $DL.identity | ?{$_.User -notlike “*Exchange*” -and $_.User -notlike “S-*” -and $_.User -notlike “*Organization*” -and $_.User -notlike “NT*” -and $_.User -notlike
“*Domain Admins*” -and $_.User -notlike “*Enterprise Admins” -and $_.User -notlike “BUILTIN*” -and $_.User –notlike “*Delegated Setup*”} | %{$_.user.tostring()};Set-DistributionGroup $DL -BypassSecurityGroupManagerCheck -ManagedBy $owners }
Refer below link for more information which has clear cut information
http://exchangeserverinfo.net/2013/12/upgrading-distribution-groups-from-exchange-2007-to-exchange-2013/
http://gallery.technet.microsoft.com/scriptcenter/8c22734a-b237-4bba-ada5-74a49321f159
Remember to mark as helpful if you find my contribution useful or as an answer if it does answer your question.That will encourage me - and others - to take time out to help you Check out my latest blog posts on http://exchangequery.com

Public folders in hosted Exchange 2013

Hi,
Is it possible to setup public folders for a tenant i Exchange 2013, eg. with custom id 0 set or something like that?
Thanks!

Hi,
If you want to deploy public folders in an Exchange 2013 multi-tenant environment, you can create a public folder mailbox per tenant.
Here is a related thread for your reference.
Public Folder Hierarchy and PF Mailboxes for Hosted setup?
http://social.technet.microsoft.com/Forums/exchange/en-US/e9062abe-f484-462b-bc5e-ebdcb0862760/public-folder-hierarchy-and-pf-mailboxes-for-hosted-setup?forum=exchangesvradmin
More information about public folder in Exchange 2013 here:
http://technet.microsoft.com/en-us/library/jj552408.aspx
Best regards,
Belinda
Belinda Ma
TechNet Community Support

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

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.

Migrate only a selection of public folders from 2007 to 2013

Similar Messages

Maybe you are looking for