Improve company productivity with a Business Account.Sign Up

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 99
  • Last Modified:

Exchange 2010: CAS array not pingable or accessible

Here is my setup:

Exchange 2010

Two locations – Main and DR Site

Main Site

Two Exchange 2010 servers - HT, MB, CAS roles
CAS Servers - CAS1 (192.168.0.8) and CAS2 (192.168.0.9)
CAS Array – outlook.domain.com (192.168.0.11)

DR Site (Azure)
One Exchange 2010 Server – HT, MB, CAS roles
CAS Server – CASDR (10.10.10.8)
CAS Array – outlookdr.domain.com (10.10.10.11)
DNS entry for outlookdr.domain.com

First, everything works fine in the main site and we are adding Azure as the DR site.
I am able to ping CASDR from either Azure or the main site.
I am able to connect to CASDR from our test account (in Outlook and OWA) to our test database that is in Azure.
I am not able to ping outlookdr (10.10.10.11) from the main site or DR site.  Ping returns the correct IP address of outlookdr (10.10.10.11).

When I place CASDR into outlookdr, I am not able to access my test account via Outlook or OWA.
Why is this happening?

Thank you!
0
fesit
Asked:
fesit
  • 3
2 Solutions
 
AmitIT ArchitectCommented:
It will not work as MS doesn't support Exchange 2010 on Azure.
1
 
Todd NelsonSystems EngineerCommented:
Fesit,

Slightly off topic but very relevant... Unfortunately, you probably won't get much, if any, support on this configuration.

Just a bit of info to expand on what Amit stated; from the TechNet article regarding Exchange 2010 virtualization...

Deployment of production Exchange servers on Windows Azure virtual machines is not supported.

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

This isn't saying it can't be done, only that it will not be supported.  However, Exchange 2013 and 2016 are supported by Microsoft in Azure if, and only if, the databases and transaction logs are on Azure premium storage.

Deployment of Exchange 2013 on Infrastructure-as-a-Service (IaaS) providers is supported if all supportability requirements are met. In the case of providers who are provisioning virtual machines, these requirements include ensuring that the hypervisor being used for Exchange virtual machines is fully supported, and that the infrastructure to be utilized by Exchange meets the performance requirements that were determined during the sizing process. Deployment on Microsoft Azure virtual machines is supported if all storage volumes used for Exchange databases and database transaction logs (including transport databases) are configured for Azure Premium Storage.

    - https://technet.microsoft.com/en-us/library/jj619301(v=exchg.150).aspx#Anchor_0

Additionally, there is this to consider as well; At the moment, Exchange (2013/2016) is only supported in Azure by Microsoft regarding all cloud-based hosts ... https://oddytee.wordpress.com/2016/04/05/is-exchange-server-supported-in-amazon-web-services/
0
 
fesitAuthor Commented:
I read what you posted and read through the links but Exchange doesn't know that it's running in an unsupported environment.  

Could we put aside the Azure part for the moment - (let's say it's located in our remote office) can you explain why the CAS array is not pingable?
0
 
AmitIT ArchitectCommented:
You need to open your firewall ports. If you have any firewall. Also what design are you trying to setup. Active/Active or Active/Passive?
0
 
AmitIT ArchitectCommented:
As per design, DAG cannot be setup with Azure.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now