Greetings Kelvin, Get new hardware. Install Windows 2000 Install and setup DNS as secondary DNS to forest root DNS . Verify it is working fine. Promote to DC and join Comppany B Forest. Create New Child Domain ("ad.company.com") Monitor/Diagnostics that all is working well. Create trust between your NT 4 domain to the new child domain. From here onwards you could use the many migration manuals/white papers/how tos microsoft has for migrating NT 4 / Exchange 5.5 to Windows 2003/Exchange 2003 http://www.microsoft.com/technet/prodtechnol/exchange/2003/library/default.m spx. This is where the information for migration from ex 5.5 is http://www.microsoft.com/technet/prodtechnol/exchange/guides/Ex2k3DepGuide/f 4e10a4c-ce19-4694-9180-97c04298fe0f.mspx Kind Regards Sarbjit Singh Gill _____ From: Kelvin Hee [mailto:Kelvin.Hee@xxxxxxxxxxxxx] Sent: Friday, January 14, 2005 10:19 AM To: [ExchangeList] Subject: [exchangelist] Migration advice http://www.MSExchange.org/ My present company (Company A in Singapore) We are still in Windows NT 4.0 domain. Our Exchange 5.5 mail server is sitting on a Win2000 member server (reason being ..we need bigger Hard Disk storage space which Windows NT 4.0 can't support). We have about 150 NT and mailbox users. Company B (in London) Windows 2000 AD domain in native-mode. The AD forest root domain is "ad.company.com". The Exchange 2003 mail server is sitting on a Win2000 server. As the Company A has been merged with Company B, we need to perform the following : We need to migrate to Windows 2000 AD domain (in mixed-mode initially till all old NT 4.0 server migrated to Win2K). All our servers hardware are old and we need to buy new servers hardware. We will be a Singapore new regional child domain, joining company B's existing domain tree of "ad.company.com". Our child domain name is "Sng.ad.company.com" We will configure our DNS as a secondary copy of the forest root _msdcs zone from the forest root domain. For reasons of autonomy, it was decided that Company A will each have their own domain. This also removes the reliance on one another, and allows Company A to administer their own domain. We want the new mail server to be Exchange 2003 running on Win2000 server, with AD connector installed so that both the Singapore new mail server and old Exchange 5.5 mail server can see each other in Address Book. This will allow us to slowly migrate the mailbox user from old server to new server. We also want both the SG new and old mail server to be able to see Company B's mail user in Address Book and vice-versa. Please advise on what is the best way of doing this migrations. Thanks. ****************************************************************** Prebon email disclaimer This email is intended only for the addressee. This email and any files transmitted with it may contain confidential or privileged information. If you are not the named addressee or the person responsible for delivering the message to the named addressee, please contact postmasters@xxxxxxxxxxxxx This email has been scanned by MIMEsweeper. ****************************************************************** ------------------------------------------------------ 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: World of Windows Networking: http://www.windowsnetworking.com 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 ------------------------------------------------------ You are currently subscribed to this MSEXchange.org Discussion List as: ssgill@xxxxxxxxxxxxxxxxxxxx To unsubscribe visit http://www.webelists.com/cgi/lyris.pl?enter=exchangelist Report abuse to listadmin@xxxxxxxxxxxxxx