Hi,

I was wondering if anyone can advise me the correct way to go about deploying a second exchange 2010 server on a network.

Server A lives on a separate subnet than the new Server B will be.  I will be deploying the CAS, Mailbox and HUB roles, but i need to utilize the same webmail address for both servers some how.

I heard load balancing may be the way to go but I have also researched there may be other ways such as silent redirection but I don't know enough about them.

Server B will relieve pressure from Server A, also mailboxes will be transferred.  I would also like the auto discover configured for both servers so outlook finds the correct  mailbox on the appropriate server.  Please note we do not want a DAG even though i am fully aware its High Availability.

Any advice would be great or any Blogs/Posts I can read up on :) 

You'll need to acquire and configure a hardware or virtual load balancer that's capable of reaching both systems, and then you'll point your URL hostnames to the load balancer.

Hi Stuart,

Important question here is the other subnet on the same AD site? If yes, you are good to go.

Cross-Site Silent Redirection:- Works for OWA in Exchange 2010 SP2, will not help in your case. This is useful when multiple Client Access servers exist in different Active Directory sites in an organization, and at least one of those sites isn't exposed to the Internet.

So you are left with the LoadBalancing option:

1. Create a CAS Array if you havn't yet

You can create a Client Access array within your Active Directory site by using the following command.

New-ClientAccessArray -Name name -Site site_name -FQDN internal_only_CAS_Array_FQDN

Note:
After the Client Access array has been created, you'll also need to create the address in DNS and associate it with the virtual IP address used for the Client Access array.

2. Add the other server to the Windows NLB or any other you have considered. (If you plan not to use DAG, then you can use NLB, but not both)

Please note that Windows NLB cannot be implemented within different subnets. NLB nodes need to be in the same subnet. You can use a VLAN that stretches across the two locations.

3. Once you have this autodiscover etc. should point to the CAS Array VIP

Hi,

Any updates?

Please refer to the following articles to create a CAS array, deploy load balance and change all services URLs to point to your load balance as what Ed said.

Understanding RPC Client Access in Exchange 2010

https://technet.microsoft.com/en-us/library/ee332317(v=exchg.141).aspx

Understanding Load Balancing in Exchange 2010

https://technet.microsoft.com/en-us/library/ff625247(v=exchg.141).aspx

Regards,

Thanks guys, all great help.