The Evolution of CAS in Exchange Server versions
Originally Published: 2011-10-30
Article Number
Applies To
RSA Web Agent
Issue
Resolution
Exchange 2000/2003 didn't have CAS servers but they had "Front End" servers. With "Front End" servers, internal clients connected with Outlook through MAPI directly to Mailbox servers (using MAPI over RPC). External clients used the "Front End" as more of a proxy that could handle RPC over HTTP (for Outlook Anywhere), HTTPS (for Outlook Web Access), POP/IMAP
Exchange 2010 introduces a new service (MSExchangeRPC) so that the CAS Role is "true" middle tier
Related Articles
Security Levels and Identity Router Connection Ciphers Number of Views IDR SSO - Step 9: Protect a Resource Number of Views Zoho Directory - SAML My Page SSO Configuration - RSA Ready Implementation Guide Number of Views Microsoft Office 365 - Add a Domain - RSA Ready SecurID Access Implementation Guide Number of Views Microsoft Office 365 - Enable Modern Authentication - RSA Ready SecurID Access Implementation Guide Number of Views
Trending Articles
Quick Setup Guide - Passwordless Authentication in Windows MFA Agent for Active Directory RSA MFA Agent 2.5 for Microsoft Windows Installation and Administration Guide RSA MFA Agent 2.3.6 for Microsoft Windows Installation and Administration Guide How to Download OTP Token Seed Files from myRSA RSA Authentication Manager 8.9 Release Notes (January 2026)
Don't see what you're looking for?
