Is it supported to connect Exchange 2013 Mailbox using Exchange 2010 CAS in Co-existence?

Hi Team,
I am in the phase of upgrading Exchange 2010 to 2013, and introduced 4 MBX and 2 CAS of 2013 servers in co-existence.
Only one production mailbox of 2010 moved to 2013. The owa of the mailbox moved to 2013, is working OK internally coz only internally configured, but when I configure outlook using 2010 settings, it got configured but when I open outlook it doesn't
open and throws an error of some "cannot open set of folders".
Is it supported to connect Exchange 2013 Mailbox using Exchange 2010 CAS in Co-existence? because I havnt configured 2013 CAS servers yet.
Kindly share some KB or tip. Any help is appreciated. Thank You.
Muhammad Nadeem Ahmed Sr System Support Engineer Premier Systems (Pvt) Ltd T. +9221-2429051 Ext-226 F. +9221-2428777 M. +92300-8262627 Web. www.premier.com.pk

I'll change Adam's wording slightly - you *MUST* install a CAS 13 server into every site where there is a MBX 13 server.
Cheers,
Rhoderick
Microsoft Senior Exchange PFE
Blog:
http://blogs.technet.com/rmilne 
Twitter:   LinkedIn:
  Facebook:
  XING:
Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

Similar Messages

  • Exchange 2013 mailbox added to the CAS array

    We are upgrading to Exchange 2013 from Exchange 2010. Following the development guide, we have
    installed the first mailbox server in the Exchange 2010 environment which has 3 Exchange 2010 CAS server
    in the array. When installing the mailbox role, we did not choose the client access role but after
    the installation we can see that the Exchange 2013 Mailbox server is added to the CAS array and yet
    we did not choose the client access role. How does this happen, and to proceed ?

    I see the same thing in my lab:
    Get-ClientAccessArray | FL
    RunspaceId        : 16b992b3-270f-4ae1-a3c3-fa9e2ea73d69
    ExchangeLegacyDN  : /o=Wingtiptoys/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=Ou
                        tlook.wingtiptoys.ca
    Fqdn              : Outlook.wingtiptoys.ca
    Site              : wingtiptoys.ca/Configuration/Sites/Default-First-Site-Name
    SiteName          : Default-First-Site-Name
    Members           : {EXCH-2010, EXCH-2013}
    AdminDisplayName  :
    ExchangeVersion   : 0.1 (8.0.535.0)
    Name              : Outlook.wingtiptoys.ca
    DistinguishedName : CN=Outlook.wingtiptoys.ca,CN=Arrays,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administr
                        ative Groups,CN=Wingtiptoys,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=wingtiptoys,DC=ca
    Identity          : Outlook.wingtiptoys.ca
    Guid              : 27968af1-1624-4ff3-85c8-e38e68183afe
    ObjectCategory    : wingtiptoys.ca/Configuration/Schema/ms-Exch-Client-Access-Array-2
    ObjectClass       : {top, server, msExchExchangeServer, msExchClientAccessArray}
    WhenChanged       : 4/12/2014 12:51:18 PM
    WhenCreated       : 4/12/2014 12:51:18 PM
    WhenChangedUTC    : 4/12/2014 7:51:18 PM
    WhenCreatedUTC    : 4/12/2014 7:51:18 PM
    OrganizationId    :
    OriginatingServer : DC-1.wingtiptoys.ca
    IsValid           : True
    Cheers,
    Rhoderick
    Microsoft Senior Exchange PFE
    Blog:
    http://blogs.technet.com/rmilne 
    Twitter:   LinkedIn:
      Facebook:
      XING:
    Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

  • Exchange 2013 EAC will not run with Exchange 2010 CAS\HT servers shut down.

    Hi Folks,
    A little background - We have just migrated all our user mailboxes and public folders to Office 365 using a hybrid configuration. Now that the migration is essentially finished, I'd like to decommission our on-prem Exchange infrastructure and remove the
    hybrid config. We are using dirsync with password sync to replicate our AD to the cloud.
    I've read that even if you remove your hybrid configuration, it's a good idea to keep one on-prem Exchange server around so you can edit Exchange attribs (such as email addresses) in a supported manner, rather than using ASDI edit, etc.
    To this end, I installed a single Exchange 2013 CA\MBX server. After installation, the EAC worked fine, and I was able to view our on-prem users, groups, etc. Last week, I shut down our two Exchange 2010 CAS\HT servers as a test to see if anything broke
    prior to decommissioning them (these were the hybrid servers as well). After doing so, the Exchange 2013 EAC no longer works for some reason, and behaves in a very bizarre fashion. About once every 20 times or so, it will actually start and run. The other
    times, it just has you enter your creds, then generates an HTTP 500 internal server error after entering them. It seems to make no difference if you attempt to access it by the fqdn, hostname, or localhost right on the box itself. Same behavior on Chrome or
    IE.
    Today as a test, I started up one of the 2010 CAS servers and lo and behold, the 2013 EAC ran without difficulty again. Any idea why this might be so? Thanks for any help,
    Ian

    Hi,
    From your description, I recommend you use the following URL to check if you can access EAC. I see it works for several people about this issue.
    https://<Exchange 2013 CAS FQDN>/ecp?ExchClientVer=15
    Hope it helps.
    Best regards,
    Amy Wang
    TechNet Community Support

  • Exchange 2013 CAS functionality in coexistence with Exchange 2010 CAS

    Hi,
    I am planning to migrate Exchange 2010 to Exchange 2013 for 15000 users. We have a pool of 6 CAS 2010 servers added in a single CAS array. So my question is if we introduce a new CAS 2013 server in same site then will it affect CAS traffic anyway ? If we
    point our HLB to all CAS servers including CAS 2010 and CAS 2013 so will the CAS 2010 servers wil take traffic or is it only CAS 2013 servers who will take traffic. We will be putting same URLs in CAS 2013 same as CAS 2010. I have read lot of MS articles and
    all say that CAS 2013 should be enabled for CAS traffic and it will proxy request to CAS 2010. But I am not sure if we will face any CAS traffic issue whenever we will introduce CAS 2013 servers in same site and traffic will be pointed to CAS 2010 and CAS
    2013 both. Is it possible to add CAS 2013 in Exchange 2010 CAS array ? Please guide. Thanks in advance.

    For mailbox that exist on Exchange 2010, EXCH2013 CAS will proxy the request to an Exchange 2010 Client Access servers that exists within the mailbox’s local site.
    For mailboxes that exist on Exchange 2013, EXCH2013 CAS will proxy the request to the Exchange 2013 Mailbox server that is hosting the active copy of the user’s mailbox which will generate the Autodiscover response.
    -->Is it possible to add CAS 2013 in Exchange 2010 CAS array ? 
    No. CAS Array is no longer exits in Exchange 2013. But concept of a single namespace for Outlook connectivity remains. Please check this and this. In
    your case you dont need to worry as you have a HLB in place it will do the job
    When a new exchange2013 is deployed Outlook Anywhere has been enabled on all Client Access servers within the infrastructure and the mail.contoso.com and autodiscover.contoso.com namespaces have been moved to resolve to Exchange 2013 Client Access server
    infrastructure. In your case it is pointed to both as you have a load balancer in place but the same URL should be configured in exch2013
    Make sure you have exchange2010-SP3  minimum as it is the prerequisite requirement for upgarding EXCh2010 to 2013. 
    Please check the exchange server deployment assistant
    tool for moving mailboxes
    After moving a mailbox check the URLs. Configure autodiscover,EWS,OAB URLs on exchange2013. Please check this as
    well for checking URLs.
    I hope you know MAPI/RPC (RPC over TCP) traffic is now replaced with RPC over HTTP/s instead in exch2013. 
    Thanks
    MAS
    Please don't forget to mark an answer if it answers your question or mark as helpful if it helps

  • Catalyst SLB - Exchange 2010 CAS RPC

    Hi.
    We're currently testing out SLB for load balancing a pair of Exchange 2010 CAS servers.  The config seems straightforward enough for single port services like 'Outlook Anywhere' or 'Outlook Web Access' (all on https).
    Does anyone have real life experience with getting straight MAPI Outlook load balancing to work?  According to Microsoft, there's only 3 ports to be concerned with - endpoint mapper, rpc.clientaccess, and address.book.  I've got the latter two set for static across both of these servers, and have 3 appropriate vservers in place pointing to the serverfarm, but a capture shows the process getting hung up on tcp135.  It's as if whatever server the endpoint request is landing on doesn't know what to do with the request.
    Thanks in advance for any replies.

    Hello Jay!
    Take a look at this doc:
    http://www.cisco.com/en/US/docs/solutions/Verticals/mstdcmsftex.html#wp609677
    RPC requires source ip sticky in order to operate correctly through a loadbalancer.  In the doc, they also walk through doing RPC over http/https - however, I have seen configurations where ACE is not L5-L7 that use RPC on port 135 as a L4 rule with sticky and it appears to work ok.
    Regards,
    Chris Higgins

  • Best practice SSL End-to-End in Exchange 2010 CAS loadbalancing

    Hi,
    I was wondering if there is a best practice for deploying SSL End-to-End in Exchange 2010 CAS loadbalancing.
    We have ACE modules A5(1.1) and ANM 5.1(0), although there seems to be a template available in ANM it doesn't work. It throws a error when deploying, i believe the template is corrupt.
    As I am undersome pressure to deploy this asap I am looking for a sample config. I found one for SSL offloading, but I need one for End-to-End SSL.
    Thanks in advance,
    Dion

    Hi Dion,
    You can open up a case with TAC to have that template reviewed and confirm if the problem is at the ACE or ANM side.
    In the meantime here is a nice example for End-To-End SSL that can help you to get that working:
    http://www.cisco.com/en/US/products/hw/modules/ps2706/products_configuration_example09186a00809c6f37.shtml
    For CAS load balancing there's nothing special other than opening the right ports, I'd advise you to get SSL working first and take it from there, if any problem comes up you can post it here and we'll give you a hand.
    HTH
    Pablo

  • Exchange 2010 CAS proxy to Exchange 2013 CAS: Use the following link to open this mailbox with the best performance:

    Hello,
    I've installed Exchange 2013 into Exchange 2010 infrastructure
    [ single Exchange 2010 server; single AD site; AD = 2003 ],
    and moved one mailbox [ Test user ] to Exchange 2013.
    When I login internally through 2013 OWA to access mailboxes on 2010, then proxy works fine.
    When I login internally through 2010 OWA to access mailboxes on 2013, then a message appears:
        Use the following link to open this mailbox with the best performance: with link to 2013 OWA...
    What is wrong ?
    I've checked and changed settings by:
    Get-OwaVirtualDirectory, Set-OwaVirtualDirectory
    [PS] C:\work>Get-OwaVirtualDirectory -Identity 'ex10\owa (Default Web Site)' | fl server,name, *auth*,*redir*,*url*
    Server                        : EX10
    Name                          : owa (Default Web Site)
    ClientAuthCleanupLevel        : High
    InternalAuthenticationMethods : {Basic, Fba, Ntlm, WindowsIntegrated}
    BasicAuthentication           : True
    WindowsAuthentication         : True
    DigestAuthentication          : False
    FormsAuthentication           : True
    LiveIdAuthentication          : False
    AdfsAuthentication            : False
    OAuthAuthentication           : False
    ExternalAuthenticationMethods : {Fba}
    RedirectToOptimalOWAServer    : True
    LegacyRedirectType            : Silent
    Url                           : {}
    SetPhotoURL                   :
    Exchange2003Url               :
    FailbackUrl                   :
    InternalUrl                   : https://ex10.contoso.com/owa
    ExternalUrl                   : https://ex10.contoso.com/owa
    [PS] C:\work>Get-OwaVirtualDirectory -Identity 'ex13\owa (Default Web Site)' | fl server,name, *auth*,*redir*,*url*
    Server                        : EX13
    Name                          : owa (Default Web Site)
    ClientAuthCleanupLevel        : High
    InternalAuthenticationMethods : {Basic, Ntlm, WindowsIntegrated}
    BasicAuthentication           : True
    WindowsAuthentication         : True
    DigestAuthentication          : False
    FormsAuthentication           : False
    LiveIdAuthentication          : False
    AdfsAuthentication            : False
    OAuthAuthentication           : False
    ExternalAuthenticationMethods : {Fba}
    RedirectToOptimalOWAServer    : True
    LegacyRedirectType            : Silent
    Url                           : {}
    SetPhotoURL                   :
    Exchange2003Url               :
    FailbackUrl                   :
    InternalUrl                   : https://ex13.contoso.com/owa
    ExternalUrl                   :
    best regards Janusz Such

    Hi Janusz Such,
    Based on my knowledge, CAS proxy can only from later version to previous version.
    Some like CAS2013 to CAS2010/2007, CAS2013 to CAS2013. 
    Thanks
    If you have feedback for TechNet Subscriber Support, contact
    [email protected]
    Mavis Huang
    TechNet Community Support

  • Exchange 2013 Mailbox Using 2010 Public Folders

    Firstly, we will not be migrating completely to Exchange 2013 public folders for quite a while.  Our first Ex2013 server is in a small branch office and won't be appropriate to hose the PF's for the entire company.  Our environment consists of
    8 Ex2010 servers and now the one Ex2013.  I setup a test mailbox on the 2013 server and it access a 2010 PF database on another server just fine.  How is that server discovered, and can we specify which one it uses?  I understand the way 2013
    public folders are moving but is there a downside to leaving our configuration this way for a long period of time?

    Yes, the procedure should be followed to move mailbox first. Once you have successfully moved all the mailbox to new exchange server, you can migrate public folder after that.
    You can also checekout this thread related to public folder migration from exchange 2010 to 2013 :
    http://social.technet.microsoft.com/Forums/exchange/en-US/b7a35a45-9b74-4910-9dc3-c997bc71f03f/migration-form-exchange2010-to-exchange2013?forum=exchangesvrdeploy
    Further, for a better convenience, you can also take a look at this application (http://www.exchangemailboxmigration.com/) which would be a good approach while migrating mailboxes and public folders
    between two exchange server. It ensures about the data security and email contents during the completion of entire migration process.

  • Exchange 2010 CAS array with Exchange 2013 Mailbox Servers

    Here is our current scenario,
    Exchange 2007
    2 - Hub Transport Servers
    2 - CAS servers (cluster NLB)
    2 - Mailbox servers (clustered)
    Exchange 2010
    2 - Huib Transport Servers
    3 - CAS servers (array NLB)
    2 - Mailbox servers (1 DAG)
    We have not migrated any users to the Exchange 2010 environment yet. We're thinking that at this point we would rather go from 2007 to 2013. Does the 2013 mailbox server work with a 2010 CAS array?

    Hi,
    As far as I know, CAS array doesn' t exist in Exchange 2013. And OWA and other requests can be proxyed and redirected from Exchange 2013 to Exchange 2010.
    For more information, you can refer to the following article:
    http://blogs.technet.com/b/exchange/archive/2013/01/25/exchange-2013-client-access-server-role.aspx
    Thanks,
    Angela Shi
    TechNet Community Support

  • Pop3 connection exchange 2010 or 2013?

    which is better for pop3 access?
    exchange 2010 or 2013?
    i have used exchange 2010 before am familar with interface

    Better? In what way?
    The interface is completely different (EAC compared to EMC) but that's true in general (not just for POP3).
    Here's some directions on enabling it (there are now two services to enable):
    http://technet.microsoft.com/en-us/library/bb124934(v=exchg.150).aspx
    Some more info:
    http://technet.microsoft.com/en-us/library/jj657728(v=exchg.150).aspx
    If you do a search, you might be able to find a step-by-step that will guide you.
    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.

  • Outlook Connectivity / Exchange 2010 Coexistence Scenarios

    Hello,
    I recently migrated to Exchange 2013, autodiscover.domain.com and mail.domain.com are pointing to CAS 2013 for external and internal access. For EX013 users, Outlook establishes connection with both CAS 2010 and CAS 2013 which is fine. For EX2010 users,
    Outlook establishes the connection only with CAS 2010 for both internal and external access. My understanding is that CAS 2013 should proxy the connection to CAS 2010, but it doesn't and also after the migration I have to remove and add the profile again for
    the changes to take effect for the migrated users. I haven't changed the namespaces, its the same. Any suggestions would be much appreciated.

    Hi,
    Your understadning is correct. Since only Exchange 2013 is Internet-facing, CAS2013 would proxy all requests for Exchange 2010 external user accessing.
    Please make sure the External URL in Exchange 2010 services are all set to $Null and Outlook Anywhere is enabled with the external host name pointed to mail.domain.com. Then the external Exchange 2010 user would connect the Autodiscover service
    with autodiscover.domain.com successfully. The other services such as EWS, OOF and OAB request would be send to Exchange 2013 then proxy to Exchange 2010.
    For more infromation about the connectivity in 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

  • Outlook client in different subnet unable to connect to Exchange 2010 CAS using Windows 2008 R2 NLB multicast mode

    Hi all,
    need urgent assistance on the following issue
    this is my Exchange 2010 setup
    2 x CAS/Hub servers with HP network teaming, and load balanced using Windows NLB multicast mode. There are 2 VIPs on the NLB, one for outlook anywhere, one for autodiscover
    2 DNS records were created for the 2 VIPs
    Clients use Outlook Anywhere (HTTPS) to connect to the CAS servers from external segment via a Palo Alto firewall, which also acts as a layer 3 router
    static arp was set on the Palo Alto firewall, with both virtual MACs pointing to the primary virtual MAC used by the NLB. 
    Observations
    1. within same segment - no issue accessing Exchange servers, even when one CAS node is offline
    2. external segment (via firewall)
    a. when both nodes are up
    outlook client able to connect to Exchange CAS VIP on 443, but will disconnect after around 30 seconds. Client will retry and the pattern will repeat
    Exchange CAS RPC logs shows client connections and disconnections to the outlook anywhere VIP address
    Firewall logs shows allowed traffic from client to the VIPs
    unable to complete profile creation
    b. with only CAS2 (CAS1 stopped/deleted from NLB cluster)
    no issues accessing Exchange servers, creating profiles etc
    c. with only CAS1
    same behaviour as (a)
    reinstalled NLB, but doesn't resolve
    deleted CAS1 from NLB cluster, and re-add. issue remain
    Q1. is teaming supported? Teaming is currently set to automatic mode, instead of specified Fault Tolerant
    Q2. are there additional settings we need to set or verify on the Palo Alto firewall, since the issue only happen to external segment? Thanks!

    Yes - I've been scarred with this for many years :(
    If it is just CAS 1 that is causing issues, then focus in on that.  The support statement for Win 2008 R2 is that NLB is still a 3rd party component and support may ask for it to be disabled.
    http://support.microsoft.com/kb/278431 
    Does CAS1 and CAS2 have the same NICs (firmware as well), driver, teaming software, and teaming config? 
    I also want to ask what the network team did for configuring the switch ports on the servers?  This will vary from vendor to vendor  - did they do the same config on both?
    Cheers,
    Rhoderick
    Microsoft Senior Exchange PFE
    Blog:
    http://blogs.technet.com/rmilne 
    Twitter:   LinkedIn:
      Facebook:
      XING:
    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.
    Thanks Rhoderick, issue still persists
    can you also help clarify what you meant by "configuring the switch ports on the servers"?
    thanks again

  • Exchange 2010 CAS Mailbox Re-direction / Proxying Not Working Properly

    Hello Team
    In my Exchange 2010  Lab Setup, CAS proxy is not working properly
    In Site A :  One DC , One HUb Server , 2 CAS Server (CAS ARRAY WIndows NLB), Mailbox Server 2 (DAG)
    In Site B : One ADC one hub and CAS( Both are in same box) One Mailbox
    Internal and External for SITE A  on Server CASARRAY1.labbites.co.in  is https://casarray1.labbites.co.in/owa  and https://casarray1.labbites.co.in/owa
    Internal and External for SITE A  on Server CASARRAY2.labbites.co.in  is https://casarray2.labbites.co.in/owa  and https://casarray2.labbites.co.in/owa
    DNS recory casarray.labbites.co.in is present 
    Internal and External for SITE B on Server INDLBGUEX01.labbites.co.in is https://indlbguex01.labbites.co.in/owa  and https://indlbguex01.labbites.co.in/owa 
    The problem is occurs , whenever the second CAS server casarray2.labbites.co.in is down (Shutdown)
    Now , when the user ifrom site A s trying to log in to the OWA with SITE B OWA LINK https://indlbguex01.labbites.co.in/owa  it redirects to always https://casarray2.labbites.co.in/owa , since casarray2 server is down the OWA  page
    is not opening
    My Question is Why the proxy re-direction is always going to second casarray2 server instead of  casarray.labbites.co.in
    how to correct it . please help me to over come the issue 

    Hi Albert
    Thanks for you update 
    Get-mailboxdatabase | FT name, RPC*
    Name                             RpcClientAccessServer 
    DB1                                casarray.labbites.co.in
    DB2                                casarray.labbites.co.in
    DB3                                casarray.labbites.co.in
    Site B Mbx -DB1              INDLBGUEX01.labbites.co.in
    The user is administartor who beloings to DB1 and accesing the OWA from the SITE B  CAS server link https://indlbguex01.labbites.co.in/owa
    and it is redirecting to https://casarray2.labbites.co.in/owa 
    so as per the above
    output , should i make RPCclientaccess server for Site B Mbx -DB1   as casarray.labbites.co.in

  • Exchange 2010 CAS server in NLB reboot forces some users to re-authenticate

    I have 4 Exchange servers.
    2 X CAS servers
    2 X Mailbox servers
    The mailbox servers are in a DAG. That works fine and replication happens between them quite happily.
    The 2 Cas servers are in a NLB and seem ok with that. However, if I reboot one of the CAS servers then some of my users get prompted for their credentials. If you try re-enter the credentials then it just keeps coming up asking for the password. If they close
    outlook and re-open then it seems to be fine. From what I can gather online this is because the Outlook session has authenticated against the CAS1 for instance. And if CAS1 goes offline, then NLB not being that intelligent swaps the connection over to CAS2.
    But CAS2 then see’s this as a new connection and so asks for the password again.
    Is this right or have I misconfigured something? If it is right then is there any way to get around it? Or is it just the way it is and on the odd occasions that we have to reboot in the middle of the day users will just have to close and re-open where necessary?

    Hi,
    Based on my research, services on the CAS are stopped when it is shut down or restarted. However, the network load balancer does not recognize that the services are offline. Thus, the client prompts the user for credentials.
    To prevent this issue, do not let the CAS accept new connections from the load balancer before the CAS is shut down or restarted. For example, issue a drainstop command to the server in Network Load Balancing Manager.
    For more information, you can refer to the following article:
    http://support.microsoft.com/kb/2634633
    Thanks,
    Angela Shi
    TechNet Community Support

  • Staging the NLB cluster Static port change of Exchange 2010 CAS or do it all in one day ?

    Folks,
    Here is the server deployment in my AD domain:
    Email flow and Outlook client connection go through the NLB cluster VIP email.domain.com.au which is served by the following server:
    PRODHT-CAS01 (HT-CAS Server Windows NLB node 1)
    PRODHT-CAS02 (HT-CAS Server Windows NLB node 2)
    Public Folder access through Outlook client goes through the following servers:
    PRODMBX01 (Stand-alone Mailbox Server 1) no DAG
    PRODMBX02 (Stand-alone Mailbox Server 2) no DAG
    Can I make the changes first on the first stack of Exchange Server set as below first:
    PRODHT-CAS01 (HT-CAS Server NLB node 1)
    PRODMBX01 (Stand-alone Mailbox Server 1) no DAG
    in order to test the Outlook email & Public Folder connectivity in the first week and then followed by the rest of the server set:
    PRODHT-CAS02 (HT-CAS Server NLB node 2)
    PRODMBX02 (Stand-alone Mailbox Server 2) no DAG
    would that cause the NLB or user email access problem?
    Do I have to make the changes all in one day for those four servers followed by the reboot?
    Reason of changing: The hardware load balancer (Riverbed) requires to have static RPC port to work properly.
    This is the article to change the Static port in my NLB cluster Exchange HT-CAS server role on Exchange Server 2010 SP2: http://social.technet.microsoft.com/wiki/contents/articles/864.configure-static-rpc-ports-on-an-exchange-2010-client-access-server.aspx
    Thanks in advance.
    /* Server Support Specialist */

    All the servers behind the load balancer must be the same.
    You can change the stand alone MBX server's RCA port as that traffic is not load balanced.
    Changing Exchange is straight forward, just be careful to enter the registry keys correctly and then check AB and RCA is listening on the new static ports after you restart the services.
    Cheers,
    Rhoderick
    Microsoft Senior Exchange PFE
    Blog:
    http://blogs.technet.com/rmilne 
    Twitter:   LinkedIn:
      Facebook:
      XING:
    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.
    Rhoderick,
    Many thanks for the suggestion. My goal here is to minimize any impact / email service downtime to the user while configuring the static ports.
    1. Do I have to dissolve the Windows NLB cluster after the static port configuration on both HT-CAS servers or can I still keep the NLB cluster?
    2. "All the servers behind the load balancer must be the same." Do you mean do I have to do the static RPC port the same day for all server set ?
    /* Server Support Specialist */

Maybe you are looking for