Probling with Throttling of Emails by Exchange 2013 servers

We are experiecing delay of emails for users because of the Throttlig on Exchange 2013 servers.
This is causing company wide Delay and users are complaining as it takes a lot of time for the queue to get cleared.
We called in Microsoft and they suggested some values changes to msexchangedelivery.exe.config file
We added the following values, but still we face issues when there is Email flood.
Any one faced this or any suggestions that you have.
mdimthyas

Hi mdimthyas,
Thank you for your question.
Could you tell more details which throttling was configured on Exchange 2013 in organization?
Could you tell me how long was emails in the queue?
Are there any other issue which could help us troubleshoot.
We could remove the customized  throttling and re-configure it to check if the issue persist.
If there are any questions regarding this issue, please be free to let me know. 
Best Regard,
Jim
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
Jim Xu
TechNet Community Support

Similar Messages

  • Exchange 2013 Servers booting from SAN

    Hi,
    One of my client has decided to go with NetApp Flexpods for implementing Exchange 2013 in their environment.
    It has also been decided that these servers will boot from SAN and
    Exchange 2013 will also be installed on SAN. 
    We are planning to Install Win 2012 R2 for OS and E2k13 CU8. Few questions:
    1) Is it supported to boot Windows Server 2012 R2 from SAN, Specially if that server is going to used for E2k13
    2) Is it supported to Install Exchange 2013 CU8 on SAN
    I researched about this and understood that this is supported from Windows OS perspective. I am more concerned about the whole configuration falling within support boundary of Exchange 2013. I found an article which talks about the complexity involved in
    troubleshooting and indicates that its mainly SAN vendor who would be troubleshooting if running into any issues.
    https://support.microsoft.com/en-us/kb/305547- This article is not yet applicable to 2012 R2. Its applicable only till 2008 R2.
    http://www.enterprisenetworkingplanet.com/datacenter/the-pros-cons-of-booting-from-san.html - Pro & Cons of booting from SAN
    The booting from SAN for Exchange servers concerns me a lot as i have never seen any implementation in Exchange 2003, 2007 & 2010 doing this in my 10 years of experience. I have supported about 10 different enterprise exchange deployments and never saw
    this. So this is an unknown territory for me, hence looking for some best practices, articles and guidance around this if its supported by Microsoft Exchange team to run Windows and Exchange from SAN.
    Thanks
    Siva

    Hello,
    Please see the “Supported storage architectures” in the following article:
    https://technet.microsoft.com/en-us/library/ee832792%28v=exchg.150%29.aspx
    Thanks,
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
    [email protected]
    Simon Wu
    TechNet Community Support

  • RPC error when configuring Exchange 2013 servers in 2nd site

    Hello. I'm running into an error when trying to configure any of my Exchange 2013 servers in my 2nd AD site. To get into the loop of what my server structure looks like, please check below:
    Site 1 servers:
    DC1 - Domain Controller
    DC2 - Domain Controller
    CAS1 - CAS server
    CAS2 - CAS server
    MBX1 - Mailbox server
    MBX2 - Mailbox server
    MATHAFTMG - TMG server
    Site 2 servers:
    CCCDC1 - Domain Controller
    CCCDC2 - Domain Controller
    CCCCAS1 - CAS server
    CCCCAS2 - CAS server
    CCCMBX1 - MBX server
    CCCMBX2 - MBX server
    CCCTMG - TMG server
    Currently I have a site-to-site vpn connection between site 1 and site 2 TMG servers via Internet connection; I can access the servers of the other site perfectly (whether I am in Site 1 or Site 2).
    All user mailboxes are currently in Site 1 MBX servers; when users are in Site 2, they connect to the CAS servers in Site 1 to access their mailboxes.
    Many users will stay permanently in Site 2, so it makes sense to have Exchange servers in Site 2 to provide faster access to mailboxes. I created the Site 2 domain controllers, and made sure AD replication is working; and it is. I then added the MBX servers
    and CAS servers in Site 2 in this order: CCCMBX1, then CCCCAS1, then CCCMBX2, then CCCCAS2.
    All Exchange servers in Site 2 installed beautifully. But then I tried to access the servers via ECP to proceed with the configuration. In ECP, I click on the server link, and all Exchange servers in both sites appear. If I try to configure the virtual directories
    of Site 1 CAS servers, no problem. But when I try to configure virtual directories of Site 2 CAS servers, I get this error message:
    The task wasn't able to connect to IIS on the server 'CCCCAS1.domain.com'. Make sure that the server exists and can be reached from this computer: The RPC server is unavailable.
    The virtual directories issue is just an example. Same thing happens if I try to configure Outlook Anywhere for Site 2 CAS servers.
    Users connect to Site 1 CAS servers via mail.domain.com. I have the A record mail.domain.com pointing to the IP address of CAS1 server, and another A record mail.domain.com pointing to the IP address of CAS2 server. Not the best load balancing going on here,
    but it works great with Exchange 2013.
    From mail.domain.com I can access OWA and ECP internally and externally; no problems there. From ECP I can access and configure any Site 1 Exchange 2013 servers.
    The only problem is when I access ECP to configure the Site 2 Exchange 2013 servers, I get the same error message:
    The task wasn't able to connect to IIS on the server '<server name>.domain.com'. Make sure that the server exists and can be reached from this computer: The RPC server is unavailable.
    Even if I try to access a Site 2 Exchange 2013 server via https://localhost/ecp to configure it, it get the same error message.
    I updated all Exchange 2013 servers in both sites to CU2 v2 and rebooted the servers in the proper order; problem still there.
    Any clue what might the problem be?
    Thank you!

    Hello. I'm running into an error when trying to configure any of my Exchange 2013 servers in my 2nd AD site. To get into the loop of what my server structure looks like, please check below:
    Site 1 servers:
    DC1 - Domain Controller
    DC2 - Domain Controller
    CAS1 - CAS server
    CAS2 - CAS server
    MBX1 - Mailbox server
    MBX2 - Mailbox server
    MATHAFTMG - TMG server
    Site 2 servers:
    CCCDC1 - Domain Controller
    CCCDC2 - Domain Controller
    CCCCAS1 - CAS server
    CCCCAS2 - CAS server
    CCCMBX1 - MBX server
    CCCMBX2 - MBX server
    CCCTMG - TMG server
    Currently I have a site-to-site vpn connection between site 1 and site 2 TMG servers via Internet connection; I can access the servers of the other site perfectly (whether I am in Site 1 or Site 2).
    All user mailboxes are currently in Site 1 MBX servers; when users are in Site 2, they connect to the CAS servers in Site 1 to access their mailboxes.
    Many users will stay permanently in Site 2, so it makes sense to have Exchange servers in Site 2 to provide faster access to mailboxes. I created the Site 2 domain controllers, and made sure AD replication is working; and it is. I then added the MBX servers
    and CAS servers in Site 2 in this order: CCCMBX1, then CCCCAS1, then CCCMBX2, then CCCCAS2.
    All Exchange servers in Site 2 installed beautifully. But then I tried to access the servers via ECP to proceed with the configuration. In ECP, I click on the server link, and all Exchange servers in both sites appear. If I try to configure the virtual directories
    of Site 1 CAS servers, no problem. But when I try to configure virtual directories of Site 2 CAS servers, I get this error message:
    The task wasn't able to connect to IIS on the server 'CCCCAS1.domain.com'. Make sure that the server exists and can be reached from this computer: The RPC server is unavailable.
    The virtual directories issue is just an example. Same thing happens if I try to configure Outlook Anywhere for Site 2 CAS servers.
    Users connect to Site 1 CAS servers via mail.domain.com. I have the A record mail.domain.com pointing to the IP address of CAS1 server, and another A record mail.domain.com pointing to the IP address of CAS2 server. Not the best load balancing going on here,
    but it works great with Exchange 2013.
    From mail.domain.com I can access OWA and ECP internally and externally; no problems there. From ECP I can access and configure any Site 1 Exchange 2013 servers.
    The only problem is when I access ECP to configure the Site 2 Exchange 2013 servers, I get the same error message:
    The task wasn't able to connect to IIS on the server '<server name>.domain.com'. Make sure that the server exists and can be reached from this computer: The RPC server is unavailable.
    Even if I try to access a Site 2 Exchange 2013 server via https://localhost/ecp to configure it, it get the same error message.
    I updated all Exchange 2013 servers in both sites to CU2 v2 and rebooted the servers in the proper order; problem still there.
    Any clue what might the problem be?
    Thank you!

  • Configure legacy public folders where user mailboxes are on Exchange 2013 servers

    Hello all,
    I have mailboxes on an exchange 2013 server than need access to public folders on a 2010 server before I migrate them over.  I followed the commands in the TechNet article with the subject "Configure legacy public folders where user mailboxes
    are on Exchange 2013 servers" (sorry, I wasn't allowed to insert a link because I wasn't verified?).  The problem is when I run the last command of "Set-OrganizationConfig -PublicFoldersEnabled Remote -RemotePublicFolderMailboxes ProxyMailbox1,ProxyMailbox2,ProxyMailbox3"
    on the 2013 server, using the mailbox name I had created, it says it cannot be found.  Of course I checked and the mailbox exists, is configured properly, and so is the new database.  The 2013 EAC also sees the mailbox with no issues. 
    Can someone tell me why I am getting this error?
    Thanks,
    Shaibal

    Hi Mavis,
    Thank you for your response.  I am the full domain admin, and check and was part of both groups mentioned above.  Also, I have only one 2010 server with public folder, and so the command I am running on the 2013 looks like this: Set-OrganizationConfig
    -PublicFoldersEnabled Remote -RemotePublicFolderMailboxes PFMailbox1. I even just created a second user and mailbox using the console instead of the shell, and still no luck.
    Below is the error I get:
    [PS] C:\Windows\system32>Set-OrganizationConfig -PublicFoldersEnabled Remote -RemotePublicFolderMailboxes PFMailbox2
    Couldn't find object "PFMailbox2". Please make sure that it was spelled correctly or specify a different object.
        + CategoryInfo          : NotSpecified: (:) [Set-OrganizationConfig], ManagementObjectNotFoundException
        + FullyQualifiedErrorId : [Server=ZOR-EXCHANGE01,RequestId=cc567b2f-34d8-41ba-9261-143223566e06,TimeStamp=3/5/2015
        4:36:10 PM] [FailureCategory=Cmdlet-ManagementObjectNotFoundException] 2EF24201,Microsoft.Exchange.Management.Sys
      temConfigurationTasks.SetOrganizationConfig
        + PSComputerName        : zor-exchange01.zubatkin.lan

  • Error 1006 - Changing Ad Site for subnet where exchange 2013 servers was setup

    We wanted to change Ad site for subnet where exchange 2013 servers was setup.
    When we do that error id 1006 appear on 2 MBX Servers : 
    The Microsoft Exchange Mailbox Replication service was unable to process jobs in a mailbox database.
    Database: Database02
    Error: An attempt to logon cross-site for Mdb 'xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx' was prevented to Server 'yyyyyyyy-yyyy-yyyy-yyyy-yyyyyyyyyyyy' in Site 'DomainAAA/Configuration/Sites/SiteB'. Local site is 'DomainAAA/Configuration/Sites/SiteA'.
    DomainAAA - Our Domain
    SiteA - AD site which temporarily cover subnet A and Subnet B
    In subnet A are installed 2 DCs (Global Catalog) and other aplication servers.
    In subnet B are installed all EX2013 servers (2 MBX and 2x CAS) ,1 DC (Global Catalog) and other app servers.
    SiteB - new created AD site intended for subnet B
    These subnets are on diferent physical location.
    When we change Ad site for subnetB from the AD siteA to AD SiteB, above error appear.
    There is a object ExchEdgeSyncService under the AD site : SiteA ,  where the installation EX2013 was done.
    So do We need to create the new edgesyncservice under the siteB ?
    What steps do we have to make ?
    Our intention is to eventually remove all servers from the siteA and move to to SiteB.
    So that siteA will no longer exist.
    Thanks in advance , and sorry for bad english.
    Best regards

    Hi,
    Why don't you just extend the VLAN so you don't have to create another site and do changes so much
    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.
    Krisna Ismayanto | My blogs: Krisna Ismayanto | Twitter:
    @ikrisna

  • Mailbox migration between two Exchange 2013 servers is horribly slow

    Hi,
    when migrating mailbox between 2 exchange 2013 servers,it s horribly slow. I have found some articles which describing problems about content indexing and missing AD group. This is not my problem, I have tried solutions but it didn't work. Both exchange
    are next to each one, same VLAN, same switch. Just migrating between databases.
    When I start batch jobs it is migrating only 1 mailbox at once and speed is really slow (2000 - 3000 mail items per 5 minutes). So mailboxes which have 10GB it's migrating 3 hours. My server is on 1gbps LAN.
    I have also checked MsExchangeMailboxReplication.exe.config on both servers:
        MaxActiveMovesPerSourceMDB="20"
        MaxActiveMovesPerTargetMDB="20"
        MaxActiveMovesPerSourceServer="100"
        MaxActiveMovesPerTargetServer="100"
        MaxTotalRequestsPerMRS="100"
    Do you have any idea where to look why only 1 mailbox is migrating at once?
    Thanks

    Hello,
    For the reason why only 1 mailbox is migrating at once when you start batch jobs, there is no official articles or blog to explain it.
    I recommend you check if the speed is slower when you move a smaller mailbox. If the issue doesn't occur, I recommend you set
    the AllowLargeItems parameter.
    Here are some articles for your reference.
    New-MigrationBatch
    http://technet.microsoft.com/en-us/library/jj219166(v=exchg.150).aspx
    Exchange 2013 Local Mailbox Moves
    http://www.msexchange.org/articles-tutorials/exchange-server-2013/mobility-client-access/exchange-2013-local-mailbox-moves-part1.html
    If you have any feedback on our support, please click
    here
    Cara Chen
    TechNet Community Support

  • Sending email using Exchange 2013 defined email addresses not the account email address.

    Currently we are using exchange 2013. Let's say a user has a mailbox account defined that has a default email reply address of [email protected] Now I define additional email address for the same account. When the user tries to send an email he can only send from
    the default email address. Is it possible to send from a defined email anndress and not the default account email address?
    Best Regards
    Best Regards

    Not natively with Exchange.
    You will need 3rd party software if you want to have only one mailbox and the ability to send as any of the proxy addresses associated with it
    Example:
    http://www.ivasoft.biz/choosefrom2007.shtml
    Not sure if Exchange 2013 is supported with it yet
    Twitter!: Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

  • Moving witness server to CAS server two Exchange 2013 servers with a DAG

    Inherited a situation where there is one Exchange 2007 Build 83.6 server running on Win2008R2, acting as witness, and hub transport and yes is a file server too.  In addition there is relays, email and service accts that need to be moved to Exchange
    2013.  
    Presently  there are two Exchange 2013 cu3 servers that are part of a DAG that also run on Win 2008r2...  We wish to add another node to the DAG, and move the witness to another server.
    Do I need to also add a CAS Exchange 2013 server to replace the Ex 2007 server?
    Can this server also act as the Witness?
    What would be the best practices for this senario. All of these machines are VM's.

    Inherited a situation where there is one Exchange 2007 Build 83.6 server running on Win2008R2, acting as witness, and hub transport and yes is a file server too.  In addition there is relays, email and service accts that need to be moved to Exchange
    2013.  
    Presently  there are two Exchange 2013 cu3 servers that are part of a DAG that also run on Win 2008r2...  We wish to add another node to the DAG, and move the witness to another server.
    Do I need to also add a CAS Exchange 2013 server to replace the Ex 2007 server?
    Can this server also act as the Witness?
    What would be the best practices for this senario. All of these machines are VM's.
    With an odd number of nodes, the File Share Witness will not be used, but you can still define it.
    Any server ( any including any non-Exchange server) can serve as the FSW as long as its not a mailbox server n the DAG and it has the Exchange Trusted SubSystem group in the local admin group on that server.
    Since you are using VMs, ensure the FSW isn't on the same host as a MBX DAG member.
    Not sure what you mean by adding a CAS Exchange 2013 server. Do you mean you have not installed the CAS role yet for 2013? If so, then absolutetly you need one.
    Twitter!: Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

  • Resource Rooms replying with tentative instead of accepting - Exchange 2013

    We setup new resource rooms in Exchange 2013, but they are replying with tentative instead of accepting.  Here are the settings to one of them:
    RunspaceId                          : e360afe4-859c-4cd1-ba2e-4efb13350e3b
    AutomateProcessing                  : AutoUpdate
    AllowConflicts                      : False
    BookingWindowInDays                 : 180
    MaximumDurationInMinutes            : 1440
    AllowRecurringMeetings              : True
    EnforceSchedulingHorizon            : True
    ScheduleOnlyDuringWorkHours         : False
    ConflictPercentageAllowed           : 0
    MaximumConflictInstances            : 0
    ForwardRequestsToDelegates          : True
    DeleteAttachments                   : True
    DeleteComments                      : True
    RemovePrivateProperty               : True
    DeleteSubject                       : True
    AddOrganizerToSubject               : True
    DeleteNonCalendarItems              : True
    TentativePendingApproval            : True
    EnableResponseDetails               : True
    OrganizerInfo                       : True
    ResourceDelegates                   : {}
    RequestOutOfPolicy                  : {}
    AllRequestOutOfPolicy               : False
    BookInPolicy                        : {}
    AllBookInPolicy                     : True
    RequestInPolicy                     : {}
    AllRequestInPolicy                  : False
    AddAdditionalResponse               : False
    AdditionalResponse                  :
    RemoveOldMeetingMessages            : True
    AddNewRequestsTentatively           : True
    ProcessExternalMeetingMessages      : False
    RemoveForwardedMeetingNotifications : False
    MailboxOwnerId                      : domain.local/Users/Room - Boardroom
    Identity                            : domain.local/Users/Room - Boardroom
    IsValid                             : True
    ObjectState                         : Changed
    Any ideas?
    Thanks!
    --Kent

    http://technet.microsoft.com/en-us/library/dd335046(v=exchg.150).aspx
    Please change automateprocessing value to autoaccept
    Set-CalendarProcessing -Identity "5th Floor Conference Room" -AutomateProcessing AutoAccept

  • Public Folders on multiple Exchange 2013 servers

    Two companies (lets call them WestCoast Company and EastCoast Company) have merged. Each one has Ex2010 with PFs of local scope (the companies don't need access to each other's PFs). I want to move them to a single Exchange Organization with one Exchange
    server in each office and possibly a 3rd Exchange in a data center. I am looking for the best/simplest solution for those legacy PFs. Questions:
    - With Exchange 2010 I can only have one PF database so I will have to merge the PF structures. If the "master" PF DB sits in the data center I can choose which folders to replicate to each regional Exchange server (ie I can have only WestCoast
    folders on the WestCoast Exchange and similar for East Coast). Are these statements correct?
    With Exchange 2013:
    - Can I have more than one PF trees (one per PF mailbox) or am I limited to a single PF hierarchy?
    - If only one PF hierarchy, am I forced to have one location that holds all the content or can the content remain distributed in different locations?
    - Can I have content (or PF mboxes) that only show up on some of the Exchange servers? (ie WestCost PFs will show up only on WestCoast Exchange)
    - Do the PF limits (10,000 folders, 1 million items, etc) apply per PF mbox or for the whole thing?
    Thanks

    There is just one public folder hierarchy.  You can assign sub-trees under the root to different mailbox databases, though, and through permissions you could restrict who can see each of them.
    You can have public folder mailboxes mounted in different mailbox databases, with different databases mounted in different locations.  So you could have the Europe folders in a mailbox in a mailbox database mounted on a European server, and the Americas
    folders in a mailbox in a mailbox database mounted on an Americas server.
    You can do that but only by grouping public folder mailboxes in mailbox databases that are mounted where you want them to be mounted.  As stated before, you might be able to hide folders through permissions, not by where they are mounted.
    Yes, the 10,000-folder limit applies to the organization.  If you have more than that, wait until the limit is increased.
    Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

  • Method to use Set-EventLogLevel against all the Exchange 2013 servers.

    Recently Ran into an issue where we needed to troubleshoot an issue that required us to turn up the logging level across multiple exchange servers using the Set-EventLogLevel command. 
    I was trying to figure out a way to run this command without having to go to each of the exchange servers. 
    PSSession doesn't work because then your not running the exchange commandlets on that remote system.
    Invoke-Command doesn't work either.
    Unfortunately because of some security settings using Connect-ExchangeServer doesn't proxy in the command either. 
    So any ideas on how we can execute an exchange cmdlet against multiple exchange servers from powershell.
    Jeff C

    I can set it via this method on Exchange 2010, I don't have Exchange 2013 in front of me but it should be same I believe.
    This will set MSExchangeIS\9000 Private\Logons level from Lowest to Low of all the Exchange server in my environment
    $test = Get-ExchangeServer
    $test | %{Set-eventloglevel "$_\MSExchangeIS\9000 Private\Logons" -Level Low}
    To see if those are set or not run this...
    $test | %{get-eventloglevel "$_\MSExchangeIS\9000 Private\Logons"}
    Blog
    |
    Get your Exchange Powershell Tip of the Day from here

  • Exchange 2013 servers not sharing Free / Busy

    Some of the users on EXMB01 are not able to see users calendar Free / Busy information on EXMB02.
    In our exchange 2013 (CU5) environment the following server: mailbox EXMB01 and EXMB02, CAS EXCAS01, EXCAS02 and EXCAS03. Server are Windows server 2012, mail domain is mail.domain.com and does not match our internal network of local.domain.xyz
    (Non standard was setup before me).  All setting point to mail.domain.com for mail configuration.  External cert from a CA was added to all three CAS servers.
    USER1 on EXMB01
    USER2 on EXMB02
    USER3 on EXMB02
    Was able to get USER1 to see a USER3 can see all Free/Busy, subject, location now (only set the Free/Busy time) .  Added USER02 see Free / Busy, subject, location (also only set Free/Busy time). Added my own calendar to the USERS01 to the
    USERS01 outlook and can see my Free/Busy, subject, location.  I only have by default Free/Busy time set no one else added.
    What settings to I check first? Is their a PowerShell command to reset a users calendar permissions?  Is something not set correctly on the servers? 

    http://public.wsu.edu/~brians/errors/their.html
    Get-MailboxFolderPermission
    https://technet.microsoft.com/en-us/library/dd335061
    Set-MailboxFolderPermission
    https://technet.microsoft.com/en-us/library/ff522363
    Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

  • Forwarding emails in Exchange 2013, when the recipitent of teh forward emails is also in the to box, she recieves no emails at all

    I have put a forward onto an user account who has gone on maternity leave,
    When an email is sent to her it is recieved by the person it is being forwarded to without issue, however when the person it is being forwarded to is also in the to box, she does not recieve either mail, the one sent to her or the forwarded mail.
    Anyone have any idea why this is happening?

    Can you track the email to see what happened with the email?

  • In-Place Hold Combined with In-Place Archiving in Exchange 2013

    Hi,
    In-Place Hold is enabled for a mailbox and set to keep everything indefinitely.  The same mailbox has a Retention Policy with a Default Policy Tag set to move everything to an archive mailbox after 2 years.
    Let's say the user keeps mail in the primary mailbox and 2 years passes.  This piece of mail should then be moved to the archive mailbox.  When this happens, does the indefinite In-Place Hold mean that the mail is ALSO kept in the primary mailbox
    (in the Recoverable Items Folder)?
    Or is the In-Place Hold smart enough to consider both the primary and archive mailbox as a single "whole" and would therefore completely purge the mail from the primary mailbox when it is moved to the archive?
    Obviously I would expect if the user were to subsequently delete the mail from the archive mailbox that In-Place Hold would actually keep the mail in the Recoverable Items Folder in the archive mailbox.
    I am essentially trying to determine if In-Place Hold effectively nullifies any space saving in the primary mailbox when mail is archived or whether the two mailboxes are treated as a single "whole" for the purpose of the hold.
    Cheers,
    David

    Hi,
    Thanks for the reply.  If that is the case, doesn't that effectively mean that when In-Place Hold is active, any In-Place Archive process actually ends up creating a second copy of the mail and therefore using twice as much space?
    One copy in the Archive mailbox and one copy kept in the Recoverable Items Folder (due to the In-Place Hold) in the Primary mailbox.
    My feeling is that Microsoft would have been smart enough to get this right and Exchange will actually bypass the In-Place Hold functionality in the specific case when the mail is being moved to the Archive - but this is just a guess.  I'd like to know
    for sure.
    Cheers,
    David

  • 2 Exchange 2013 Servers in 2 sites

    Hi. I have 2 Exchange Servers total, one in main site and the other one in a branch ofice. Both of them belongs to the same forest, and also both of them have MBX
    and CAS roles installed. The goals is to have them in a Database Copy configuration so both of them have the same DBs in case of an issue with any of them (if this is the proper design configuration).
    After 2nd server installation I'm not able to connect to it through PowerShell (even though I'm logged on locally in it) as it redirects the connection to the 1st server. Within ECP (of the primary one) I can't see the 2nd server in the Servers tab, nor
    the default DB it hosts.
    I'm very confused about what the design must be in order to have them replicated with the same functionality. Would you please advice?
    Thanks!
    Infrastructure Management Sr. Analyst | MCSA Windows Server 2012

    As for the design, I would probably add another node in the primary site so you have some local HA.  What happened after you forced replication?  Did it show up in the EAC?  What happens if you go into the shell in the main site and run get-exchangeserver?
    Can you also make sure that the Exchange Trusted Subsystem security group is a  local administrator on both Exchange Servers?  Also, make sure you have a global catalog in each site .
    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