• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Retiring a Server

Dahak

Diamond Member
We have a Win2k Server that is running AD, DNS(just to speed up logins to AD,redirecting to our router) and our Point of Sale software.

Now I have a new server running Win2k3 Server and now is almost ready to be put live. My main question what is the proper way of getting rid of the older server as the new one will be replacing it.

These are the steps that I was going to take are as follows.
Add 2k3 server to domain,leaving both on to make sure all replication is done.
Remove 2k server from domain via dcpromo
so only domain controller is 2k3 server
Remove 2k server phycically.
Happy running 2k3server

Any comments/suggestions welcome




 
We have a Win2k Server that is running AD, DNS(just to speed up logins to AD,redirecting to our router)

You say that as if it is optional. It isn't.

Which leads me to some steps you left out. Assuming the current zone on the 2000 DC is AD integrated, install the DNS service on the 2003 server after you promote it. Then make sure the clients are pointing to it as their primary DNS server.

Since you are going to be removing the 2000 DC, the client should have ONLY the new server for DNS. No secondary should be configured on the client.

If the hardware can handle it, I highly recommend you rebuild the 2000 server as a 2003 box and make it an additional DC.
 
Originally posted by: STaSh
Since you are going to be removing the 2000 DC, the client should have ONLY the new server for DNS. No secondary should be configured on the client.

I made this mistake once and had a really rough time fixing things. I had already physcially moved the old server (God bless E-bay) and couldn't put it back on the network. It will probably take some time for everything to propogate to the new DC. Good luck.
 
STaSh: yeah, forgot to mention that the dns is intergrated, so i will have to install dns on the new server, and then have the clients point over to the new server. Thanks for the tip.

the reason I'm moving to server 2k3 is because, my current hardware is getting outdated,(dual p2 300) and we are going to be migrating to a new point of sale system as well which sql base.
 
You really should have a second DC...but I understand not keeping that old one!

I would also go to your DHCP server, and shorten up your lease times during the DNS migration, so your clients migrate faster. Once the migration is done, then you can set your leases back to the longer timeframe.

A few comments:
Get DNS running first on the new server, leave it alone for 3-5 days, to make sure the new DNS is working ok, and clients are migrating.
DCpromo the new box, and leave both up for another 3-5 days before DCpromo-ing down the old box.
 
Back
Top