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
RSA Governance & Lifecycle Exchange 2007 Powershell Connector Datasheet 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 Governance & Lifecycle Integration: Microsoft Exchange Summary Number of Views RSA Governance & Lifecycle Exchange 2013 Powershell Connector Datasheet Number of Views
Trending Articles
How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device RSA SecurID software token .sdtid file fails to import into RSA SecurID Software Token 5.0 for Windows RSA Authentication Manager 8.9 Patches and Hotfixes Readme Download RSA SecurID Access Cloud User Event audit logs using Cloud Administration REST API CLU RSA MFA Agent 2.5 for Microsoft Windows Installation and Administration Guide
Don't see what you're looking for?
