New company division: exchange/forest questions

[nostic]

Hello all,

Our company has decided to re-brand our security division so I have been tasked to prepare a new domain/email server. I would like to consolidate as much as possible so I have a few questions as to the path I should take:

We currently have a mixed 2003/2008 std environment with the domain controllers 2008 std. We are currently running exchange 2003 however are upgrading to exchange 2010.

Example of current domain is hvac.com and the new division is security.com

If I create a new tree in the existing forest so we can share AD account/shares/etc will the new forest be named security.hvac.com or can it be just security.com? What we are looking for is to keep hvac.com and security.com for the reason of the exchange tie in.

While the new domain isn't a huge deal the biggest issue is the exchange tie in. I would love to use 1 exchange server to handle both domains. Is it possible to have 1 exchange server send mail from 2 different domains automatically? meaning can I edit an exchange user and select their default sending domain so all mail sent from them would be security.com or hvac.com?

I understand that I can do a from box though outlook but that wont cover the owa users and smartphone users.

I guess I'm just looking for a bit of advice on which direction I should research.

So a quick recap:
1.) Need to create a new domain (security.com added to existing hvac.com) but need to share AD shares and internal resources.

2.) Need to setup exchange for new security.com as both send and receive connector for security.com users.

 

[58sniper]

You can certainly have more than one SMTP domain configured in Exchange, and can, as an administrator, specify which address will be their primary address. Users don't have that ability when dealing specifically with Exchange mailboxes unless you use third party software.

Is the new SMTP domain the only reason why you're thinking about having another domain?

Pat Richard MVP
Plan for performance, and capacity takes care of itself. Plan for capacity, and suffer poor performance.

http://www.ucblogs.net/blogs/exchange/

 

[nostic]

For the most part yes, the new domain is mainly for the exchange configuration. The other consideration was just incase the new division ever branched off to a new location, it would be nice to have seperate domains if there are seperate location.

 

[58sniper]

Separate locations generally isn't enough to do a separate domain. You'd be increasing administrative work for no real advantage. It will be cheaper and less complex to just add the new SMTP domain to Exchange and be done with it. No new hardware, no new software, no new licenses.

Pat Richard MVP
Plan for performance, and capacity takes care of itself. Plan for capacity, and suffer poor performance.

http://www.ucblogs.net/blogs/exchange/