Okay, I am moving Exchange 5.5 from an old NT4 server to a W2k server (no active directory) that will have the same exact name. The old server also served as a BDC (I will need to know if I should delete Exchange from it and keep it as a BDC when I am done). I've written out steps and I need to make sure it will all work.
My boss is concerned that if I change SID's it won't work--I told him it wouldn't matter if I went to NT4 on the new server or w2k, I would still have a different sid.
So here are the steps:
I am trying to delineate steps towards getting the new Exchange server at Warwick up and running. Any and all feedback is appreciated.
1) Loaded W2K Server with seat licensing (name Warwick02msx) and joined NRDCMSX domain. (Drives are configured exactly as they are on the old exchange server)
2) Loaded most recent service packs and all patches up to date
3) Loaded PC Anywhere
4) Loaded IIS--will be needed for the HP Tools software
5) Unplugged from network and loaded Exchange 5.0, Exchange 5.5 update and Exchange 3 service pack (still need to load Exchange 4 service pack)--ran performance optimizer and made sure to set all the settings to match the warwick01msx server as it is now---location of directories and information. (Created a new site and used the same organization and site names that are on the original server)
6) Changed name of server to Warwick01msx and logged on locally.
7) Attempted to open Exchange Administrator to begin setting it up but the services will not start on a local machine
Plan to complete:
8) Load HP Tools
9) Load Virus scan and ArcServe 2000 with Exchange Agent (will not start this service until migration complete)
10) Attempt to restore tape backup from original machine at this point (I actually haven't done this as I don't think it wil work--our backups are currently done with Windows NT 4 backup)
Whether or not this works--
11) Shut down present warwick01msx server
12) Remove it from domain through server manager tool on my laptop
13) Reboot new server and add it to domain as warwick01msx
14) Ensure that all the Exchange services start and I can open Exchange Administrator
15) Remove network cable
16) Delete warwick01msx server from domain using server manager
17) Restart old warwick01msx server and add it back to the domain
18) Copy all the settings of the old server to the new one that are needed (I am not sure how much information will already be there if the restore works prior to bringing the new server on the network--including the connector properties)
19) Make a backup of the entire Exchsrvr directory to tape drive including all exchsrvr directories from every drive
20) Run perwiz -z and not any customized settings on the original warwick01msx server.
21) Check if key management service is running and if it is copy the km server information stored in exchsrvr\kmsdata directory (I don't think this is installed)
22) Stop Exchange services
23) Copy the Exchsrvr directories to the new computer--since they do have the same hardware platform I will only copy the dsadata, dxadata, imcdata, mbdata, and mtadata directories. The ccmcdata, insdata, kmsdata and tracking.log directories will be copied if they exist on the original server.
24) Configure key server if it was used originally and then restart all exchange services
25) Restore all of the information that relates to site connectors and x.400 connectors 26) Double check that all directories match what is on the original server (size, location, etc). Go through each screen to ensure that all settings match.
27) Down the old server and remove it from the domain
28) Restart the new server and read it to the domain
29) Test the server by sending email various sites on the domain and over the Internet.
So, my question is: what am I missing. Will this work. Will the dir.edb be functional even though it will have a different sid. What are the ramifications of not having a bdc at my site? How much will it slow down authentication?
I am offering alot of points for this one but I need answers ASAP. I now NT and W2K but I've never built an Exchange Server--I've only administrated one and kept it up and running on very antiquated equipment.