Window 2K server upgrade

  • Thread starter Thread starter Scott Elgram
  • Start date Start date
S

Scott Elgram

Hello everyone,
This coming weekend I plan on moving a windows 2k server to another,
faster computer. I would much rather upgrade to wk3 but this is not a large
company and they would just rather I replace this existing w2k server box
without killing their current domain/login information. The current w2k
server is our domain/dns server and I would like to know if anyone knows of
any articles out there or can offer up any tips that could help me
accomplish this as smoothly as possible.
 
Add the new server to the domain as a member server. Then run dcpromo to
make it a DC.
Transfer the FSMO roles from the old DC to the new, see:
http://support.microsoft.com/kb/255690/en-us

Make it a Global Catalog, there is a section in this link on how to do this,
see:
http://support.microsoft.com/kb/320824/en-us

Set up DNS on the new server see:
http://support.microsoft.com/kb/280061/en-us

then work out how to point your AD clients to the new server, change the
scripts to reflect the new DC name and test.


hth
DDS
 
Mr. Sanders,
Thank you for this.....it makes it seem so simple and I hope it will go
just as smoothly as all this makes it out to seem.
From what I have read here once I have installed W2k Server on the
Destination box I should promote it and install Active Directory Then run
dcpromo and make it a replica in an existing domain. After that I can
simply follow the articles you have generously provided. However, I am
unclear how I am to point my AD clients to the new server. Is there an
article you or someone could provide that could detail this more for me or
is it as simple as just taking the source box offline at this point?

-Scott



Danny Sanders said:
Add the new server to the domain as a member server.
make it a DC.
Transfer the FSMO roles from the old DC to the new, see:
http://support.microsoft.com/kb/255690/en-us

Make it a Global Catalog, there is a section in this link on how to do this,
see:
http://support.microsoft.com/kb/320824/en-us

Set up DNS on the new server see:
http://support.microsoft.com/kb/280061/en-us

then work out how to point your AD clients to the new server, change the
scripts to reflect the new DC name and test.


hth
DDS
Click to expand...
 
From what I have read here once I have installed W2k Server on the
Destination box I should promote it and install Active Directory Then run
dcpromo and make it a replica in an existing domain.
Click to expand...

Installing Win 2k will make it a standalone server. Add it to the existing
AD domain as a member server (just add it to the domain as you would a XP
machine).

Run dcpromo after it is added to the domain, which will install AD and make
it a DC in an existing domain.

However, I am
unclear how I am to point my AD clients to the new server. Is there an
article you or someone could provide that could detail this more for me or
is it as simple as just taking the source box offline at this point?
Click to expand...

I am assuming that your existing DNS server is on the DC you are removing.
If it's not you don't have to install DNS on the new server and you don't
have to worry about changing where your clients look for DNS resolution.

Not sure if you are using DHCP or not. If so you will need to set up DHCP on
the new server. See:
http://support.microsoft.com/kb/325473/en-us

Then you would change the entry for the scope option 006 (DNS servers) to
list the IP address of the new server.

If you are not using DHCP then that information would have to be changed by
hand. You would go to the properties of my network places, then go to the
properties of the network card, then go to the properties of TCP/IP and
manually input the IP address of the new DNS server.


hth
DDS

Scott Elgram said:
Mr. Sanders,
Thank you for this.....it makes it seem so simple and I hope it will go
just as smoothly as all this makes it out to seem.
From what I have read here once I have installed W2k Server on the
Destination box I should promote it and install Active Directory Then run
dcpromo and make it a replica in an existing domain. After that I can
simply follow the articles you have generously provided. However, I am
unclear how I am to point my AD clients to the new server. Is there an
article you or someone could provide that could detail this more for me or
is it as simple as just taking the source box offline at this point?

-Scott
Click to expand...
 
Mr. Sanders,
First off here I would like to thank you for your continued help and
apologize partially in advance for my ignorance on this subject. I have
never had to do this before but the state of our existing DC is forcing my
hand.
You are correct in assuming that DNS is also on the DC I plan on
removing. In addition, this network is not using DHCP. Am I correct in
thinking that once I have configured everything on the new DC I could simply
remove the old DC from the network and change the IP address of the new DC
to that of the old DC?

-Scott
 
You are correct in assuming that DNS is also on the DC I plan on
removing. In addition, this network is not using DHCP.
Click to expand...

Then you don't have to worry about setting up DHCP on the new server. You
will have to go to the properties of my network places - properties of your
network card - properties of TCP/IP and input the IP address of the new DNS
server.

Am I correct in
thinking that once I have configured everything on the new DC I could
simply
remove the old DC from the network and change the IP address of the new DC
to that of the old DC?
Click to expand...

If you want to give the new DC the same IP address as the old DC you will
have to set it up with a temporary IP address, once you remove the old DC
(by running dcpromo to remove AD and choose the option that this is not the
last DC in the domain, once AD is removed it is then a member server, remove
it from the domain as you would any client by putting it into a workgroup)
then you should go into the DNS zone and delete all records for that IP
address that point to the old DC, then give the new DC the IP address and
restart the server. Remember *this* server should list it's own IP address
as the DNS server for it to use.

hth
DDS
 
Mr. Sanders,
Thank you for all your help, I hope this all goes over as smoothly as
all these docs make it out to seem.

-Scott
 
Mr. Sanders,
I would like to thank you again. Everything went just as smoothly as I
had hoped and I didn't have to sacrifice my whole weekend.

-Scott
 
Good deal!!!

DDS


Scott Elgram said:
Mr. Sanders,
I would like to thank you again. Everything went just as smoothly as I
had hoped and I didn't have to sacrifice my whole weekend.

-Scott
Click to expand...
 
Back
Top