Edge Transport Server - Exchange 2013 coexistence Exchange 2007

Hi Exchange-Gurus,
We have one Exchange Org.
sub AD Domain1: A.domain.com (with Exchange 2007 SP3 R10)
sub AD Domain2: B.domain.com (with Exchange 2013 CU6); DMZ contains Exchange Transport Server - Exchange 2013
Is it possible to install within the DMZ of AD Domain1   a Edge Transport Server - Exchange 2013?
Thanks.
Guitarman

Hi Guitar,
Thank you for your question.
Is it possible to install within the DMZ of AD Domain1 
an Edge Transport Server - Exchange 2013?
A: Yes, we could create an Exchange 2013 Edge server on the DMZ of AD domain1.
Notice: Before we create an EdgeSync Subscription between an Exchange 2007 Hub Transport server and an Exchange 2013 SP1 Edge Transport server, we need to install Exchange 2007 SP3
Update Rollup 13 or later on the Exchange 2007 Hub Transport server.
We could refer to the following link:
https://technet.microsoft.com/en-us/library/aa996719(v=exchg.150).aspx
If there are any questions regarding this issue, please be free to let me know.
Best Regard,
Jim

Similar Messages

  • Exchange active sync cannot connect to server after migration mailbox user from exchange 2007 to exchange 2013 coexistence

    Hello, everyone, my name is rafl
    I have a problem with exchange 2013 active sync.
    I have installed exchange 2013 coexistence with legacy exchange 2007, I have to migrate user mailboxes: [email protected] from exchange 2007 to exchange 2013.
    but any problem with active sync connection on the mobile device after moving mailbox user. I reconfigure the exchange ActiveSync external connection domain (latest.domain.com) on mobile device replacing legacy exchange ActiveSync external connection domain
    (legacy.domain.com)
    the process of moving mailboxes successfully without error.
    Access OWA for exchange 2007 and exchange 2013 is running normally
    access mail from Outlook running normally
    Certificate request has been installed and has no problem with it
    The OWA virtual directory is configured for internal and external connections and different from the legacy exchange
    The autodiscover virtual directory is configured for internal and external connections and different from the legacy exchange
    ActiveSync virtual directory is configured for internal and external connections and different from the legacy exchange
    user mailboxes are still on exchange 2007 is not problematic.
    only problem with Exchange Active Sync on mobile devices, where I set up an email with android, iphone, windows phone. the error message: cannot connect to the server.
    but, if I create a new user and create user mailboxes directly in exchange server 2013, ActiveSync can run without error on mobile device, access through OWA, MsOutlook, Outlook Anywhere also run normally.
    only the results of user migration from exchange 2007 to exchange 2013 which is troubled with exchange ActiveSync connection.
    any ideas for this problem, and what should I check on the exchange server ..?

    i have run the activesync test connectivity and get some error :
    Testing TCP port 443 on host domain.co.id to ensure it's listening and open.
    The specified port is either blocked, not listening, or not producing the expected response.
    A network error occurred while communicating with the remote host.
    Elapsed Time: 3091 ms.
    Testing TCP port 443 on host autodiscover.domain.co.id to ensure it's listening and open.
    The specified port is either blocked, not listening, or not producing the expected response.
    A network error occurred while communicating with the remote host.
    Elapsed Time: 21072 ms.
    Testing TCP port 80 on host autodiscover.domain.co.id to ensure it's listening and open.
    The specified port is either blocked, not listening, or not producing the expected response.
    A network error occurred while communicating with the remote host.
    Elapsed Time: 21049 ms.
    I have allowed access to port 443 (https) and 80 (http) on the firewall and re-run testconnectivity, but still with the same results. if I enable active sync for users who created directly in Exch 2013 there is no problem with the ActiveSync, just a problem
    for users who moved from Exch 2007 to Exch 2013. @Android, iPhone, and Blackberry the error message "cannot connect to the server"

  • Deploy Exchange 2013 Edge Transport Server for multi-site environment

    Hi,
    I have a multi-site Exchange 2013 environment. The configurations are as below.
    Active Directory Sites and Exchange Servers.
    SiteA - EXMB1 & EXCAS1
    SiteB - EXMB2 & EXCAS2
    SiteC - EXMB3 & EXCAS3
    All sites are connected via VPN. (Good speed. No latency issues)
    All the three Mailbox Servers are in DAG. Only one mailbox database. All servers running Exchange 2013.
    I am planning to deploy Edge Servers in the infrastructure (I am doing it for the first time). Normally, it will be in DMZ.
    Now, I can deploy 2 Edge Servers for reliability.
    Question.
    1. Can I deploy 2 Edge Servers and create subscription to all the mailbox server in 3 different site? Or, is it like one edge server can make subscription to only mailbox servers in one Active Directory Site? I am not sure about this and could not find much
    information from TechNet.
    One Edge Server can make subscription to all 3 mailbox server in 3 sites. Similarly, I can make the subscriptions in the second edge server as well. Configure 2 external MX records with the same priority so that there will be some load balancing.
    Also, in such a case if the mailbox database become active from a different site, I need not make any new changes to the Edge Servers right?
    2. If the first way is not correct, I will have to deploy 1 Edge Server each for each of the Active Directory Site. (In DMZ only, not in domain)
    Make Edge Subscription to the mailbox server in corresponding site.
    Make 1 MX record and point it to the Edge Server which is subscribed to the Mailbox Server from which the Database is Active. The problem is, every time will have to change the DNS record when ever the database copy is activated from a different mailbox
    server. And the issues with propagation.. delay..
    I am not sure which of the above 2 ways will work. Appreciate suggestions from anyone who have previous experience with similar infrastructure.
    Thanks in advance. :)

    Hi 
    One or more Edge Transport servers can be subscribed to a single Active Directory site. However, an Edge Transport server can't be subscribed to more than one Active Directory site. If you have more than one Edge Transport server deployed, each server can be
    subscribed to a different Active Directory site. Each Edge Transport server requires an individual Edge Subscription.
    A subscribed Edge Transport server is associated with a particular Active Directory site. If more than one Mailbox server exists in the site, any of them can replicate data to the subscribed Edge Transport servers.
    I don't think there is a solution to subscribe  edge servers for more than 1 site. Edge Servers can be scoped only to one site.
    Remember to mark as helpful if you find my contribution useful or as an answer if it does answer your question.That will encourage me - and others - to take time out to help you Check out my latest blog posts on http://exchangequery.com Thanks Sathish
    (MVP)

  • Does Edge transport server for Exchange 2013 work with Exchange 2010?

    Hello everyone,
    I want to install Edge transport server for my Exchange servers,
    Could you tell me if Edge transport server 2013 works with Exchange 2010?
    Thank you in advance

    Hello
    tip:
    https://technet.microsoft.com/en-us/library/jj898583%28v=exchg.150%29.aspx
    2   If you want to create an EdgeSync
    Subscription between an Exchange 2010 Hub Transport server and an
    Exchange 2013 SP1 Edge Transport server, you need to install Exchange
    2010 SP3 Update Rollup 5 or later on the Exchange 2010 Hub Transport
    server.
    sorry my english

  • Outlook Anywhere settings in a Exchange 2013 coexistence scenario with Exchange 2007

    I have exchange 2013 and 2007 set up in a coexist environment.  At the moment, the few mailboxes I am testing on Exchange 2013 are getting multiple pop ups in outlook and cannot connect to items like Public Folders on 2007.  I found an article
    that told me to change the authentication method from Negotiate to NTLM and that broke some of my Lync 2013 compatibility issues on users on exchange 2007 (ie conversation history and they got outlook integration errors.)  I would like someone to confirm
    if the change I am about to make from doing research will help me in my situation.
    Current Setup:
    Exchange 2007 OA CAS Settings
    ExternalClientAuthenticationMethod : Basic
    InternalClientAuthenticationMethod: NTLM
    IISAuthenticationMethods : {Basic, Ntlm}
    Exchange 2013 OA CAS Settings
    ExternalClientAuthenticationMethod : Negotiate
    InternalClientAuthenticationMethod: Negotiate
    IISAuthenticationMethods : {Basic, Ntlm, Negotiate}
    New Settings I am considering based on research:
    Exchange 2007 OA CAS Settings
    ExternalClientAuthenticationMethod : Basic
    InternalClientAuthenticationMethod: Basic
    IISAuthenticationMethods : {NTLM}
    Exchange 2013 OA CAS Settings
    ExternalClientAuthenticationMethod : Basic
    InternalClientAuthenticationMethod: Basic
    IISAuthenticationMethods : {Basic}
    Will this work and eliminate my popups?

    Hi,
    The following TechNet article indicates that:
    “In order to support access for Outlook Anywhere clients whose mailboxes are on legacy versions of Exchange, you will need to make some changes to your environment which are documented in the steps within the
    Exchange Deployment Assistant. Specifically,
    you will need to enable Outlook Anywhere on your legacy Client Access servers and enable NTLM in addition to basic authentication for the IIS Authentication Method.”
    Client Connectivity in an Exchange 2013 Coexistence Environment
    http://blogs.technet.com/b/exchange/archive/2014/03/12/client-connectivity-in-an-exchange-2013-coexistence-environment.aspx
    As for the Autodiscover service, please make sure the Autodiscover.domain.com is pointed to your Exchange 2013 in Internal and External DNS. For more detailed information about Exchange 2013 coexistence with Exchange 2007, please refer to:
    http://blogs.technet.com/b/meamcs/archive/2013/07/25/part-3-step-by-step-exchange-2007-to-2013-migration.aspx
    Regards,
    Winnie Liang
    TechNet Community Support

  • Exchange 2010 edge transport server, degraded desktop / remote desktop

    I have a 2010 edge transport server loaded on windows server 2008 R2 that after about 3 days will no longer allow RDP connections or desktop logons due to a serious performance lag / time out. A reboot clears the performance issue for about another 3 days. 
    I allowed an RDP connection to stay open for the 3 days and it continues to work however actions like trying to load the task manager, start button, computer or any windows not currently open takes an extremely long time. Task manager and perf mon show very
    little processor and memory usage. 
    Tried the following to resolve:
    Replaced hard drives (raid 1)
    Replaced server (moved drives from one server to another chassis)
    Monitoring iops, memory usage and proc transactions. Nothing shows any unusually high usage.
    I tried disabled AV services, log monitoring and backup services both while the issue was happening and as preventative measure before the issue arose.  

    hi cna you check if by any chance you have bandwidth limitations configured. either on router or on tour switch. i had this kind of issue and it ended with bandwidth issue which was configured wrongly. you said this is happening with RDP. hows the performance
    when accesing locally
    did you check performance counters and event viewer.. anything there
    Mark as useful or answered if my replies helped you solving your query.
    Thanks, Happiness Always
    Jatin
    Skype: jatider2jatin, Email: [email protected]

  • Cannot send mail from Exchange 2013 to Exchange 2007

    I have an
    Exchange 2007server with all roles in the same server (Version:
    08.03.0327.001 ) on a Windows 2008 R2 server. I have now installed two Exchange 2013 servers both with CAS and MBX roles on Windows 2012 servers
    (full patched). There is also a DAG between the new servers. All mail goes through a BorderWare besides the internal mail.
    I can send mail from both environments to the Internet. I can also send internal mail from Exchange 2007 to Exchange 2013.But the problem is that I am unable to send from Exchange 2013 to Exchange 2007. I've debugged, but not solved the problem and there are
    few articles on the Internet.
    Any suggestions?

    These two sentences are in conflict : "I can also send
    internal mail
    from Exchange
    2007 to
    Exchange 2013. But
    the problem is
    that I am unable
    to send from Exchange
    2007 to
    Exchange 2013. "
    Can you describe what is your real problem? Flow from E2007->E2013? Or vice versa?
    Please mark as helpful if you find my contribution useful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you. Thank you! Damir

  • Introduce an "passive" Exchange 2013 in Exchange 2010 environment without user or administration impact.

    Hi
    We wish to introduce an Exchange 2013 server in our existing Exchange 2010 environment.
    The Exchange 2013 server is only needed for migration purposes where we wish to leverage the new features of the migration-batch functionality.
    It’s important that the Exchange 2013 server will not have any “visible” impact on the Exchange 2010 environment, or take over any functionality, right now, since the customer wish to stay on 2010.
    Can you guys come up with anything to be aware of?
    Oblivious we disable the Autodiscover SCP for the Exchange 2013 server, so that the clients will not hit this server. Nor will we point any URLs to the Exchange 2013
    I can see that a new “Default Offline Address Book (Exch2013)” is created and set as default when EX2013 is installed. We will change this back to the default EX2010.
    The server will properly take part in the Shadow Redundancy feature, and is doesn’t seem to be possible to exclude the server or avoid, unless disabling Shadow Reduncancy.
    I can only come up with these 3 things that will have a "direct" impact on the environment, but any input will be highly appreciated!
    BR,
    Martin

    Hi,
    I agree with Li Zhen’s suggestion. If you don’t migrate from Exchange 2010 to Exchange 2013, we can disable add services in Exchange 2013 and don’t use it any more.
    If you want that the Exchange 2013 server will not have any “visible” impact on the Exchange 2010 environment, or take over any functionality, please keep the published server to pointed to Exchange 2010. Then the original configuration in Exchange 2010
    would not be changed to the new configuration in Exchange 2013.
    If you want to use Exchange 2013, then we can point the published server to Exchange 2013 and configure the virtual directories in Exchange 2013. Though all mailboxes are still located in Exchange 2010, all external requests would be proxy or redirected
    from CAS 2013 TO CAS 2010 automatically.
    For more information about Client Connectivity in an Exchange 2013 Coexistence Environment, please refer to:
    http://blogs.technet.com/b/exchange/archive/2014/03/12/client-connectivity-in-an-exchange-2013-coexistence-environment.aspx
    Regards,
    Winnie Liang
    TechNet Community Support

  • Exchange 2013 and Exchange 2010 coexistense

    We have a and exchange 2010 organization with SP3 on most servers except for one 2010 CAS server that still requires SP1 for the purpose of legacy application compatibility. Can we introduce exchange 2013 in the org or will the setup detect
    that there is an exchange 2010 server still with SP1 and fails to continue?

    Hi,
    For Exchange 2013 coexistence with Exchange 2010, the mininum version of Exchange server is Exchange 2010 SP3 on all Exchange 2010 servers in the organization. For more information about it, please refer to the Coexistence of Exchange 2013 and earlier versions
    of Exchange server part in the article below:
    http://technet.microsoft.com/en-us/library/jj898583(v=exchg.150).aspx
    Personal suggestion, please upgrade your legacy application to the latest version which is supported with Exchange 2010 SP3 or higher Exchange version.
    Regards,
    Winnie Liang
    TechNet Community Support

  • Positioning and role of Edge Transport Server

    Good afternoon, all!
    I'm working on a new Exchange design and implementation project.  I had some research that seemed to indicate that I could have my Edge Transport server in the DMZ to receive Internet mail and to act as a web proxy for the Client Access server residing
    in the internal network.  However, in my testing I haven't found where that is possible.
    Will the Edge Transport server provide that capability or will I need to open a path to the Client Access/Mailbox server?  Is there a tradeoff in separating the Client Access server into a separate machine in the DMZ for remote access, that is, if the
    Edge Transport server won't supply web proxy services, will I need to make a separate machine for Client Access?
    Thanks!
    Gregg

    Hi Gregg,
    Based on my knowledge, Edge Server role handles Internet-facing mail flow and act as an SMTP relay and smart host for Exchange servers in your internal network. We can use Edge server if don't want to expose internal CAS and MBX. We can also
    configure Anti-Spam on Edge server to block specific emails.
    Unlike other Exchange server roles, the Edge server doesn’t need to be a member of an AD domain, so locating it within a DMZ does not create any difficult firewall configurations.
    Confirm that any firewall between your Exchange servers and Edge servers allow port 53 for DNS resolution and port 25 for SMTP traffic.
    Thanks
    If you have feedback for TechNet Subscriber Support, contact
    [email protected]
    Mavis Huang
    TechNet Community Support

  • Edge Transport Server Limitations - messages delivered per day?

    I'm currently on the hunt for some kind of baseline / benchmark that will indicate how many messages per day (or per second) an Edge Transport server is capable of handling. I feel like this should be in some whitepaper somewhere for when Edge Transport
    is designed, so you know how many to deploy, but I can't find it.
    I know system specs will be a factor. We have the current hardware in our box:
    2 processors (2.67 GHz)
    16 GB RAM
    64-bit OS (Windows Server 2008 R2 Enterprise)
    If anyone has come across any kind of guideline for email delivery limitations of ET, I'd appreciate being pointed to them.
    Thanks

    The current Exchange servers are much faster and beefier than they were when I worked with Exchange 4 Beta 2 with a customer many years ago.  They tried to swamp their Exchange server (dual 90 MHz Pentium server with 128 MB RAM) using six Unix workstations
    running Mailstorm against it.  They had to stop when their primary Unix systems handling inbound email were overloaded due to how they set up their test.  And the Exchange server never skipped a beat.
    Another customer situation that may help is that I have seen 10,000 messages in an Exchange 2010 queue (due the smart host they were using for external delivery was offline for maintenance) drop to zero within 15 minutes.  I'd suggest that you run some
    sort of test of your own to determine how many messages your edge is capable of delivering, but these may give you an indication of the expected capabilities.

  • Migrating to Exchange 2013 from Exchange 2003, EV7, Office 2003 and XP

    What is the best approach for migrating our 300 user Exchange 2003 organisation to Exchange 2013.? We use Enterprise vault v7.5 and the clients are Office 2003 on an XP desktop.
    We are also planning to upgrade to Windows7 and Office 2013 this year so I am trying to understand the sequence. Should we just aim to upgrade to Exchange 2010 with Outlook 2010 instead?
    Many thanks.

    Hi,
    You can't install Exchange 2013 until and unless you decommission your Exchange 2003. Coexistence of Exchange 2013 with Exchange 2003 is not supported. You first need to upgrade to Exchange 2010 SP3 and then move users to Exchange 2010 and decommission your
    Exchange 2003 servers. Once you are done with the decommissioning of your Exchange 2003 server you will be able to install your first Exchange 2013 machine in your messaging infrastructure.
    Kindly mark this as answer if it fulfill your requirements. Thanks.
    Regards, Riaz Javed Butt Consultant Microsoft Professional Services MCITP, MCITP (Exchange), MCSE: Messaging, MCITP Office 365

  • Exchange 2013 CU2/Exchange 2010 SP3 Coexistance OWA Redirection

    Hi, 
    I am trying to sign into OWA 2013 with a 2010 mailbox user and I just get the following page
    something went wrong
    Sorry, we can't get that information right now. Please try again later. If the problem continues, contact your helpdesk.
    Want to be able to use your email when you're offline?
    Next time you are connected:
    1. At the top of Outlook Web App, next to your name, click Settings
    2. Click Offline settings and turn on offline access
    3. That's it! You'll never see this message again.
    I checked the logs and it looks like it might be trying to redirect to the Exchange 2010 Front end. 
    Exchangecas13 is the 2013 CAS server, Exchangefe1 is the 2010 CAS/Transport Server.  
    2013-07-26T20:42:01.691Z,8e66a7cb-63bc-4651-b769-d0062f7c7665,15,0,712,12,,,,,,,,,,,,,EXCHANGECAS13,,,,,,,,,,,,,,,,,,,,,,,,,,600050.0544,,,,,,,,,,,,,,,,,,S:ActivityStandardMetadata.Action=GlobalActivity;I32:ADR.C[SUPPR]=6;F:ADR.AL[SUPPR]=2.428583;I32:ADS.C[SUPPR]=1;F:ADS.AL[SUPPR]=2.1359,
    2013-07-26T20:42:18.433Z,17bed7ea-9bce-4759-bdd5-c8a25667f521,15,0,712,12,,Owa,exchangecas13,/owa/,,FBA,False,,,,Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.1; WOW64; Trident/6.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; .NET4.0C;
    .NET4.0E; MS-RTC EA 2; Media Center PC 6.0; InfoPath.3),192.168.1.30,EXCHANGECAS13,302,,,,,,,,,,,,0,,,,,,,,,,,,,2,,,,,,,,,,,,1,1,1,1,,,OnBeginRequest=0;NoCookies=302 - GET/E14AuthPost;,
    2013-07-26T20:42:18.438Z,41574515-5ea0-43b4-8a13-d327ec109d19,15,0,712,12,,Owa,exchangecas13,/owa/auth/logon.aspx,,FBA,False,,,,Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.1; WOW64; Trident/6.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729;
    .NET4.0C; .NET4.0E; MS-RTC EA 2; Media Center PC 6.0; InfoPath.3),192.168.1.30,EXCHANGECAS13,200,,,,,,,,,,,,0,,,,0,,,,,,,,,1.9969,,,,,,,,,,,,1,1,1,1,?url=https%3a%2f%2fexchangecas13%2f&reason=0,,OnBeginRequest=0;,
    2013-07-26T20:42:18.464Z,02c9d811-e43d-4dab-a1eb-78a85b73f3e5,15,0,712,12,,Owa,exchangecas13,/owa/auth/logon.aspx,,FBA,False,,,,Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.1; WOW64; Trident/6.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729;
    .NET4.0C; .NET4.0E; MS-RTC EA 2; Media Center PC 6.0; InfoPath.3),192.168.1.30,EXCHANGECAS13,200,,,,,,,,,,,,0,,,,0,,,,,,,,,2.0001,,,,,,,,,,,,1,1,1,1,?replaceCurrent=1&url=https%3a%2f%2fexchangecas13%2f,,OnBeginRequest=0;,
    2013-07-26T20:42:24.930Z,54e8f566-4c32-4fbe-9e84-d56bee916785,15,0,712,12,,Owa,exchangecas13,/owa/auth.owa,,FBA,True,LWGINC\pslager,,Sid~S-1-5-21-1186999560-1424097373-3473557-14162,Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.1; WOW64; Trident/6.0; SLCC2;
    .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; .NET4.0C; .NET4.0E; MS-RTC EA 2; Media Center PC 6.0; InfoPath.3),192.168.1.30,EXCHANGECAS13,302,,,POST,,,,,WindowsIdentity,,,,121,,,,1,17,,0,,0,,0,0,19.9095,0,,,,,,,,17,1,,18,18,19,19,,,OnBeginRequest=0;DownLevelTargetHash=0/0/1;ClientAccessServer=EXCHANGEFE1.LWGINC.com;ResolveCasLatency=0;,
    2013-07-26T20:42:24.937Z,f81832cf-43c4-49ed-942f-3ff1e951bd6a,15,0,712,12,,Owa,exchangecas13,/owa/auth.owa,,FBA,True,LWGINC\pslager,,Sid~S-1-5-21-1186999560-1424097373-3473557-14162,Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.1; WOW64; Trident/6.0; SLCC2;
    .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; .NET4.0C; .NET4.0E; MS-RTC EA 2; Media Center PC 6.0; InfoPath.3),192.168.1.30,EXCHANGECAS13,302,,,POST,,,,,WindowsIdentity,,,,121,,,,0,1,,0,,0,,0,0,2.9963,1,,,,,,,,1,0,,2,2,2,2,,,OnBeginRequest=0;DownLevelTargetHash=0/0/1;ClientAccessServer=EXCHANGEFE1.LWGINC.com;ResolveCasLatency=0;,
    Any ideas?

    Hi
    One try， please move administrator mailbox to 2013 server
    Cheers
    If you have any feedback on our support, please click
    here
    Zi Feng
    TechNet Community Support

  • Risk of not having an Edge Transport server

    What is the risk of not using an Edge Transport server? Is it worth the extra cost? Environment is Exchange 2010 and ForeFront TMG 2010.

    Hi,
    if the internal server can handle the load I don't see any problem.
    Regarding the CAS server is facing the Internet you should have a firewall in front of it that stopps most of the attacks.
    Greetings
    Christian
    Christian Groebner MVP Forefront

  • Exchange 2013 CU5 , Exchange Power Shell very very very slow reasponse when using get command.

    Exchange 2013 CU5 , Exchange Power Shell very very very slow reasponse when using get command.
    First my organize has Exchange on 2 site like
    site A (internet facing) : 2CAS 2 MB all are Services pack1
    site B (DR Site , no user active on this site) : 2CAS 2MB all are Services pack 1
    so today I upgrade Exchange 2013 from SP1 to CU5 start on "site B" and I found this issue and the details is....
    When I open EMS on any CU5 for query something (like get-mailboxdatabasecopystatus) the response return very slow and some query will not return at all (like get-owavirtualdirectory).
    But If I using EMS on SP1. Everything is ok then I try to use EMS on SP1 connect to CU5 and try to query something. the result is
    some query command cannot return for any result that are server on siteB (just some query command)
    Problem
    EMS on CU5 return very slow result.
    EMS on SP1 still ok.
    Does anyone face this problem before for CU5??? Please help me figure this out. Thank you
    reply from Social.technet

    Hi,
    Have you used the above cmdlets to check your Exchange server health?
    "all other command that I ran on EMS didn't logged on event viewer.", my environment is the same with you. I use Exchange 2013, only errors will be displayed in MSExchange Management. Actually, it is not related to slow EMS response.
    Hope it helps.
    Best regards,
    Amy Wang
    TechNet Community Support

Maybe you are looking for