Thanks!  We haven't migrated the autodiscover service to 2010 yet so it comes 
back with nothing.  We were just trying to do as much testing as we could 
before we made the switch.  I am fairly confident that, once we move 
autodiscover to the 2010 environment, these errors should resolve themselves.

From: [email protected] [mailto:[email protected]] On 
Behalf Of Michael B. Smith
Sent: Monday, June 24, 2013 2:05 PM
To: [email protected]
Subject: [Exchange] RE: New 2010 CAS

In Exchange 2010, excepting only PF folder internal connections, all 
communication is via CAS.

Now, if you are asking about RAW MAPI vs. MAPI encapsulated in RPC/HTTPs, that 
can depend on a number of things, such as the configuration of CAS, of 
Autodiscover, of the Outlook provider, etc.

If you do a "test e-mail autoconfiguration" from within Outlook, the XML output 
tab should tell you everything you need to know.

From: [email protected]<mailto:[email protected]> 
[mailto:[email protected]]<mailto:[mailto:[email protected]]>
 On Behalf Of Rimmel, Carl
Sent: Monday, June 24, 2013 1:53 PM
To: [email protected]<mailto:[email protected]>
Subject: [Exchange] New 2010 CAS

We are beginning a migration from 2007 to 2010 and have stood up the 2010 CAS 
Array with a Citrix Netscalar HLB in front of it.  Everything is working thru 
the HLB but for some odd reason we keep getting prompted with certificate 
errors from the CAS servers whenever we attempt to use the HLB VIP for regular 
MAPI (RPC) connections.  The prompts are all the typical trust issues from the 
self-signed certificates, although we have installed trusted, 3rd party 
certificates and enabled IIS, POP and IMAP.

Using Wireshark, we have determined that the connections are HTTPS connections 
back to the CAS servers in the array.  Why exactly would the Outlook client be 
connecting to the CAS servers via HTTPS?

________________________________
CONFIDENTIALITY NOTICE: This email contains information from the sender that 
may be CONFIDENTIAL, LEGALLY PRIVILEGED, PROPRIETARY or otherwise protected 
from disclosure. This email is intended for use only by the person or entity to 
whom it is addressed. If you are not the intended recipient, any use, 
disclosure, copying, distribution, printing, or any action taken in reliance on 
the contents of this email, is strictly prohibited. If you received this email 
in error, please contact the sending party by reply email, delete the email 
from your computer system and shred any paper copies.

Note to Patients: There are a number of risks you should consider before using 
e-mail to communicate with us. See our Privacy & Security page on 
www.henryford.com<http://www.henryford.com> for more detailed information as 
well as information concerning MyChart, our new patient portal. If you do not 
believe that our policy gives you the privacy and security protection you need, 
do not send e-mail or Internet communications to us.

Reply via email to