gpwalk
asked on
Replacing windows 2000 server domain controller with new hardware running server 2012 r2. best/easiest procedure
Replacing Domain controller currently running Server 2000 on ancient hardware with new hardware. The new hardware will be running windows server 2012 R2. What is the best way to go about this? It is a small network with about 25 clients. The clients are mostly Windows 7 Pro.
ASKER
Some additional information: there are two addition servers on the network. Both are configured as application servers, both running server server 2003. one is x64, the other is 32 bit.
The other member servers won't change the procedure.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
That seems simple enough but:
What about the machine name of the servers. Does the matter as long as they are not the same?
What about the SIDs? and share name the clients are linked to?
I'm not sure how to identify all of the FSMO roles.
What about the machine name of the servers. Does the matter as long as they are not the same?
What about the SIDs? and share name the clients are linked to?
I'm not sure how to identify all of the FSMO roles.
ASKER
Now this is beginning to NOT sound simple enough.
I have 24 hours to accomplish this once I begin.
I have 24 hours to accomplish this once I begin.
There are 5 FSMO Roles (PDC Emulator, Domain Naming Master, Infrastructure Master, RID Master and Schema Master).
Transferring them is a well documented process:
http://support.microsoft.com/kb/255690
http://support.microsoft.com/KB/255504
http://www.petri.com/transferring_fsmo_roles.htm
As for the Machine Name, you are correct, they cannot be the same.
Don't concern yourself with the SIDs. These are generated in AD and since you are not creating a new Domain, they will not be affected.
-saige-
Transferring them is a well documented process:
http://support.microsoft.com/kb/255690
http://support.microsoft.com/KB/255504
http://www.petri.com/transferring_fsmo_roles.htm
As for the Machine Name, you are correct, they cannot be the same.
Don't concern yourself with the SIDs. These are generated in AD and since you are not creating a new Domain, they will not be affected.
-saige-
What version of 2012 R2 are you going to use (Standard or DataCenter)?
-saige-
-saige-
Also you mentioned Shares. Do you have shares on your existing DC?
-saige-
-saige-
ASKER
it Sage
2012 R2 is standard
Yes the current 2000 domain controller is a data server as well, with shared drives.
2012 R2 is standard
Yes the current 2000 domain controller is a data server as well, with shared drives.
ASKER
What would be the pitfalls of just creating a new domain using the 2012 server?
Since the entire Domain consists of 4 servers(One is the win 2K controller and the others are 2003 servers)
Other than:
1. New SIDs, which would be a new desktop on each client there are 24 clients total.
2. Possibly having to reinstall networked applications
3 New user profile.
4 Moving the shared data on the old controller(WIN2K) to the new controller/
Since the entire Domain consists of 4 servers(One is the win 2K controller and the others are 2003 servers)
Other than:
1. New SIDs, which would be a new desktop on each client there are 24 clients total.
2. Possibly having to reinstall networked applications
3 New user profile.
4 Moving the shared data on the old controller(WIN2K) to the new controller/
Ultimately, I think this would cause more work than you realize and you would not be able to get this completed in a 24hour period. You would end up with literally days [if not weeks] of clean-up work because this user is missing this or that user is missing that, etc...
No, if you can't promote one of your existing 2003 servers to a domain controller, I was thinking of leveraging Hyper-V on the new server (unless someone else has a better idea).
In a nutshell, here are the steps involved:
1. Install Server 2012.
2. Join the server to the domain as a member server.
3. Add the Hyper-V role (and only the Hyper-V role).
4. Create a virtual guest for a 2003 Server.
5. Install the 2003 server OS and join it to the domain.
6. Promote the 2003 server to a DC.
7. Transfer your FSMO roles.
8. Ensure correct replication.
9. Demote the 2000 server (but leave it online).
10. Raise the Forest and Domain Functional Levels to Windows Server 2003.
11. Create a virtual guest for a 2012 Server.
12. Install the 2012 server OS and join it to the domain.
13. Promote the 2012 server to a DC.
14. Repeat steps 7 and 8.
15. Demote the 2003 server and remove it from the domain.
16. Remove the 2003 guest from the Hyper-V console.
As I said this is just a quick summary of the steps, there is a lot of work to do and I don't want you to do anything that you are not comfortable with. If you feel that you can create a new domain and accomplish everything, then I want you to do that.
-saige-
No, if you can't promote one of your existing 2003 servers to a domain controller, I was thinking of leveraging Hyper-V on the new server (unless someone else has a better idea).
In a nutshell, here are the steps involved:
1. Install Server 2012.
2. Join the server to the domain as a member server.
3. Add the Hyper-V role (and only the Hyper-V role).
4. Create a virtual guest for a 2003 Server.
5. Install the 2003 server OS and join it to the domain.
6. Promote the 2003 server to a DC.
7. Transfer your FSMO roles.
8. Ensure correct replication.
9. Demote the 2000 server (but leave it online).
10. Raise the Forest and Domain Functional Levels to Windows Server 2003.
11. Create a virtual guest for a 2012 Server.
12. Install the 2012 server OS and join it to the domain.
13. Promote the 2012 server to a DC.
14. Repeat steps 7 and 8.
15. Demote the 2003 server and remove it from the domain.
16. Remove the 2003 guest from the Hyper-V console.
As I said this is just a quick summary of the steps, there is a lot of work to do and I don't want you to do anything that you are not comfortable with. If you feel that you can create a new domain and accomplish everything, then I want you to do that.
-saige-
ASKER
My ultimate decision was to build a new forest and DC, then move the users and PC to the new domain.
Thank you all. It came down to business decision rather than a technical solution only. There were very few technical issues
Thank you all. It came down to business decision rather than a technical solution only. There were very few technical issues
Join it to the domain.
Promote it to a domain controller.
Move all the FSMO roles from the server being replaced to the new server.
Demote the old server.
Remove the old server from the domain.
FWIW, I strongly recommend at least two DCs for fault tolerance. If you don't have two DCs, have very good backups.