none
Two Exchange Servers in One single domain

    Вопрос

  • I'm trying to create two exchange servers in one single
    domain in production environment. We want to create a brand new exchange server
    to handle only traffic going to *@marketing.domain.com.
    We already have working exchange server 2010 deployed and just wanted to add
    one more exchange server to separate different traffics.

    Exchange1 = all traffics to *@domain.com

    Exchange2 = all traffic to *@marketing.domain.com

    Any idea where should I begin with? Is that easy to do?

    Thank you in advance for all inputs!!


     
    16 февраля 2012 г. 17:26

Ответы

  • I've done this before. Since Exchange 2007 and later routing is based on AD rather than RGC's, you need to setup a new AD Site in Sites and Services. The only purpose that site will serve is as a "resource site" for the seperate exchange install. By deploying in this manner, you can have a seperate MX record and firewall NAT that goes to the HUB in the Exchange2 AD site. The second piece is to insure, of course, that you make sure that the people with those SMTP domain email addresses have their mailboxes only housed on the Exchange2 system.

    Deploying in this manner, your mailflow is isolated from the *@domain.com email. Each has their own path. You can (and I would) even setup a seperate OWA entry point and ActiveSync/OA entrypoint for those users too. That would achieve full seperation.

    Some light reading:

    Exchange 2010 Routing: http://technet.microsoft.com/en-us/library/aa998825.aspx

    • Предложено в качестве ответа Adam Gamble 16 февраля 2012 г. 18:01
    • Помечено в качестве ответа exchangenewbie2 25 февраля 2012 г. 0:31
    16 февраля 2012 г. 18:00
  • The site needs to be associated by subnet, and the exchange server subnet will have to be associated with that site to make it work.

    See this: http://technet.microsoft.com/en-us/library/cc732761.aspx

    • Помечено в качестве ответа exchangenewbie2 25 февраля 2012 г. 0:32
    16 февраля 2012 г. 19:35
  • You'll need to create a new Address Policy and a new Accepted domain, both in the EMC up top at the Organization Level.

    Then you can create mailboxes with a @marketing.domain.com email, and your exchange server will accept them.

    Of course this opens up a whole nother discussion on email addressing, and if you want these new mailboxes to have their primary SMTP address as the @marketing or not. If so, you'll need to key in and filter them based on something...you'll see what I'm talking about when you do your new email address policy..lets get through that and go from there.

    Let me know!

    • Помечено в качестве ответа exchangenewbie2 25 февраля 2012 г. 0:32
    23 февраля 2012 г. 22:42

Все ответы

  • I've done this before. Since Exchange 2007 and later routing is based on AD rather than RGC's, you need to setup a new AD Site in Sites and Services. The only purpose that site will serve is as a "resource site" for the seperate exchange install. By deploying in this manner, you can have a seperate MX record and firewall NAT that goes to the HUB in the Exchange2 AD site. The second piece is to insure, of course, that you make sure that the people with those SMTP domain email addresses have their mailboxes only housed on the Exchange2 system.

    Deploying in this manner, your mailflow is isolated from the *@domain.com email. Each has their own path. You can (and I would) even setup a seperate OWA entry point and ActiveSync/OA entrypoint for those users too. That would achieve full seperation.

    Some light reading:

    Exchange 2010 Routing: http://technet.microsoft.com/en-us/library/aa998825.aspx

    • Предложено в качестве ответа Adam Gamble 16 февраля 2012 г. 18:01
    • Помечено в качестве ответа exchangenewbie2 25 февраля 2012 г. 0:31
    16 февраля 2012 г. 18:00
  • Adam, Thanks for the quick reply!! IC!! So basicaly I will need to create a new AD Site and treat it like 1 domain, 2 sites, and 2 exchagne servers right? I already installed the Exchange2 ahread of time (Before posting). And now I will need to create a new AD sites under AD sites and services. Sicne I already installed Exchange2 already and what do I need to do to point the new Exchange2 to the new site?

    Thanks again for all your help! =)

    16 февраля 2012 г. 18:56
  • The site needs to be associated by subnet, and the exchange server subnet will have to be associated with that site to make it work.

    See this: http://technet.microsoft.com/en-us/library/cc732761.aspx

    • Помечено в качестве ответа exchangenewbie2 25 февраля 2012 г. 0:32
    16 февраля 2012 г. 19:35
  • Got it! Thanks!! I just found out from the dev team they are going to create custom transport agent and they do not need any email box or storage from the Exchange2. They want to have any email with *@Marketing*.domain.com to route to new Exchange2 server. Some example are

    1234@Marketing1.domain.com

    213@Marketing3.domain.com

    I'm thinking i will need to setup some kind of rules under Exchange1. Is that possible?

    Thanks!

    16 февраля 2012 г. 19:56
  • I'm confused then, if they want it to route to Exchange2...yet Exchange2 will have no email boxes...where does the email end up going?

    Do they just want a dedicated HUB transport server to handle that mail while its being directed to its final destination? And if so, why?

    16 февраля 2012 г. 20:14
  • Adam, turst me i'm confused from my dev people too! =) Anyway, now I'm back to the original question. I have new site up in different subnet. I also created another writable DC and GC on new site. Now I have Site A + Site B exchange server and trying to figure out how to setup new email box from Site B by using *@marketing.domain.com. When I was trying to create a new email box on Site B, I can only create under *@domain.com. Do I need to create a brand new sub domain just for that? Do I need to create a new "Send Connectors" under Hub Transport?

    Thanks again for your help!

     
    22 февраля 2012 г. 23:49
  • You'll need to create a new Address Policy and a new Accepted domain, both in the EMC up top at the Organization Level.

    Then you can create mailboxes with a @marketing.domain.com email, and your exchange server will accept them.

    Of course this opens up a whole nother discussion on email addressing, and if you want these new mailboxes to have their primary SMTP address as the @marketing or not. If so, you'll need to key in and filter them based on something...you'll see what I'm talking about when you do your new email address policy..lets get through that and go from there.

    Let me know!

    • Помечено в качестве ответа exchangenewbie2 25 февраля 2012 г. 0:32
    23 февраля 2012 г. 22:42


  • Thanks
    again Adam!! One quick question, do you know is there any way we can create
    some kind of wildcard for the new email box? For example, I want people to
    email *@marketing.domain.comand
    all those email will go to email@marketing.domain.com
    mail box?



    Let me clarify
    what I’m trying to accomplish. Our development team wanted to create a
    customize hub transporter to our live email server but we don’t want them to do
    that. That’s why we created a brand new site and new exchange server and let
    them play with the new email server instead. I did a lot of research and found
    out there is no way they can create a customize hub transporter apply just on
    the new email server without touching the live email server since it must apply
    the customize hub transporter under the organization configuration.



    Their end
    goal is following:  



    *@domain.com<~~ Live



    *@marketing.domain.com<~~ new
    server for the development team



    I have one
    mailbox already setup email@marketing.domain.com
    on the new server and the development want to have any email with *@marketing.domain.com(123@marketing.domain.comor 321@marketing.domain.comor anything@marketing.domain.com) to
    forward all the emails to one single email box.


    24 февраля 2012 г. 16:48
  • Ok, I see.

    First, let me point out how bad an idea this is...accepting any email sent to that domain with no recipient filtering leaves you wide open to a DoS attack or anything really. Hello SPAM! ;) I would strongly strongly recommend you have your development team create specific email address that you back with specific mailboxes.

    That being said, if you want to proceed down this path...I think this is what you're looking for

    http://technet.microsoft.com/en-us/library/bb691132.aspx

    Take care

    adam

    24 февраля 2012 г. 16:53
  • Thanks again Adam!! The specific email server and mail box will be for internal use only for now. =) I was looking at the Cath-All mailbox too the other day but that required edge server and it is for routing external email only right?


    24 февраля 2012 г. 17:14
  • correct, you'll need an edge.

    Without that..I dont think its going to be possible...not 100% though, but I dont know how you would do it off the top of my head.

    I'll dig around some.

    24 февраля 2012 г. 17:20