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 Identity Governance and Lifecycle - Microsoft Exchange Application Guide Number of Views 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 KCA has problems publishing to Microsoft Exchange Server Number of Views
Trending Articles
Unable to login to RSA Authentication Manager Security Console as super admin Authentication Manager Administration Server with operations console service Fails to Start with "No config.xml Was Found"… Authentication Manager Security Console and Operations Console Inaccessible After Certificate Update RSA Authentication Manager Upgrade Process RSA SecurID Software Token Distribution to Android from RSA Authentication Manager 8.1
Don't see what you're looking for?
