Don't forget dcpromo on the 2003 box between c) and d) to demote it from being a DC. Also might have to repoint DNS on clients and other stuff like that.
To the OP, please do a bit of reading about this before you attempt it, and if possible recreate the environment and test in a virtual lab. On Mon, Feb 15, 2010 at 1:17 PM, Phil Brutsche <[email protected]> wrote: > If this domain controller isn't doing anything but then it is really > very simple, and not any different than a 2000 -> 2003 upgrade: > > a) adprep to get the AD schema up-to-date > b) dcpromo the 2008 box to make it a DC > c) transfer FSMO roles to 2008 box > d) shut down 2003 DC > > Burian, Matthew J. (mjb) wrote: > > All, > > > > I am currently in the process of planning the migration of a primary > > domain controller running Windows Server 2003 R2 to Windows Server > > 2008. The 2003 server is running on hardware that is going to be > > retired, and the 2008 server will be installed on new hardware. I > > need to get all of the AD services and data up and running on the 2008 > > box so that I can pull the 2003 box out and the 2008 will take over > > with as little downtime as possible. > > > > Has anyone had experience doing this recently and could share some > > techniques that worked well? In theory, I was thinking that I would > > leave the 2003 server running, install the 2008 server and connect it > > to the domain as a member server, then transfer all of the AD/DNS data > > to the 2008 box and promote it to a DC. However, I am not sure of the > > best way to accomplish this task. Any input would be appreciated. > > Thanks! > > -- > > Phil Brutsche > [email protected] > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ > ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
