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

Similar Messages

  • 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

  • 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

  • Public folders not replicating Exchange 2010

    Earlier this year I did a migration from a single 2003 Exchange server to a single Exchange 2010 server. I didn't notice until recently that my GAL isn't being updated in cached mode in Outlook 2010+ but is in OWA and with cached mode turned off. So,
    I dug a little more, and also noticed that I also having errors when trying to go into Public Folder Management Console when I right click and and select update content on anything under Default Public Folders or System Public Folders I get an error about
    no replica being found.
    Microsoft Exchange Error
    Action 'Update Content' could not be performed on object 'OFFLINE ADDRESS BOOK'.
    OFFLINE ADDRESS BOOK
    Failed
    Error:
    Server 'JASMAIL01' doesn't have a replica of public folder '\NON_IPM_SUBTREE\OFFLINE ADDRESS BOOK'. Public folder content can be synchronized only from a server that has a replica of that public folder.
    When I update anything inside the Offline Address Book Folder I get:
    Microsoft Exchange Error
    Action 'Update Content' could not be performed on object 'EX:/o=AmicalolaEMC/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)'.
    EX:/o=AmicalolaEMC/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)
    Failed
    Error:
    Cannot start content replication against public folder '\NON_IPM_SUBTREE\OFFLINE ADDRESS BOOK\EX:/o=AmicalolaEMC/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)' on public folder database 'Public Folder Database 1904981871'.
    MapiExceptionNoReplicaAvailable: StartContentReplication failed. (hr=0x80004005, ec=1129)
    Diagnostic context:
        Lid: 1494    ---- Remote Context Beg ----
        Lid: 3010    StoreEc: 0x8004010F
        Lid: 3010    StoreEc: 0x8004010F
        Lid: 3650    StoreEc: 0x8004010F
        Lid: 18128   StoreEc: 0x469     
        Lid: 18536   StoreEc: 0x469     
        Lid: 18544   StoreEc: 0x469     
        Lid: 18560   StoreEc: 0x469     
        Lid: 18740   StoreEc: 0x469     
        Lid: 1267    StoreEc: 0x469     
        Lid: 33819   StoreEc: 0x469     
        Lid: 27225   StoreEc: 0x469     
        Lid: 1750    ---- Remote Context End ----
        Lid: 26322   StoreEc: 0x469     
    OK
    I've been searching for a month or so and have come up with nothing, any ideas? Thank you!

    This is what happens when I try to run that command:
    Identity: Default Global Address List
    WARNING: The recipient "amicalolaemc.com/Microsoft Exchange System Objects/OAB Version 2" is invalid and couldn't be
    updated.
    WARNING: The recipient "amicalolaemc.com/Microsoft Exchange System Objects/OAB Version 3a" is invalid and couldn't b
    updated.
    WARNING: The recipient "***.com/Microsoft Exchange System Objects/OAB Version 4" is invalid and couldn't be
    updated.
    WARNING: The recipient "***.com/Microsoft Exchange System Objects/Schedule+ Free Busy Information - First
    Administrative Group" is invalid and couldn't be updated.
    WARNING: The recipient "***.com/Users/SystemMailbox{1f05a927-2cd9-4dbe-8f19-98848d21a898}" is invalid and
    couldn't be updated.
    WARNING: The recipient "***.com/Users/SystemMailbox{e0dc1c29-89c3-4034-b678-e6c29d823ed9}" is invalid and
    couldn't be updated.
    WARNING: The recipient "***.com/Users/FederatedEmail.4c1f4d8b-8179-4148-93bf-00a95fa1e042" is invalid and
    couldn't be updated.
    Hi,
    The error message also mentions that your system mailboxes are invalid. Please run the Get-Mailbox -Arbitration command to check result.
    Besides, please find the following objects under the Microsoft Exchange System Objects container and delete them to check result.
    OAB Version 2
    OAB Version 3a
    OAB Version 4
    Schedule+ Free Busy Information - First Administrative Group
    Here is a related thread for your reference.
    https://social.technet.microsoft.com/Forums/exchange/en-US/92264b4d-56d5-4354-b3aa-828f18e0068f/exchange-2010-orphaned-public-folder-gal-entries
    Hope this is helpful to you.
    Best regards,
    Belinda Ma
    TechNet Community Support

  • Problem with Exchange 2010 Public Folders after installing Exchange 2013 in my environment.

    I currently have an Exchange 2010 server with all the roles installed.  Before installing Exchange 2013, I was able to launch the Public Folder Management Console but now I get an error.  When I installed Exchange 2013, I got an error saying I
    had a instance of Exchange 2000 or Exchange 2003, but I didn't have any of these servers left.  There was still something in AD referencing my old server. I went into ADSIedit and deleted an old administrative group.  This deletion caused my access
    to my public folders to get messed up.  I followed this article, http://blog.bruteforcetech.com/archives/766, and I was able to gain access back in my outlook client but I still can't see the public folders in OWA.  I also get this error when
    trying to access either Default or System Public Folders.  "Cannot complete the operation because there isn't an available public folder database on server 'ExchangeServer'. It was running the command 'get-publicfolder - getchildren -identity '\'
    -server 'ExchangeServer' "
    My Public Folder Database exists and is mounted.  Any help is appreciated.

    Hi Belinda,
    Thank you for responding.  Yes you do understand my problem correctly.  One correction is that after deleting this entry in ADSIEdit, we couldn't access public folders at all either in Outlook or OWA.  I followed these steps in the below article:
     http://blog.bruteforcetech.com/archives/766
    After following these steps and recreating the entry on FolderHieachies in ADSI edit, I was able to gain access to the public folders again through Outlook, but still can't see them in OWA and can't access them in Public Folder Management Console.
    Here are the results to your requests:
    et-PublicFolder -Recurse | Format-List Name
    Name : IPM_SUBTREE
    Can't get the public folder database using legacy distinguished name '/O=HEROIX CORPORATION/OU=EXCHANGE ADMINISTRAT
    GROUP (FYDIBOHF23SPDLT)/CN=CONFIGURATION/CN=SERVERS/CN=EXCHANGE2010/CN=MICROSOFT PUBLIC MDB'.
        + CategoryInfo          : NotSpecified: (:) [Get-PublicFolder], TaskInvalidOperationException
        + FullyQualifiedErrorId : B546E0B0,Microsoft.Exchange.Management.MapiTasks.GetPublicFolder
    [PS] C:\Windows\system32>Get-PublicFolder -Identity \NON_IPM_SUBTREE -Recurse | Format-List Name
    Name : NON_IPM_SUBTREE
    Name : EFORMS REGISTRY
    Can't get the public folder database using legacy distinguished name '/O=HEROIX CORPORATION/OU=EXCHANGE ADMINISTRATIVE
    GROUP (FYDIBOHF23SPDLT)/CN=CONFIGURATION/CN=SERVERS/CN=EXCHANGE2010/CN=MICROSOFT PUBLIC MDB'.
        + CategoryInfo          : NotSpecified: (:) [Get-PublicFolder], TaskInvalidOperationException
        + FullyQualifiedErrorId : B546E0B0,Microsoft.Exchange.Management.MapiTasks.GetPublicFolder
    Also the msExchOwningPFTree attribute should be correct because this was edited with the correct value when I followed the instructions in the above article:
    CN=Public Folders,CN=Folder Hierarchies,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=Heroix Corporation,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=hero,DC=net

  • Migrating Public folders Fatal error MapiExceptionNoReplicaAvailable

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

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

  • How can i know if move successfully my PF from Exchange 2003 to Exchange 2010

    Hello I need from your help, recently I install exchange 2010 in mi Exchange 2003 orgamnization and follow the next article
    http://technet.microsoft.com/en-us/library/gg576862(v=exchg.141).aspx but i don't know if the Public Folders migrating correctly I first move them through the powershell scrip
    MoveAllReplicas.ps1 but aparently nohtimg happend after that y use the option MoveAllReplicas using right click over the public folder store, and take a lot of time but aparently the allreplicas were moved, but really in other side, Exchange 2010 i can't see
    all the System Public Folders it missing SYSTEM CONFIGURATION and HIERARCHY using the public folder viewer from Exchange 2010, so I am not sure about that, so I shutdown the Exchange Server 2003 during one day until now, and all works fine, that means all
    public folders have been moved succeesfully?
    Thanks in advance for your help
    Felxs
    Felx

    Hi,
    To verify that public folder replication is successful, you can check the item count of public folders between replicas. If the item count matches, then this replication succeed.
    You can use the Get-PublicFolderStatistics cmdlet to get item count of public folders.
    Here is an related blog for your reference.
    Comparing public folder item counts
    http://blogs.technet.com/b/exchange/archive/2013/05/28/comparing-public-folder-item-counts.aspx
    Hope this helps.
    Best regards,
    Belinda
    Belinda Ma
    TechNet Community Support

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

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

  • Exchange 2010 - visibility of items in Public Folders

    Hello all,
    I already posted this question to the German Exchange 2010 forum, but have not gotten an answer yet. So I hope to be more lucky in the English forum.
    Environment: Exchange 2010 SP3 RU4, 2 replicas for Public Folders, Outlook 2007 cache Mode
    Problem:
    Some of our users have a phenomenon when working with mail enabled Public Folders:
    User has the focus set to Public Folder A, an email is sent there (and correctly delivered) but remains invisible to the user. When he changes the focus to point to his inbox or to Public Folder B and directly changes back to folder A he can see the email.
    Other users can see the email directly on delivery without leaving the folder first.
    When an affected user adds Public Folder A to his Public Folder Favorites he can see that an email is delivered from the change in numbers of unread mails (number in brackets behind folder name).
    I already checked the Exchange server to see if there is a replication related problem (though the default Public Folder DB is the same for all mailbox databases). Even after a successful replication an effected user does not see the email unless he leaves
    the folder and re-opens it.
    As the problem does not affect all users having permissions to this folder I picked one affected user and tried to remedy the issue as follows:
    - deleted the existing Outlook profile and re-created it => without success
    - deleted the user profile and re-created it => without success
    We use Outlook Cache Mode (set by policy, so the user cannot deactivate it) but there is no Public Folder data downloaded.
    When I create a new mail enabled Public Folder to test the scenario with an affected user everything works without problems, he can see an email on delivery.
    As far as I know this problem occurs with only two folders (and for both folders only a few users are affected - different users for each folder) I do not know what else to do. Can someone please give me a hint where to look at? Thanks in advance.
    Kind regards,
    Klaus

    The user is caching the public folder.  When he changes the focus and goes back, it tells Outlook to update.  In my experience, I've seen that Outlook only gets the update notices for the primary mailbox, so cached shared mailboxes are generally
    rarely updated.  We have stopped caching shared mailboxes for this reason and others.  Think of the following scenario:
    Ten different users perform actions on items in a shared mailbox
    When they first get the message, they move it to a subfolder in the mailbox (so it won't be there for other users)
    Since users are working in Cached mode, they will see an out-of-date image of the mailbox - they will move the item in their copy of the mailbox, but that won't be reflected in the other mailboxes until their copy updates to the server, then the server updates
    the other copies.  Talk about being lagged ...

  • Exchange 2003 to Exchange 2010 Public Folders

    Hi Gurus, I’m in the process of moving public folders from Exch03 to Exch2010 and I have some clarifications before I proceed with this task. As I have understood the replication process between public folders working in a multi-master environment, I still
    need some deep understanding. Okay, the task is to ensure that we don’t lose any PF when I remove the last Exch03 where there’s a lot of PF residing. From my understanding, these PFs found at Exch03 are only replicas from Exch2010. From testing I can verify
    that the Outlook clients are looking at Exch2010. The way I tested this is by creating a test PF from Outlook and it did reflected on Exch2010 PF. Looking Exch03 for a couple of days, the test PF never reflected there so I'm just just assuming that there's
    no replication happening between Exch2010 and Exch2010.
    Please verify on this. Does it mean that Exch2010 is not replicating to Exch03?
    If yes, if I remove the PFs from Exch2003 without moving the replicas first to Exch2010, like plainly removing them for decommission, will that delete/remove the PFs on Exch2010?
    I have a feeling that it don’t because the PFs I’m creating/deleting at Exch03 are all replicas and I don't see any of the PFs that I deleted at Exch03 to also get deleted at Exch2010. More likely the PFs I'm creating at Exch2010 are not replication across
    to Exch03 and therefore removing these PFs at Exch03 should not affect the PFs at Exch2010.
    Please confirm on this before I proceed.
    Note that I've already taken copy of these Exchange servers because these are all VMs.
    Thanks....

    Hi,
    When you add Exchange 2010 to the replica list on Exchange 2003 server, it will replicate the Exchange 2003 Public Folder hierarchy and content to Exchange 2010, not from Exchange 2010 to Exchange 2003.
    You can remove public folders on Exchange 2003 without affecting the public folders which have been replicated to Exchange 2010.
    Before you decide to remove Exchange 2003 server, I recommend you put the Exchange 2003 server offline temporarily to check if Exchange 2010 works well.
    Best regards,
    Belinda
    Belinda Ma
    TechNet Community Support

  • Public folders are not in sync after settting up Replicas between Exchange 2003 and 2010

    I have setup Public Folder replicas between the 2 Exchange servers and I can see all the top and sub level folders.
    For those mailboxes that were migrated over to Exchange 2010,  I have noticied  a lower number of item contents in these fodders when views from an Outlook client whose mailbox had been migrated over to Exchange 2010.
    On Exchange 2003 System Manager, if I properties one of the Public Folders, under the Replicataion tab, I can see the old and new server there. On the Exchange server 2003 box, I can see the last update reviced was a few weeks ago.
    I did see an option to synchronize content but I am not sure which server to run this one from. The Exchange 2003 or 2010 server.
    There is also a Resend Changes... option. Should I use this instead?
    Can anyone advise?

    Hi,
    The "Resend changes" and "Synchronize content" options in Exchange 2003 ESM are used to initiate hierarchy and content replication.
    To update public folder hierarchy and content from Exchange 2010 side, you can use the following commands.
    Update-PublicFolderHierarchy
    Update-PublicFolder
    Please run the Get-publicfolderstatistics cmdlet to get public folder details such as item count, this information will help you compare content replicated between the source and destination servers.
    Besides, here is a blog about public folder replication troubleshooting for your reference.
    http://blogs.technet.com/b/exchange/archive/2006/01/17/417611.aspx
    Hope this is helpful to you.
    Best regards,
    If you have feedback for TechNet Subscriber Support, contact
    [email protected]
    Belinda Ma
    TechNet Community Support

  • Public folders stuck in Mail queue when replicating to Exchange 2010

    This last weekend I installed Exchange 2010. Moved everyone over the same night to the new server. Mail flows in and out in ex 2010. The problem is I can't get the Public folders to replicate across. At the same time I found I can't send mail between the
    two exchange servers. In the message Queue on the Ex 2007 box I see the public folders are just sitting there waiting to be sent but stuck. Along with my test emails.
    I found an artical that talks about going into ADSIEdit and delete the old exchange 2003 empty server folder. Did that and email is still not flowing.
    Servers are in the same AD same subnet. ex 2007 is installed on a 2003 box. ex 2010 is on 2008r2.
    Thanks,
    Steve

    Hi vasdavidson,
    For this issue, I suggest you follow these steps to troubleshoot the problem:
    1.      
    Please paste the exact error you got in queue viewer.
    2.      
    On Exchange 2007, (use telnet) send emails to Exchange 2010, then check whether it can receive email or not.
    Thanks,
    Evan
    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Maybe you are looking for