Configuring NLB Exchange 2010

Our environment only has one CAS/HT server.  No NLB Array was configured.  I wanted to verify the steps on getting this properly configured:
Build and patch NEW server – server 2010-2.
Install Pre – Requests.
Install Exchange CAS/HUB server roles.
Rename current CAS/HT server from 2010 to 2010-1 and change IP.
Install NLB.
Create NLB Cluster – name cluster 2010 keep same IP of current CAS/HT server.
Add DNS entry for cas array – name to be 2010.domain.com IP of current 2010 server.
Check to make sure mailbox databases RPCClientAccess Server is pointing to CAS array 2010.domain.com
Thanks

Read this : http://www.kraftkennedy.com/blog/bid/102109/Configuring-NLB-for-Exchange-2010-CAS-Load-Balancing
Install new Exchange server, Create a CAS Array, Create NLB "VIP" IP, Configure NLB to include your 2 CAS/HUB Server, Do all your Exchange Shell commands to point RPC, ext to CAS Array, Point CAS Array.domain.com to point to the LB "VIP". 
TEST
TEST
TEST
If its not working role back and see what steps you missed :)

Similar Messages

  • Exchange Server 2013 OAB Web Distribution Configuration in Exchange 2010 & 2013 Coexistence.

    Hi,
    We have OAB Issue for Exchange 2010 Users in our Organization.
    We have Exchange 2010 and Exchange 2013 Coexistence.While Checking in Exchange Server 2010 Server OAB properties in Org Configuration--> Mailbox-->OAB Properties -->Distribution we are not seeing any CAS servers and Its Grayed Out.
    Please let us know How to add Exchange 2010 CAS in Exchange 2013 Web distribution.

    They made alot changes with the OAB in Exchange 2013, and it doesn't really function in the same manner as it did in 2010.  It might be best to take a look at the following blog posts from the Exchange Team, they should give you a better understanding
    on how it works and how to manage it going forward.
    http://blogs.technet.com/b/exchange/archive/2012/10/26/oab-in-exchange-server-2013.aspx
    http://blogs.technet.com/b/exchange/archive/2013/01/14/managing-oab-in-exchange-server-2013.aspx
    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

  • Configure new exchange 2010 while old exchange 2003 running ?

    Hello,
    I'm in the process of deploying a new fresh installation of SBS 2011/Exchange 2010 server. Currently
    I have SBS2003/Exchange 2003 running. I want to retired the server and replace with the new server. No migration. By doing that, I am setting up the new server SBS2011 name/domain/ip everything the same as the old server and will replace once all the configuration
    is completed.
    1. Since they both using the same domainname/ip, can I setup the new server Exchange 2011 while the old
    server is alive? If yes, how's the process?
    2. If I export and import users email in .pst (on user outlook client) and when the new server is put in place alive does it will regenerate the database
    in new Exchange 2011? 
    Thanks in advance =)

    For the 1st question, both servers are in different/isolated network. So you were saying yes i can do that correct? will not going to have any issue running both servers having all the same configuration while configuring the new server up? 
    the 2nd. since i am not migrating, i am planing to export/import user email from outlook client and when i replace the old server with the new server, i setup the user email client and import the .pst back.  

  • Iphone 4s configured for exchange 2010 rebuilds inbox

    My iphone 4S keeps rebuilding the inbox multiple times per day. no events in the exchange server logs. this happen on wi-fi also.
    can this be the resync timeout value that the ios 4 suffered with?
    Thank You

    I have the same problem on mu iPhone 4S, running iOS 5.1 .
    I have 4 exchange profiles on my iPhone, but it's only the gmail account (which has been set up as exchange push)  that rebuilds his inbox x times a day. 
    It's only since a couple of weeks, before it worked perfectly.

  • ACE20 Module with Exchange 2010 Configuration

    Hello all,
    I have deployed the following configuration for Exchange 2010, if all services are up on the two servers it functions good but if a service goes down on one server (especially outlook) some clients are disconnected (stickiness) ...
    Stickiness is needed for all services by ip source sticky and by coockies for OWA.
    Because all services are on the same server (ip address) the configured sticky causes problems !!! when a service is down the ACE usually forwards  requests to it !!!! Any help please.
    Configuration :
    XXXXX-ACE1/CTXT-EXCHANGE(config)# do sh run
    Generating configuration....
    access-list BPDU-Allow ethertype permit bpdu
    access-list EXCH-LB line 10 extended permit ip any any
    probe http HTTP-GET
      interval 10
      passdetect interval 10
      request method get url /iisstart.htm
      expect status 200 202
    probe icmp PING
      interval 3
    probe tcp abport
      port 7575
      interval 2
      faildetect 2
      passdetect interval 10
      passdetect count 1
      connection term forced
    probe tcp epmap
      port 135
      interval 2
      faildetect 2
      passdetect interval 10
      passdetect count 1
      connection term forced
    probe tcp http
      interval 2
      passdetect interval 2
      passdetect count 1
      connection term forced
    probe http http-probe
      interval 60
      passdetect interval 60
      passdetect count 2
      request method get url /exchweb/bin/auth/owalogon.asp
      expect status 400 404
    probe tcp https
      port 443
      interval 2
      passdetect interval 2
      passdetect count 1
      connection term forced
    probe http https-probe
      interval 60
      passdetect interval 60
      passdetect count 2
      request method get url /owa/auth/login.aspx
      expect status 400 404
    probe tcp imap
      port 143
      interval 2
      passdetect interval 2
      passdetect count 1
      connection term forced
    probe tcp imaps
      port 993
      interval 2
      passdetect interval 2
      passdetect count 1
      connection term forced
    probe udp ipsec
      port 500
      interval 2
      passdetect interval 2
      passdetect count 1
    probe icmp ping
      interval 2
      passdetect interval 2
      passdetect count 1
    probe tcp pop3
      port 110
      interval 2
      passdetect interval 2
      passdetect count 1
      connection term forced
    probe tcp pop3s
      port 995
      interval 2
      passdetect interval 2
      passdetect count 1
      connection term forced
    probe tcp rpcport
      port 7576
      interval 2
      faildetect 2
      passdetect interval 10
      passdetect count 5
      connection term forced
    probe tcp smtp
      port 25
      interval 2
      passdetect interval 2
      passdetect count 1
      connection term forced
    rserver host CAS1
      ip address 172.22.101.74
      inservice
    rserver host CAS2
      ip address 172.22.101.76
      inservice
    rserver host HUB1
      ip address 172.22.101.75
      inservice
    rserver host HUB2
      ip address 172.22.101.77
      inservice
    rserver redirect RPC-REDIRECT
    rserver redirect SSLREDIRECT
      webhost-redirection https://mail.tunisiana.com/owa 302
      inservice
    serverfarm host CAS-Outlook
      probe PING
      probe abport
      probe epmap
      probe rpcport
      fail-on-all
      rserver CAS1 135
        inservice
      rserver CAS1 7575
        inservice
      rserver CAS1 7576
        inservice
      rserver CAS2 135
        inservice
      rserver CAS2 7575
        inservice
      rserver CAS2 7576
        inservice
    serverfarm host CAS-http
      probe HTTP-GET
      probe PING
      rserver CAS1 80
        inservice
      rserver CAS2 80
        inservice
    serverfarm host CAS-https
      probe https
      probe ping
      rserver CAS1 443
        inservice
      rserver CAS2 443
        inservice
    serverfarm host CAS-imap
      probe PING
      probe imap
      rserver CAS1 143
        inservice
      rserver CAS2 143
        inservice
    serverfarm host CAS-imaps
      probe imaps
      probe ping
      rserver CAS1 993
        inservice
      rserver CAS2 993
        inservice
    serverfarm host CAS-ipsec
      probe ipsec
      probe ping
      rserver CAS1
        inservice
      rserver CAS2
        inservice
    serverfarm host CAS-pop3
      probe ping
      probe pop3
      rserver CAS1 110
        inservice
      rserver CAS2 110
        inservice
    serverfarm host CAS-pop3s
      probe ping
      probe pop3s
      rserver CAS1 995
        inservice
      rserver CAS2 995
        inservice
    serverfarm host CAS-smtp
      probe ping
      probe smtp
      fail-on-all
      rserver CAS1 25
        inservice
      rserver CAS2 25
        inservice
    serverfarm host HUB
      probe ping
      probe smtp
      rserver HUB1
        inservice
      rserver HUB2
        inservice
    serverfarm redirect RPC-REDIRECT
    serverfarm redirect SSLREDIRECT
      rserver SSLREDIRECT
        inservice
    parameter-map type http STICKY
      persistence-rebalance
    parameter-map type connection TCP_IDLE_30min
      set timeout inactivity 1800
    sticky ip-netmask 255.255.255.255 address source HUB-ST
      timeout 30
      replicate sticky
      serverfarm HUB
    sticky ip-netmask 255.255.255.255 address source CAS-http-ST
      timeout 30
      replicate sticky
      serverfarm CAS-http
    sticky ip-netmask 255.255.255.255 address source CAS-https-ST
      timeout 30
      replicate sticky
      serverfarm CAS-https
    sticky ip-netmask 255.255.255.255 address source CAS-imap-ST
      timeout 30
      replicate sticky
      serverfarm CAS-imap
    sticky ip-netmask 255.255.255.255 address source CAS-imaps-ST
      timeout 30
      replicate sticky
      serverfarm CAS-imaps
    sticky ip-netmask 255.255.255.255 address source CAS-smtp-ST
      timeout 30
      replicate sticky
      serverfarm CAS-smtp
    sticky ip-netmask 255.255.255.255 address source CAS-pop3-ST
      timeout 30
      replicate sticky
      serverfarm CAS-pop3
    sticky ip-netmask 255.255.255.255 address source CAS-pop3s-ST
      timeout 30
      replicate sticky
      serverfarm CAS-pop3s
    sticky ip-netmask 255.255.255.255 address source CAS-ipsec-ST
      timeout 30
      replicate sticky
      serverfarm CAS-ipsec
    sticky ip-netmask 255.255.255.255 address source CAS-Outlook-ST
      timeout 30
      replicate sticky
      serverfarm CAS-Outlook
    sticky http-cookie sessionid exchange-sticky-sessionid-grp
      timeout 20
      serverfarm CAS-http
    sticky http-cookie cookie OWA-STICKY
      cookie insert browser-expire
      timeout 60
      replicate sticky
      serverfarm CAS-http
    sticky http-header Authorization CAS-RPC-HTTP
      serverfarm CAS-http
    class-map match-any CAS-OUTL-MAPI-VIP
      2 match virtual-address 172.22.101.69 tcp any
    class-map match-any CAS-Outlook-VIP
      2 match virtual-address 172.22.101.69 tcp eq 135
      3 match virtual-address 172.22.101.69 tcp eq 7575
      4 match virtual-address 172.22.101.69 tcp eq 7576
    class-map match-any CAS-http-VIP
      2 match virtual-address 172.22.101.69 tcp eq www
    class-map match-any CAS-https-VIP
      2 match virtual-address 172.22.101.69 tcp eq https
    class-map match-any CAS-imap-VIP
      2 match virtual-address 172.22.101.69 tcp eq 143
    class-map match-any CAS-imaps-VIP
      2 match virtual-address 172.22.101.69 tcp eq 993
    class-map match-any CAS-ipsec-VIP
      2 match virtual-address 172.22.101.69 udp eq 500
    class-map match-any CAS-pop3-VIP
      2 match virtual-address 172.22.101.69 tcp eq pop3
    class-map match-any CAS-pop3s-VIP
      2 match virtual-address 172.22.101.69 tcp eq 995
    class-map match-any CAS-smtp-VIP
      2 match virtual-address 172.22.101.69 tcp eq smtp
    class-map match-all CAS_SERVERS
      2 match source-address 172.22.101.64 255.255.255.192
    class-map match-any HUB-VIP
      2 match virtual-address 172.22.101.80 any
    class-map match-all HUB_SERVERS
      2 match source-address 172.22.101.64 255.255.255.192
    class-map match-all OWA-OUTLOOKANYWHERE-SSL
      2 match virtual-address 172.22.101.69 tcp eq https
    class-map match-all OWA-SSL-CM
      2 match virtual-address 172.22.101.69 tcp eq https
    class-map match-all OWAREDIRECT
      2 match virtual-address 172.22.101.69 tcp eq www
    class-map type management match-any REMOTE-MGT
      201 match protocol snmp any
      202 match protocol http any
      203 match protocol https any
      204 match protocol icmp any
      205 match protocol ssh any
      206 match protocol telnet any
    policy-map type management first-match REMOTE-MGT
      class REMOTE-MGT
        permit
    policy-map type loadbalance first-match CAS-Outlook-policy
      class class-default
        sticky-serverfarm CAS-Outlook-ST
    policy-map type loadbalance first-match CAS-http-policy
      class class-default
        sticky-serverfarm CAS-http-ST
    policy-map type loadbalance first-match CAS-https-policy
      class class-default
        sticky-serverfarm CAS-https-ST
    policy-map type loadbalance first-match CAS-imap-policy
      class class-default
        sticky-serverfarm CAS-imap-ST
    policy-map type loadbalance first-match CAS-imaps-policy
      class class-default
        sticky-serverfarm CAS-imaps-ST
    policy-map type loadbalance first-match CAS-ipsec-policy
      class class-default
        serverfarm CAS-ipsec
    policy-map type loadbalance first-match CAS-pop3-policy
      class class-default
        sticky-serverfarm CAS-pop3-ST
    policy-map type loadbalance first-match CAS-pop3s-policy
      class class-default
        sticky-serverfarm CAS-pop3s-ST
    policy-map type loadbalance first-match CAS-smtp-policy
      class class-default
        serverfarm CAS-smtp
    policy-map type loadbalance first-match HUB-policy
      class class-default
        serverfarm HUB
    policy-map type loadbalance first-match OWA-OUTLOOKANYWHERE
      match OUTLOOK_ANYWHERE http header User-Agent header-value "MSRPC"
    policy-map type loadbalance first-match OWA-SSL-PM
      class class-default
        sticky-serverfarm OWA-STICKY
    policy-map type loadbalance http first-match SSLREDIRECT
      class class-default
        serverfarm SSLREDIRECT
    policy-map multi-match CAS-Outlook-POLICY-MAP
      class CAS-Outlook-VIP
        loadbalance vip inservice
        loadbalance policy CAS-Outlook-policy
        loadbalance vip icmp-reply
        connection advanced-options TCP_IDLE_30min
    policy-map multi-match CAS-http-POLICY-MAP
      class CAS-http-VIP
        loadbalance vip inservice
        loadbalance policy CAS-http-policy
        loadbalance vip icmp-reply
        connection advanced-options TCP_IDLE_30min
    policy-map multi-match CAS-https-POLICY-MAP
      class CAS-https-VIP
        loadbalance vip inservice
        loadbalance policy CAS-https-policy
        loadbalance vip icmp-reply
        connection advanced-options TCP_IDLE_30min
    policy-map multi-match CAS-imap-POLICY-MAP
      class CAS-imap-VIP
        loadbalance vip inservice
        loadbalance policy CAS-imap-policy
        loadbalance vip icmp-reply
        connection advanced-options TCP_IDLE_30min
    policy-map multi-match CAS-imaps-POLICY-MAP
      class CAS-imaps-VIP
        loadbalance vip inservice
        loadbalance policy CAS-imaps-policy
        loadbalance vip icmp-reply
        connection advanced-options TCP_IDLE_30min
    policy-map multi-match CAS-ipsec-POLICY-MAP
      class CAS-ipsec-VIP
        loadbalance vip inservice
        loadbalance policy CAS-ipsec-policy
        loadbalance vip icmp-reply
    policy-map multi-match CAS-pop3-POLICY-MAP
      class CAS-pop3-VIP
        loadbalance vip inservice
        loadbalance policy CAS-pop3-policy
        loadbalance vip icmp-reply
        connection advanced-options TCP_IDLE_30min
    policy-map multi-match CAS-pop3s-POLICY-MAP
      class CAS-pop3s-VIP
        loadbalance vip inservice
        loadbalance policy CAS-pop3s-policy
        loadbalance vip icmp-reply
        connection advanced-options TCP_IDLE_30min
    policy-map multi-match CAS-smtp-POLICY-MAP
      class CAS-smtp-VIP
        loadbalance vip inservice
        loadbalance policy CAS-smtp-policy
        loadbalance vip icmp-reply
        connection advanced-options TCP_IDLE_30min
    policy-map multi-match EXCH-POLICY
      class CAS-imap-VIP
        loadbalance vip inservice
        loadbalance policy CAS-imap-policy
        loadbalance vip icmp-reply
        connection advanced-options TCP_IDLE_30min
      class CAS-imaps-VIP
        loadbalance vip inservice
        loadbalance policy CAS-imaps-policy
        loadbalance vip icmp-reply
        connection advanced-options TCP_IDLE_30min
      class CAS-pop3-VIP
        loadbalance vip inservice
        loadbalance policy CAS-pop3-policy
        loadbalance vip icmp-reply
        connection advanced-options TCP_IDLE_30min
      class CAS-pop3s-VIP
        loadbalance vip inservice
        loadbalance policy CAS-pop3s-policy
        loadbalance vip icmp-reply
        connection advanced-options TCP_IDLE_30min
      class CAS-smtp-VIP
        loadbalance vip inservice
        loadbalance policy CAS-smtp-policy
        loadbalance vip icmp-reply
        connection advanced-options TCP_IDLE_30min
      class CAS-http-VIP
        loadbalance vip inservice
        loadbalance policy CAS-http-policy
        loadbalance vip icmp-reply
        connection advanced-options TCP_IDLE_30min
      class CAS-https-VIP
        loadbalance vip inservice
        loadbalance policy CAS-https-policy
        loadbalance vip icmp-reply
        connection advanced-options TCP_IDLE_30min
      class CAS-OUTL-MAPI-VIP
        loadbalance vip inservice
        loadbalance policy CAS-Outlook-policy
        loadbalance vip icmp-reply
        connection advanced-options TCP_IDLE_30min
    policy-map multi-match HUB-POLICY-MAP
      class HUB-VIP
        loadbalance vip inservice
        loadbalance policy HUB-policy
        loadbalance vip icmp-reply
        connection advanced-options TCP_IDLE_30min
    interface vlan 52
      description #### vlan client side EXCHANGE ####
      bridge-group 1
      access-group input BPDU-Allow
      access-group input EXCH-LB
      service-policy input REMOTE-MGT
      service-policy input HUB-POLICY-MAP
      service-policy input EXCH-POLICY
      no shutdown
    interface vlan 54
      description #### vlan client side ACE_EXCHANGE ####
      bridge-group 1
      access-group input BPDU-Allow
      access-group input EXCH-LB
      service-policy input REMOTE-MGT
      service-policy input HUB-POLICY-MAP
      service-policy input EXCH-POLICY
      no shutdown
    interface bvi 1
      ip address 172.22.101.123 255.255.255.192
      peer ip address 172.22.101.122 255.255.255.192
      description EXCHANGE-Bridged-vlans
      no shutdown
    ip route 0.0.0.0 0.0.0.0 172.22.101.126
    Best Regards

    Thank you for your email. I am out of the office until March 25th, I will have limited access to my e-mail during this period.
    In my absence, please feel free to contact Mr Akram Allani : [email protected]
    Thank you for your understanding.
    Best regards,
    Youssef Boukari

  • Migration Exchange 2010 to Exchange 2013 with CAS Array and DAG

    Dear All,
    I am starting the migration of Exchange 2010 2 servers (CAS/Mailbox) with DAG no CAS Array to Exchange 2013 with 2 servers CAS array and 2 Mailbox servers with DAG. I read on some blogs that no requirement of CAS array on Exchange 2013. My concern how to
    configure NLB on CAS servers for the client to connect.
    Please guide and have any deployment guide for this, kindly share.
    Thanks

    Hi ,
    As you said there is no use and meaning of having the cas array in exchange 2013 and also thanks a lot to Microsoft for introducing an single namespace facility in exchange 2013.
    My suggestion and Microsoft recommendation should be to go with hardware load balancers for exchange 2013 rather than using the windows NLB and round robin method.
    Why we need to go for HLB ?
    Disadvantages
    of some load balancing methods :
    Windows
    NLB :-
    If you use Windows NLB then it can provide redundancy on server level failure and not on application level.
    DNS
    round robin :-
    In case if we use the windows round robin method for load balancing then it wouldn't provide server level
    and application level redundancy during the failures.At the Same time we need to manually adjust the DNS records during the server failure but on the client end dns caches will create the issues.
    Configuring NLB for exchange 2013 : 
    http://msexchangeguru.com/2013/08/14/windowsnlb/
    NLB configurations for exchange 2010 and 2013 will be same.
    Configuring round robin for exchange 2013 : 
    http://exchangeserverpro.com/exchange-2013-client-access-server-high-availability/
    Advisable method is to have the CAS and MBX roles on the same box if NLB not comes it to play.Because windows failover clustering and NLB cannot be configured on the same box.In exchange 2013 cas role is a stateless server role so there is no need to have
    that role on a separate box.
    Thanks & Regards S.Nithyanandham

  • Legacy integration between Exchange 2003 and Exchange 2010

    Dear Team,
    we are using Microsoft Exchange 2003 & 2010 Server for Emails, now we have both servers are connected, we want to raise new Single incident request for doing this activity, we want disconnect 2003 server from 2010 server so accordingly need support,
    we are ready to pay for this incident, 
    pls do the needful,
    Thanks & regards
    Anteshwar Bhosale

    Hi Anteshwar,
    If you want to remove Exchange 2003 from your coexistence environment, please perform the following procedure:
    1. Move all mailboxes to an Exchange 2010 server in the organization.
    2. Move all content from the public folder database on the legacy Exchange 2003 server to a public folder database on an Exchange 2010 server in the organization.
    3. On Exchange 2003 servers, for each offline address book (OAB), move the generation process to an Exchange 2010 server.
    4. Verify that Internet mail flow is configured to route through your Exchange 2010 transport servers.
    5. Verify that all inbound protocol services (Microsoft Exchange ActiveSync, Microsoft Office Outlook Web App, Outlook Anywhere, POP3, IMAP4, Autodiscover service, and any other Exchange Web service) are configured for Exchange 2010.
    If all above steps have been prepared, we can remove the last Exchange 2003 server from the Exchange 2010 organization from ADSIEdit. For detailed steps about this, please refer to:
    https://technet.microsoft.com/en-us/library/gg576862(v=exchg.141).aspx
    Regards,
    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]
    Winnie Liang
    TechNet Community Support

  • 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 2010 - 2013 Coexistence Issues

    I am migrating from Exchange 2010 to Exchange 2013, the Exchange 2013 is built in a different Geo-location site with its dedicated domain controllers in the new site. I have confirmed the mail flow between Exchange 2010 and 2013 mailboxes. I am able to discover
    Exchange 2010 servers from 2013 environment via Get-ExchangeServer shell command. However, I am not to discover Exchange 2013 servers from 2010 environment. 
    I need to configure Outlook Anywhere and Service Connection Point (Autodiscover) on Exchange 2010 to accept connections from Exchange 2013 servers. 
    Any suggestions would be much appreciated, thanks!

    Hi ,
    Please have a look in to the below mentioned blog after reading that blog i came to know few things .
    I am not sure ,i thought exchange 2013 servers will not be displayed in exchange 2010 management shell.
    Better and advisable method is to configure your exchange 2010 and 2013 servers via EAC or Shell in exchange 2013.
    http://exchangeserverpro.com/exchange-server-2010-2013-migration-managing-co-existence-environment/
    Taken from the above blog :
    You can’t use the Exchange 2010 EMC to manage Exchange 2013 objects and servers. While customers upgrade to Exchange 2013, we encourage them to use the EAC to:
    Manage Exchange 2013 mailboxes, servers, and corresponding services.
    View and update Exchange 2010 mailboxes and properties.
    View and update Exchange 2007 mailboxes and properties.
    We encourage customers to use Exchange 2010 EMC to create Exchange 2010 mailboxes.
    We encourage customers to use Exchange 2007 EMC to create Exchange 2007 mailboxes.
    Customers can continue to perform management tasks using the Exchange Management Shell and script tasks.
    Regards
    S.Nithyanandham
    Thanks S.Nithyanandham

  • Correctif cumulatif 2 Exchange 2010 SP3

    Good day ,
    I did migration from exchange 2003 to exchange 2010  SP3 everything work fine except the Public folder migration didn't work When I find the MSExchange Store Driver 1020 Event recomend to install  correctif cumulatif  2 Exchange 2010 SP3 to
    fix the problem
    http://support.microsoft.com/kb/2855083
    If I install I don't have any impact about my configuration of exchange 2010 it's safe ?
    Regards
    e

    Hi,
    Firstly, I’d like to explain, it’s safe to install the Update Rollup 2 for Exchange Server 2010 SP3.
    Alternatively, since the error is always caused by an empty server container, we can remove the container to resolve the issue:
    1.Start the ADSI Edit tool. To do this, click Start , click Run , type adsiedit.msc , and then click OK
    2.Expand Configuration Container [servername.domainname.com] , and then expand CN=Configuration,DC=DomainName,DC=com
    3.Expand CN=Services, expand CN=Microsoft Exchange, and then expand CN=OrganizationName where OrganizationName is the name of your Exchange organization.
    4.You will see the empty Administrative Group. Expand the CN=AdministrativeGroupName
    5.Expand CN=Servers
    6.Verify there are no server objects listed under the Servers container
    7.Right click on the emtpy CN=Servers Container and choose Delete.
    http://support.microsoft.com/kb/2487271
    http://blogs.technet.com/b/exchange/archive/2010/05/05/3409916.aspx
    If you have any question, please feel free to let me know.
    Thanks,
    Angela Shi
    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 NLB on Nexus1000v - UCS - Cat4500

    Server Infrastructure: Microsoft Server 2012 Hyper-V installed on UCS Blade Servers. Network infrastructure is Nexus1000v for HyperV - FI62xx (endhost mode) uplinked to Catalyst 4510 Core Switch.
    Plan: Deploy Exchange 2010 NLB with two servers, each with one network card, NLB mode: IGMP multicast
    Configured:
    - Catalyst: static ARP for Cluster VIP
    - Nexus1000v: disabled IGMP snooping on servers VLAN
    All configuration is acting strangely, it works for some clients but not for others, if we stopped one node in NLB, more things stops working but some works fine.
    Nexus1000v configuration guide describes only NLB Unicast scenario.
    I suppose that something is missing in configuration.

    N1k only supports Unicast NLB.  For multicast & multicast+IGMP NLB there are a few things we can do that are not ideal because there will be excessive traffic flooding.
    http://www.cisco.com/en/US/docs/switches/datacenter/nexus1000/sw/4_2_1_s_v_1_5_1/release/notes/n1000v_rn.html#wp117941
    NLB with multicast (non-IGMP)-
    The NLB cluster uses a unicast IP address and non-IGMP multicast mac (03:bf) so IGMP is not used. N1k floods this frame.
    This method could overwhelm the network in some situations.
    1.    Use a dedicated VLAN for NLB VMs to limit mcast replication & flooding.
    NLB with Multicast+IGMP-
    Microsoft violates RFC2236 by putting a unicast IP in the IGMP Group messages.  N1k drops these messages since they violate the RFC.  CSCue32210 - "Add support for Microsoft NLB - Multicast+IGMP mode in Nexus 1000v" is targeted for a future release.  Before this feature exists we can configure the network as follows:
    1.    Dedicate a VLAN for NLB VMs to limit mcast replication & flooding.
    2.    Disable IGMP snooping on that vlan
    vlan 10
    no ip igmp snooping
    3.    Add a static entry on upstream router for NLB cluster IP & shared MAC.
    int vlan 10
    ip arp 14.17.124.40 0100.5e7f.7c28
    4.    Use mac-pinning configuration with manual pinning NLB vEths to one set of uplinks.  This will isolate flooding to a single upstream fabric interconnect & switch.
    port-profile type veth NLB-VM
      channel-group auto mode on mac-pinning relative
      pinning id 0 backup 1   <-these numbers may differ in your environment
    Matthew

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

  • Configure sharepoint 2013 with Microsoft exchange 2010

    Hi,
    I am want to configure SharePoint 2013 with Microsoft exchange 2010.
    Please let me how can I integrate these server to Send/ Receive domain E-mails.
    Thanks,   
    C Mahone

    For email integration there really isn't anything special about Exchange 2010 vs. any other mail server.  Check the links here on configuring Incoming and Outgoing mail in SharePoint:
    http://technet.microsoft.com/en-us/library/ee956941(v=office.15).aspx
    Paul Stork SharePoint Server MVP
    Principal Architect: Blue Chip Consulting Group
    Blog: http://dontpapanic.com/blog
    Twitter: Follow @pstork
    Please remember to mark your question as "answered" if this solves your problem.

  • Hide / Remove access to Organization Configuration in Exchange Management console Ex 2010

    Hello,
    I am planning to give EMC access to helpdesk and modified Helpdesk Role so that they have Mail Recipient Creation and Mail Recipents Assigned roles.
    Helpdesk are able to created new and also modify exixiting mail enabled objects fine.
    My boss wants me Hide / Remove access to Organization Configuration in Exchange Management console Ex 2010 as they are able to edit Client access policies. Is this possible ?
    Thanks,
    Ne0

    Hi,
    Please use the following cmdlet to check the permission of Helpdesk support group on all management roles.
    Get-ManagementRoleAssignment -GetEffectiveUsers | Where { $_.EffectiveUserName -Eq "Helpdesk support group" }
    Then you can remove some unnecessary permissions of the Helpdesk support group.
    Hope it helps.
    If there is any problem, please feel free to let me know.
    Best regards,
    Amy
    Amy Wang
    TechNet Community Support

Maybe you are looking for