I'm on my way to perform a migration from Windows 2000 Server with Exchange 2000 to Windows 2003 SBS R2.
Exchange-related discussion is here: http://www.experts-exchange.com/OS/Microsoft_Operating_Systems/Server/SBS_Small_Business_Server/Q_22976910.html
I do not have any experience with multidomain networks, so I need some information which can make my life and migration easier. I do not have experience with Exchange as well, but I was forced to accept this job and I have to learn and perform it. However, I have some experience setting up and maintaining Windows Server and AD. Some details about existing setup:
a. T1 line with 32 public IPs, Riverstone RS3000 router and Netscreen firewall (both of them locked and I do not have a password but maybe I will find the person who set them years ago). If I connect computer directly to the router it can pickup one of available public static IPs but cannot go online without setting up of DNS server address manually (but Skype works without setting up DNS).
b. Windows 2000 Server, domain controller for domain alpha.com which public domain is not in use but users authenticate using this domain name, with Exchange 2000 which serve mail for domain beta.com. Beta.com is public domain with hosted site somewhere in internet and mail server which is running all the time in the office and I cannot stop it during the day (that means the migration should be performed with minimum downtime, but it's fine if the server is down for 12-24 hours during weekend and not accepting new mail).
c. New SBS server box will be domain controller for domain beta.com and will serve mail for the same domain (firstname.lastname@example.org). I will need to transfer everything from existing user accounts to new server - old email, contact, tasks, calendars.
d. There is no DHCP server set on old w2k server, all the workstations use static IP addresses whcih I set manually when I started because most of the workstations initially was with public IPs (the company got 32 public IPs and previous administrator assigned them to workstations). Some of them are Windows XP Home so they cannot join a domain anyway but I will upgrade them. Below is what I got from IP config:
C:\Documents and Settings\Administrator.ALP
Windows 2000 IP Configuration
Host Name . . . . . . . . . . . . : alpha-1
Primary DNS Suffix . . . . . . . : alpha.com
Node Type . . . . . . . . . . . . : Broadcast
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : alpha.com
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Compaq NC3120 Fast Ethernet NIC
Physical Address. . . . . . . . . : 00-B0-88-6D-8E-00
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.1.2
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 192.168.1.2
C:\Documents and Settings\Administrator.ALP
So far I know that the mail server (old 2000 Server box with Exchange) is on IP address xxx.266.206.194 and somebody told me that this address is mapped in the router and everything which is compung on this address is forwarded to 192.168.1.2 which is server's LAN address.
Right now I have my new SBS server OS installed on new box. I used additional router to separate new server from existing network and set it up as domain controller using private addresses 192.168.16.xxx as it was proposed by setup and domain name is set as beta.lcl to avoid future conflicts with 3 or 4 Macs. I set net router to use public IP address xxx.266.26.200 on WAN site, xxx.266.26.193 as Gateway and appropriate DNS server using information obtained from ISP. From LAN side the router is set to use 192.168.1.1 as its own address and run DHCP server 126.96.36.199....100. As I said, new server is with 192.168.16.2 and its WAN interface is set to use 192.168.1.1 as GW and itself as DNS. Secondary LAN adapter on the server will be used to connect 24-switch for internal network.
1. I feel that I did something wrong with this initial setup, and probably I do not even need second router and should connect the new server to any unused port on old Riverstone router and just assign to it any unused address from 192.168.1.xxx - for example, 192.168.1.5 which is not in use. Am I right? There is not a problem for me to reinstall Windows 2003 SBS from scratch and instead of using 192.168.16.xxx I can use 192.168.1.xxx. My point is that there is no DHCP server running on old box or on the router so I can exclude some of IPs whcih are currently assigned to existing workstations from DHCP range and have DHCP server running on new box. How does it sounds for you?
2. If I do the setup in way I described above, can I have both servers runnings in the same network together (they use different domains, but I am not clear will the new server affect for any reason mail delivery to domain beta.com which is still accepted by old server). ANd new server actually uses beta.lcl as domain name...
3. Actually, should I use beta.lcl as domain name or I can use directly beta.com as domain name for new server in case I will run Exchange server on it and will host web site on it? I am confused because before some people here at EE told me that if I'm going to host Exchange is better to use real public domain (beta.com, not beta.lcl). WHich way is easier, or it doesn't matter because actually DNS records for domain name are on different name server and all what I have to do is set new IP address for new server or even just remove old one and replace it with new one which will use the same IP address once I'm ready?
4. OK, if everything above (#1...3) is done and I have new server up and running as domain controller for beta.com, I can start thinking about Exchange. There will be not a problem to join a domain from workstations, they as I said will be connected to new switch which will be connected to LAN port on SBS server (I will install ISA server later, it comes with SBS Premium anyway, do you recommend this sequency or I should install it immediately). The reason why I was thinking about installing it later is because I'd like to see everything up and runnings (Exchange, shares) and then install ISA insead installing ISA and then troubleshooting problems related to firewall :-).
At this point, I have old server running and accepting mail at xxx.266.206.194. New one use xxx.266.206.200 if I am right with my plan. How can I test the new server and especially new Exchange or there is no way to do it until DNS settings are chenged to point to xxx.266.206.200?
5. Shoud I import old user data before I switch to new server or I can start using new server and process mail and later just merge old user data to appropriate accounts? Which way is recommended?
Sorry for such a long explanation and (probably) useless details provided above, just trying to give you the whole picture as I see it so you can give me the right way how it's better to do it. Any comments, advise or so how to perform this part of the migration process will be greatly appreciated and used almost immediately (it will be nice if I can finish with everything until the end of the week).
Please let me know if I am wrong in my reasonings, I'll be more than happy to learn better or right way to do it. Maybe I will need to ask you additional questions here or in separate topics to clarify the process. Thanks.