Post Views: 6,763 The current article dedicated to the subject of Exchange public infrastructure. When we relate to the topic of Exchange 2013 coexistence environment and client protocol connectivity flow, one of the most fundamental factors that determine and influence, the “client protocol connectivity flow” is the physical location of the Exchange clients. In simple…
Post Views: 12,079 Let’s start from the end – what is the only purpose of the Exchange CAS server? And the answer is: “deliver” information or a specific service to his clients (By Proxy the Exchange client request to additional Exchange server) or, by “point” (Redirect) Exchange client to an “element” that can provide them…
Post Views: 6,122 In the current article, we will focus on two main subjects: The essence of the relationship that exists between Exchange client and their Exchange CAS server. We will review the different scenario in which different Exchange client addresses the Exchange CAS 2013 asking for specific information or a specific service. The meaning…
Post Views: 6,746 The essence of the connectivity protocol flow in Exchange environment is the Exchange CAS server. We can relate to the Exchange CAS server is the Gatekeeper that stands between Exchange client and all the rest of the Exchange infrastructure. For this reason, it is imperative that we get a better understanding of…
Post Views: 7,719 The current article is the fourth article of four articles series, on the subject of: “Exchange 2013/2010 coexistence environment and mail client protocol connectivity flow”. In this article, our primary focus is reviewing two types of client protocol connectivity flow in Exchange 2013/2010 coexistence environment: ActiveSync client protocol connectivity flow Exchange web…
Post Views: 6,377 Implementing an Exchange 2013 coexistence environment, could consider a challenging project because to be able to build the “coexistence environment successfully,” we will need a good understanding of the Exchange 2013 CAS architecture and the “Legacy Exchange infrastructure” (Exchange 2010 or Exchange 2007). Additionally to the lack of “comprehensive understanding” of the…
