2007 SP3 to 2013 Migration - Public Folders Migration (-2147467259)

Hi Guys
I'm currently undertaking an Exchange 2007 SP3 to Exchange 2013 migration, and all has been going swimmingly so far.  We've moved all mailboxes across and are at the final stages and just want to move the public folders across.
I've been following the instructions in: http://technet.microsoft.com/en-us/library/jj150486(v=exchg.150).aspx this article, and we have gotten up to stage 5 (Start
the Migration Request).  The process gets around 20% of the way through, and from what we can tell seems to migrate all content from PF folders, however it then stops.  I've posted an extract of the log below, which should show you the error we're
currently getting (it tries then exhausts retries & stops).
16/01/2014 9:13:15 AM [EX2013] Transient error MapiExceptionUnknownUser has
occurred. The system will retry (58/60).
16/01/2014 9:13:50 AM [EX2013] The Microsoft Exchange Mailbox Replication service
'EX2013.mydomain.local' (15.0.775.35 caps:3F) is examining the request.
16/01/2014 9:13:50 AM [EX2013] Connected to target mailbox
'db1f9a09-a4ab-435e-aedf-122095797a10', database 'Shared', Mailbox server
'EX2013.mydomain.local' Version 15.0 (Build 775.0), proxy server
'EX2013.mydomain.local' 15.0.775.35 caps:07FFCB07FFFF.
16/01/2014 9:13:50 AM [EX2013] Connected to source mailbox '', database
'EX05\Public Folders\Public Folders', Mailbox server 'ex05.mydomain.local' Version
8.3 (Build 327.0).
16/01/2014 9:13:50 AM [EX2013] Request processing continued, stage LoadingMessages.
16/01/2014 9:13:50 AM [EX2013] Copying messages is finished. Copying rules and
security descriptors.
16/01/2014 9:13:51 AM [EX2013] Transient error MapiExceptionUnknownUser has
occurred. The system will retry (59/60).
16/01/2014 9:14:25 AM [EX2013] The Microsoft Exchange Mailbox Replication service
'EX2013.mydomain.local' (15.0.775.35 caps:3F) is examining the request.
16/01/2014 9:14:25 AM [EX2013] Connected to target mailbox
'db1f9a09-a4ab-435e-aedf-122095797a10', database 'Shared', Mailbox server
'EX2013.mydomain.local' Version 15.0 (Build 775.0), proxy server
'EX2013.mydomain.local' 15.0.775.35 caps:07FFCB07FFFF.
16/01/2014 9:14:25 AM [EX2013] Connected to source mailbox '', database
'EX05\Public Folders\Public Folders', Mailbox server 'ex05.mydomain.local' Version
8.3 (Build 327.0).
16/01/2014 9:14:25 AM [EX2013] Request processing continued, stage LoadingMessages.
16/01/2014 9:14:25 AM [EX2013] Copying messages is finished. Copying rules and
security descriptors.
16/01/2014 9:14:25 AM [EX2013] Transient error MapiExceptionUnknownUser has
occurred. The system will retry (60/60).
16/01/2014 9:15:00 AM [EX2013] The Microsoft Exchange Mailbox Replication service
'EX2013.mydomain.local' (15.0.775.35 caps:3F) is examining the request.
16/01/2014 9:15:00 AM [EX2013] Connected to target mailbox
'db1f9a09-a4ab-435e-aedf-122095797a10', database 'Shared', Mailbox server
'EX2013.mydomain.local' Version 15.0 (Build 775.0), proxy server
'EX2013.mydomain.local' 15.0.775.35 caps:07FFCB07FFFF.
16/01/2014 9:15:00 AM [EX2013] Connected to source mailbox '', database
'EX05\Public Folders\Public Folders', Mailbox server 'ex05.mydomain.local' Version
8.3 (Build 327.0).
16/01/2014 9:15:00 AM [EX2013] Request processing continued, stage LoadingMessages.
16/01/2014 9:15:00 AM [EX2013] Copying messages is finished. Copying rules and
security descriptors.
16/01/2014 9:15:00 AM [EX2013] The job encountered too many transient failures (60)
and is quitting.
16/01/2014 9:15:00 AM [EX2013] Fatal error MapiExceptionUnknownUser has occurred.
Furthermore, in the event log, I get the following logged as the PF migration errors out:
Request '' (d0963f2b-9d8e-4470-924a-72749ca32a36) failed.
Error code: -2147467259
MapiExceptionUnknownUser: Unable to make connection to the server. (hr=0x80004005, ec=1003)
Diagnostic context:
    Lid: 49064   dwParam: 0x1
    Lid: 37288   StoreEc: 0x6AB     
    Lid: 49064   dwParam: 0x2
    Lid: 49191   EMSMDBMT.EcDoConnectEx called [length=193]
    Lid: 65063   EMSMDBMT.EcDoConnectEx exception [rpc_status=0x6D9][latency=0]
    Lid: 62184  
    Lid: 16280   dwParam: 0x0 Msg: EEInfo: ComputerName: n/a
    Lid: 8600    dwParam: 0x0 Msg: EEInfo: ProcessID: 4744
    Lid: 12696   dwParam: 0x0 Msg: EEInfo: Generation Time: 0414-01-16T01:15:00.7170000Z
    Lid: 10648   dwParam: 0x0 Msg: EEInfo: Generating component: 2
    Lid: 14744   dwParam: 0x0 Msg: EEInfo: Status: 1753
    Lid: 9624    dwParam: 0x0 Msg: EEInfo: Detection location: 501
    Lid: 13720   dwParam: 0x0 Msg: EEInfo: Flags: 0
    Lid: 11672   dwParam: 0x0 Msg: EEInfo: NumberOfParameters: 4
    Lid: 8856    dwParam: 0x0 Msg: EEInfo: prm[0]: Unicode  string: ncacn_ip_tcp
    Lid: 8856    dwParam: 0x0 Msg: EEInfo: prm[1]: Unicode  string: EX06
    Lid: 12952   dwParam: 0x0 Msg: EEInfo: prm[2]: Long val: 3749909585
    Lid: 12952   dwParam: 0x0 Msg: EEInfo: prm[3]: Long val: 382312662
    Lid: 45169   StoreEc: 0x824     
    Lid: 50544   ClientVersion: 15.0.775.34
    Lid: 52080   StoreEc: 0x824     
    Lid: 44273  
    Lid: 49064   dwParam: 0x1
    Lid: 37288   StoreEc: 0x6AB     
    Lid: 49064   dwParam: 0x2
    Lid: 59431   EMSMDB.EcDoConnectEx called [length=193]
    Lid: 34855   EMSMDB.EcDoConnectEx returned [ec=0x3EB][length=56][latency=15]
    Lid: 59505   StoreEc: 0x3EB     
    Lid: 50544   ClientVersion: 15.0.775.34
    Lid: 52080   StoreEc: 0x3EB     
    Lid: 1494    ---- Remote Context Beg ----
    Lid: 22086  
    Lid: 27206  
    Lid: 17990  
    Lid: 16966   StoreEc: 0x8004010F
    Lid: 32121   StoreEc: 0x3EB     
    Lid: 9486    StoreEc: 0x3EB     
    Lid: 1750    ---- Remote Context End ----
    Lid: 51152  
    Lid: 52465   StoreEc: 0x3EB     
    Lid: 60065  
    Lid: 33777   StoreEc: 0x3EB     
    Lid: 59805  
    Lid: 52487   StoreEc: 0x3EB     
    Lid: 19778  
    Lid: 27970   StoreEc: 0x3EB     
    Lid: 17730  
    Lid: 25922   StoreEc: 0x3EB     
Context:
Operation: ISourceMailbox.GetFolder
Operation: ISourceMailbox.GetFolder
OperationSide: Source
Public Folders ()
EntryIDs: [count:1, [len=46, data=000000001A447390AA6611CD9BC800AA002FC45A0300E76376BFA766CD4CB9725A08AC252BC90000000027220000]]
Folder: 'Public Root/NON_IPM_SUBTREE/StoreEvents{93ED8190-881A-40D2-B0FD-3615ADEB16CE}', entryId [len=46, data=000000001A447390AA6611CD9BC800AA002FC45A0300E76376BFA766CD4CB9725A08AC252BC90000000027220000], parentId [len=46, data=000000001A447390AA6611CD9BC800AA002FC45A03007943AF354860F8418A0338BB019906EE0000000000020000]
I've attempted to find some solutions, and searching for the respective error codes has suggested a couple of ideas, such as not being a PF Admin (checked), resource issues on source/destination servers (checked, and restarted for good measure), I saw mention
of a problem with NETBIOS resolution so added the source server into the host files (checked).
Any assistance would be greatly appreciated
Cheers

Hello,
Thank you for your post.
This is a quick note to let you know that we are performing research on this issue.
Thanks,
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected]
Simon Wu
TechNet Community Support

Similar Messages

  • Migrating Exchange server from 2007 SP3 to 2013

    Hi All,
    We are planning to migrate our exchange server 2007 SP3 to 2013 , what are all the best options available?
    Thanks,
    Mani L
    Mani L

    Hi,
    Here are some articles which can help you to migrate from Exchange 2007 to Exchange 2013 for your reference.
    Upgrade from Exchange 2007 to Exchange 2013
    http://technet.microsoft.com/en-us/library/jj898581(v=exchg.150).aspx
    Checklist: Upgrade from Exchange 2007
    http://technet.microsoft.com/en-us/library/ff805032(v=exchg.150).aspx
    Install Exchange 2013 in an Existing Exchange 2007 Organization
    http://technet.microsoft.com/en-us/library/jj898582(v=exchg.150).aspx
    Hope this helps.
    Best regards,
    Belinda
    Belinda Ma
    TechNet Community Support

  • Migrating public folders to exchange 2013 hebrew issue

    I am migrating public folders to exchange 2013. half of them a named in hebrew.
    The migration fails, the error is character  related. 
    Is it possible at all to migrate hebrew named public folders?

    Hi,
    Did you got the error message mentioned in the following thread?
    http://social.technet.microsoft.com/Forums/exchange/en-US/8b383a46-b710-4fc0-aa0b-e52f288cf93d/e2010-to-e2013-public-folders-migration-failed?forum=exchangesvrdeploy
    If so, please check if they are mail-enabled public folders. If they are mail-enabled public folders, please make sure there are no invalid characters in alias.
    Based on the description, you couldn't migrate public folders named in Hebrew, other public folders could be moved successfully. If I misunderstood your concern, please let me know.
    If the issue persists, I'm afraid you need to rename these public folders in English.
    Best regards,
    Belinda
    Belinda Ma
    TechNet Community Support

  • Users unable to create or delete folders in migrated public folders using Outlook

    We have an Exchange 2013 CU3 environment migrated from Exchange 2007.
    The public folder migration was completed over the weekend.
    The environment has several public folder mailboxes.
    Post migration users are unable to create/delete new sub folders,  or modify permissions using Outlook on any of the migrated public folders.  Users can however create new top level folders using outlook. They can also create and delete new posts
    in migrated public folders.
    Admins are able to create folders and set permissions on migrated folders using the EAC.
    Test User accounts used for testing are set to use the Primary Hierarchy mailbox as their default public folder mailbox.
    Test Users have been given Owner permissions from the root down on the folders we are testing with.
    We have tested with Outlook 2010 and 2013 getting the same "Cannot create the folder" error.

    Further testing
    We moved a top level folder from a secondary PF mailbox to the primary PF mailbox using the New-PublicFolderMoveRequest command in powershell.
    After the move completed we could create new folders under the moved top level folder.
    The top level folder that was moved had it's own sub-folders that we did not move to the primary mailbox. (We didn't move the whole branch.. Just the top level folder)
    We still cannot create or modify the existing sub-folders after moving the top level folder.
    We then moved the newly created sub-folder to a secondary PF mailbox.
    At that point we could no longer create sub-folders in the folder form outlook.
    From what I can tell you can only create new sub-folders in folders homed to the primary PF mailbox when using outlook.
    Is this a bug or as designed?
    According to this Tech ed presentation Clients connecting to a secondary PF mailbox should have folder changes proxy to the primary PF mailbox.. (See slide 10)
    http://channel9.msdn.com/Events/TechEd/NorthAmerica/2013/OUC-B329#fbid=
    Update : 2-5-2014
    Not much new to report other than it appears that users need to be homed to the primary PF mailbox to delete calendar meetings.
    Opened a ticket with Premier support.
    Update 2-11-2014
    Premier support continues to look into the issue. No ideas as to the cause yet.
    2-24-13
    Still no resolution from support or even a clue what is causing this.

  • Migrating Public folders Fatal error MapiExceptionNoReplicaAvailable

    I am trying to migrate our public folders from our old 2010 server to the new 2013 one. I have created the folders (one) as per instructions and can see the structure under the name "Public" with "Mailbox1" in ecp but when I run the command
    to migrate and run the check I see the error referred to above.
    The full output from the get-statistics command is
    RunspaceId                       : b6e18ee6-c158-40d7-a6a6-18b04c3d43d9
    Name                             : PublicFolderMigration
    Status                           : Failed
    StatusDetail                     : FailedMAPI
    SyncStage                        : CreatingFolderHierarchy
    Flags                            : IntraOrg, Pull, Suspend, SuspendWhenReadyToComplete
    RequestStyle                     : IntraOrg
    Direction                        : Pull
    Protect                          : False
    Priority                         : Normal
    Suspend                          : True
    SourceVersion                    : Version 14.3 (Build 123.0)
    SourceDatabase                   : Public_Folders
    SourceServer                     : EXCSRV03.Walton.local
    BatchName                        :
    OutlookAnywhereHostName          :
    RemoteCredentialUsername         :
    AuthenticationMethod             : Basic
    RemoteMailboxLegacyDN            :
    RemoteMailboxServerLegacyDN      :
    BadItemLimit                     : 0
    BadItemsEncountered              : 0
    LargeItemLimit                   : 0
    LargeItemsEncountered            : 0
    FolderToMailboxMap               : {\}
    QueuedTimestamp                  : 2/22/2014 10:18:37 AM
    StartTimestamp                   : 2/22/2014 10:18:43 AM
    LastUpdateTimestamp              : 2/22/2014 10:18:46 AM
    InitialSeedingCompletedTimestamp :
    FinalSyncTimestamp               :
    CompletionTimestamp              :
    SuspendedTimestamp               :
    OverallDuration                  : 01:10:03
    TotalFinalizationDuration        :
    TotalDataReplicationWaitDuration :
    TotalSuspendedDuration           :
    TotalFailedDuration              : 01:09:54
    TotalQueuedDuration              : 00:00:03
    TotalInProgressDuration          : 00:00:06
    TotalStalledDueToCIDuration      :
    TotalStalledDueToHADuration      :
    TotalStalledDueToReadThrottle    :
    TotalStalledDueToWriteThrottle   :
    TotalStalledDueToReadCpu         :
    TotalStalledDueToWriteCpu        :
    TotalStalledDueToReadUnknown     :
    TotalStalledDueToWriteUnknown    :
    TotalTransientFailureDuration    :
    TotalIdleDuration                : 00:00:02
    MRSServerName                    :
    EstimatedTransferSize            : 0 B (0 bytes)
    EstimatedTransferItemCount       : 0
    BytesTransferred                 : 0 B (0 bytes)
    BytesTransferredPerMinute        :
    ItemsTransferred                 : 0
    PercentComplete                  : 10
    PositionInQueue                  :
    PreventCompletion                : True
    FailureCode                      : -2147467259
    FailureType                      : MapiExceptionNoReplicaAvailable
    FailureSide                      : Source
    Message                          : Error: MapiExceptionNoReplicaAvailable: Unable to get replica list for the folder.
                                       (hr=0x80004005, ec=1129)
                                       Diagnostic context:
                                           Lid: 40487   EMSMDBMT.EcDoRpcExt2
    called [length=53]
                                           Lid: 56871   EMSMDBMT.EcDoRpcExt2
    returned [ec=0x0][length=192][latency=15]
                                           Lid: 52176   ClientVersion:
    15.0.516.30
                                           Lid: 50032   ServerVersion:
    14.3.123.2
                                           Lid: 23226   --- ROP
    Parse Start ---
                                           Lid: 27962   ROP:
    ropGetOwningMDBs [66]
                                           Lid: 17082   ROP Error:
    0x469    
                                           Lid: 18017 
                                           Lid: 21921   StoreEc:
    0x469    
                                           Lid: 27962   ROP:
    ropExtendedError [250]
                                           Lid: 1494   
    ---- Remote Context Beg ----
                                           Lid: 26426   ROP:
    ropGetOwningMDBs [66]
                                           Lid: 3010   
    StoreEc: 0x8004010F
                                           Lid: 3010   
    StoreEc: 0x8004010F
                                           Lid: 3650   
    StoreEc: 0x8004010F
                                           Lid: 53151 
                                           Lid: 1750   
    ---- Remote Context End ----
                                           Lid: 26849 
                                           Lid: 21817   ROP Failure:
    0x469    
                                           Lid: 16814 
                                           Lid: 20910   StoreEc:
    0x469    
                                           Lid: 61040 
                                           Lid: 61104   StoreEc:
    0x469    
    FailureTimestamp                 : 2/22/2014 10:18:46 AM
    IsValid                          : True
    ValidationMessage                :
    OrganizationId                   :
    RequestGuid                      : 9929f03f-d4a3-4a1d-945c-22d8bf04d3ca
    RequestQueue                     : Staff_2014
    ExchangeGuid                     : 4db20d25-f308-42d9-83f2-4c104e4aed62
    Identity                         : RequestGuid (9929f03f-d4a3-4a1d-945c-22d8bf04d3ca), RequestQueue:
                                       (6a17b86c-969d-4c16-8210-1d52a28eaa76)
    Report                           : 2/22/2014 10:18:36 AM [EXCSRV05] 'Walton.local/Technicians/Jonathan RUBINSTEIN'
                                       created request.
                                       2/22/2014 10:18:42 AM [EXCSRV05] The Microsoft Exchange
    Mailbox Replication service
                                       'EXCSRV05.Walton.local' (15.0.516.29 caps:3F) is examining
    the request.
                                       2/22/2014 10:18:42 AM [EXCSRV05] Connected to target
    mailbox 'Public Folders
                                       (4db20d25-f308-42d9-83f2-4c104e4aed62)', database 'Staff_2014',
    Mailbox server
                                       'EXCSRV05.Walton.local' Version 15.0 (Build 516.0),
    proxy server
                                       'EXCSRV05.Walton.local' 15.0.516.29 caps:03DF07FFFF.
                                       2/22/2014 10:18:42 AM [EXCSRV05] Connected to target
    mailbox 'Public Folders
                                       (309db159-1c82-407f-a8f2-5e3be77323da)', database 'Staff_2014',
    Mailbox server
                                       'EXCSRV05.Walton.local' Version 15.0 (Build 516.0),
    proxy server
                                       'EXCSRV05.Walton.local' 15.0.516.29 caps:03DF07FFFF.
                                       2/22/2014 10:18:42 AM [EXCSRV05] Connected to source
    mailbox 'Public Folders ()',
                                       database 'Public_Folders', Mailbox server 'EXCSRV03.Walton.local'
    Version 14.3
                                       (Build 123.0).
                                       2/22/2014 10:18:42 AM [EXCSRV05] Connected to source
    mailbox 'Public Folders ()',
                                       database 'Public_Folders', Mailbox server 'EXCSRV03.Walton.local'
    Version 14.3
                                       (Build 123.0).
                                       2/22/2014 10:18:43 AM [EXCSRV05] Request processing
    started.
                                       2/22/2014 10:18:43 AM [EXCSRV05] Mailbox signature will
    not be preserved for
                                       mailbox 'Public Folders ()'. Outlook clients will need
    to restart to access the
                                       moved mailbox.
                                       2/22/2014 10:18:43 AM [EXCSRV05] Mailbox signature will
    not be preserved for
                                       mailbox 'Public Folders ()'. Outlook clients will need
    to restart to access the
                                       moved mailbox.
                                       2/22/2014 10:18:45 AM [EXCSRV05] Stage: CreatingFolderHierarchy.
    Percent complete:
                                       10.
                                       2/22/2014 10:18:46 AM [EXCSRV05] Fatal error MapiExceptionNoReplicaAvailable
    has
                                       occurred.
    ObjectState                      : New
    We only use one or our existing public folders and I'm wondering about simply unlocking the structure and restoring the emails from Veeam backup.  I need to get rid of the old exchange server for disk space.  However I'd really like to get the
    migration done properly in case we turn out to need some further stuff.
    Is there any way to debug this issue and get the migration done?
    Many thanks

    Hi Jay,
    This issue occurs because there are some legacy system folders in the public folder database. 
    To resolve this issue, follow these steps:
    Open the Public Folder Management Console. 
    Expand and then click System Public Folders so that it is highlighted and populates the Result pane. 
    Right-click schema-root and then select Remove.
    Right-click all "OWAscratchpad" entries and then select Remove.
    Migrate public folders to Exchange Server 2013. For more information about how to do this, refer to the following Microsoft TechNet article:
    Migrate public folders to Exchange 2013 from previous versions
    More details in the following KB:
    Cannot replicate public folder to Exchange Server 2013
    http://support.microsoft.com/kb/2866631
    Hope it is helpful
    Thanks
    Mavis
    Mavis Huang
    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

  • Migrating Public Folders on Exchange Server 2007 SP1 to Exchange Online\Office 365

    Hello,
    Our company is looking to migrate from Exchange 2007 on premises to Exchange Online/Office 365. We have a number of public folders on our exchange server that function similarly to how the new shared mailboxes work in Exchange Online. That is to say that
    we have many outside users (customers and wholesale dealers) emailing this public folder ([email protected]) and our end users are given permission to view and respond as themselves ([email protected]). I've been looking all over but haven't found a clean
    way to migrate the current public folders directly into shared mailboxes. I'd just start from scratch, but we want to keep the records of the emails we've received at these public folders for customer support reasons. Can anyone help?

    Hi psh8989,
    According to your description, I know that you want to migrate public folder from Exchange 2007 to Office 365.
    Since Office 365 is different from Exchange On-Premises, I suggest ask Office 365 Forum for help so that you can get more professional suggestions. For your convenience:
    http://community.office365.com/en-us/default.aspx
    However, I can also share some information for your reference : )
    Based on my knowledge, Exchange supports moving your public folders to Office 365 and Exchange Online from Exchange 2007 SP3 RU10 or later. I notice that your Exchange server version is SP1, please upgrade to SP3 RU10 first and perform migration.
    More detailed information to see:
    Migrate legacy public folders to Office 365 and Exchange Online 
    http://technet.microsoft.com/en-us/library/jj983799(v=exchg.150).aspx
    Thanks
    Mavis Huang
    TechNet Community Support

  • Accounts made in o365 can't access legacy public folders - Migrated through 2010/2013 Hybrid can access

    We've added two 2013 hybrid servers to our existing 2010 environment.  Added the CAS role to all 2010 mailbox servers per ( https://technet.microsoft.com/en-us/library/dn249373%28v=exchg.150%29.aspx ) and currently have public folders (located on our
    2010 mailbox servers) working in Outlook client for users whose mailboxes have been migrated from on-prem 2010 to o365.  The problem is when we create a new user in o365, that user CAN see that we have public folders via Outlook client, but when we expand
    the public folder list a credential window pops up and will not accept any set of credentials (even those of working hybrid migrated accounts).
    We are following this method when creating new o365 accounts:
    1) Make a user in AD
    2) Dirsync the user
    3) License the user for exchange
    4) Run on on-prem mailbox server via Exchange Management Shell: Enable-RemoteMailbox "[email protected]" -RemoteRoutingAddress "[email protected]"
    5) In o365 Remote Exchange Powershell run: Get-Mailbox -identity "[email protected]" |fl Identity,ExchangeGUID
    6) Copy ExchangeGUID
    7) Back on on-prem mailbox server via Exchange Management Shell: Set-RemoteMailbox "[email protected]" -ExchangeGUID <paste GUID here>
    8) Dirsync the user again
    I've compared two Remote User Mailboxes, ones that were migrated via Hybrid, and ones that were created in o365 and the settings look identical outside of the attribute "RemoteRecipientType" is set to Migrated vs ProvisionMailbox.  I'm not
    sure what else the difference in these accounts could possibly be that would be causing this credential failure.
    Any thoughts would be appreciated.

    Hi,
    Please do the following steps to create an Exchange Online mailbox in your Hybrid environment:
    Method 1: Create a remote mailbox for an existing user.
    If you already have created a user in Active Directory, and the user has already been synced to online with license, we can give that user a mailbox in Exchange Online by using the Exchange Management Shell cmdlet Enable-RemoteMailbox on
    your on-premise Exchange server:
    Get-User “User1” | Enable-RemoteMailbox
    Then the mailbox is enabled with an Exchange Online mailbox. We can check the mailbox by running the following command in On-premise Exchange server:
    Get-RemoteMailbox “Test1” | FL *address*
    Method 2: Directly create a new remote mailbox.
    1. Create the remote mailbox in On-premise Exchange server by running:
    $Credentials = Get-Credential
    New-RemoteMailbox -Name "Test2" -Password $Credentials.Password -UserPrincipalName
    [email protected]
    2. Launch dirsync and assign a license to the newly created user with Office 365 account.
    Then Test2 can sign in, using his on premises credentials, and open his online mailbox.
    For more information about the remote mailbox, please refer to:
    http://blogs.technet.com/b/ilvancri/archive/2011/08/24/exchange-online-exchange-on-premises-shared-namespace-how-about-mail-routing.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 to new shared mailbox & Mailboximprotrequesthelp.

    hi i have several public folders stored within the exchange mailbox database, i am wanting to migrate over to shared mailbox's as i find them easier to look after.
    i already have mail flowing to the new shared mailbox's so nothing goes to the public folders as i disabled mail-enabled
    what i now want to do is take all of the old emails and import them into the shared mailbox's.
    i can do it via PST export in outlook and mailboximportrequest, this works but it creates an odd folder structure, if i use the following command it creates the folder IPM_SUBTREE folder in testmove inbox then in the IPM_SUBTREE folder is the inbox that
    contains the emails so it goes Testmove > inbox > IPM_SUBTREE > inbox > emails
    New-MailboxImportRequest -Mailbox testmove -FilePath "\\exchangeserver\publicfolders\testmove.pst" -TargetRootFolder "inbox" -Verbose
    is there a way of either cleaning up the folder structure or another way around doing the import / export as this seems a bit of a messy way of doing it, considering when i do the real public folders they have emails going back to 2010 so thousands and thousands
    of them.
    Many Thanks

    Ed is correct and if you are looking for a 3rd party tool that will allow you to accomplish this check out Lucid8's DigiScope
    http://www.lucid8.com/product/digiscope.asp as it can do what you desire and much more
    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

  • SBS2003- SBS2011 migration - public folders still replicating...

    Doing a SBS2003 to SBS2011 migration using the MS method.  All is going well so far except the public folder replication is taking forever.  I've done all the tricks like increasing the replication priority and limits but it's still going (I think,
    anyways, it's hard to tell sometimes).  The public folder instances still shows several pages of folders although about two thirds of the folders have moved so at least it's working (I hope).  A few questions regarding my situation:
    1) Is it OK to execute the "Move all replicas" command in SBS2003 ESE again?  Or should I goto the SBS2011 and try the MoveAllReplicas.ps1 exchange powershell command?
    2) Can I move onto the next steps of moving the OWA and moving the actual mailboxes?  It would save me time if I could just continue and get back to this later.
    3) Any other tips on how to compare the two public folder stores and be sure they all got transferred?
    Thanks.
    -- Al

    The replication takes time if you have a lot of public folders. Good you have it working though, since you said most of the folders have moved over.
    1) Yes, it is safe, go ahead. The powershell command in destination doesn't work with the legacy source server as I recall.
    2) Yes, you can move mailboxes and public folders at the same time. Go ahead and proceed and let the PF's replicate in the background
    3) The folders are transferred properly when they disappear from the SBS2003 ESM PF instances. To see the status of the migrated folders in the target server, get a script from here:
    http://blog.mikewalker.me/2013/05/exchange-2010-public-folder-replication.html. But the move needs to be initiated and controlled from the source ESM.
    Additional tips:
    - if you think the replication has stalled, you can debug it by enabling logging on the Default SMTP Connector in the target server. If you see replication related messages in the logs, the replication should be working.
    - check that the target message size limits (in SMTP connector and in database) are not preventing the replication if you have large items in your PF database
    - sometimes the values in the source server PF replication settings are blank. Set default values + always run if that is the case
    - sometimes it helps with some folders that won't move, if you go to destination server EMC and mail disable them.
    - redoing "move all replicas" and a reboot of the source helps occasionally too

  • Migrating Public folders, can't log in

    We are using a Linux Sles 10 Server with GW 7.02 beta. User migrations work
    fine. We pre-create them and then update the Data Migration CSV file with
    their User ID and Password assigned when they were created. Security is set
    to low. However, we can figure out how to migrate the public folders. All
    we get is "can't log in".
    Ideas would greatly be appreciated as this is our last piece in moving from
    Exchange to Groupwise.

    I can't remember exactly how this works, but public folders get migrated to GroupWise as folders that are owned by a 'resource' object, and everyone is given rights to proxy into the resource's account. Resource objects in GroupWise need to have an 'owner' that is a valid GroupWise user. So, if you're having login issues, it may be something to do with the owner of the resource. The utility needs to log in as the user in order to make changes, so it needs to have the owning user's password available.
    Is the owner of the resource(s) that will house the folders included in the CSV file? Is the password specified there?
    It seems like if you let the utility create the users and generate random passwords it goes pretty smoothly. You don't have to manually edit the CSV file in that case.
    >>> Pat H.<[email protected]> 4/12/07 7:17 PM >>>
    We are using a Linux Sles 10 Server with GW 7.02 beta. User migrations work
    fine. We pre-create them and then update the Data Migration CSV file with
    their User ID and Password assigned when they were created. Security is set
    to low. However, we can figure out how to migrate the public folders. All
    we get is "can't log in".
    Ideas would greatly be appreciated as this is our last piece in moving from
    Exchange to Groupwise.

  • Exchange 2010 - Decommissioning Exchange 2007 Coexistence and Removal of Public Folders

    We are about to decommission exchange 2007, currently in coexistence with Exchange 2010.
    We do not want to use ANY public folders in exchange 2010 going forward. Will do this after decom of 2007:
    http://technet.microsoft.com/en-us/library/dd876883(v=exchg.141).aspx
    I see this in the outlook connection status in outlook:
    I have changed all Exchange 2010 mailbox databases to use a temporary 2010 public folders db named "public1" so that it is not communicating with the 2007 mailbox virtual server. However, the exact same connection status appears after I changed
    the 2010 mailbox DBs to use a 2010 public folder db instead of the old 2007.
    Question is, is it safe to decom the 2007 environment now? Is it normal to still have a connection to 2007  in "connection status" in outlook when the users mailbox is on a 2010 mailbox db? Is this connection related to public folders or something
    else that needs modified before decom?
    Thanks,
    Josh

    So, that wasn't the answer. I switched the Public folder DB on each mailbox database to a exchange 2010 server, PF DB, but hadn't actually moved any data from 2007 to 2010. 
    I didnt realize this is needed when we don't use public folders except for free-busy, default, etc.
    What is the correct way to move the default public folders to a 2010 public folder?
    I'm using the below URL as a template to migrate this info to a 2010 PF db.
    https://www.simple-talk.com/sysadmin/exchange/upgrade-from-exchange-2007-to-exchange-2010---part-ii/
    "The user Public Folders then need to be replicated to the Exchange 2010 Public Folder database as well. It is possible to manually configure
    all Public Folders with a new replication partner, but it’s better to use PowerShell scripts that Microsoft delivers with Exchange Server 2010. Open the Exchange Management Shell and navigate to the Scripts directory
    by entering the CD $ExScripts command,
    and execute the following script:
    AddReplicaToPFRecursive.ps1 -Server 2007MBX -TopPublicFolder "\" 
    -ServerToAdd 2010MBX"
    My question is, do I have to do this "3rd step" since I don't think i have any custom "user public folders". Is this the user's free busy that I have to migrate, or is this author referring to custom PF db info?
    Do I have to have public folders for free-busy and default exchange services at all in 2010?

  • Outlook 2007 Outlook Anywhere Clients - No Public Folders?

    I have MS Outlook 2007 clients connecting to an Exchange 2013 server using Outlook Anywhere. My problem is that I can't see the Public Folders section in the Folder list (I'm sure I'm viewing the Folder list and not the Mail view). Any ideas why this is
    the case?

    What does your connection status window show? Does is show "connecting" for public folders? This might point to a network or DNS resolution issue especially if it works fine in a different location. 
    http://technet.microsoft.com/en-us/library/bb123650(v=exchg.65).aspx
    DJ Grijalva | MCITP: EMA 2007/2010 SPA 2010 | www.persistentcerebro.com
    It says "Connected to Microsoft Exchange". No indication it is trying to connect and we aren't having any other issues with the connection.
    Just to clarify: For all our computers on our domain at our location, the Public Folders section shows up. For remote users that are connecting via Outlook Anywhere the Public Folders section is gone. Not even certain folders within that - the whole section
    just doesn't show up like my screenshot shows. Weird.
    Should there be a Public Folders section in OWA? If I'm not seeing it there I guess it would make sense that my remote users connecting via Outlook Anywhere wouldn't be seeing it?

  • Exchange 2013 SP1: Public Folders in OWA

    Hello!
    Tell me please should I be able to use Public Folders in OWA 2013 SP1? I can see them on People tab of OWA, I can send mail to them, but I don't see them on Mail tab (in the folder tree):
    Thank you in advance,
    Michael

    Hello,
    In Exchange 2013 OWA, we can only see public folders on Directory by default. If you add public folder under Favorites, please follow the Martina's suggestion.
    Besides, you can't create or delete public folders.
    If you have any feedback on our support, please click
    here
    Cara Chen
    TechNet Community Support

  • Issue after public folders migration Ex 2013 Cu3

    Hello,
    after successful PF migration, Ex2010 to Ex2013 I could see everything working from Outlook.
    Anyway, I wanted at the very end to compare folder statistics and permissions against legacy settings.
    Unfortunately, at about 600 folders I could get error:
    The security principal specified is already on the permission set.
    I've checked one of affected folders via Outlook / Folder Permissions and could see doubled entries for same identity (imagine, two times the same account with the same Owner permissions) I've tried to delete it ;) but the result is that folder
    lost completely the permissions and I can NOT change it over shell, ECP or Outlook anymore even I was the former owner.
    So, is there something like ExFolders so I could reset the ACL on the affected folder ? It is quite urgent for me as I need to decide if I should do rollback or keep it as it is risking some future issues ... 
    Thanks
    Peter
    PeBe

    Hi,
    As we know, ExFolders is not updated.and it is not supported for exchange 2013 currently.
    I recommend you can create a script to re-add the permissions for all the folders. 
    If needs urgent, I recommend you post the requirement on Script forums :
    http://social.technet.microsoft.com/Forums/scriptcenter/en-US/home?category=scripting
    Thanks.
    Niko Cheng
    TechNet Community Support

Maybe you are looking for