Exchange 2003 - 2010. Moving public folders one at a time

Hi all,
I'm in the process of decomisioning our old Exchange 2003 server (long overdue after what has been a relativly smooth and trouble free transition to 2010). As the first step in the decomisioning process, I'm looking to move the public folders from the 2003
box to the 2010 box. From my understanding there are a couple of ways to achieve this (please correct me if I'm wrong). The first is to add the Exchange 2010 server as a new replication partner, allow for replication of the PFs to occur, and then remove the
2003 partner from the replication partnership. The other option is to use MoveAllReplicas.ps1.
I opted for the first option, but the problem I have is that the initial replication process started to generate a very large number of transaction logs on the Exchange 2010 server, to the point I was slightly conccerned I was going to run out of space on
the volume (our server is backed up nightly at which point the transaction logs are normally flushed).Whilst I know I could potentially increase the size of the volume or turn on cicular logging for the duration of the migration (neither of which is appealing
as it will involve down time), I was wondering if there was a way to move a smaller set of Public folders one at a time with a powershell command, or is it an all or nothing operation? My other option may be to replicate a small subset of folders everyday,
but that just a little painful as there are a large number of child folders with in the structure. Any other suggestions welcome!
Many thanks,
Rob

Hi,
If your Public Folder Database is large, you can use tool like Exfolders or ESM to add replica folder by folder.
A related article for your reference.
http://careexchange.in/moving-public-folders-from-exchange-2003-to-exchange-2010/
Note: Microsoft is providing this information as a convenience to you. The sites are not controlled by Microsoft. Microsoft cannot make any representations regarding the quality, safety, or
suitability of any software or information found there. Please make sure that you completely understand the risk before retrieving any suggestions from the above link.
And it is recommended to replicate public folders off business hours.
Best regards,
Belinda Ma
TechNet Community Support

Similar Messages

  • Exchange 2013 / 2010 / 2007 - Public Folders

    I have read that legacy public folders and 2013 public folders canot co-exist.
    If I have legacy public folders A, B and C, does this mean...
     that if I migrate folder A to 2013, i cannot maintain a replica on legacy systems, but folders B and C are still accessible
    ..or..
     If I migrate folder A to 2013, I must migrate folders B and C also.
    If I am need to import folder D, from an external Exchange 2013 installation, into my legacy public folder system, is it possible to migrate folder D out of the external 2130 environment into my legacy public folder environment? If so, is there any extra functionality
    2013 PF has that the users will lose if the folders are down graded to legacy?
    Thanks!
    Tom

    Hi,
    User mailboxes on Exchange 2013 servers can connect to legacy public folders, but legacy Exchange mailboxes are unable to access the public folder hierarchy on Exchange 2013 server.
    Exchange 2013 public folders and legacy public folders can’t exist in your Exchange organization simultaneously.
    Before you migrate public folders, you need to migrate mailboxes to Exchange 2013 first.
    Please refer to the following article.
    http://technet.microsoft.com/en-us/library/jj150538(v=exchg.150).aspx
    Besides, here is a related thread for your reference.
    http://social.technet.microsoft.com/Forums/office/en-US/7603f02e-beb4-4c3d-8cb9-613ad806766b/public-folder-migration-from-multiple-exchange-2007-to-exchange-2013?forum=exchangesvrsharingcollab
    Best regards,
    Belinda Ma
    TechNet Community Support

  • Moved Public Folders - 4 System Folders wont Remove

    I have moved Public Folders from one Exchange 2007 Server to another Exchange 2007 Server using the ./movereplicas script.  All Folders have replicated ok, but on the old server which I want to decomission I am unable to remove the public
    folder DB because it says not all folders have replicated. 
    If I run Get-publicfolderstatistics on both servers I am left with 4 system folders on the old server.  These seem to have replicated across to the new server ok - the item count is higher on the new server. 
    I have tried running the script again, but these 4 folders never get removed.  The folders are OAB, Store Events which have an item count of 0 on both serversthese two are higher on the new Public Folder DB.
    Hope someone can advise
    Thanks
    Dave

    Hi,
    If they're system folders you don't need, like those other than SCHEDULE+ FREE BUSY, OFFLINE ADDRESS BOOK and EFORMS REGISTRY (if you use Organizational Forms), then you can delete them.
    Based on the description, it looks like the four system folders have replicas on another Exchange 2007 server, you can just delete these system folders.
    Best regards,
    Belinda
    Belinda Ma
    TechNet Community Support

  • Exchange 2003 /2010 Co-existence plus 2010 migration to new hardware

    Hi,
    Here is our current scenario;
    Exchange 2003/2010 co-existence. This has been running perfectly for a couple of months now.
    Exchange 2003 - exch1.domain.lan
    Exchange 2010 (SP3) - exch2.domain.lan (local domain name)  /  mail.domain.com.au (external domain name)
    ActiveSync, autodiscover, legacy etc are all working. Our UAC certificate from GoDaddy has all the required names for exch2 - except it doesn't have the local domain name as they don't allow certificates with that anymore. I've configured all the required
    services to be the external domain name and am running split DNS.
    The first Exchange 2010 server I installed was lower spec'd and only has about 25 users on it. I now need to install a second Exchange 2010 server (exch3.domain.local), which is properly spec'd and will host the entire company. I won't be running DAG as
    I need to repurpose the first Exchange 2010 server once it's removed.
    My high level questions are;
    1) Should I migrate everyone off Exchange 2003 onto Exchange 2010, decommission the 2003 server, and then install the second 2010 server? OR
    2) Should I install the second Exchange 2010 server, migrate everyone from the first Exchange 2010 server, decommission that one, then do the migration from 2003 to 2010?
    OR does it matter which way I do it?
    I've read what I can find about installing the second Exchange 2010 server into the organisation. It seems to be pretty simple at first. Just install Exchange 2010 with HT, mailbox and CAS roles which will automatically configure it into the same Exchange
    organisation.
    1) Do I configure CAS to be externally facing right from the get go or do I do that later?
    2) As soon as I install the second Exchange 2010 server, will I encounter any mail flow problems? Will mail be trying to flow out of the second Exchange 2010 server as well as the first?
    In regards to SSL, so obviously the second Exchange 2010 server will have a different local domain name than the first, but ultimately, I want it to have the same external domain name, eg mail.domain.com.au. As my certificate doesn't contain any local domain
    names, can I export the certificate from exch1 and import it into exch2, or should I just generate a new CSR from exch2 and get GoDaddy to reissue it?
    OR should I look at creating a CAS Array from exch1 and adding exch2 to it. (I don't fully understand the workings of this at the moment).
    Any guidance on the above is helpful.
    Thanks.
    Steve

    Hi Steve I will try my best to answer each of these 
    My high level questions are;
    1) Should I migrate everyone off Exchange 2003 onto Exchange 2010, decommission the 2003 server, and then install the second 2010 server? OR
    2) Should I install the second Exchange 2010 server, migrate everyone from the first Exchange 2010 server, decommission that one, then do the migration from 2003 to 2010?
    OR does it matter which way I do it?
    doesn't matter at all. Since you want to move to a new hardware you can setup a new Server CASH/HUB/Mailbox. Once installed start migrating the mailboxes from Exchange 2003 to this mailbox server. This way you will not have to redo the migration from 2010
    to new 2010 sever -- like you mentioned in 1) it will save you a lot of time and repeating procedure. 
    I've read what I can find about installing the second Exchange 2010 server into the organisation. It seems to be pretty simple at first. Just install Exchange 2010 with HT, mailbox and CAS roles which will automatically configure it into the same Exchange organisation.
    1) Do I configure CAS to be externally facing right from the get go or do I do that later?
    Keep your existing 2010 internet facing for now. Once you finished migrating the mailboxes then you will need to do it.
    2) As soon as I install the second Exchange 2010 server, will I encounter any mail flow problems? Will mail be trying to flow out of the second Exchange 2010 server as well as the first?
    Mail will not flow to 2ndry server unless you add that server as a source serve in the transport.
    In regards to SSL, so obviously the second Exchange 2010 server will have a different local domain name than the first, but ultimately, I want it to have the same external domain name, eg mail.domain.com.au. As my certificate doesn't contain any local domain
    names, can I export the certificate from exch1 and import it into exch2, or should I just generate a new CSR from exch2 and get GoDaddy to reissue it?
    You  can always export the certificate and then import it to the newly installed Exchange 2010.
    OR should I look at creating a CAS Array from exch1 and adding exch2 to it. (I don't fully understand the workings of this at the moment).
    You will only need to setup the CAS array if you are going to use both the server which can be done later.
    Hope that help
    Where Technology Meets Talent

  • Exchange 2003 -2010 cross forest (NDR 5.4.6)

    Hi.
    Have: Exchange 2003+2010 in source forest. Exchange 2010 in target forest.
    Successful migrate mailbox to target forest (in source forest this mailbox convert to mailuser).
    When try send e-mail to this mailbox (it`s in target forest) from Exchange 2003 mailbox get this:
    A configuration error in the e-mail system caused the message to bounce between two servers or to be forwarded between two recipients.
    If send from Exchange 2010 (source/target) - all mail ok.
    If delete this mailuser (in source forest) - all set to ok.
    x500?
    Please, help.
    Thanks.

    Hi,
    In the error event, 5.4.6 means "Routing loop detected" (RFC1893).
    This issue occurs if the source Exchange organization is authoritative for the target domain. Because the source Exchange organization is responsible for mail delivery to target, the categorizer tries to find locally a recipient for
    that message. The categorizer does not succeed, and then you receive the NDR.
    More details in the following KB:
    You receive an NDR with a 5.4.6 status code when you send a message to a specific domain in Exchange
    http://support.microsoft.com/kb/324732/en-us
    Hope it is the solution.
    Thanks
    Mavis
    Mavis Huang
    TechNet Community Support

  • Exchange 2003-2010 co-existence environment

    i have exchange 2003 -2010 co-existence environment .
    Everything works fine accept below;weird issue,i tried to re-create routing group connector but issue is same.
    My issue is very simple,The mail flow as below:
    exchange 2003 to outside............
    exchange 2010 to outside ...........works
    exchange 2010 to 2003 ...............works
    exchange 2003 to 2010................is not 

    Hi Huzefa,
    Can you try creating a new bidirectional RGConnector and check?
    New-RoutingGroupConnector -Name "NameOfRG" -SourceTransportServers "Ex2010.contoso.com" -TargetTransportServers "Ex2003.contoso.com" -Cost 10 -Bidirectional $true -PublicFolderReferralsEnabled $true
    http://technet.microsoft.com/en-us/library/aa997292(v=exchg.141).aspx
    Thanks, MAS
    Please mark as helpful if you find my comment helpful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you.

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

  • Exchange 2010 System Public Folders trying to replicate to decommissioned Exchange 2003

    I was checking the mail queue on Exchange 2010 and noticed several hundred messages in retry. Looking at the messages I found that they were all destined for an old 2003 exchange that has been decommissioned. I looked at the System Public Folders and found
    replication is set up on "events root, OWAScatchpad, SchemaRoot, and Store Events. They are set to replicate to the old mail server. When I try to remove the old server from replication it gives me an error;
    Microsoft Exchange Error
    The following error(s) occurred while saving changes:
    Set-PublicFolder
    Failed
    Error:
    You must specify a value with the Replicas parameter.
    OK
    Not sure where to go with this error.  Could someone point me in the right direction?
    Thank you,
    Wade Harris

    Hi,
    For this issue, I recommend you add an Exchange 2010 public folder database to the replica list and then remove Exchange 2003 server from this list to check result.
    I tested in my lab, and I got the same error with yours, we need to keep at least one public folder database in the replica list.
    Best regards,
    Belinda
    Belinda Ma
    TechNet Community Support

  • Exchange 2010 SP2 Public Folders Stubborn Replicas (OAB)

    I migrated to a new server with 2010 SP3 all is working good, I am able to see all Public Folders and their contents fine. Now I need to delete this stubborn Public Folder on the older 2010 SP2 server to decommission it. But I get the dreadful 'you cannot
    delete this database because it contain replicas' blah blah. Very annoying.
    This is what the stats pulled up. They are not folders to me, and the new server is the default for OAB. Not sure what to do, I just want to delete this database the right way without resorting to ASIEDIT. I do not want to use that tool, read many horrible
    stories of people deleted the database only to have hours of after affects where other public stores went into an inconsistent state. HELP! 
    [PS] C:\Program Files\Microsoft\Exchange Server\V14\scripts>Get-PublicFolderStatistics -server server-04
    Name                                     ItemCount                                  
                        LastAccessTime
    EX:/o=LMV/ou=Exchange Administrative ... 28                                                       10/25/2014 9:20:35 PM
    EX:/o=LMV/ou=first administrative group  10                                                       10/25/2014 9:13:30
    PM
    OAB Version 2                            28                                          
                10/25/2014 9:44:33 PM
    OAB Version 4                            16                                          
                10/25/2014 9:44:33 PM

    Did you create replicas of these folders on the other server and remove the replicas from the server you want to uninstall? Have you configured the OAB so that it's generated on the new server?
    Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

  • Exchange 2013 with Outlook 2010 anywhere - Public Folders disappear from Outlook favourites

    Hi,
    we have a 3 server Exchange 2013 SP1 DAG published with Forefront TMG. 
    Outlook 2010 anywhere connection works fine (only anywhere connection is possible, there are no clients in the exchange server AD).
    The users are adding public folders to their local Outlook favorites. In about 10% of the Outlook starts, those public folders are missing in the favorites. Local favorites folders are still there, public folders are connected.
    After restarting the Outlook a few times, the favorites are back. 
    Deleting the outlook.xml brought no success, the favorites seem to be saved somewhere on the exchange server.
    Outlook 2010 is up to date, all hotfixes are installed.
    There are no related entries in servers or clients eventlogs, the logs of the TMG server are normal.
    Does anyone have a simular behavior?
    Thanks in advance!

    Hi,
    According to your description,it is clear that something got corrupted, but it is hard to say directly what caused it. However, there are a few troubleshooting steps to determine what caused it and you can also make a backup of your Favorite Folders list
    so you can easily restore it when it still happens.
    Pleaser refer to the following article:
    Favorite Folders empty upon restart
    Note: Microsoft is providing this information as a convenience to you. The sites are not controlled by Microsoft. Microsoft cannot
    make any representations regarding the quality, safety, or suitability of any software or information found there. Please make sure that you completely understand the risk before retrieving any suggestions from the above link.
    Hope this helps!
    Thanks.
    If you have feedback for TechNet Subscriber Support, contact
    [email protected]
    Niko Cheng
    TechNet Community Support

  • Problems moving public folders for 2k3 to 2k7 migration

    Hello,
    i'm having problems with moving the public folder from the 2k3 to 2k7, following the steps i've found on mig docs and googling for this issue and i cant seem to solve it, letme detail:
    There are only 3 user created public folders, all with contacts, they weight less than a MB combined.
    So first thing, iin E2k3 ESM i right click the public folder store and select "move all replicas", it works succesfully.
    if i expand the pf store and check replicas i see a ton of system folders with 2 replicas.
    i also check every user folder, change the replication to always and urgent and resend changes/synch content from 2k3 to 2k7
    Now according to migration documents the "pf instances" should empty by itself after some time....
    well it's been a day and in fact i see more items than before on the 2k3, if i expand the instances on the 2k7 i see 4/5 folders, none of the user ones!.
    I also ran the moveallreplicas.ps1 script.
    if i run Get-publicfolder -recurse |fl name,replicas i only get:
    Name     : IPM_SUBTREE
    Replicas : {}the next step is apparantely to move the public folder "folder" itself from the 2k3 admin group to the 2k7, i can do that and it gives no error but i'm worried that if i decommision the 2k3 that it will all fail horribly.
    ¿whats going on, how can i move this thing for once?

    Hi,
    Make sure you have added the Exchange 2007 in the Replication tab list of all folders in Exchange Server 2003.
    In Exchange 2003, please increase the logging level to Maximum on the diagnostic logging categories: Replication Incoming Messages and Replication Outgoing Messages.
    Here is a related article which can help you for your reference.
    How to troubleshoot public folder replication problems in Exchange 2000 Server and in Exchange Server 2003
    http://support.microsoft.com/kb/842273/en-us
    Another useful article:
    Some Public Folder content is not replicating from Exchange 2003 to Exchange 2007
    http://blogs.technet.com/b/dblanch/archive/2009/04/10/some-public-folder-content-is-not-replicating-from-exchange-2003-to-exchange-2007.aspx
    Best regards,
    Belinda
    Belinda Ma
    TechNet Community Support

  • Namespace for Exchange 2003 == 2010 == 2013 Migration

    Hi
    Hope someone can help.  I am working on an Exchange 2003 to 2010 migration, which will then quickly move onto a 2010 to 2013 migration and need some clarification on the namespaces to use.  I am aware that if I do not do this right at the 2003
    to 2010 migration, this will cause a headache at the 2010 to 2013 migration.
    Some background:
    2003 Functional Level Domain - 2 x 2008 DC's
    Currently users are on a 2003 exchange cluster with a mix of RPC (internal users) and RPC over HTTP connections (roaming users)
    We will be installing Exchange 2010 on a single server, with CAS, HUB and Mailbox roles and no load balancer, as we will be moving quickly to 2013.
    We have two Kemp load balancers ready for Exchange 2013.
    Exchange 2010 is installed on a single server (exh2010.domain.local) and configured with an CAS array name (exh-cas.domain.local) which is resolvable internally only.
    Currently we have multiple smtp namespaces e.g. @company.com, @company2.com.
    Our main website etc is www.company.com
    Our public facing services are at https://service.mycompany.com
    Our 2003 RPC address is https://webmail.mycompany.com
    I understand that the 2010 RPC CAS array name should be separated from the Outlook Anywhere (RPC over HTTPS) address so that when 2013 takes over the HTTPS address, the RPC connections are not broken.
    Two Questions:
    Do we have to use the HTTPS same namespace for 2013 as we do in 2010?  Its just I would want to test the Kemp load balancers before making them live (slow careful transition), and giving them a different namespace, e.g.
    https://mail.mycompany.com would allow a migration, rather then a cutover.
    Can we use the *.mycompany.com address rather then the company.com address, even though we have no SMTP addresses at mycompany.com?  Can autodiscover still work?
    Thanks in advance for any guidance
    Cheers
    Steve

    1. No, but you can.  Exchange 2013 will proxy all services for Exchange 2010, so if you set up everything right, you should be able to simply swing the name from Exchange 2010 to 2013.
    2.  Your web services can be published with any domain as long as the hostname is in the certificate.  Only Autodiscover needs to match the e-mail domain(s).  So in your example, you could publish OWA, ECP, ActiveSync, Web Services and OAB
    at owa.mycompany.com.  You would need autodiscover.company.com, autodiscover.company2.com, etc., but if you don't have e-mail addresses with mycompany.com, you don't need autodiscover.mycompany.com.  If all users have a company.com e-mail address,
    the you only need autodiscover.company.com as long as users know to enter that e-mail address when configuring profiles on PCs or devices.  If you're going to have to have Autodiscover for multiple domains, then you might consider using an SRV record
    instead because it can greatly simplify your certificate requirements.
    Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

  • Exchange 2003/2010 Co-Existence - Distribution Group Management

    We're running both exchange 2010 and Exchange 2003.  I have an issue where some distribution groups were upgraded to Exchange 2010 (v14.0.100) and the manager of those lists who are on Exchange 2003 can no longer modify members, they get the error:
    "Changes to the distribution list membership cannot be saved.  You do not have sufficient permission to perform this operation on this object".
    We've already implemented the myDistributionGroupsManagement role with success to allow Exchange 2010 users to manage their own list without allowing them to create new ones.
    http://blogs.technet.com/b/exchange/archive/2009/11/18/3408844.aspx
    Trying to apply the "Default Role Policy Assignement" to the exchange 2003 users returns an error.  Is there any way Exchange 2003 users can manage Exchange 2010 Distribution list they owned without being upgraded to Exchange 2010?  If not, is
    there any way to downgrade distribution group to Exchange 2003 once they've been upgraded?

    Hi,
    From my lab, legacy exchange user can manage the distribution group which has been  upgrade to Exchange 2010.
    Exchange 2010 sp2, Exchange 2003 with sp2.
    I can add/remove member for distribution group from address book via outlook.
    Xiu Zhang
    TechNet Community Support

  • Exchange 2003 - 2010 Local Mail box move Error

    Hey everyone,
    I have just finished a transition from Microsoft Exchange 2003 to 2010, and I am having problem with moving the Legacy mailboxes over.
    I have managed to move all the mail boxes over bar 2, using the " New local move Request".
    So the problem is just these 2 mail boxes with the same error as below.
    Any Advice?
    Summary: 1 item(s). 0 succeeded, 1 failed.
    Elapsed time: 00:00:39
    Sifiso Mguni
    Failed
    Error:
    Service 'net.tcp://tvt-exchange.vtrust.local/Microsoft.Exchange.MailboxReplicationService' encountered an exception. Error: MapiExceptionLogonFailed: Unable to open message store. (hr=0x80040111, ec=-2147221231)
    Diagnostic context:
        Lid: 18969   EcDoRpcExt2 called [length=131]
        Lid: 27161   EcDoRpcExt2 returned [ec=0x0][length=48][latency=0]
        Lid: 23226   --- ROP Parse Start ---
        Lid: 27962   ROP: ropLogon [254]
        Lid: 17082   ROP Error: 0x80040111
        Lid: 26937 
        Lid: 21921   StoreEc: 0x80040111
        Lid: 31418   --- ROP Parse Done ---
        Lid: 22753 
        Lid: 21817   ROP Failure: 0x80040111
        Lid: 26297 
        Lid: 16585   StoreEc: 0x80040111
        Lid: 32441 
        Lid: 1706    StoreEc: 0x80040111
        Lid: 24761 
        Lid: 20665   StoreEc: 0x80040111
        Lid: 25785 
        Lid: 29881   StoreEc: 0x80040111
    Exception details: MapiExceptionLogonFailed (80040111): MapiExceptionLogonFailed: Unable to open message store. (hr=0x80040111, ec=-2147221231)
    Diagnostic context:
        Lid: 18969   EcDoRpcExt2 called [length=131]
        Lid: 27161   EcDoRpcExt2 returned [ec=0x0][length=48][latency=0]
        Lid: 23226   --- ROP Parse Start ---
        Lid: 27962   ROP: ropLogon [254]
        Lid: 17082   ROP Error: 0x80040111
        Lid: 26937 
        Lid: 21921   StoreEc: 0x80040111
        Lid: 31418   --- ROP Parse Done ---
        Lid: 22753 
        Lid: 21817   ROP Failure: 0x80040111
        Lid: 26297 
        Lid: 16585   StoreEc: 0x80040111
        Lid: 32441 
        Lid: 1706    StoreEc: 0x80040111
        Lid: 24761 
        Lid: 20665   StoreEc: 0x80040111
        Lid: 25785 
        Lid: 29881   StoreEc: 0x80040111
    Exchange Management Shell command attempted:
    'vtrust.local/Valley Trust Users/Users/Staff/Sifiso Mguni' | New-MoveRequest -TargetDatabase 'Mailbox Database 0271422377'
    Elapsed Time: 00:00:39

    HI. I had the same problem while trying to migrate a user from Exchange 2003 to 2010. And the same error as you have appeared. I tried to skip more e-mails in case some fails but couldn't get successful.
    Check if the user have accessed the mail at all on Exchange 2003 because if the user didn't accessed it it may contain many mails and when we try to migrate the mailbox, the mailbox size on Exchange 2003 may be grater than on the 2010.
    On my case after many reading we just see that the user didn't access the mail at all on our Exchange 2003. (Let me know if you need to know how you can check if the user accessed the mail or not or you can just google it). So what we have done is we just
    reset the user password on Active Directory. Because as you can see the error is related with Logon Failure.
    This solved the issue for me. Can you check this way
    Thanks

  • Exchange 2003/2010 Coexistance - User login Issue

    Hello
    We have deployed Exchange 2010 SP3 in coexistance with 2003 and created connectors.
    2003/2010 both Users are not able to login on 2010 OWA and error showing that username/PW is wrong although they are working on OWA 2003 perfectly.
    When i add the same user to the local admin group on the Ex2010 server, it works fine with email send/receive. i am confused please suggest what i am missing....Regards
    Waseem

    Hello
    This is the error that occured during that time.
    SACL Watcher servicelet encountered an error while monitoring SACL change.
    Got error 1722 opening group policy on system SERVER.DOMAIN in domain MYDOMAIN.
    Event ID 6003
    Source : MSExchange SACL Watcher
    i am not sure if its related to this problem.
    Secondly i have also tested to run the "Microsoft Exchange Active Directory Topology Service" with a new user having all the rights of exchange & AD groups but its showing giving the error that it cant run the dependency
    services. currently this service is running with the local account rights.
    I just add the test users (moved from 2003 and new user created in 2010) to the local admin group and it works fine, please give any idea what may be the problem in rights or something else ??
    Regards
    Waseem

Maybe you are looking for