Plan, Install, Configure and

Manage Client Access:

Troubleshoot Client Connectivity

Troubleshoot client connectivity

This objective may include but is not limited to:

– Troubleshoot Outlook Anywhere connectivity

– Troubleshoot POP/IMAP

– Troubleshoot Authentication

– Troubleshoot web services

– Troubleshoot AutoDiscover

– Troubleshoot mobile devices

•The Company:

•HomeMassageFacial.com

•Problem:

•Using on-premise Exchange they want to make sure client connectivity will not be an issue

•Goal:

•Review options to troubleshoot initial setup and other issues

Scenario: In-home Massage and Facial Experts

Configuration troubleshooting could involve anything and everything:

DNS configuration

Client issues

Network connectivity

CAS configuration

Etc..

Once something is working, if it STOPS working, this involves a completely different type of troubleshooting

Helpful if you have a monitoring solution to help

Two Types of Troubleshooting

Available here:

http://go.microsoft.com/fwlink/?LinkId=154308

A web-based tool designed to help IT Administrators troubleshoot connectivity issues with their Exchange deployments

It simulates different client logon and mail flow scenarios

When a test fails (as is often the case, sometimes partially) the robust report that comes back can be very helpful

The Remote Connectivity Analyzer

What does the CAS role do?

– Brokers all client communication (including public folder and Unified

Messaging) by either proxying or redirecting that connection

What services are provided through CAS?

– Remote PowerShell

– Outlook Web App (OWA)

– ActiveSync

– Exchange Admin Center (EAC)

– EAC for End Users

– Autodiscover service

– Outlook Anywhere

– IMAP/POP

– Availability service

Source of Trouble: Misunderstanding CAS

•You can use the Test-PowerShellConnectivity cmdlet to test the connection to the PowerShell virtual directory

ECP and OWA go hand in hand so use similar virtual directory settings

Autodiscover works differently on the LAN than externally

– Internally Autodiscover will look for a Service Connection Point (SCP) object in AD

– External Autodiscover uses one of two URL’s to connect (both looking for the autodiscover.xml file) using DNS (and depending on your version of Outlook it will also try to look for a service locate (SRV) record for Autodiscover

Points to Remember

•Outlook Anywhere: – All client connectivity is done using RPC over HTTP (aka Outlook

Anywhere)

– There are two hostname settings you can configure (external and internal)

– You can configure OA through the EAC or the EMS

– Clients can use Autodiscover (through AD or DNS) to locate the URLs for services and then it responds with an XML file with those services and URLs in the file

•POP/IMAP – Remember, if you have CAS and MB split, you have to enable the

services on BOTH servers

Points to Remember (cont.)

•Availability service: – Free/busy information used to be part of the public folder store for

legacy Outlook but with 2013 (and the new Modern public folder mailbox arrangement) clients need to use this service and the information is retrieved directly from mailboxes using Exchange Web Services

– The Availability service, when working with Outlook’s scheduling assistant also provides cool things like suggested meeting times and more granular calendar sharing

Points to Remember (cont.)

Client Access Proxying (Single Site)

Client Access Server Mailbox Server

Outlook or OWA

End-User

Florida

Client Access Proxying (Multiple Sites)

Client Access Server Mailbox Server

Outlook or OWA

End-User

Florida

Client Access Server Mailbox Server

New York

Client Access Redirection (Multiple Internet Facing Sites)

Client Access Server Mailbox Server

OWA

End-User

Florida

Client Access Server Mailbox Server

New York

•Reasons for using a load balancer: – Higher availability

– Service interruption (purposeful for offline maintenance)

– Load balancing

•Layer 4 vs. Layer 7 (Know your OSI model)

•Server affinity is not longer a concern with 2013

Load Balancing

We’ve reviewed methods for testing client access like the Remote Connectivity Analyzer

We also reviewed the various services that can access the Client Access role and discussed the

difference between proxying and redirection

We finished up with a review of load balancing

Scenario: Home Massage Facial

Additional Research

•Exchange Remote Connectivity Analyzer Tool (TechNet)

•http://technet.microsoft.com/en-us/library/dd439364(v=exchg.80).aspx

•Mastering Exchange 2013 (published by Wiley/Sybex)

•Chapter 21: Understanding the Client Access Server