Why do you think that local management and replication will require you to add them as a sub-domain? You will be adding replication traffic with the additional domain, not removing it. Don't forget that you've got to have a GC at the site for Exchange. And the amount of traffic for replication isn't really that big.
As to management, that's what the OU is for. Whoa, wait a second. I just reread what you said. You are going to have a DC at the office but not an Exchange Server? And you are worried about replication traffic? Replication traffic is going to be less than a percent of the mail traffic that you'll receive. And authentication traffic will be just as low. And you are only adding complexity by adding the domain, Exchange would be easy! If they've got to have local authentication, just stick a set of servers and make it a new site. As to the specifics of your question, yes, it's actually easy to do. But to do so requires that you have an understanding of Exchange and the AD. And to be able to decide that a new domain is needed, you need more understanding of Exchange and the AD. I'm not kidding, if you are having problems understanding how to extend Exchange to an additional domain, you really shouldn't be adding the domain, there are many other issues that you haven't even seen yet. -----Original Message----- From: Michael Morisoli [mailto:[EMAIL PROTECTED]] Posted At: Monday, March 11, 2002 5:50 PM Posted To: Exchange Sunbelt Conversation: E2K, New Sub-Domain in AD, How To? Subject: RE: E2K, New Sub-Domain in AD, How To? This is a remote office 2000 miles away. There are local management issues as well as replication issue that require us to add them as a sub-domain. I never said it would be the ONLY DC out there, but there has to be a first. I understand what you are saying, but there is a time and place for almost everything and this is the time and place. I really don't want to add to their complexity of this remote office by adding Exchange onto a server located there. There must be a way to have my Exchange infrastructure support messaging on a sub-domain. Thanks again, Mike -----Original Message----- From: Woodrick, Ed [mailto:[EMAIL PROTECTED]] Sent: Monday, March 11, 2002 2:44 PM To: MS-Exchange Admin Issues Subject: RE: E2K, New Sub-Domain in AD, How To? Don't add an additional domain. Just add an OU for the users. You are only asking for a lot of work. First off, you should never add a single domain controller for the domain, they should always be installed in pairs. Then you have to worry about DNS, then machine accounts, then moving users, then, then, then,,,, Just don't add another domain! -----Original Message----- From: Michael Morisoli [mailto:[EMAIL PROTECTED]] Posted At: Monday, March 11, 2002 5:41 PM Posted To: Exchange Sunbelt Conversation: E2K, New Sub-Domain in AD, How To? Subject: E2K, New Sub-Domain in AD, How To? I have an existing W2K and Exchange2K domain with several servers up and running fine. Today I am adding my first Domain Controller as a sub domain called "sales". What do I need to do to allow Exchange to service accounts located on the new sub-domain? I was thinking that I might need to run forest prep to modify the schema, but it's just a sub-domain to an existing domain that already has the modified schema. I am sure this is simple, I am just having a bad brain day. I would also like to add the Exchange admin tools to the new DC. Mike List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm
