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

Similar Messages

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

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

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 :)

Exchange 2010 to Exchange 2013 Migration and Architect a resilient and high availability exchange setup

Hi,
I currently have a single Exchange 2010 Server that has all the roles supporting about 500 users. I plan to upgrade to 2013 and move to a four server HA Exchange setup (a CAS array with 2 Server as CAS servers and one DAG with 2 mailbox Servers). My
goal is to plan out the transition in steps with no downtime. Email is most critical with my company.
Exchange 2010 is running SP3 on a Windows Server 2010 and a Separate Server as archive. In the new setup, rather than having a separate server for archiving, I am just going to put that on a separate partition.
Here is what I have planned so far.
1. Build out four Servers. 2 CAS and 2 Mailbox Servers. Mailbox Servers have 4 partitions each. One for OS. Second for DB. Third for Logs and Fourth for Archives.
2. Prepare AD for exchange 2013.
3. Install Exchange roles. CAS on two servers and mailbox on 2 servers. Add a DAG. Someone had suggested to me to use an odd number so 3 or 5. Is that a requirement?
4. I am using a third party load balancer for CAS array instead of NLB so I will be setting up that.
5. Do post install to ready up the new CAS. While doing this, can i use the same parameters as assigned on exchange 2010 like can i use the webmail URL for outlook anywhere, OAB etc.
6. Once this is done. I plan to move a few mailboxes as test to the new mailbox servers or DAG.
7. Testing outlook setups on new servers. inbound and outbound email tests.
once this is done, I can migrate over and point all my MX records to the new servers.
Please let me know your thoughts and what am I missing. I like to solidify a flowchart of all steps that I need to do before I start the migration.
thank you for your help in advance

Hi,
okay, you can use 4 virtual servers. But there is no need to deploy dedicated server roles (CAS + MBX). It is better to deploy multi-role Exchange servers, also virtual! You could install 2 multi-role servers and if the company growths, install another multi-role,
and so on. It's much more simpler, better and less expensive.
CAS-Array is only an Active Directory object, nothing more. The load balancer controls the sessions on which CAS the user will terminate. You can read more at
http://blogs.technet.com/b/exchange/archive/2014/03/05/load-balancing-in-exchange-2013.aspx Also there is no session affinity required.
First, build the complete Exchange 2013 architecture. High availability for your data is a DAG and for your CAS you use a load balancer.
On channel 9 there is many stuff from MEC:
http://channel9.msdn.com/search?term=exchange+2013
Migration:
http://geekswithblogs.net/marcde/archive/2013/08/02/migrating-from-microsoft-exchange-2010-to-exchange-2013.aspx
Additional informations:
http://exchangeserverpro.com/upgrading-to-exchange-server-2013/
Hope this helps :-)

Exchange 2010 - WS-Management Service does not support

Hi,
We have a tool which was used for bulk Mailbox creation, Mailbox Movement etc. This we have used in Exchange 2007 also and was working fine. Now in Exchange 2010 we are facing some issues. Tool is written in VB.
Exchange 2010 SP2 is running in all servers and we have 2 Mailbox Servers in DAG and 2 HUBCAS in CAS Array/NLB.
When Team is trying to fetch the DB details in exchange 2010 through tool they are not able to connect and getting error as
"Connecting to remote Server failed with the following error message. The WS-Management Service does not support the request."
I have checked everything from Exchange like Remorepowersell status, WinRM, WS Managemet dll location and entry in config file everthing seems to be fine.
I checked through EMTShooter tool also and no issues reported and connection was success through EMTShooter.
Pls suggest if anymore we can check to fix the problem.
Note: everything is working frine from Powershell and Exchange Management console.
Regards:Mahesh

Hi
Yes, i got it confirmed and coding team claims that no issue with code and its working in some other setup.
<v:shapetype coordsize="21600,21600" filled="f" id="_x0000_t75" o:preferrelative="t" o:spt="75" path="m@4@5l@4@11@9@11@9@5xe" stroked="f"><v:stroke joinstyle="miter"><v:formulas><v:f
eqn="if lineDrawn pixelLineWidth 0"><v:f eqn="sum @0 1 0"><v:f eqn="sum 0 0 @1"><v:f eqn="prod @2 1 2"><v:f eqn="prod @3 21600 pixelWidth"><v:f eqn="prod @3 21600 pixelHeight"><v:f eqn="sum @0 0 1"><v:f eqn="prod @6 1 2"><v:f eqn="prod @7 21600 pixelWidth">Below
is the snapshot of error with coding <v:f eqn="sum @8 21600 0">
<v:f eqn="prod @7 21600 pixelHeight">
<v:f eqn="sum @10 21600 0">
</v:f></v:f></v:f></v:f></v:f></v:f></v:f></v:f></v:f></v:f></v:f></v:f></v:formulas>
<v:path gradientshapeok="t" o:connecttype="rect" o:extrusionok="f">
<o:lock aspectratio="t" v:ext="edit">
</o:lock></v:path></v:stroke></v:shapetype><v:shape alt="" id="Picture_x0020_2" o:spid="_x0000_i1025" style="width:631.5pt;height:148.5pt;" type="#_x0000_t75">
<v:imagedata o:href="cid:[email protected]" src="file:///C:\Users\aralele\AppData\Local\Temp\msohtmlclip1\01\clip_image001.jpg">
</v:imagedata></v:shape>
Regards:Mahesh

Exchange 2010 SP3 upgrade on Windows Server Standard SP2

I'm midway through the swing upgrade process of migrating from Exchange 2003 - Exchange 2010 to Exchange 2013. Everything has gone smoothly between the Exchange 2003 and Exchange 2010 migration which I started two days ago. it has been running
great. I am beginning the final stages of moving from the Exchange 2010 server to a new Exchange 2013 server, but it requires my Exchange 2010 server to be upgraded to SP3. I am now trying to install Exchange Server 2013 SP3 Upgrade and I'm
getting (3) Client Access Role Prerequisites errors. Finding any of these HotFixes and patches is frustrating, because any link provided does not work. It has gotten me nowhere. Here is my Readiness Checks:
Summary: 6 item(s). 5 succeeded, 1 failed.
Elapsed time: 00:01:06
Configuring Prerequisites
Completed
Elapsed Time: 00:00:00
Organization Prerequisites
Completed
Elapsed Time: 00:00:08
Languages Prerequisites
Completed
Elapsed Time: 00:00:02
Hub Transport Role Prerequisites
Completed
Elapsed Time: 00:00:15
Client Access Role Prerequisites
Failed
Error:
Install hotfix Microsoft Knowledge Base article 982867 from http:// code.msdn.microsoft.com/KB982867.
Click here for help... http:// technet.microsoft.com/en-US/library/ms.exch.err.default(EXCHG.141).aspx?v=14.3.123.3&e=ms.exch.err.Ex28883C&l=0&cl=cp
Error:
Install hotfix Microsoft Knowledge Base article 979917 from http:// code.msdn.microsoft.com/KB979917.
Click here for help... http:// technet.microsoft.com/en-US/library/ms.exch.err.default(EXCHG.141).aspx?v=14.3.123.3&e=ms.exch.err.Ex28883C&l=0&cl=cp
Error:
This computer requires the update described in Microsoft Knowledge Base article KB977592 (http:// go.microsoft.com/fwlink/?LinkId=194843). Without this update, the Outlook Anywhere feature may work unreliably.
Click here for help... http:// go.microsoft.com/fwlink/?linkid=30939&l=en&v=ExBPA.14&id=249bbd89-16b4-4efa-9b66-7ec87f90e44c
Elapsed Time: 00:00:15
Mailbox Role Prerequisites
Completed
Warning:
Multi-mailbox search of on-premises and Office 365 mailboxes in a hybrid configuration requires installation of the update mentioned in Microsoft Knowledge Base article 982867 (http:// code.msdn.microsoft.com/KB982867).
Elapsed Time: 00:00:24
I put a space between the http://" space "URL so I could display the links.
Any help/guidance suggestions would be greatly appreciated.
Chris

I just got these two to go away:
Error:
Install hotfix Microsoft Knowledge Base article 982867 from http:// code.msdn.microsoft.com/KB982867.
Click here for help... http:// technet.microsoft.com/en-US/library/ms.exch.err.default(EXCHG.141).aspx?v=14.3.123.3&e=ms.exch.err.Ex28883C&l=0&cl=cp
Error:
This computer requires the update described in Microsoft Knowledge Base article KB977592 (http:// go.microsoft.com/fwlink/?LinkId=194843). Without this update, the Outlook Anywhere feature may work unreliably.
Click here for help... http:// go.microsoft.com/fwlink/?linkid=30939&l=en&v=ExBPA.14&id=249bbd89-16b4-4efa-9b66-7ec87f90e44c
still have this one outstanding:
Error:
Install hotfix Microsoft Knowledge Base article 979917 from http:// code.msdn.microsoft.com/KB979917.
Click here for help... http:// technet.microsoft.com/en-US/library/ms.exch.err.default(EXCHG.141).aspx?v=14.3.123.3&e=ms.exch.err.Ex28883C&l=0&cl=cp
I have tried the FIX: WCF services that are hosted by NLB computers to route messages to Exchange Server fail when WebHeader settings are added by using a .NET Framework 3.5 SP1 application
Windows6.0-KB2637518-x64.msu
when I run it, it tells me "The Update does not apply to your system. So im thinking I need to remove the .NET Framework 4 Client Profile and the .NET Framework 4 Extended. reboot, then install
Windows6.0-KB2637518-x64.msu and then reinstall .NET Framework 4 Client Profile and the .NET Framework 4 Extended
this has taken a day or so to figure out the order of dependencies and the order to put them on.
Frustrating, since I won't be using Exchange 2010, were moving all the way to Exchange 2013 on a brand new server.
Chris

Migration Exchange 2010 to Exchange 2013 in a different site

Hi all, I have
an Exchange 2010 with these characteristics
Site A
- 2 Servers DAG for mailboxes
- 2 Servers Client Access and
Hub Transport in Microsoft
NLB
- 2 Domain Controllers Windows
Server 2008 R2
I want to upgrade to Exchange 2013 but in another
Site, Site B. When the migration is complete,
the mail system will only be in Site
B.
The connection between Site A and Site
B is a reliable connection.
Is there any problem to upgrade Exchange 2013
to another Site, other than Site
A?
regards
Microsoft Certified IT Professional Server Administrator

Hi all, I have
an Exchange 2010 with these characteristics
Site A
- 2 Servers DAG for mailboxes
- 2 Servers Client Access and
Hub Transport in Microsoft
NLB
- 2 Domain Controllers Windows
Server 2008 R2
I want to upgrade to Exchange 2013 but in another
Site, Site B. When the migration is complete,
the mail system will only be in Site
B.
The connection between Site A and Site
B is a reliable connection.
Is there any problem to upgrade Exchange 2013
to another Site, other than Site
A?
regards
Microsoft Certified IT Professional Server Administrator
It is like any other Migration (Same Forest) You just need to make sure that AD is been replicated from Site A (Exchange 2010) to Site B (Exchange 2013).
No Network or replication issue between the sites. Having more than 1 DC on Site B would be good idea.
Once you have all these set, rest of the things are same.
Extend the AD Schema.
Deploy the Exchange Server 2013 CU6
Create the Cert request for 2013.
Install Cert on Exchange 2013.
Configure the Virtual Directories for Exchange 2013.
Test the Coexistence between 2010 and 2013.
Perform the Cutover from 2010 to 2013.
Test the Cutover and start the Test migration phase.
Once the test phase is fine, start the full fledge migration.
Move Mailbox and Public Folder Database.
Cheers,
Cheers,
Gulab Prasad
Technology Consultant
Blog:
http://www.exchangeranger.com    Twitter:
  LinkedIn:
   Check out CodeTwo’s tools for Exchange admins
Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

Applying Windows 2008 R2 SP1 on Exchange 2010 SP2 servers

Hi All,
Our current setup is Primary Site and DR site with a DAG.
Primary site is having 2 Mailbox servers, 2 hubcas servers with an NLB and one CAS server for OWA.
DR Site is having 1 mailbox server, one hubcas server and one CAS server. All these exchange servers are SP2 with update roll up5.
But the OS is Windows 2008 R2, need to apply Windows 2008 R2 SP1 on these servers, and what are things to be considered.
Does this affect CAS servers IIS?
Thanks,
Kanishka.

Agreed. One thing to mention - Win 2008 R2 needed SP1 a while back, no security updates have been released for a while.
Exchange 2010 SP2 goes out of support next month. please plan to update to SP3 for Exchange 2010.
http://blogs.technet.com/b/rmilne/archive/2013/10/08/save-the-date-end-of-exchange-2003-support-t-minus-6-months.aspx
The details for that, and a link to the lifecycle page are in the above post.
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 2010 to 2013 Migration Question

Hi Folks,
This is where I'm at: We have 2 Exchange 2010 servers (both multi role) and I was given 4 VM's for exchange 2013. I just completed installing Exchange on the four 2013 VM's (2 dedicated CAS and 2 dedicated MBX) and applied SP1. I documented all
of the 2010 server config info (i.e. all the URL's for the namespaces, etc). We have a hardware NLB and a MacAfee host in the DMZ where all inbound/outbound email routes to check for AV/Spam. My question is, what are my next steps that
take place so that I'm truly in co-existence mode? I'm assuming I want to make the 2013 servers primary now so that all mail routes to/from them and all client connections are made to them? Could someone point me in the right direction maybe
to an article on what my next steps are? I want to get everything cut over while in co-existence so that I can start moving mailboxes. Thanks a lot !

Exchange Server Deployment Assistant is good starting point:
http://technet.microsoft.com/en-US/exdeploy2013/Checklist?state=2284-W-AAAAAAAAQAAAAAEAAAAAAA%7e%7e
Upgrade from Exchange 2010 to Exchange 2013:
http://technet.microsoft.com/en-us/library/jj898583(v=exchg.150).aspx
http://msexchangeguru.com/2013/05/10/exchange2013-migration/
http://www.petenetlive.com/KB/Article/0000788.htm
Below is high level migration plan:
1. Update active directory schema for exchange 2010 sp3.
2. Install Exchange 2010 SP3 and rollup updates on existing servers.
3. Update active directory schema for exchange 2013 CU3.
4. Install and configure new Exchange 2013 CU3 servers.
5. Install public SSL Certificate.
6. Configure Web URL's for Exchange 2013 servers.
7. Configuration Hardware Load Balancer for:
a) High availability of Client Access roles.
b) Reverse Proxy for outlook web app.
8. Create mailbox databases and configure database copies for the corresponding DAG.
9. Test High Availability environment.
10. Test mail flow to & from internet/internally for all locations.
11. Test BlackBerry device connectivity with Exchange 2013 environment (if nay)
12. Test migrate mailbox from Exchange 2010 to Exchange 2013.
13. Test Outlook & OWA connectivity for migrated test mailbox.
14. Validate new Exchange 2013 environment.
15. Pilot mailboxes migration from Exchange 2010 to Exchange 2013.
16. Migrate mailboxes from Exchange 2010 to Exchange 2013.
17. Migrate Public Folders from Exchange 2010 to Exchange 2013
18. Dismount & stop Exchange 2010 services on all servers for few days before decommissioning of Exchange 2010 servers.
19. Decommission Exchange 2010 servers gracefully.
If this will help then please mark it as answer...thanks
Best of luck!
Liaqat

Single name space in between Exchange 2010 and 2013

Hi,
In my current environment I have 2 Exchange 2010 servers with DAG no CAS NLB. I installed Exchange 2013 with 2 CAS with WNLB and 2 Mailboxes with DAG. The main requirement is to configure Single name space to access in between Exchange 2010 and Exchange
2013. On Exchange 2010 DAG there is a URL using is owa.domain.com and I also configured in Exchange 2013 all the virtual directories with this name owa.domain.com but having an issue that when I open explorer and use the owa.domain.com URL the user on Exchange
2013 gets their mailbox but user on Exchange 2010 gets error HTTP 403 blank page.
I observed that in Exchange Organization settings CAS settings one server OWA, ECP etc shows their internal external URL but the other server unable to open the OWA, ECP URL and give error message that "An IIS directory entry
couldn't be created. The error message is Access is denied. HResult = -2147024891"
Please guide how to resolve this issue and use the same name URL in Exchange 2010 and Exchange 2013
Thanks,

Hi,
See the below brief:
User will connect to mail.contoso.com as his namespace endpoint. CAS2013 in Site1 will authenticate the user, do a service discovery, and determine that the mailbox version is 2010 and is located within the local AD site. CAS2013 will proxy the
request to an Exchange 2010 Client Access server which will retrieve the necessary data from the Exchange 2010 Mailbox server
Go through the full blog for better understanding of the redirection.
Client Connectivity with Exchange 2013
Hope you have changed your DNS records to direct connections only to your new Exchange 2013 server. You'll move the host names (for example, mail.contoso.com) users have been using to connect to Outlook Web Access, Autodiscover, and so on, from your
Exchange 2010 server to your Exchange 2013 server. When an Exchange 2010 user tries to open their mailbox, the Exchange 2013 server will proxy their request and communicate with the Exchange 2010 server on their behalf.
Configuring DNS includes the following:
Change the primary host names, such as mail.contoso.com, autodiscover.contoso.com, and owa.contoso.com (if used) to point to the external, publically-accessible, IP address of the Exchange 2013 Client Access server with your public DNS provider.
Change the primary host names, such as mail.contoso.com (or internal.contoso.com if you're using different internal host names) and owa.contoso.com (if used) to point to the internal machine name of the Exchange 2013 Client Access server on your internal
DNS servers.
NOTE- Go through the Exchange Deployemnt Assitant - Configure DNS Records section
Regards,
Satyajit
Please“Vote As Helpful”
if you find my contribution useful or “MarkAs Answer” if it does answer your question. That will encourage me - and others - to take time out to help you.

Exchange 2010 High availabilty

hello ,
i have exchange 2010 installed on my head office
sevrer 1 : mailbox server
server2 : hub+cas
i want to install high availabilty solution in DR without buying hardware loadbalancer .
incase of our head office disaster should i able sending and receving from DR
regards
MCP MCSA MCSE MCT MCTS CCNA

Hi,
For CAS/HUB servers, you can still use Windows NLB to load balance traffic. It is supported but the recommendation is to user HLB. Besides, it is recommended to create a Client Access server array even if you only have a single Client Access server within
your organization.
For DAG, we shoule note that each member of the DAG must also be running the same operating system.
More information about datacenter switchover, please refer to
Datacenter Switchovers.
Hope this helps.
Best regards,
Belinda
Belinda Ma
TechNet Community Support

Workaround instead of Upgrading Exchange 2010 Severs to SP3

Hi
I have a customer in an exchange 2010 environment who has 4 exchange servers in place with DAG and NLB setup. We plan to go ahead with a Hybrid setup however just need to clarify if there is any workaround that we could apply instead of having to upgrade
there exchange server to 2010 SP3?
Thanks & Regards
Aaqib

Hi,
I notice that you want to deploy hybrid environment, and don’t upgrade to Exchange 2010 SP3.
Depending on the Microsoft document, Exchange 2010 SP3 support hybrid deployment with Exchange 2013 CU1 or later version, however Exchange 2010 SP1 and SP2 are not supported.
More details about Hybrid deployment prerequisites, for your reference:
https://technet.microsoft.com/en-us/library/hh534377(v=exchg.150).aspx
Best Regards,
Allen Wang

Strange Exchange 2010 Traffic

Hi Guys,
I've a strange and mysterious Traffic dropping all the network caused by one of the HUB\CAS servers.
We have Exchange 2010 Environment 2 DAG Members and 2 HUB\CAS Servers we are using WNLB as a load-balancing Solution.
We have two physical hosts and we virtualized the all servers mailbox and HUB\CAS
MBX-01 -- HUB-CAS-01 on HV1
MBX-02 -- HUB-CAS-02 on HV2
When Both servers are up strange traffic begin and all telephony system "Avaia" go down.
I've disabled the replication on the MAPI network on both DAG members to ensure that the replication traffic goes throw the private network and changed the mode of NLB " Multicast and then Unicast" and nothing changed any ideas.
All servers running Exchange 2010 SP3.
Thanks
Best Regards
Mohamed Attia

Hi,
Based on the description, you used WNLB as a load-balancing Solution, however, it is recommended to use the HLB instead in the production environment.
From the "Network requirements" topic in the article
Planning for High Availability and Site Resilience, DAG must have a single MAPI network, which is used by a DAG member to communicate with other servers (for example, other Exchange 2013 servers or directory servers), and zero or more Replication networks,
which are networks dedicated to log shipping and seeding.
So nothing changed, even though you disabled the replication on the MAPI network on both DAG members. It is the expected behavior.
Do you connect the telephony system "Avaia" to an Unified Messaging server?
Best regards,
Belinda
Belinda Ma
TechNet Community Support

Exchange 2010 SP3 and UR6 Query - Order of Install

hi,
I need to update my Exchange 2010 SP2 Servers to SP3 and Update Rollup 6.
Can someone confirm the update order for me?
I have 5 servers;
Live Data Centre:
2 x HUB / CAB (Using Windows NLB)
2 x Mailbox (DAG)
Disaster Recovery:
1 x Multi-Role Server (CAS / HUB and Mailbox) - this is also Part of the DAG
Two Questions:
1.) What is the Order in which I install SP3 on these Servers? Should it be Live Data Centre: HUB / CAS, Mailbox Servers and THEN the Multi-Role Server at DR?
2.) When Upgrading each server, should I do SP3, reboot, check and THEN install Update Rollup 6 - or should I upgrade all Servers to SP3 and then start the process again to get to Update Rollup 6?
Thanks in advance for your help with this query.
Regards,
Adam

1) Internet facing CAS first in each AD site. Order: CAS> HUB> UM> MBX
2) Personally, I would install SP3, reboot, then install SP6, but its really up to you.
http://technet.microsoft.com/en-us/library/bb629560(v=exchg.141).aspx
Upgrade Exchange 2010 to Exchange 2010 SP1, Exchange 2010 SP2, or Exchange 2010 SP3
Twitter!: Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

Exchange 2010 NLB on Nexus1000v - UCS - Cat4500

Similar Messages

Maybe you are looking for