Jandakel2
asked on
Migrate Windows 2000 Servers to Server 2003
Hello all,
A neighboring school district in my community recently purchased a brand spanking new rack mount PowerEdge with Server 2003 to replace their two existing 2000 Advanced Servers. They are currently using the servers for DHCP, NAT, Home Directories, applications, etc. and need everything transferred to the new server. What would be the most effective way to accomplish this? The new server is currently up and running, but not a domain Controller, just a member server in the current domain. If someone could walk me through the best way to road map this switch I would greatly appreciate it. Please bear in mind that the Server 2003 will be REPLACING the other servers. I know how to transfer the FSMO's and do the adprep/forest prep etc. prior to promoting the 2003 Server, it's just finding the most expdeditious way to transfer everything that I need to know.
Thanks,
JK
A neighboring school district in my community recently purchased a brand spanking new rack mount PowerEdge with Server 2003 to replace their two existing 2000 Advanced Servers. They are currently using the servers for DHCP, NAT, Home Directories, applications, etc. and need everything transferred to the new server. What would be the most effective way to accomplish this? The new server is currently up and running, but not a domain Controller, just a member server in the current domain. If someone could walk me through the best way to road map this switch I would greatly appreciate it. Please bear in mind that the Server 2003 will be REPLACING the other servers. I know how to transfer the FSMO's and do the adprep/forest prep etc. prior to promoting the 2003 Server, it's just finding the most expdeditious way to transfer everything that I need to know.
Thanks,
JK
ASKER
I don't know how to migrate everything, that is the issue here. I know how to duplicate the services, DHCP for example, but what is the easiest way to transfer the current DHCP Settings, i.e. scopes, reservations, etc. to the new server. How do you migrate the User Data to the new server without creating Ownership issues? If they are all mapped individually to \\OldServer\HomeDirectorie
JK
JK
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
One more suggestion I have is to keep a second DC around for redundancy purposes. If your sole DC goes down you will be dead in the water.
ASKER
So if I was to create a "road map" How would this be:
1) Perform Full Backup of Both servers being replaced
2) Perform appicable preparation ad/domain/forest
2) Join New Server into domain as Primary Domain Controller
3) Install DNS Role on New Server
4) Make new server Global Catalog
5) Transfer all User Data to new server using xcopy pointing applicable scripts/policies to new server\share
6) Migrate DHCP, NAT etc. to New Server but Don't enable yet.
** At this point, as far as I can tell the users should not be affected in anyway. I would like to be able to test and make sure everything is going well before I transfer all the FSMO roles. Bascially, I would like to be certain that the changeover is successful on a test machine/account before I make a global change. Any idea how I would do this?
7) Transfer FSMO roles
8) Make DNS Alias/registry entry
9) Shutdown old servers, test new server in production
10) If all goes well, wait 2 days to make sure
11) Shutdown New Server, Demote old servers,
12) Mission accomplished
How's that sound...please advise on any flaws in the plan, as I really don't want to screw up 500 users accounts, etc. THANKS!!
JK
1) Perform Full Backup of Both servers being replaced
2) Perform appicable preparation ad/domain/forest
2) Join New Server into domain as Primary Domain Controller
3) Install DNS Role on New Server
4) Make new server Global Catalog
5) Transfer all User Data to new server using xcopy pointing applicable scripts/policies to new server\share
6) Migrate DHCP, NAT etc. to New Server but Don't enable yet.
** At this point, as far as I can tell the users should not be affected in anyway. I would like to be able to test and make sure everything is going well before I transfer all the FSMO roles. Bascially, I would like to be certain that the changeover is successful on a test machine/account before I make a global change. Any idea how I would do this?
7) Transfer FSMO roles
8) Make DNS Alias/registry entry
9) Shutdown old servers, test new server in production
10) If all goes well, wait 2 days to make sure
11) Shutdown New Server, Demote old servers,
12) Mission accomplished
How's that sound...please advise on any flaws in the plan, as I really don't want to screw up 500 users accounts, etc. THANKS!!
JK
Join New Server into domain as Primary Domain Controller - In Windows 2000-2003 there is no PDC/BDC, they are all peers.
Step 3a) run dcdiag.exe on the new DC to verify everything is working. (must install support tools from the support directory on the w2k3 CD.)
Step 3b) Change DNS address being handed out to clients via DHCP to the new server's IP address.
Switch steps 8 and 9
Step 8a - Make sure all client computers have either restarted or ipconfig /release then ipconfig /renew to get the new DNS server address.
Step 11) do not shut down new server. Run DCPromo on old servers to demote them while the new server is still running.
step 12) after old servers are demoted you can shut them down.
Step 3a) run dcdiag.exe on the new DC to verify everything is working. (must install support tools from the support directory on the w2k3 CD.)
Step 3b) Change DNS address being handed out to clients via DHCP to the new server's IP address.
Switch steps 8 and 9
Step 8a - Make sure all client computers have either restarted or ipconfig /release then ipconfig /renew to get the new DNS server address.
Step 11) do not shut down new server. Run DCPromo on old servers to demote them while the new server is still running.
step 12) after old servers are demoted you can shut them down.
There is nothing really to test at 6a) because the old servers are still in production servicing AD requests. Running DCDiag will allow you to check that the new ADC is functioning properly.
Oh and I forgot Step 13) Raise the functionality level of the domain to Windows 2003. (only if all of your DC are W2k3 at this point)
I still suggest upgrading one of the old boxes to w2k3 to keep redundancy. If these servers have to go back for leases or whatever at least setup a desktop with W2k3 server and promote it to a DC.
Oh and I forgot Step 13) Raise the functionality level of the domain to Windows 2003. (only if all of your DC are W2k3 at this point)
I still suggest upgrading one of the old boxes to w2k3 to keep redundancy. If these servers have to go back for leases or whatever at least setup a desktop with W2k3 server and promote it to a DC.
ASKER
Have you any experience with the File Server Migration Toolkit?
http://www.microsoft.com/windowsserver2003/upgrading/nt4/tooldocs/msfsc.mspx
Just wondering if this would be a better solution than the Xcopy/DNS Alias/ registry fix
Thanks for your guidance- You da man
JK
http://www.microsoft.com/windowsserver2003/upgrading/nt4/tooldocs/msfsc.mspx
Just wondering if this would be a better solution than the Xcopy/DNS Alias/ registry fix
Thanks for your guidance- You da man
JK
I'm not familiar with the file server migration toolkit, but it looks like it might make things easier for you to migrate. It looks like it will setup DFS in the process. I highly reccommend DFS for your file sharing needs.
ASKER
Would you think DFS would be necessary with just one server? This is not my recommendation either by the way, it is being done this way to get rid of service/maintenance fees. I have considered putting up another server just for the NAT, so at least there would be another copy of SYSVOL floating around....
I just perform a mirgrate last weekend. What we did we was,
1. promote one of the windows 2003 as a DC
2. configure DCHP/DNS and all the services on the new DC (you can manule enter them it should not be hard at all)
3. demote the old dc, take it off line, then delete the computer account on the new dc.
4. name the other windows 2003 server the same name of the old dc, then promote the second dc.
5. configure DHCP/DNS and all other services on the second DC ( I will keep both new dcs for DHCP and DNS as resendent sercices)
6. restore all the files to the second DC which as the same name of the old dc. make sure restore to the same directory (D, E, ect) *(I use backup exec which will perserve NTFS permissions, this is very important)
7. Share folders and printers the same name as old the old DC
8. You should back in business.
Good luck
1. promote one of the windows 2003 as a DC
2. configure DCHP/DNS and all the services on the new DC (you can manule enter them it should not be hard at all)
3. demote the old dc, take it off line, then delete the computer account on the new dc.
4. name the other windows 2003 server the same name of the old dc, then promote the second dc.
5. configure DHCP/DNS and all other services on the second DC ( I will keep both new dcs for DHCP and DNS as resendent sercices)
6. restore all the files to the second DC which as the same name of the old dc. make sure restore to the same directory (D, E, ect) *(I use backup exec which will perserve NTFS permissions, this is very important)
7. Share folders and printers the same name as old the old DC
8. You should back in business.
Good luck
ASKER
I would have probably gone that route, markp if I was only replacing one with the other, unfortunately I am consolidating two into 1. Thanks for the input though!
JK
JK
ASKER
Thanks for all the help mcsween. Appreciated.
JK
JK
1. ad/prep forestprep and /domainprep, then the new server is a DC in your existing domain.
2. duplicate all services, such as DHCP, on the new server
3. migrate all shared folders, and then decommission as necessary.
Good Luck,