I have a Dell windows 2000 server that is a few years old that needs to be replaced with a new server that will also use windows 2000. It is a very small setup with a domain and around 15 users and computers, nothing too complicated just a simple file server. I would like to replace the old server and keep the current domain structure intact. I am trying to keep the servers down time to a minimum and not have to go to the trouble of migrating all the users profiles to a new domain because none of the profiles are roaming. I have gotten some advise to setup the new server as a backup domain controller or something like that and then migrate all the domain information over to it. The only problem is I have never done this before. I not really sure where to begin or if this is even the best way to go about doing this. Thanks for any suggestions that anyone has to this problem.
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations TouchToneTommy on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Replace old server 2
- Thread starter tatum
- Start date
-
1
- #2
GrnEyedLdy
Instructor
Tatum,
"I would like to replace the old server and keep the current domain structure intact.
I'm not sure I understand this. You say Server...is it a Domain Controller?
If it is a DC, be sure you demote it before removing it from the network. This will insure that your Active Directory is up to date with regard to this machine.
Do you have other Domain Controllers in your network?
If you have more than one DC you will not lose any Active Directory information by removing and replacing that server regardless of whether or not it is a DC.
If you have no other DC's on your network you would need to create another one so that once replicated it will have all your current AD data. You will not need to recreate user or migrate anything.
Post more info about your network configuration...
Patty![[ponytails2]](/data/assets/smilies/ponytails2.gif "[ponytails2] [ponytails2]")
"I would like to replace the old server and keep the current domain structure intact.
I'm not sure I understand this. You say Server...is it a Domain Controller?
If it is a DC, be sure you demote it before removing it from the network. This will insure that your Active Directory is up to date with regard to this machine.
Do you have other Domain Controllers in your network?
If you have more than one DC you will not lose any Active Directory information by removing and replacing that server regardless of whether or not it is a DC.
If you have no other DC's on your network you would need to create another one so that once replicated it will have all your current AD data. You will not need to recreate user or migrate anything.
Post more info about your network configuration...
Patty
- Thread starter
- #3
I am sorry if I did not post enough before or if I made no sense. This is new to me.
The server is the only server on the network. I am pretty sure it is a domain controller. All the IP addresses are distrubuted by the router's DHCP and the server was just assigned a static IP within that range.
I just want to able to replace this old server with a new and keep the SID's for domain and users the same so I wont have problems with the profiles and other things on the workstations.
I just dont know how to go about doing this. Thanks for bearing with me.
The server is the only server on the network. I am pretty sure it is a domain controller. All the IP addresses are distrubuted by the router's DHCP and the server was just assigned a static IP within that range.
I just want to able to replace this old server with a new and keep the SID's for domain and users the same so I wont have problems with the profiles and other things on the workstations.
I just dont know how to go about doing this. Thanks for bearing with me.
-
1
- #4
Tatum,
Right click on My Computer, click on properties, and about halfway down the resulting window should be a note that says the computer is a domain controller. If so, just add the new server to the network and promote it to domain controller. After replication all of the account info should be on the new server. AND, if I remember right, you'll also need to make it a Global Catalog server before you demote your old server since you'll only have one server on your network.
HTH,
Joe Brouillette
Right click on My Computer, click on properties, and about halfway down the resulting window should be a note that says the computer is a domain controller. If so, just add the new server to the network and promote it to domain controller. After replication all of the account info should be on the new server. AND, if I remember right, you'll also need to make it a Global Catalog server before you demote your old server since you'll only have one server on your network.
HTH,
Joe Brouillette
- Thread starter
- #5
It is a domain controller. Let see if I have this right. So I would install windows 2000 on the new server and before I would do anything to it, put it on the network and do I think it is dcpromo (maybe, not sure). Make the server the domain controller. The account info will be replicated during that (right?)
Is there an option to make it the global catalog server when it is promoted to domain controller or do I have to do something specific?
Then I can demote the old server and take it off the network.
Does that sound right to yall?
Is there an option to make it the global catalog server when it is promoted to domain controller or do I have to do something specific?
Then I can demote the old server and take it off the network.
Does that sound right to yall?
Yep. What you do is put the Windows 2000 CD in and go to START, RUN, type DCPROMO and hit enter. That will promote the server to a domain controller. You'll need to answer a few questions like "Add to existing domain?". If you're not exactly sure of the domain name you can browse for the domain. AND, I don't remember how often Windows 2000 servers replicate so give it time to synch.
As for the Global Catalog server, I did it to my server but I don't remember the steps. I'll have to look it up and get back to you.
Joe Brouillette
As for the Global Catalog server, I did it to my server but I don't remember the steps. I'll have to look it up and get back to you.
Joe Brouillette
GrnEyedLdy
Instructor
Tatum
During promotion of your new Server to a Domain Controller, all the Active Directory information about the domain you area joining will be written to you new DC. After that, the default replication interval between Domain Controllers in the same domain is every 15 minutes.
To make a DC a global cataloge server:
Start|Programs|Administrative Tools|Active Directory Sites and Services
Expand Sites
Expand Default-First-Site-Name
Expand Servers
Expand your server
Right-click NTDS settings and choose Properties
Check the box for Global Catalog
Have fun!
Patty
During promotion of your new Server to a Domain Controller, all the Active Directory information about the domain you area joining will be written to you new DC. After that, the default replication interval between Domain Controllers in the same domain is every 15 minutes.
To make a DC a global cataloge server:
Start|Programs|Administrative Tools|Active Directory Sites and Services
Expand Sites
Expand Default-First-Site-Name
Expand Servers
Expand your server
Right-click NTDS settings and choose Properties
Check the box for Global Catalog
Have fun!
Patty
- Thread starter
- #8
![[yinyang]](/data/assets/smilies/yinyang.gif "[yinyang] [yinyang]")
Hello,
I am almost in the same predicament as Tatum is, except I have two (2) DC (domain controllers)on my network. I am in the process of replacing my third DC (global catalog) server, but I wanted to be sure that I am approaching this in the correct manner.
My questions are as follows:
1) How do you 'demote' a DC before removing it from the network? Like I said, the server that I am replacing is the Global Catalog server.
2) Is there anything else that I need to know or do to make this transition go as smooth as possible?
Thank you,
Matrix15
I am almost in the same predicament as Tatum is, except I have two (2) DC (domain controllers)on my network. I am in the process of replacing my third DC (global catalog) server, but I wanted to be sure that I am approaching this in the correct manner.
My questions are as follows:
1) How do you 'demote' a DC before removing it from the network? Like I said, the server that I am replacing is the Global Catalog server.
2) Is there anything else that I need to know or do to make this transition go as smooth as possible?
Thank you,
Matrix15
GrnEyedLdy
Instructor
Matrix15,
"How do you 'demote' a DC before removing it from the network?"
To demote, run DCPROMO just as you did to promote. The command is the same.
"the server that I am replacing is the Global Catalog server.
Since you have other Domain Controllers in your domain, the role of Global Catalog server should be automatically passed to another DC during demotion. However, if you want, you can manually configure another DC in your Domain to be a GC as was outlined in a post above.
Casanovaj,
"the server that im trying to replace has NT 4.0, can I run the DCPROMO too???
Nope, sorry...
Patty
"How do you 'demote' a DC before removing it from the network?"
To demote, run DCPROMO just as you did to promote. The command is the same.
"the server that I am replacing is the Global Catalog server.
Since you have other Domain Controllers in your domain, the role of Global Catalog server should be automatically passed to another DC during demotion. However, if you want, you can manually configure another DC in your Domain to be a GC as was outlined in a post above.
Casanovaj,
"the server that im trying to replace has NT 4.0, can I run the DCPROMO too???
Nope, sorry...
Patty
GrnEyedLdy
Instructor
Can you give us a little more information about how your network is set up?
Is the server that you want to replace with Win2K the PDC?
Do you have a BDC?
Are your clients all NT?
Patty
Hi Patty,
Thank u for your answer.
In my network I have 3 diferent domains, each domain has its own server (each one is a PDC; and the three have NT4). The 3 have trust relations.
I want to replace only one of this servers, who has like 20 pcs under his domain. Those PCs have win98 and XP, mainly.
I don't have BCD.
thanks,
Jorge
Thank u for your answer.
In my network I have 3 diferent domains, each domain has its own server (each one is a PDC; and the three have NT4). The 3 have trust relations.
I want to replace only one of this servers, who has like 20 pcs under his domain. Those PCs have win98 and XP, mainly.
I don't have BCD.
thanks,
Jorge
GrnEyedLdy
Instructor
Casanovaj,
You can simply run an Upgrade of Windows 2000 Server on your PDC and it will become the root of the new Win2K Domain. Should be very simple. You may have to re-establish trusts with the other NT domains afterwards.
However, it is always highly recommended that before you do this you bring up an additional BDC, allow it to replicate with the PDC and then take that BDC offline. Now should the upgrade process fail you would then be able to bring the BDC back online and in the absence of the original PDC, the BDC would promote itself to that position and your original data would still be intact.
Keep in mind that NT is not my speciality, perhaps there are some NT experts out there with more info for you.
Hope this helps,
Patty
You can simply run an Upgrade of Windows 2000 Server on your PDC and it will become the root of the new Win2K Domain. Should be very simple. You may have to re-establish trusts with the other NT domains afterwards.
However, it is always highly recommended that before you do this you bring up an additional BDC, allow it to replicate with the PDC and then take that BDC offline. Now should the upgrade process fail you would then be able to bring the BDC back online and in the absence of the original PDC, the BDC would promote itself to that position and your original data would still be intact.
Keep in mind that NT is not my speciality, perhaps there are some NT experts out there with more info for you.
Hope this helps,
Patty
- Status
Similar threads
- Locked
- Question
- Locked
- Question