Hey Chris, Why can't you put the 2003 machine on the NT 4.0 domain? It would save you a lot of hassle. Instead of doing witchcraft, why not walk the same way everybody does when migrating? ;) If the application that is critical can be run only on NT 4.0, let it be. But it won't know the difference if the domain is on a 2003 server or if it is on a NT server. That's transparent... Otherwise, you'd need to route all SMTP mail to the new 2003 server configuring the IMC to deliver mail on the 2003 server. However, once this is done every mail that is addressed to your company will go there unless configured otherwise. There are ways to configure that, if a recipient can't be found on one server, it'll forward the message to another. In Exch2k that's cool. But I've never done it in 5.5. I'd walk the migration path... it's transparent, easy as moving mailboxes between servers, and won't affect your application. Tiago de Aviz _____ From: Chris Wall [mailto:Chris.Wall@xxxxxxxxxxxxxxxxxxx] Sent: quinta-feira, 5 de fevereiro de 2004 02:40 To: [ExchangeList] Subject: [exchangelist] FW: Exchange 5.5 to 2003 http://www.MSExchange.org/ I guess this was a stupid question? No replies or ideas... Thanks, Chris _____ Hello all, I am on a fact-finding mission in preparation for an Exchange upgrade to occur later in the year. I was wondering if any of you can provide some insight. Information: [in the form of a Microsoft Certification question :-) ] You are the administrator of an NT 4.0 network.... to AD. Instead, we are planning on creating a New seperate AD domain to be hosted in the HQ datacenter (so there will be one NT4.0 domain and a Win 2003 AD domain hosted Currently our North America operations has 3 main NT 4.0 domains that are all connected via trusts. The exchange infrastructure is Exchange 5.5. We have one Exchange Organization and 3 different Exchange Sites (one for each domain). Due to mission critical services that are ONLY compliant with NT 4.0, the current Corporate HQ domain can not be upgraded from the same site). Slowly we will move users over to the new domain and leave their accounts active on the old NT 4.0 domain until the services can be replaced with 2003 compliant applications... Questions: If I implement Exchange 2003 in the new domain, could I configure it to use the same domain (@globalknowledge.com) as the existing Exchange 5.5 infrastructure? I guess my main question is - is it possible to create trusts between the new AD domain with the old NT4.0 domains so that mail can be received by Exchange 2003 and routed to mailboxes that currently exist in the Exchange 5.5 setup? Vice Versa, I would like to have any e-mails that are created on the exchange 5.5 mailboxes in the remote locations to be sent out through the new Exchange 2003 setup - until the remote domains can be brought in as OU's or the domain has been upgraded to 2003 AD as well. Is this where the ADC comes into play? I appreciate your reply and any information that would point me to an upgrade path similar to this. ------------------------------------------------------ List Archives: http://www.webelists.com/cgi/lyris.pl?enter=exchangelist Exchange Newsletters: http://www.msexchange.org/pages/newsletter.asp Exchange FAQ: http://www.msexchange.org/pages/larticle.asp?type=FAQ ------------------------------------------------------ Other Internet Software Marketing Sites: Leading Network Software Directory: http://www.serverfiles.com No.1 ISA Server Resource Site: http://www.isaserver.org Windows Security Resource Site: http://www.windowsecurity.com/ Network Security Library: http://www.secinf.net/ Windows 2000/NT Fax Solutions: http://www.ntfaxfaq.com ------------------------------------------------------ ------------------------------------------------------ List Archives: http://www.webelists.com/cgi/lyris.pl?enter=exchangelist Exchange Newsletters: http://www.msexchange.org/pages/newsletter.asp Exchange FAQ: http://www.msexchange.org/pages/larticle.asp?type=FAQ ------------------------------------------------------ Other Internet Software Marketing Sites: Leading Network Software Directory: http://www.serverfiles.com No.1 ISA Server Resource Site: http://www.isaserver.org Windows Security Resource Site: http://www.windowsecurity.com/ Network Security Library: http://www.secinf.net/ Windows 2000/NT Fax Solutions: http://www.ntfaxfaq.com ------------------------------------------------------