Mac mail exchange 2007
The same principles will apply for Mail.app, provided it is a true ActiveSync client: simply point Mail.app at your CAS host. Here, look to Microsoft’s IAS server, which would be placed into the DMZ and then allow connections from Entourage and other ActiveSync/OWA clients.Ī number of people have been asking about ActiveSync clients, for Snow Leopard. But in larger environments where all data needs to be proxied in some way, you may find the move to a CAS role complicated. Clients can simply connect over port 80 or 443 (not including the LDAP lookups obviously). In smaller environments, where ports are directly coming into the server from the WAN, you won’t find the CAS role to be a big design consideration. However, if you change CAS servers you may find yourself performing some client reconfiguration. This has never been a feature of Entourage (although you can use a clustered pair), but now you point all clients to your CAS host and the mailboxes can then be moved between Storage Groups and Servers without having to touch the clients. With Microsoft Outlook clients, you could migrate a mailbox between Exchange Servers and Outlook would read the new location of the mailbox automatically and reconfigure itself for the new server. There are certain design considerations CAS imposes, as well as benefits to how things were handled in Exchange 2003. This is a change from previous versions, where you could enable IIS on any host and point clients there however, it is similar in that CAS is very similar to the front end functionality that this option entailed. Outlook Web Access (OWA) and/or OWA Light clientsĮntourage falls into this category, and so when you are deploying Exchange 2007 alongside Entourage you will point your clients at your host running CAS.In Exchange 2007, the Client Access Server (CAS) role accepts connections from clients in order to allow them access to the Exchange Server infrastructure (mailboxes, public folders, GAL, etc).