Did you have to do anything special on the Email server? -----Original Message----- From: Greg Kras [mailto:[EMAIL PROTECTED]] Sent: Friday, March 22, 2002 11:47 AM To: MS-Exchange Admin Issues Subject: RE: AD Design Question as it relates to Exchange 2000
I don't have direct experience with your situation but I can say that we use a different domain than the legacy domain. In addition to that the domain that we use primarily for email, sunbelt-software.com, is not the domain we use for our AD. So far, so good :) Greg Kras MCP+I MCSE Sunbelt Software Technical Services Manager > -----Original Message----- > From: Alan Osborne [mailto:[EMAIL PROTECTED]] > Sent: Friday, March 22, 2002 12:39 PM > To: MS-Exchange Admin Issues > Subject: AD Design Question as it relates to Exchange 2000 > > > I am wanting some advice about different directions we could > take in the > structure of DNS and AD as it relates to a migration from > Exchange 5.5 to > 2000. > > Our current structure is a singe domain called "Assembly". > Our Exchange > 5.5 server services email sent to "legislature.state.tn.us". > Should we : > > A. Make root DNS Domain, and AD Root > Legislature.state.tn.us? This will > give us an AD Domain name of "legislature.state.tn.us" and a > legacy domain > name of "assembly. This seems like the easy route, but I > hate that the > legacy domain name is different than the new domain name. > > B. Make the root DNS Domain, and AD Root > Assembly.state.tn.us? Will this > cause problems with email server since it service email sent to > Legislature.State.Tn.US? This Email server also serves as > the Exchange > Server that users login to. It seems like this route will > require some > major restructuring of email system. > > Thanks, > Alan > > 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