There shouldn't be any problem doing this at all. First you will need to upgrade the domain schema and forest so that the 2008 dc can be supported. Once the schema is upgraded, just dcpromo in the new box. Since you will keep 2003 dc(s) then you will leave the forest functional level where it is at.
I generally recommend to have all domain controllers run DNS so as far as moving DNS in terms of workstations, that would be determined by DHCP. Once the 2008 box becomes a DC, if it's running DNS it will get all DNS data replicated to it for your AD domain. To have a painless DHCP move, lower the lease times on the current DHCP server to something pretty low, 8 hours for example, and then let all currently leases expire. So if the current lease time is 8 days, set it to 8 hours, and then wait 8 days. This is by no means necessary but gives you the best chance of not having duplicate IP's. If you move this before school starts it would be manageable problem to just do it all in one day. Delete all the current leases and stand up the new DHCP scope. Curtis McKay Network Administrator Belleville Township High School District 201 [email protected]<mailto:[email protected]> From: [email protected] [mailto:[email protected]] On Behalf Of Chris Franzen Sent: Thursday, July 29, 2010 9:22 AM To: tech-geeks Subject: [tech-geeks] adding a 2008 server to the mix I just got a new server (win 2008 R2) and want to put it in my network to control DHCP, DNS, and be global catalog server / domain controller. My remaining servers will stay on 2003 as they dont have the beef to make the jump. I would like to keep the existing network infrastructure (domain name and sites and services setup) First is this advisable? Second is their a particular order I should do things? (make it a DC, move DNS, move DHCP?) Third anything to watch out for? thanks for any pointers. Chris Franzen Technology Coordinator Nokomis School District 511 Oberle St. Nokomis, IL 62075
| Subscription info at http://www.tech-geeks.org |
