COM1
asked on
Replace Server 2003 Domain Controller with Server 2008
Greetings,
Current Local Network Setup = Server 2003 Standard 32 bit File Server (our one and only Server on the Network) acting as the sole Domain Controller and managing Active Directory, DHCP, DNS. No Exchange.
15 user/Computer Network.
I need to replace the 2003 Standard File Server (remove from the Network) with a new Server 2008 Standard 64bit and have this new Server 2008 Server act as the Sole Domain Controller managing Active directory, DHCP, and DNS.
There appears to be specfic steps that need to be taken to "demote" and "promote" Domain Controllers within a Network.
My questions are:
1. Since there is a minimal amount of user data and configurations to "re-enter" into the new Server 2008 Server is it possible to simply use the same Server Name and IP address as the Server 2003 Server when setting it up the new Server 2008 Server as a Domain Controller and avoid having to perform the steps to demote / promote?
2. IF I do need to follow and impliment the demote / promote steps (Restructering?) I'd like to know the simplest steps to take to accomplish this Server Replacement.
3. Is it possible to use the same Server name and IP address on the new Server 2008 Server that is currently on the Server 2003 Server?
4. Since the AD info is outdated, are there "minimal" steps I can take to demote / promote without transferring the necessary information? (the current Server 2003 DHCP & DNS config info is still valid)
Thank you in advance.
Current Local Network Setup = Server 2003 Standard 32 bit File Server (our one and only Server on the Network) acting as the sole Domain Controller and managing Active Directory, DHCP, DNS. No Exchange.
15 user/Computer Network.
I need to replace the 2003 Standard File Server (remove from the Network) with a new Server 2008 Standard 64bit and have this new Server 2008 Server act as the Sole Domain Controller managing Active directory, DHCP, and DNS.
There appears to be specfic steps that need to be taken to "demote" and "promote" Domain Controllers within a Network.
My questions are:
1. Since there is a minimal amount of user data and configurations to "re-enter" into the new Server 2008 Server is it possible to simply use the same Server Name and IP address as the Server 2003 Server when setting it up the new Server 2008 Server as a Domain Controller and avoid having to perform the steps to demote / promote?
2. IF I do need to follow and impliment the demote / promote steps (Restructering?) I'd like to know the simplest steps to take to accomplish this Server Replacement.
3. Is it possible to use the same Server name and IP address on the new Server 2008 Server that is currently on the Server 2003 Server?
4. Since the AD info is outdated, are there "minimal" steps I can take to demote / promote without transferring the necessary information? (the current Server 2003 DHCP & DNS config info is still valid)
Thank you in advance.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
You do need to run adprep to "prepare" the domain structure for Server 2008's new improvements.
With Server 2008 R2 from memory is that there is tools to migrate all settings from another server (2003/2008). This includes DNS & DHCP. You'd have to read up about it though.
http://technet.microsoft.c om/en-us/l ibrary/dd3 65353%28WS .10%29.asp x
I thought that if you wanted to upgrade the server from Server 2003 to Server 2008 (just a basic install-upgrade) it could ease the process. Your best bet may be the migration tools however.
With Server 2008 R2 from memory is that there is tools to migrate all settings from another server (2003/2008). This includes DNS & DHCP. You'd have to read up about it though.
http://technet.microsoft.c
I thought that if you wanted to upgrade the server from Server 2003 to Server 2008 (just a basic install-upgrade) it could ease the process. Your best bet may be the migration tools however.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
I forgot to mention, after the new server is promoted and before you pull down the other server, make sure you set the new servers DNS to 127.0.0.1 so it looks to itself for dns.
with adprep also you'll have to run the 32bit version from the Server 2008 DVD. If you only have the 64bit then you'll have to source a 32bit version (I can't remember if both are on the DVD or not).
They're both there. I gave the command for it - aprep32 /forestprep.
I just fought with that the other day for like 15 minutes until i realized there was a different file. Felt like a complete n00b.
I just fought with that the other day for like 15 minutes until i realized there was a different file. Felt like a complete n00b.
Ah, tired eyes. Yeah - had total hell with it in the past when we had to push the settings in for Exchange in the past, got caught there too.
COM1: what do you use for e-mail on that network?
COM1: what do you use for e-mail on that network?
ASKER
Thanks Kiwistag & mwiener1....I appreciate your time!
kiwistag: We are using Google Apps (Paid) for Business for our email.
mwiener1: I am confused...in your first post you mention running dcpromo on the S2k3 Server twice at separate points...once after running adprep32 and then again after running NTDSUtil (?).
Also, which Server do I run the NTDSUtil from?...it sounds like I would run it from the 2003 Server side....if this is the case does it at some point ask for static IP of new DC?....."make sure that you pick new DC in existing forest" = the time you designate IP address of new DC?
kiwistag: We are using Google Apps (Paid) for Business for our email.
mwiener1: I am confused...in your first post you mention running dcpromo on the S2k3 Server twice at separate points...once after running adprep32 and then again after running NTDSUtil (?).
Also, which Server do I run the NTDSUtil from?...it sounds like I would run it from the 2003 Server side....if this is the case does it at some point ask for static IP of new DC?....."make sure that you pick new DC in existing forest" = the time you designate IP address of new DC?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
You run adprep on old server, dcpromo on new server to promote, and then dcpromo on old server to demote.
ASKER
Thank you kiwistag,mwiener1 & Sandeshdubey.
mwiener1: thanks for clarification of dcpromo...got it
Sandeshdubey: VERY thourough info, thank you.
It all comes together when combing info from all 3 contributing experts!
It appears relinqiushing control is tricky business....whether your a Domain Controller or Dictator of a county!
Thank you all for contributing. I will execute the DC change over & impliment all provided info this weekend
mwiener1: thanks for clarification of dcpromo...got it
Sandeshdubey: VERY thourough info, thank you.
It all comes together when combing info from all 3 contributing experts!
It appears relinqiushing control is tricky business....whether your a Domain Controller or Dictator of a county!
Thank you all for contributing. I will execute the DC change over & impliment all provided info this weekend
ASKER
Forgot to thank the 4th expert, mkline71 for his input and links.
Thank you all again for your contributions.
Thank you all again for your contributions.
no problem, just glad you were helped
Thanks
Mike
Thanks
Mike
ASKER
No, the new Server 2008 does not have to have the same Server name...I thought it might simplify other network set ups.
" install the Active Directory data for Server 2008 on the Server 2003 AD "
I'm confused about what you mean about installing AD data from Server 2008 on the Server 2003 Server?....do you mean running adprep then raise the functional level?
It sounds like I'll need to run adprep.exe/forestprep & adprep.exe/domainprep on the Server 2003 Server while the Server 2003 is connected to the network then raise Domain functional level on the Server 2003 to Server 2008 level (?).....then what?