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 Chris Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

?'s about 2008 DC promo and DHCP/NAME/IP 2

Status
Not open for further replies.

drewdown

IS-IT--Management
Apr 20, 2006
657
US
I have two 2003 DC's currently, one needs to be replaced with new hardware and I figured why not replace it with 2008. Ok I can transfer the roles/run adprep etc..

But I have some questions about DHCP, naming and IP addressing. Currently DHCP is handled by the DC that is going to be replaced, I want the new DC to handle DHCP and I want the name and IP address of the new server to match that of the old one.

Is that too much to ask? Or am I making it harder than it needs to be? I want to do it this way so I don;t have to change a fair amount of static devices that point to the failing DC for authentication, DNS, etc...
 
I would imagine you could use this procedure to move the DHCP database to the new 08 box;


Personally I never re-use a name for a new DC but it can be done, you would have to rename it after demoting and decommissioning the old one


yep you could then change the IP address after demoting and decommissioning the old server

Paul
MCTS: Exchange 2007, Configuration
MCSA:2003
MCSE:2003
MCITP:Enterprise Administrator

RFC 2795 - The Infinite Monkey Protocol Suite (IMPS)
 
I agree - I never reuse a name for DC either. Is there a requirement or just a desire? Under most circumstances, users don't know the name of DCs. Unless you have something else pointing there, like file shares. But those should get mapped in login scripts, which are easily edited.

Pat Richard MVP
Plan for performance, and capacity takes care of itself. Plan for capacity, and suffer poor performance.
 
Now that I think about DNS name shouldn't matter. As long as I change the IP address back to the original DC I shouldn't run into any problems.

I have another 2003 box which I can migrate the DHCP scope to, but I figured I should go ahead use 2008 for DHCP. I could always moved it to the other 2003 DC and then over the to the 2008 DC when its up.

One last question, more of a confirmation, once I run adprep on the 2003 DC do I need to promote/demote the new and old box immediately or should I run adprep when I am ready to do that?

I would like to bring up the 2008 box, promote it and let it run before demoting the 2003 box.

 
backup, backup, backup.
backup backup backup :-D
Do the adprep bits

promote 2008 to DC - make sure to select global catalog tick box (I think it's ticked by default actually)

wait a while

move fsmo roles to new 08 box if you want

remove global catalog from 2003 dc

demote it to member server





Paul
MCTS: Exchange 2007, Configuration
MCSA:2003
MCSE:2003
MCITP:Enterprise Administrator

RFC 2795 - The Infinite Monkey Protocol Suite (IMPS)
 
backup backup backup
run adprep
wait for AD to replicate
promote box and make GC
wait
verify things are ok (event logs, etc)
move FSMO roles & verify that all DCs have the correct info
remove GC from old server & wait
demote old server
backup


Pat Richard MVP
Plan for performance, and capacity takes care of itself. Plan for capacity, and suffer poor performance.
 
Looks like everything is running smoothly at this point. I just promoted the 2008 box and installed DNS/DHCP. I can connect to it via the AD console and it shows as a GC.

But what is weird when I run AD console from that new 2008 box and 'Change Domain Controller' it brings up all 3 but says the 2008 box is 'Unavailable' while the other 2 show as online. I can still connect to it, but it doesn't default to it.

Also in that very same window it shows my other 2 DC's, the one I am replacing is showing as a GC, new 2008 is showing as GC and the other static one (not being replaced) is showing as a DC.

Is that normal behavior?
 
Question about transferring roles, I attempted to transfer the 'Infrastructure' role to my new 2008 box and received a message stating: xxxx is a GC server. The infrastructure operations master role should not be transferred to a GC.''

Is that expected? It is currently assigned to my current GC and has worked fine since I set this domain up. Should I just transfer that to my other 2003 DC?
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top