Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 192
  • Last Modified:

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!
0
philodendrin
Asked:
philodendrin
4 Solutions
 
dooleydogCommented:
sounds right, make sure you allow plenty of time for replication, and that when you rename the new DC to the old DC name, you give it plenty of time to replicate also. A weekend should be plenty.

Good Luck,
0
 
mcsweenSr. Network AdministratorCommented:
I suggest not renaming the new DC to the old DC's name and IP.  I would instead change the DNS address being handed out by DHCP to the new server's IP.  Changing the name of a DC has a lot of potential issues that comes along with it.

If you want to rename it to keep from having to change your login scripts/users's home directories just use an Alias in DNS with the old server's name and point it to the new server.  Make the following registry change on the new server.

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\lanmanserver\parameters\DisableStrictNameChecking should be set to "1"


Also when it's all said and done, raise the functionality level of the domain to Windows 2003.  This should only be done if all ADCs in the domain are Windows 2003 Server.

0
 
markpower60Commented:
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
0
 
Jay_Jay70Commented:
Hi philodendrin,

you have been given good advice from mark and others, one hitch you may find with renaming the server is the DNS records sometimes dont update, all you have to do is manually create a new host record for the server and make sure the old one is gone - thats just my two cents
0
 
philodendrinAuthor Commented:
Thanks to everyone for the helpful advice.  I will keep this open a couple more days and then will likely split the points since everyone who chimed in had very helpful things to say.
0

Featured Post

Configuration Guide and Best Practices

Read the guide to learn how to orchestrate Data ONTAP, create application-consistent backups and enable fast recovery from NetApp storage snapshots. Version 9.5 also contains performance and scalability enhancements to meet the needs of the largest enterprise environments.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now