What endpoint to connect to is defined by a property of a mailbox database called “RPCClientAccessServer”. One of the evil-doers is the RPC Client Access Endpoint: because RPC over TCP was used, Outlook needed an (RPC) endpoint to which it could connect to. In a typical site-resilient architecture, you could potentially end up with up to 8 namespaces. RPC over TCP is dead, long live RPC over HTTP!Įxchange 2010 was – especially with regards to namespaces – relatively complicated.
In this article, we will dig a bit deeper into this subject and cover some of the questions I’ve received over the past few days. Instead, Outlook clients will now connect using HTTPS (Outlook Anywhere). In a previous post, I already mentioned there were some fundamental changes in the way Outlook clients would connect to Exchange: RPC (over TCP) is no longer supported as a direct access mechanism for Outlook clients. Although it’s not very likely that big changes will occur between now an RTM, it might. All the information in this blog post is subject to change as Exchange Server 2013 is still under construction.
0 kommentar(er)
