Public Folder Migration Exchange 2010 to 2013 Stuck on Queued

I submit the request New-PublicFolderMigrationRequest and the status is stuck on "Queued". What are the steps to troubleshoot this? I have followed the article in on Technet to perform my PF migration.

[PS] C:\Windows\system32>New-PublicFolderMigrationRequest -SourceDatabase (Get-PublicFolderDatabase -Server "exchange3.a
npinetwork.com") -CSVData (Get-Content "C:\PFMigration\foldertomailbox.csv" -Encoding Byte)
Name                                           SourceDatabase                          
      Status
PublicFolderMigration                          Public Folder Database 1055175278              Queued
[PS] C:\Windows\system32>Get-PublicFolderMigrationRequest | Get-PublicFolderMigrationRequestStatistics -IncludeReport |
Format-List
RunspaceId                       : c2270d62-665e-44ad-8829-43f5befde1f9
Name                             : PublicFolderMigration
Status                           : Queued
StatusDetail                     : Queued
SyncStage                        : None
Flags                            : IntraOrg, Pull, SuspendWhenReadyToComplete
RequestStyle                     : IntraOrg
Direction                        : Pull
Protect                          : False
Priority                         : Normal
Suspend                          : False
SourceVersion                    : Version 14.3 (Build 123.0)
SourceDatabase                   : Public Folder Database 1055175278
SourceServer                     : exchange3.anpinetwork.com
BatchName                        :
OutlookAnywhereHostName          :
RemoteCredentialUsername         :
AuthenticationMethod             : Basic
RemoteMailboxLegacyDN            :
RemoteMailboxServerLegacyDN      :
BadItemLimit                     : 0
BadItemsEncountered              : 0
LargeItemLimit                   : 0
LargeItemsEncountered            : 0
FolderToMailboxMap               : {\}
QueuedTimestamp                  : 1/16/2014 1:44:08 PM
StartTimestamp                   :
LastUpdateTimestamp              : 1/16/2014 1:44:10 PM
InitialSeedingCompletedTimestamp :
FinalSyncTimestamp               :
CompletionTimestamp              :
SuspendedTimestamp               :
OverallDuration                  : 00:00:23
TotalFinalizationDuration        :
TotalDataReplicationWaitDuration :
TotalSuspendedDuration           :
TotalFailedDuration              :
TotalQueuedDuration              : 00:00:23
TotalInProgressDuration          :
TotalStalledDueToCIDuration      :
TotalStalledDueToHADuration      :
TotalStalledDueToReadThrottle    :
TotalStalledDueToWriteThrottle   :
TotalStalledDueToReadCpu         :
TotalStalledDueToWriteCpu        :
TotalStalledDueToReadUnknown     :
TotalStalledDueToWriteUnknown    :
TotalTransientFailureDuration    :
TotalIdleDuration                :
MRSServerName                    :
EstimatedTransferSize            : 0 B (0 bytes)
EstimatedTransferItemCount       : 0
BytesTransferred                 :
BytesTransferredPerMinute        :
ItemsTransferred                 :
PercentComplete                  : 0
PositionInQueue                  : 6/6 (Position/Queue Length)
PreventCompletion                : True
FailureCode                      :
FailureType                      :
FailureSide                      :
Message                          :
PoisonCount                      : 0
FailureTimestamp                 :
IsValid                          : True
ValidationMessage                :
OrganizationId                   :
RequestGuid                      : 238914aa-baf7-42b2-91d0-4b27e22e3a81
RequestQueue                     : ANPIMDB02
ExchangeGuid                     : 0c62c485-3fd1-4aaf-b29d-67cfa078ac41
Identity                         : 6209b848-c493-4147-9937-d91e3f16f846\238914aa-baf7-42b2-91d0-4b27e22e3a81
DiagnosticInfo                   :
Report                           : 1/16/2014 1:44:07 PM [LSVGNV04EXC01] 'anpinetwork.com/Springfield/Users and
                                   Computers/Network Services/Users/Mitch Givner' created request.
ObjectState                      : New
[PS] C:\Windows\system32>

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.

  • Migrate Exchange 2010 to 2013 External Mail Flow

    Dear All,
    I am in the middle of Exchange Server 2010 to 2013 Migration. The scenario is I have single Exchange 2010 server with HUB/CAS/Mailbox and installed new Exchange 2013 with single CAS and single Mailbox server. The internal email flow between Exchange
    2010 to 2013 and 2013 to 2010 is working. Having some issues and need assistance to resolve at earliest.
    The issue with the external mail flow and I want to Exchange 2010 should be configured to send external email while migrating users to Exchange 2013. Once migrate all users to Exchange 2013 then will configure Exchange 2013 send connector.
    How can I configure single name space of web URL for OWA both on Exchange 2010 to Exchange 2013, if user mailbox is in Exchange 2010 can access same OWA URL as user migrate to Exchange 2013.
    How to configure SSL certificate, I have single URL certificate this would be enough for OWA, ActiveSync and Anywhere.
    Is that possible if directly move the Exchange 2010 database to Exchange 2013 database, this will move all users mailboxes in one go or do I need to migrate users mailbox individual or in bulk.
    Kindly guide if any thing missing that need to address during start the migration activity.
    Thanks in Advance

    Hi ,
    Sorry for delay.
    Question : Thanks for your valuable response. On
    point no.2, I want to use same external URL for Exchange 2010 and Exchange 2013, is this possible if user is on exchange 2010 server or migrated on Exchange 2013 can use same external single name space URL to access OWA ?
    Yes you can have the same External URL for the exchange 2010 owa and exchange 2013 owa.So users from exchange
    2010 and exchange 2013 can access owa on the same URL from external world.For exchange 2010 users owa connections will be proxied from exchange 2013 to exchange 2010.
    For mailbox connectivity issue in exchange 2013 :
    1.From internal outlook clients ,Please check the internal outlook anywhere name is resolved to exchange
    2013 server and also make sure the authentication set on the outlook anywhere is set to NTLM. Same time we need to have the internal outlook anywhere name on the SAN certificate.
    2.Make sure the names used exchange on 2013 URL'S is available on the SAN certificate and also the certificate
    needs to installed on the exchange server and that certificate has to be enabled for the required services like iis,pop.imap,smtp.
    3.Make sure the outlook client request coming for internal outlook anywhere name and also to autodiscover
    service is not reaching the proxy server if you have on your network.
    In case if you have proxy server in your environment for internet access ,So for that we need to add the internal outlook anywhere name and autodiscover name
    on the internet explorer proxy exceptions for all the internal outlook clients.We can globally achieve it through group policy.
    4.please share me the output for the below mentioned command.
    get-ClientAccessServer -Identity “server name”  | fl AutodiscoverServiceInternalURI 
    5.If you are having outlook 2007 then make sure it fully patched with latest sp and updates.
    6.On which operating system version those outlook 2007 clients are installed?
    Please reply me if anything is unclear.
    Thanks & Regards S.Nithyanandham

  • Public folder migration Exchange 2007 to Ex2013

    Hi Team,
    Below is my co-existence enviroment . Everything is working fine but getting issue while migrating public folder
    Dc-2003 , Ex2007 SP3 rollup10 , Ex2013 with Rollup2
    ==============================================
    [PS] C:\Documents and Settings\Administrator.HCL>C:\Script\PublicFolderToMailbox
    MapGenerator.ps1
    Parameter declarations are a comma-separated list of variable names with option
    al initializer expressions.
    At C:\Script\PublicFolderToMailboxMapGenerator.ps1:15 char:144
    +         HelpMessage = "Size (in Bytes) of any one of the Public folder mailbo
    xes in destination. (E.g. For 1GB enter 1 followed by nine 0's)")] <<<<
    [PS] C:\Documents and Settings\Administrator.HCL>

    thanks Martina for your reponse . I have tried all the ways please see print shot below no help. But the same command was working with Ex2010 i have successfully migrated public folder also from Exchge 2010 to 2013
    [PS] C:\PFScript>.\Export-PublicFolderStatistics.ps1 C:\PF\stats.txt
    Parameter declarations are a comma-separated list of variable names with optional initializer expressions.
    At C:\PFScript\Export-PublicFolderStatistics.ps1:16 char:168
    +         HelpMessage = "Full path of the output file to be generated. If only
    filename is specified, then the output file will be generated in the current directory.")] <<<<
    =====================================
    [PS] C:\PFScript>.\Export-PublicFolderStatistics.ps1 C:\PF\stats.csv hcl-ex2007
    Parameter declarations are a comma-separated list of variable names with optional initializer expressions.
    At C:\PFScript\Export-PublicFolderStatistics.ps1:16 char:168
    +         HelpMessage = "Full path of the output file to be generated. If only
    filename is specified, then the output file will be generated in the current directory.")] <<<<
    ======================================
    [PS] C:\PFScript>.\Export-PublicFolderStatistics.ps1 C:\PF\stats.csv hcl-ex2007.
    hcl.com
    Parameter declarations are a comma-separated list of variable names with option
    al initializer expressions.At
    C:\PFScript\Export-PublicFolderStatistics.ps1:16 char:168
    +         HelpMessage = "Full path of the output file to be generated. If only
    filename is specified, then the output file will be generated in the current di

  • How to Migrate Exchange 2010 to 2013

    am planning to migrate my existing Exchange 2010 Environment to Exchange 2013, My Existing setup as follows below.
    2MBX Which is part of DAG, 1CAS/1HUB/1Archival MBX . Please advise me how to initiate and complete successfully.
    OS : windows server 2008 R2 Ent.
    Forest Functional Level : Windows server 2003
    Domain Functional Level : Window server 2003
    Also we have Gateway for external emails SPAM Filtering.
    Thanks, Venkatesh. &quot;Hardwork Never Fails&quot;

    You're in the Lync forums, I'd post this question in the Exchange forums:
    http://social.technet.microsoft.com/Forums/exchange/en-US/home?forum=exchangesvrgeneral
    Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question please click "Mark As Answer".
    SWC Unified Communications

  • Questions about migrating Exchange 2010 to 2013

    We currently have two Exchange 2010 servers with roles separated.  One local mailbox server without CAS in our building and a CAS with no mailboxes in a remote datacenter.
    We plan to migrate to 2013 with two new servers hosting all roles on each and then shut down the 2010 servers. There will be one local and one in a datacenter for Exchange 2013 so that either server could be individually restarted without internal LAN users
    losing email access. (We do not want to open network access from the Internet to the onsite CAS). Is it practical to set it up this way?  
    How do we get the existing certificates (mail, autodiscover, and the local host name etc.) moved from the 2010 to the 2013 to the new servers when I assume they both must be running side by side for at least a short time while mailboxes are moved form 2010
    to 2013?  Will we need to buy new SSL certificates since the local host machine names for the Exchange server 2013 servers will be new and there will be more than one CAS?

    Most of the CAs allow issuing duplicate certificate (as if you are requesting for a new cert) for the servers running same application. If your CA doesn't provide duplicates you can export the certificate and import to Exchange2013. http://msexchangeguru.com/2013/06/29/import-cert-e2013/
    In certificate you dont need your internal FQDN. Especially in future you wont be able to add your internal FQDN in your certificate as most of the CAs wont allow you to add internal FQDN.
    When you migrate to exchange 2013 you just need to configure the external URLs of Ex2010 in Ex2013 for both (i.e. same URLs for internal and external URLs) and point your common name and autodiscover to Exc2013 as Ex2013 will proxy the requests to your legacy
    Ex2010 server. i.e. Your client interface will be Ex2013. 
    Please check this it will help you configure Split DNS and configure your URLs
    http://exchange.sembee.info/2013/install/clientaccesshostnames.asp
    http://www.mustbegeek.com/configure-external-and-internal-url-in-exchange-2013/ GUI
    Configure split DNS to resolve external name from internal network.
    Keep both Ex2010 CAS and Ex2013 CAS servers till all get logged in atleast once to connect to Ex2013 mailbox automatically.
    As your DAG stretched across the data centers make sure
    your DAG is in DAC mode.
    http://technet.microsoft.com/en-us/library/dd979790(v=exchg.150).aspx
    Please read this as well for details about DAG configured in multiple site
    http://technet.microsoft.com/en-us/library/dd638129(v=exchg.150).aspx
    Ensure you use Exchange2013 SP1 as it is already released and available for download
    http://www.microsoft.com/en-us/download/details.aspx?id=41994
    Do you have a load balancer in place? 
    Regarding internet facing it depends.  You can configure CAS2013 server in DMZ if you wish to.
    Thanks, MAS
    Please mark as helpful if you find my comment helpful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you.

  • Outlook clients are connecting to different site public folder rather than same site public folder on exchange 2010

    Team,
    users are unable to expand public folder from outlook, but they are able to navigate through outlook web access.
    noticed the outlook connections are connected to other child domain PF server rather than local site public folder server.
    due to this issue, users are unable to navigate to pf's , by restarting RPC Client access service , now users are able to connect to local public folder servers.
    all the databases are pointed to local pf database. all the settings looks good.
    any suggestions would be appreciated.
    Regards
    Srinivasa K
    Srinivasa K

    Hi Srinivasa,
    How about OWA?
    If it works in OWA, it seems an issue on the Outlook client side.
    I suggest run Outlook under safe mode to avoid some AVs and add-ins.
    I also suggest make sure the Outlook client has the latest patch.
    Also try to re-install Outlook.
    Thanks
    Mavis
    Mavis Huang
    TechNet Community Support

  • Public Folder Migration - 2010 to 2013 - Downtime incurred at "Lockdown" Stage

    Looking for some information from those who have completed a successful Public Folder migration from 2010 to 2013.
    1.  Size of 2010 Public Folder Store
    2.  Downtime incurred upon the "Lock down 2010 Public Folder" stage once all mailboxes moved to 2013 and ready to cut-over to 2013

    I would like to refer you at this well explained technet library and check whether you follow all the required prerequisites for a successful public folder migration from Exchange 2010 to 2013 : http://technet.microsoft.com/en-us/library/jj150486%28v=exchg.150%29.aspx
    Also, please check this another article resource : http://www.msexchange.org/articles-tutorials/exchange-server-2013/migration-deployment/migrating-public-folders-exchange-2013-part1.html
    Apart from above resources, you may also consider at this comprehensive application(http://www.exchangemigrationtool.com/) that can be a better alternative approach while migrating public folder database
    between two exchange server.

  • Exchange 2013 users cannot open public folders on exchange 2010

    Migrating from Exchange 2010 SP3 to Exchange 2013 CU3 in same forest and domain
    client version is outlook 2013
    outlook any where is disable (default) on exchange 2010 which must be disabled as organization policy
    outlook any where external host name field is blank (we need to keep outlook any where disable for external)
    outlook anywhere internal authentication is set to NTLM and Client require SSL to false   
    I have moved a mailbox from Exchange 2010 to Exchange 2013, user moved from exchange 2010 to 2013 cannot access public folder on exchange 2010. I have been stuck on this kindly suggest  

    Hello,
    Please explain the sentence "The user moved from exchange 2010 to 2013 cannot access public folder on exchange 2010". Do you mean the moved user can't see the public folder or the user has no permission to see the public folder?
    If the moved user can't see the public folder, please check if the moved user can see the public folder via owa. When you use outlook to view public folder, you can following the method: Open outlook, click folder list at the bottom of left panel.
    If the user has no permission to see the public folder, please check the permission.
     =============================================================
    1. Open ADSIEDIT.
    2. Navigation to CN=Configuration, DC=Your domain name -> CN=Services ->CN=Microsoft Exchange ->CN=Your organization name ->CN=Administrative Groups ->CN=Exchange
    Administrative Group ->CN=Databases ->CN= PF Database.
    3. Right-click the PF Database, and then select Properties. Under Security, check if everyone has read permission.
    Besides, please check if public folder replication is ok. You can use Get-PublicFolderStatistics cmdlet to compare item count, size.
    Additional article for your reference.
    http://technet.microsoft.com/en-us/library/jj150486(v=exchg.150).aspx
    If you have any feedback on our support, please click
    here
    Cara Chen
    TechNet Community Support

  • Public Folder Migration Cross Forest

    Hello,
    We are in the middle of planning a cross forest migration from Exchange 2010 to Exchange 2013. 
    To give some context:
    We already have an Exchange 2013 environment complete with mailboxes, and public folders etc. We have a 2010 Exchange server in a different forest that we would like to migrate all existing mailboxes and public folders from to the Exchange 2013 forest. We will
    be keeping the domain/forest that currently contains 2010 so all mailboxes that will be moved will end up being linked mailboxes in the 2013 organization with the accounts held in the other forest. 
    One of the big unanswered questions remains around public folder access. During migration there will be a time when some users will be in the Exchange 2010 organization, and some will be in the Exchange 2013 organization. I have two main questions around this
    1. Is there any way possible that anyone can think of that the users moved to 2013 can access the public folders still on 2010?
    2. What is the best way to migrate the public folders over from 2010 to 2013? Do we have to create the public folders and permissions on 2013 before hand or do we use a 3rd party tool or other method to achieve this goal?

    Hi,
    To reduce needless trouble, I recommend migrate mailbox first and public folder second.
    However, public folder will works fine no matter where it located. If you experience an issue about user in Exchange 2013 mailbox cannot access Public Folder in Exchange 2010, please change the RPC authentication to NTML.
    More details about it, please refer to:
    https://social.technet.microsoft.com/Forums/exchange/en-US/3172435f-4c06-41b3-b7a7-937dc0160049/exchange-2013-users-unable-to-access-exchange-2007-public-folders?forum=exchangesvrdeploy
    Additional, step by step to migrate Public folder to Exchange 2013, for your reference:
    http://blogs.technet.com/b/meamcs/archive/2013/07/25/part-4-step-by-step-exchange-2007-to-2013-migration.aspx
    Thanks
    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]
    Allen Wang
    TechNet Community Support

  • Exchange 2010 to 2013 Public Folder Migration -- Token Serialization

    Here is the log entry,Failed to save admin audit log for this cmdlet invocation. Organization: First Organization Log content:Cmdlet Name: New-PublicFolderMigrationRequestObject Modified: f0daff33-6a93-4367-b609-662cfa0b92de\71fc0595-b5d7-4f15-8b7c-bffcefbd810fParameter: SourceDatabase = Public Folder Database Parameter: CSVData = VGFyZ2V0TWFpbGJveCxGb2xkZXJQYXRoDQpDb2JvY28gUEYsXA0KQ29ib2NvIFBGLFxJUE1fU1VCVFJFRVxBcg==...Caller: ExternalAccess: FalseSucceeded: TrueRun Date: 2015-07-07T12:41:45OriginatingServer: (15.00.0995.012)Error:Microsoft.Exchange.Data.ApplicationLogic.AuditLogAccessDeniedException: The requesting account doesn't have permission to access the audit log. --- System.Web.Services.Protocols.SoapException: The requesting account does not have permission to serialize tokens. at...

    Hey Guys!
    I'm in the process of testing a Public Folder migration from Exchange 2010 to 2013, I've been following the recommened migration scenario from Microsoft but have ran into this issue when running New-PublicFolderMigrationRequest. I let the request sit at a queued status for over 6 hours and then decided to look at the event logs. I'm receiving an access denied, requesting account does not have permission to serialize tokens.
    Luckily this is just a test and not in a production environment :-)
    Any suggestion or help to point me in the right direction would be appreciated
    Thanks Guys
    This topic first appeared in the Spiceworks Community

  • Exchange 2010 - 2013 Public Folder Migration target database gets much bigger than source database

    Hi,
    i have a question about the pf migration from Exchange 2010 to Exchange 2013. The source database ist about 370 GB. The migration process is still running. At the moment the target database is already 491GB big. Is that a normal behaviour during the migration
    process.
    Thanks

    Hi,
    After you have finished the public folder migration process, you can compare the item count of public folders to make sure all public folders have been moved to Exchange 2013.
    You can check this by comparing the snapshots before and after the migration. You can refer to the "How do I know this worked?" section in the following article.
    Migrate Public Folders to Exchange 2013 From Previous Versions
    http://technet.microsoft.com/en-us/library/jj150486(v=exchg.150).aspx
    Best regards,
    Belinda
    Belinda Ma
    TechNet Community Support

  • Public Folder Migration from Exchange 2007 to 2013

    Hi Guys,
    I have a general Exchange 07-13 migration question about migrating the PF's and System Folder Information, I read somewhere that the SystemFolder info doesn't come across, can someone shed some light on this for me please?
    Thanks,
    Ray

    Hi Ray,
    Free/Busy information is stored in system public folder. If you want to decommission the Exchange 2007 Server, you need to add the replicas to Exchange 2013 Server.
    What's more, if the users use Outlook 2003, they will rely on the Free/Busy folders. If the users are using Outlook 2007 or newer, then Outlook utilizes something called the Availability Service and no longer relies on the Free/Busy folder.
    Please refer to the following article to migrate public folders from Exchange 2007 to Exchange 2013.
    Migrate Public Folders to Exchange 2013 From Previous Versions
    http://technet.microsoft.com/en-us/library/jj150486.aspx
    Besides, here is a helpful thread for your reference.
    move/migrate Public Folder from Exchange 2007 to Exchange 2010
    http://social.technet.microsoft.com/Forums/exchange/en-US/44b29a93-0149-4734-8e19-6679ad7701ce/movemigrate-public-folder-from-exchange-2007-to-exchange-2010?forum=exchange2010
    Hope it helps.
    If there are any problems, please feel free to let me know.
    Best regards,
    Amy
    Amy Wang
    TechNet Community Support

  • 2010 to 2013 Public Folder Migration - PF work in OWA but not outlook Client, password prompt?

    Hello All,
    I have migrated all public folders from Exchange 2010 Sp3 to Exchange 2013 Cu7. You can access the public folders without any problems in OWA.
    When trying to access in outlook i will get a password/username prompt. If i enter my details in this it will keep popping up even with the remember me button ticked.
    When i check the connection status i see the below the status which is "connecting" is the PF; it will never connect.
    I have done:
    Reboots
    Restart the Microsoft Exchange RPC Client Access service on the Exchange 2013 server
    Tried changing the Logon network security in the outlook client which made no difference:
    Tried logging into the outlook client as different user which made no difference
    What else can i do please?
    Help Appreciated!

    Hi,
    Please check if you have NTLM configured for Outlook Anywhere on your Exchange 2010.
    Get-OutlookAnywhere | fl Identity,*auth*
    And please check the server the public folder is trying to connect.
    Best regards,
    Belinda Ma
    TechNet Community Support

  • Exchange 2013 Public Folder Migration Problem

    Hi All,
    Wonder if any of you can assist with a public folder issue I am having with Exchange 2013. We have migrated from Exchange 2010 to 2013.
    I have followed the guide for public folder migration here
    http://technet.microsoft.com/en-us/library/jj150486(v=exchg.150).aspx
    Everything went fine and as per the document - except I had to use the "largeitemlimit" parameter to get the public folder migration to complete.
    We tested the public folder migration by adding content to public folders and creating public folders and it all appeared to be OK, we completed the migration and removed our old public folder databases from Exchange 2010.
    However we noticed later that users cannot CREATE folders in SOME public folders. It appears from some testing that any folder that does not lie in the first public folder mailbox, end users cannot create public folders.  Administrators can create them
    fine from the ECP - just not from outlook.
    It also appears some users cannot see some folders that they have permissions to.
    Can anyone assist with some ideas to resolve ?
    Thanks.

    Question?
    Are you able to create the Folder in OWA?
    Cheers,
    Gulab Prasad,
    Technology Consultant
    Blog:
    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.
    it is not functionally possible to create Public Folders in OWA user interface in Exchange 2013!.... From admin ECP it works fine!
    My Bad, that's what I was trying to say.
    Testing the same thing in the LAB, should have some update tomorrow morning.
    Cheers,
    Gulab Prasad,
    Technology Consultant
    Blog:
    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.

Maybe you are looking for