asked on

Namespace design consideration for Exchange Server 2016 coexistence

People,

I need some help and explanation as to why I need multiple different name spaces for Exchange 2010-2016 co existence ?

With an Exchange 2010 site-resilient design, you needed up to eight different namespaces:

two Internet Protocol namespaces
two for Outlook Web App fallback
one for Autodiscover
two for RPC Client Access
one for SMTP.

My AD domain is just single forest domain.com so what are the best suggested name to choose ?

ASKER CERTIFIED SOLUTION

Jamie McKillop

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

SOLUTION

Will Szymkowski

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

Albert Widjaja

ASKER

This really comes down to DNS configuration. How do you currently have your DNS namespaces setup for your Exchange environment?

It is hosted internally by Windows Server AD integrated.

How many internet facing Sites do you have?

1 in the Data Center only.

Can you also provide the resource that illustrates what you are talking about?

I need to plan for which SSL certificate to renew or buy with this new upgrade.

Albert Widjaja

ASKER

ok, can I use the minimum name space as follows:

mail.domain.com --> for OWA, SMTP, Activesync, Outlook client
autodiscover.name.com -->first time lookup for Outlook and ActiveSync I guess ?

Note, I am planning to use Citrix Netscaler VPX appliance as the load balancer.

SOLUTION

Jamie McKillop

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

Albert Widjaja

ASKER

Thanks !