Join Exchange 2003 server to SBS 2008 domain already running Exchange 2007

Can this be done without any problems? Will the SBS 2008 instance of Exchange have any problems with a 2nd Exchange server (2003) being added to the domain?
drl1DirectorAsked:
Who is Participating?
 
Lee W, MVPTechnology and Business Process AdvisorCommented:
You keep saying - "fickle SBS" - what does this mean - I've used SBS for years... it's not "fickle" - it's got certain requirements.

If you're sending mass mailings, why not just use an SMTP server - why use all of exchange?  IIS has an SMTP server.

SBS or not - I don't know if you can install an Exchange 2003 server in an Exchange 2007 org.  I don't know for certain because this is NOT a typical or normal thing to do.
0
 
Lee W, MVPTechnology and Business Process AdvisorCommented:
Frankly, I'm not sure SBS 2008 would take kindly to adding an OLDER version of Exchange being added to the domain - you CAN add the same or newer versions...

why would you want to add a 2003 Exchange server to a 2007 Exchange install?
0
 
drl1DirectorAuthor Commented:
Thanks for the reply. I suspected SBS might have an issue with another Exchange server being added, hence asking the question, to get a better understanding of the likely fall out.

For clarity, I'm not looking to "add a 2003 Exchange server to a 2007 Exchange install". What I am looking to do is this:

SERVER A: SBS 2008 including Exchange 2007 in domain A
SERVER B: Server 2003 including Exchange 2003 in domain B

Domain A contains 99% of our business systems (8 servers, Exchange, IIS, SQL, 40 users etc.). Domain B contains only SERVER B and nothing else (legacy domain with everything but SERVER B migrated to domain A).

I'd like to add SERVER B to domain A, so that I am only running one domain, can consolidate DNS activity and such like. I know how fickle SBS can be but am not clear on the impact of adding a 2nd instance of Exchange to a domain (not to the SBS box itself, obviously).
0
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

 
Lee W, MVPTechnology and Business Process AdvisorCommented:
You can't just slam Exchange into a new domain - if it wasn't in the domain to begin with, you would have to uninstall it and then re-install it... so what's the point?

Export the mailboxes and pull them into the 2007 Exchange.  (Again, WHY would you want to add a second instance of Exchange?)  

If you can explain more clearly I may be able to better assist you.
0
 
drl1DirectorAuthor Commented:
I wasn't intending to simply slam Exchange 2003 in to the new domain! I know how fickle SBS can be and so am very cautious about doing anything that might upset it, this is why I'm trying to understand how best to improve my current set up without causing problems.

Extra info as requested...the Exchange 2007 instance is used as our primary mail server and hosts all user mailboxes. The Exchange 2003 server is used for mass mailing to subscriber base of 170,000 members and contains only one mailbox. Essentially bulk emails are generated by a SQL SP and pumped through the SMTP service on the Exchange 2003 instance. We often send 100k emails per day and historically have always segregated this activity from the main mail server activity so as not to overload that Exchange server or compromise other business activities i.e. general email flow to/from clients. I'd still like to maintain this type of segregation to manage Exchange load, balancing use of bandwidth (each Exchange server uses a different gateway) however instead of having two Exchange servers sitting in different domains, it would be preferable (as long as SBS can handle the 2nd Exchange instance existing in the same domain) to be running one domain only, or such is my perception.
0
 
drl1DirectorAuthor Commented:
I'm referring to SBS as being 'fickle' as that is how it has been on some occasions in my experience spanning 2000, 2003 and 2008. Anyhow, that is beside the point and 2008 is much better than previous versions IMO.

There's no specific need to use all of Exchange as it currently is used simply to pump our mass email and not handle user mailboxes, so I'm open to (and appreciate) suggestions for a better approach. Essentially this Exchange instance is a left over item from when we ran two offices and two domains so it hasn't been intentionally set up to serve the situation it is in now.

With the IIS SMTP server would I still be able to target that SMTP service using a SQL SP? Currently all SQL SP-generated emails use cdosys and target the IP of the Exchange 2003 server. Would it be as simple as changing that setting to point to the IP of the IIS server? How do I access the IIS SMTP server to check/set things like FQDN? I'm used to using Exchange System Manager or Exchange Management Console/Shell for all things SMTP/Exchange related, so not familiar with SMTP admin as part of IIS.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.