Forum Discussion

ph1llies05's avatar
ph1llies05
Copper Contributor
May 22, 2024
Solved

Exchange on premise

I would like to know the best possible solution to block outlook connections (i.e. autodiscover, mail transport....) to only use specific mailbox servers. Here's my scenario. My root domain is called Philly, where I have three exchange servers ex1, ex2, and ex3 installed. Each of the exchange servers are configured with hub/cas/mbx roles. I also have 3 Tree domains named sales.com, HR.com, and marketing.com. I would like to have users from each tree domain connect to the respective exchange server where their mailbox is created when utilizing outlook. Example, mailbox users from sales.com domain will only use ex1, HR.com will use ex2, and marketing will use ex3. I have configured mail flow policies to prevent mail from being sent to other tree domains. Users from each domain will only be allowed to send to users within it's domain. I have also created Address book policy routing agents so users will only be able to see users within their respective domains address book. They will not be able to see the GAL. All of the above is working fine, but I'm running into a problem with Outlook connecting to any of the Exchange servers. How do I restrict Outlook to only connecting to a specific mail server? Is there an exchange powershell command that would restrict connections ? Thanks any help is appreciated.

  • ph1llies05 

    Configure Exchange Server per domain!
    1. AD , Exchange(sales.com)
    2. AD , Exchange(HR.com)
    3. AD , Exchange(marketing.com)

3 Replies

  • ph1llies05 

    Configure Exchange Server per domain!
    1. AD , Exchange(sales.com)
    2. AD , Exchange(HR.com)
    3. AD , Exchange(marketing.com)

    • ph1llies05's avatar
      ph1llies05
      Copper Contributor
      Thanks for the great responses. I was trying to answer a customers request and wasn't able to come up with anything other than configuring Exchange in each domain as you mentioned. Thanks
  • Dan_Snape's avatar
    Dan_Snape
    Bronze Contributor
    That's not really the way Exchange in this scenario is designed to work. My view is to keep the deployment as simple as possible and follow best practices. I'd personally be using the 3 servers in a DAG and having users across all three servers. This will provide high availability and redundancy for your users, which they'd probably appreciate more. Also, Exchange will route messages across all servers to satisfy redundancy as well.
    You can try use DNS and different namespaces to point users to a particular server, but again not recommended as it will require extra configuration.
    Maybe it might be better to put the Exchange servers in the child domain for each organisation