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 RSA Identity Governance and Lifecycle - Microsoft Exchange Application Guide Number of Views How to retrieve content files - Client Number of Views Microsoft Exchange Management Console/PowerShell error with RSA Authentication Agent 8.0 for Web for IIS Number of Views AFX Connector "Accepted DH prime length is 2048 or higher" message in SecurID Governance & Lifecycle Number of Views
Trending Articles
RSA Authentication Manager Upgrade Process RSA Authenticator 6.2.2 for Windows Administrator Guide RSA MFA Agent 2.3.6 for Microsoft Windows Installation and Administration Guide RSA SecurID software token .sdtid file fails to import into RSA SecurID Software Token 5.0 for Windows RSA Release Notes: Cloud Access Service and RSA Authenticators
Don't see what you're looking for?
