philodendrin
asked on
Migrating from W2K Server to Server 2003 / Keeping same server name
This weekend, I am going to migrate my old Windows 2000 Advanced Server and replace it with a new Dell on which I will install Windows Server 2003 Standard. I have another server running on the network already (Windows Server 2003 with Exchange running) which is a DC and also runs DNS. After the new server is up, I will demote this server so it is only a member server running Exchange, rather than running an additional DNS server, etc. There is no problem with it running DNS for a little longer if it makes the transition easier for the other server. Mainly, I want some advice as to whether my plan is sound for this transition:
1. build said new machine
2. once built, run dcpromo from a command line and go through the steps
3. Add DNS to new machine
4. move over DHCP scopes but dont activate yet
5. move over FSMO roles
6. let it sit for a few days
7. check logs
8. move all the files from the current file server to the new one and recreate all the shares
9. activate new DHCP scope
10. dcpromo the old one back to a member server
11. check logs
12. disjoin old server from the domain, delete computer object, rename new DC to old dc's name and IP.
I found these helpful instructions elsewhere on the 'net. Am I leaving any steps out? It is very important (to my boss, anyway) that the server name be the same. Since our organization is fairly small, I convinced him that we need just one DNS server running, as our Exchange server is getting old and doesn't need to playing so many roles.
While I'm not 100% sure that I know exactly how to enact each of the steps above, I am good at figuring things out, which is why I mainly want to know whether this plan is, at first glance anyway, sound. Any advice you experts could provide would be very helpful for me. Thanks much!
1. build said new machine
2. once built, run dcpromo from a command line and go through the steps
3. Add DNS to new machine
4. move over DHCP scopes but dont activate yet
5. move over FSMO roles
6. let it sit for a few days
7. check logs
8. move all the files from the current file server to the new one and recreate all the shares
9. activate new DHCP scope
10. dcpromo the old one back to a member server
11. check logs
12. disjoin old server from the domain, delete computer object, rename new DC to old dc's name and IP.
I found these helpful instructions elsewhere on the 'net. Am I leaving any steps out? It is very important (to my boss, anyway) that the server name be the same. Since our organization is fairly small, I convinced him that we need just one DNS server running, as our Exchange server is getting old and doesn't need to playing so many roles.
While I'm not 100% sure that I know exactly how to enact each of the steps above, I am good at figuring things out, which is why I mainly want to know whether this plan is, at first glance anyway, sound. Any advice you experts could provide would be very helpful for me. Thanks much!
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER