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.

Similar Messages

  • 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

  • Move mailboxes and public folders from exchange 2007 to Exchange 2013

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

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

  • Public folders from exchange 2007 to exchange 2013

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

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

  • Exchange 2013 users cant connect to public folders on Exchange 2010

    Hi
    I recently migrated all users from exchange 2010 to 2013 and now nobody can connect to public folders. 
    Ive read several forums with similar issue, but none of the solutions have fixed my problem.
    My configuration on exchange 2013:
    ExternalClientAuthenticationMethod : Ntlm
    InternalClientAuthenticationMethod : Ntlm
    IISAuthenticationMethods           : {Basic, Ntlm, Negotiate}
    ive also removed negotiation from the rpc site on the IIS.
    Is there something else im missing?
    Thanks
    /Carlos

    Are you getting any error message when accessing the Public Folder?
    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.

  • 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

  • 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.

  • OWA still lands at Exchange 2010 for users migrated from Exchange 2010 to 2013

    I never had any issues with OWA redirection for a few users that I migrated from Exchange 2010-2013 initially. For users that I am migrating in the past few days, the OWA 2013 is landing on Exchange 2010 despite the mailbox being successfully migrated to
    Exchange 2013.
    Troubleshooting:
    1. I have restarted the IIS Services
    2. I have restarted MSExchangeOWAAppPool.
    3. I have also checked the homeMDB attribute of the 2013 migrated user with the Exchange 2013 database.
    I would really appreciate if anyone could share their experiences on similar issues.

    I have checked it, the migration status is completed. In regard to the namespaces, both CAS 2010 and 2013 are set to mail.domain.com; CAS 2013 is the internet facing. I have also checked the internal access for OWA, it's the same scenario. Migrating them
    back to 2010 and 2013 won't resolve the issue in my case, because the issue persists for every new user that I am migrating.
    I recently found the following when I login with a user who is not effected and then logout:
    1. Login in back with the affected user without closing the browser or clearing the cache, it lands at CAS 2013 OWA.
    2. However, I get the below listed error message when I logout. 
    Your request couldn't be completed.
    Click here to continue working.
    This may have occurred for security reasons or because your session timed out.

  • Copy UCC from Exchange 2010 to 2013

    I'm starting to setup my Exchange 2013 server. I'm able to migrate users from 2010 and access their mailbox. I'd like to export the UCC SSL cert from 2010 to 2013. The cert if from GoDaddy. Do I need to add the SAN name of the new Exchange 2013 server to
    the certificate? If so, how will that affect my 2010 server?
    Is the process to export from Exchange 2010 and do an import on the 2013 server? What else am I missing? 

    Hi,
    Do you access the 2013 FE server’s address and log on a Exchange 2010 user? If so, it is a expected behavior, see below:
    http://technet.microsoft.com/en-us/library/bb310763(v=exchg.141).aspx
    If an Exchange 2013 user log on the Exchange 2013 OWA but he is still redirected to the Exchange 2010 OWA, I suggest we check the redirection setting on the Exchange 2013 ‘s Default
    web site and OWA Virtual Directory.
    Regards,
    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

  • Removing Public Folders from Exchange 2007

    Hello
    I am part way through migrating from Exch 2007 to 2010.
    All my mailboxes are over and the new server is working as I want it to.  The problem has come when trying to un-install the 2007 server.  I get the following error:
    Summary: 3 item(s). 2 succeeded, 1 failed. 
    Elapsed time: 00:00:20
    Mailbox Role Prerequisites
    Failed
    Error:
    Uninstall cannot continue. Database 'Public Folder Database': The public folder database "JUPITER\Second Storage Group\Public Folder Database" contains folder replicas. Before deleting the public folder database, remove the folders or move the replicas to
    another public folder database. For detailed instructions about how to remove a public folder database, see http://go.microsoft.com/fwlink/?linkid=81409.
    Recommended Action: http://go.microsoft.com/fwlink/?linkid=30939&l=en&v=ExBPA.12&id=b6e3b32a-8848-46cb-9567-72288ac15f60
    I've gone round google at least 3 times now reading posts about moving the mailboxes and force-able removing them but nothing works and the folders remain.  Below is what I get when trying to follow the standard process of moving them.
    [PS] C:\Windows\system32>MoveAllReplicas -Server Old -newserver new
    Set-PublicFolder : The parameter "Replicas" cannot be $null or an empty array.
    At C:\Program Files\Microsoft\Exchange Server\Scripts\ReplaceReplicaOnPFRecursi
    ve.ps1:147 char:24
    +         $_ | set-publicfolder <<<<  -server $_.OriginatingServer;
        + CategoryInfo          : InvalidOperation: (\NON_IPM_SUBTRE...ne Address
       Book:PublicFolderId) [Set-PublicFolder], InvalidOperationException
        + FullyQualifiedErrorId : 7492CDDB,Microsoft.Exchange.Management.MapiTasks
       .SetPublicFolder 
    I'm not the most experienced exchange admin so it could be something simple ive over looked.
    Thanks in advance.

    If you can confirm the PF's have been replicated properly and rehomed to the Exchange 2010 Server then you can just manually remove the Ex2007 PF store, I have had to do this a few times so I could just get the Ex2007 uninstall to proceed.
    In ADSIEdit, go to Configuration, Configuration, Services, Microsoft Exchange, FirstOrganization, Administrative Groups, Exchange Administrative Group, Servers, Servername, Information Store, First Storage Group.  Then on the right hand pane, highlight
    the Public Folder Store and Delete it.MVP Exchange Server

  • Problems with Public Folders in Exchange 2010

    Last month I upgraded my servers from 2000 to 2010. The route I took for exchange was 2000 -> 2003 -> 2010. Everything went fairly smooth and I have had no real problems until this week. (I have uninstalled the older exchange servers.) I have been
    trying to clean out some of the remnants that have been left over from the older servers (for whatever reason the uninstall did not remove the information on the new server). I used ASDI edit to remove some old information that was pointing to the old exchange
    server (First Administration Group I think it was called).
    After that I upgraded to SP1 and Rollup 1. The Public folder database no longer appears under Organization Configuration, Mailbox. I am not sure if it was there after my deletion or not, so I am unsure if the problem is caused by my deletions or the upgrade.
    I followed the instructions found here, http://technet.microsoft.com/en-us/library/bb727370%28EXCHG.80,printer%29.aspx . The CN=Public folders was found in CN=Folder Hierarchies. However
    msExchOwningPFTree is greyed out, so I cannot update it. I have tried to delete it and remake it, same thing.
    I also get the following events which I am assuming is caused by the Public Folders database not being mounted:
    Log Name:      Application
    Source:        MSExchangeRepl
    Date:          10/28/2010 11:03:51 AM
    Event ID:      3154
    Task Category: Service
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      sachdc00001.sunshineacres.local
    Description:
    Active Manager failed to mount database Public Folder Database 1678798462 on server sachdc00001.sunshineacres.local. Error: An Active Manager operation failed with a transient error. Please retry the operation. Error: Database action failed with transient error.
    Error: A transient error occurred during a database operation. Error: MapiExceptionADPropertyError: Unable to mount database. (hr=0x80004005, ec=2418)
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="MSExchangeRepl" />
        <EventID Qualifiers="49156">3154</EventID>
        <Level>2</Level>
        <Task>1</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2010-10-28T18:03:51.000000000Z" />
        <EventRecordID>42074</EventRecordID>
        <Channel>Application</Channel>
        <Computer>sachdc00001.sunshineacres.local</Computer>
        <Security />
      </System>
      <EventData>
        <Data>Public Folder Database 1678798462</Data>
        <Data>sachdc00001.sunshineacres.local</Data>
        <Data>An Active Manager operation failed with a transient error. Please retry the operation. Error: Database action failed with transient error. Error: A transient error occurred during a database operation. Error: MapiExceptionADPropertyError:
    Unable to mount database. (hr=0x80004005, ec=2418)
    </Data>
      </EventData>
    </Event>
    Log Name:      Application
    Source:        ExchangeStoreDB
    Date:          10/28/2010 11:03:51 AM
    Event ID:      231
    Task Category: Database recovery
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      sachdc00001.sunshineacres.local
    Description:
    At '10/28/2010 11:03:51 AM', the copy of database 'Public Folder Database 1678798462' on this server encountered an error during the mount operation. For more information, consult the Event log on the server for "ExchangeStoreDb" or "MSExchangeRepl"
    events. The mount operation will be tried again automatically.
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="ExchangeStoreDB" />
        <EventID Qualifiers="49156">231</EventID>
        <Level>2</Level>
        <Task>1</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2010-10-28T18:03:51.000000000Z" />
        <EventRecordID>42073</EventRecordID>
        <Channel>Application</Channel>
        <Computer>sachdc00001.sunshineacres.local</Computer>
        <Security />
      </System>
      <EventData>
        <Data>Public Folder Database 1678798462</Data>
        <Data>0855badd-62f3-421f-9175-86cf26891c8a</Data>
        <Data>Store</Data>
        <Data>GenericMountFailure</Data>
        <Data>
        </Data>
        <Data>Store</Data>
        <Data>There is only one copy of this mailbox database (Public Folder Database 1678798462). Automatic recovery is not available.</Data>
        <Data>10/28/2010 11:03:51 AM</Data>
      </EventData>
    </Event>
    Log Name:      Application
    Source:        MSExchangeIS
    Date:          10/28/2010 11:03:51 AM
    Event ID:      9519
    Task Category: General
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      sachdc00001.sunshineacres.local
    Description:
    While starting database 0855badd-62f3-421f-9175-86cf26891c8a, the following error occurred: 0x972. 
    Look up of DB Info failed.
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="MSExchangeIS" />
        <EventID Qualifiers="49158">9519</EventID>
        <Level>2</Level>
        <Task>6</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2010-10-28T18:03:51.000000000Z" />
        <EventRecordID>42072</EventRecordID>
        <Channel>Application</Channel>
        <Computer>sachdc00001.sunshineacres.local</Computer>
        <Security />
      </System>
      <EventData>
        <Data>0x972</Data>
        <Data>0855badd-62f3-421f-9175-86cf26891c8a</Data>
        <Data>Look up of DB Info failed</Data>
        <Binary>5B444941475F4354585D00002E000000FF8C170000000000000220000000496340107209000068284010720900003DE900104000060E3DD1401072090000</Binary>
      </EventData>
    </Event>
    Also, the CN=InformationSore is empty. Is this normal?
    Now I am assuming I deleted something that I shouldn't have.

    Tried that, I get the following when I go to the Public Folder Management Console:
    Cannot complete the operation because there isn't an available public folder database on server
    And even if I did that how does that help me retrieve my missing information?

  • Mailbox Move Issues and Errors - Exchange 2010 to 2013

    I'm trying to move mailboxes from 2010 to 2013, but I'm experiencing a lot of issues.
    My move batches keep hanging (stalled) for minutes and hours on end, and I can't seem to keep them going consistently.
    I have two DAG's, one for Archive boxes, and one for Primary mailboxes. Each DAG has three members with DB copies of each DB. The npdes and the clusters themselves are up and healthy. However, at random some of the DB's Content Index state will go to Failed
    or SuspendedandFailed. At which point I force a catalog refresh and DB index update, and it goes to healthy.
    I've created the "ContentSubmitters" AD group (and assigned it permissions), reset the Search and Host controller services on each server, and restarted the Replication service. I also deleted and recreated the Index for each DB prior to restarting
    services. No dice. I've also already moved the system mailboxes over to the 2013 databases.
    I'm also getting some "Transient" errors in the user move log, things like this: 
    Transient error ResourceUnhealthyException has occurred. The system will retry"
    5/4/2014 8:43:55 AM [exmb1] The job encountered too many transient failures (60) and is quitting.
    5/4/2014 8:43:55 AM [exmb1] Fatal error ResourceUnhealthyException has occurred.
    Error: MigrationPermanentException: Warning: Target mailbox unlock operation was not replicated. If a lossy failover occurs after the target mailbox was unlocked, the target mailbox could remain inaccessible. Error details: The store ID provided isn‎'t an ID of an item. --> MapiExceptionNetworkError: Unable to open entry ID. ‎(hr=0x80040115, ec=0)‎ Diagnostic context: Lid: 45025 Lid: 45345 StoreEc: 0x80040115 Lid: 22894 Lid: 24942 StoreEc: 0x80040115
    Any ideas would be appreciated!!!

    Hi 
    I would suggest you to run the below command for this "My move batches keep hanging (stalled) for minutes and hours on end" issue and see the result
    Get-MoveRequest -Identity "Mailbox Name" | Get-MoveRequestStatistics -IncludeReport | FL Report
    Just check if the MRS health is fine by running the below command
    Test-MRSHealth -Identity "CAS Server" -MonitoringContext $true | Export-CliXml "C:\temp\CAS_MRSHealth.xml" and look at the xml file to get more information
    When I run the Test command against either of my CAS servers, I get: " 'EXCH1' does not have the right Exchange Server version or role required to support this operation."
    Run i run that command against any of the mailbox servers, it completes and generates the XML file, but I'm not sure what I need to be looking for within that file.
    The first command spits out a ton of data, here's a little excerpt:
    5/5/2014 8:59:28 AM [exmb1] Transient error ResourceUnhealthyException has occurred. The system will retry
    (2/60).
    5/5/2014 9:00:02 AM [exmb1] The Microsoft Exchange Mailbox Replication service 'exmb1.contoso.com'
    (15.0.847.31 caps:03FF) is examining the request.
    5/5/2014 9:00:07 AM [exmb1] Connected to target mailbox 'Primary (072dc240-bd79-495c-b7f2-c571e8f910f2)',
    database 'newmbi', Mailbox server 'Exmb1.contoso.com' Version 15.0 (Build 847.0).
    5/5/2014 9:00:07 AM [exmb1] Connected to target mailbox 'Archive (812ee554-4a1e-4feb-b591-a435fcbdee16)',
    database 'newarci', Mailbox server 'EXARC2.contoso.com' Version 15.0 (Build 847.0), proxy server
    'EXARC2.contoso.com' 15.0.847.31 caps:1FFFCB07FFFF.
    5/5/2014 9:00:07 AM [exmb1] Connected to source mailbox 'Primary (072dc240-bd79-495c-b7f2-c571e8f910f2)',
    database 'exmbi', Mailbox server 'Chsexmb2.contoso.com' Version 14.3 (Build 181.0).
    5/5/2014 9:00:08 AM [exmb1] Connected to source mailbox 'Archive (812ee554-4a1e-4feb-b591-a435fcbdee16)',
    database 'Exarci', Mailbox server 'CHSEXARC1.contoso.com' Version 14.3 (Build 181.0)
    5/5/2014 9:00:12 AM [exmb1] Request processing continued, stage LoadingMessages.
    5/5/2014 9:00:36 AM [exmb1] Messages have been enumerated successfully. 6657 items loaded. Total size:
    332.3 MB (348,411,982 bytes).5/5/2014 9:06:14 AM [exmb1] The long-running job has been temporarily postponed. It will be picked up
    again when resources become available.

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

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

  • Exchange 2010 to 2013 Migration Question

    Hi Folks,
    This is where I'm at: We have 2 Exchange 2010 servers (both multi role) and I was given 4 VM's for exchange 2013.  I just completed installing Exchange on the four 2013 VM's (2 dedicated CAS and 2 dedicated MBX) and applied SP1.  I documented all
    of the 2010 server config info (i.e. all the URL's for the namespaces, etc).  We have a hardware NLB and a MacAfee host in the DMZ where all inbound/outbound email routes to check for AV/Spam.  My question is, what are my next steps that
    take place so that I'm truly in co-existence mode?  I'm assuming I want to make the 2013 servers primary now so that all mail routes to/from them and all client connections are made to them?  Could someone point me in the right direction maybe
    to an article on what my next steps are?  I want to get everything cut over while in co-existence so that I can start moving mailboxes.  Thanks a lot ! 

    Exchange Server Deployment Assistant is good starting point:
    http://technet.microsoft.com/en-US/exdeploy2013/Checklist?state=2284-W-AAAAAAAAQAAAAAEAAAAAAA%7e%7e
    Upgrade from Exchange 2010 to Exchange 2013:
    http://technet.microsoft.com/en-us/library/jj898583(v=exchg.150).aspx
    http://msexchangeguru.com/2013/05/10/exchange2013-migration/
    http://www.petenetlive.com/KB/Article/0000788.htm
    Below is high level migration plan:
    1. Update active directory schema for exchange 2010 sp3.
    2. Install Exchange 2010 SP3 and rollup updates on existing servers.
    3. Update active directory schema for exchange 2013 CU3.
    4. Install and configure new Exchange 2013 CU3 servers.
    5. Install public SSL Certificate.
    6. Configure Web URL's for Exchange 2013 servers.
    7. Configuration Hardware Load Balancer for:
    a) High availability of Client Access roles.
    b) Reverse Proxy for outlook web app.
    8. Create mailbox databases and configure database copies for the corresponding DAG.
    9. Test High Availability environment.
    10. Test mail flow  to & from internet/internally for all locations.
    11. Test BlackBerry device connectivity with Exchange 2013 environment (if nay)
    12. Test migrate mailbox from Exchange 2010 to Exchange 2013.
    13. Test Outlook & OWA connectivity for migrated test mailbox.
    14. Validate new Exchange 2013 environment.
    15. Pilot mailboxes migration from Exchange 2010 to Exchange 2013.
    16. Migrate mailboxes from Exchange 2010 to Exchange 2013.
    17. Migrate Public Folders from Exchange 2010 to Exchange 2013
    18. Dismount & stop Exchange 2010 services on all servers for few days before decommissioning of Exchange 2010 servers.
    19. Decommission Exchange 2010 servers gracefully.
    If this will help then please mark it as answer...thanks
    Best of luck!
    Liaqat

Maybe you are looking for