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
AFX Connector "Accepted DH prime length is 2048 or higher" message in SecurID Governance & Lifecycle Number of Views RSA Governance & Lifecycle Exchange SSH Connector Datasheet Number of Views Microsoft Exchange 2010 AFX Connector Enable-mailbox command fails with 'Value cannot be null' in RSA Identity Governance … Number of Views RSA Identity Governance and Lifecycle - Microsoft Exchange Application Guide Number of Views KCA has problems publishing to Microsoft Exchange Server Number of Views
Trending Articles
How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device How to Detect and Resolve Stalled Workflows and Workpoint Issues in RSA Identity Governance & Lifecycle How to change the default Oracle Statistics History Retention period for RSA Identity Governance & Lifecycle RSA Governance & Lifecycle 8.0.0 Installation Guide Upgrade from 7.2.1 or earlier version to SecurID Governance & Lifecycle 7.5.0 or later version stalls at step ACM-102799.sql
Don't see what you're looking for?
