Link to home
Create AccountLog in
Avatar of spectragases
spectragases

asked on

Replacing existing Windows 2000 DC with 2003

Hello,
I am replacing a Windows 2000 DC with a Windows Server 2003 DC. I have promoted the new server, installed DNS and DHCP. I have not added a DHCP scope or done anything to DNS. I do not see the new server OR the old one in AD Sites and Services. Does the new server need to be a GC? Why wouldn't I see the servers in AD Sites and Services? The old server is only running DHCP not DNS.
What is the best practice for removing the old server and replacing it with the new?  
Sorry for all the questions and thanks in advance!
j
ASKER CERTIFIED SOLUTION
Avatar of Brian Pierce
Brian Pierce
Flag of United Kingdom of Great Britain and Northern Ireland image

Link to home
membership
Create an account to see this answer
Signing up is free. No credit card required.
Create Account
Avatar of spectragases
spectragases

ASKER

I installed Win 2003, assigned static ip, and subnet mask, pointed DNS to the correct server, and joined the domain.
When you say R2, is that SP2?
I promoted the machine to a DC, however I do not see the computer in AD Sites and Services so that I can make it a GC. Should I manually add it?
I installed DNS and DHCP.
The server it is replacing is not the FSM
<<When you say R2, is that SP2?
R2 is release 2. Not the same as SP2. RS is the OS release version. If you just bought it within.....oh, the past 2 years, it's probably R2. Look on the CD itself....or from the server, right click 'my computer', choose properties, then on the general tab you will see system: Microsoft Windows Server 2003 (R2?). So yeah, if you see R2, then it's R2. If not, then you don't have R2.  

Hope this helps.
R2 and SP2 are not the same thing. if its not R2 then Windows is on a single CD - use ADPrep from the i386 folder. You still need to run ADPREP. If the server is not replacing the FSMO roles then you can ignore that bit.
The new DC should appear in the Domain Controllers OU in AD Users and Computers - if it doesn't there may be a problem.
Ok, it is not R2, just SP2.
I have to run ADPREP even if there have been other 2003 DC installs? (done by someone else)
It does appear in the DC OU in ADUC, just not in AD Sites and Services.
Hello,
I figured out why the server did not appear in AD Sites and Services. For some reason it was being placed in a different container than the one I thought it would go to. Anyway, I moved the server to the container I wanted it to be in.
I have installed DNS and will also be installing DHCP. (Our organization is small so not worried about the workload). Also made the server a GC and the server it is replacing is not the FSM.
I regards to the transition of DNS and DHCP from the old server to the new, what is the best practice?
Open the 'manage your server' on your new server. Go through the wizard for DNS (refer to your old DNS server if you forget any settings). You will want to keep your other server's DNS up and running until you get your new one running correctly. More info on DNS server configurations...
http://technet2.microsoft.com/windowsserver/en/library/4e1c7b17-16ab-4e7d-a333-15befb15c82e1033.mspx?mfr=true

Do the same for DHCP. Go through the wizard for DHCP, again referring to your old server for scope options. Note: you will add your new DNS server for DNS. You will have to make sure that the new scope has an exclusion list that excludes the IP addresses already assigned from your old server. So for instance let's say your old server handed out IP addresses 192.168.0.1 - 192.168.0.50. Make this an exclusion list in your new DHCP scope under Address Pool. So effectively your new DHCP server will only hand out 192.168.0.51-192.168.0.254. Don't forget to make an exclusion for any static IP address you have as well (server, printers, router/firewalls/switches/et...). Once your done with the wizard and all the scope options, turn off DHCP on your old server. At some point you will want to change the DNS scope options to make sure your old DNS server is deleted from the list. Then remove DNS from your old server once everything is working well on your new DNS server.  


I hope this helps.
Sorry for all the questions, but if DNS is already setup on this network, do I need to do any further configuration?
And if I configure the same scope in DHCP as the current Scope and then shut down the old DHCP server will that be a problem?
<<Sorry for all the questions, but if DNS is already setup on this network, do I need to do any further configuration?
Are you saying you have a 3rd DNS server?

<<And if I configure the same scope in DHCP as the current Scope and then shut down the old DHCP server will that be a problem?
As long as you make the exclusion lists in the new scope options and to be sure and be sure to change the old DNS (after you verify your new one is working) you should be OK. I'd make sure your new DNS server is up and running fine before you start to switch everyone over.
If you think you have DNS properly setup at this point....I'd take a test machine and statically assign the IP address for it. Use the same IP address, subnet, gateway....but change the DNS server to point to your new DNS server. Do not put any other DNS servers in the list. Reboot. Then see if everything is fine. If everything is fine, then your ready to delete the other DNS server from your DHCP scope options, and everything should be done.
good idea. i'll try it now
it worked but i have another problem. I am configuring the ip range in DHCP and now it's asking me for exclusions. not sure what to enter here...help! :)
<<I am configuring the ip range in DHCP and now it's asking me for exclusions. not sure what to enter here...help! :)

This is what I was getting at in my second post. Go to your old server. Open up DHCP, go to address leases. Note the IP address leased.... These are the address you want to put in the exclusion. Also, you need to add any IP addreses of any other static IP devices (Servers, routers/firewalls, switches).
Exclusions are basically the IP address (or range or IP addresses) you DON'T want your new DHCP server to hand out. You don't want to hand out already used IP addresses on your network, otherwise bad things happen.
got it. it was asking what address i wanted to exclude from within my range...which was none.
now it's asking for a wins server. do i need to install WINS or just point it to another server running WINS?
what I would do, is install WINS on your new server. Go back to the 'configure your server' and install wins. Then after that, you can point DHCP wins to your new server.
I panicked and pointed it to another server that is running WINS in a different location. So far everything seems to be working fine. I turned off DHCP on the old server and then shut the server off completely. I'll leave it off for a few days and then remove DHCP and demote it.
Can I install WINS on the new server now and point it to itself somehow?
I am awarding you the points. Thank you very much for your help!
SOLUTION
Link to home
membership
Create an account to see this answer
Signing up is free. No credit card required.
Create Account
<<With your old server shut down, i would leave it untouched for a few weeks maybe a month....just to be sure.
Scratch that. I misread you were going to demote it and put it back on your network.
Do you really need WINS - you can do without it in most cases.
Exchange 2000/2003 and SQL can require WINS. If you had WINS before, I'd keep it around. But yes, you may or may not need it.
If its a single domain, single subnet then you don't need WINS. Add it if you are not sure - it won't do any harm.
I have Exchange 2003, SQL, multiple subnets, but a single domain, so I guess I do require WINS. I have already awarded points to NetAdmin2436 for my question because he worked with me more to answer my questions.
KCTS - You have also given me some useful info. Should I start another post for the WINS question? I want to know if I can install WINS now and point DHCP to WINS on the local server now that I have already pointed it to another server.
I would have though my inital comment merited some points as it outlined the entire process !
BTW you have not awarded any points yet !
I don't see that you have awarded points yet, so you can use the 'accept multiple answer' and split the points to what you see fit.

Yes, you can install wins and point DHCP to it. Read my above comments again.
Thanks again the help from both of you!! :)