Upgrade to Server 2012/2012 domain

[DTracy]

I am currently starting an upgrade from domain controller Server 2003 Standard x86 to Server 2012. I have studied the information in thread:

http://www.tek-tips.com/viewthread.cfm?qid=1706296

I have a couple of questions:

1) First, I install the 2012 server and add to current domain and transfer the DNS and DHCP. When I promote the 2012 to the catalogue server, what happens to the three existing 2003 servers that are domain controllers? I don’t think I understand how a 2003 server could be a BDC for a 2012 domain controller.

2) Microsoft suggests an exit plan of disconnecting one or more of the 2003 domain controllers during the upgrade process. If I do this how do I get it back into the domain after the upgrade process?

3) Is this Current Domain Forest Level adequate for the upgrade to 2012?
domainFunctionality: 1 = ( DS_BEHAVIOR_WIN2003_WITH_MIXED_DOMAINS );
forestFunctionality: 1 = ( DS_BEHAVIOR_WIN2003_WITH_MIXED_DOMAINS );
domainControllerFunctionality: 2 = ( DS_BEHAVIOR_WIN2003 );

I think I’m going to be asking a lot more questions before I pull the trigger on this process.

Thanks in advance, Dave.

 

[DTracy]

I think I've discovered the answer to #1, adprep for the forest and schema will fix up the 2003 domain to the 2012 level.

Maybe on #2 replication will fix it up, not sure on this one.

#3 I can't find anything specifically wrong the the current Forest Level. Maybe it's ok?

Any additional information on this would be greatly appreciated.

Thanks,
Dave.

 

[ShackDaddy]

On #1, there are no BDC's, it's a decentralized AD replication environment, and the 2012 server just gets added to the mix, and knows it has to downgrade some of its security to communicate with the 2003 servers. That's what the ADPrep/ForestPrep does.

#2 - as long as the removed DC hasn't been offline for more than 30 days, the DC you took out of the mix will "catch up" as far as replication goes once it is reintroduced to the network. The reason you take it offline is to have a backup copy in case everything explodes.

#3 - you should be fine once you switch both forest and domain to NATIVE mode and not MIXED. You should be able to do this with the Win2003 AD GUI tools.

Dave Shackelford
ThirdTier.net
TrainSignal.com

 

[DTracy]

Thanks for the help ShackDaddy, should I change the mode to native before I upgrade, or after?

Dave.

 

[ShackDaddy]

Before!

Dave Shackelford
ThirdTier.net

 

[DTracy]

Thanks man, after I re-read the Tech Notes again I realized that I should fix that before, so I did. Now I have that problem taken care of and on to the next.

I've been thinking about the DHCP and the IP of the old server. The new server will have a different IP but all the static configurations of printers, etc, still point to the old server's IP. After I get the DHCP moved to the new server can I just change it's IP to the old value or do I have to chase down all these addresses and change them?

Thanks for your help.

Dave.