Moving domain controller functions
I currently have 2 domain controllers. The Master is a Windows 2000 Sever and the other one is a Windows 2003 Server. I think they are both Global Catalog servers. And, these servers are doing other roles as well. The Windows 2003 server has Exchange server and also does the DHCP duties. And, over the years, while I wasn't here, other people have installed all sorts of odd software on these machines. I just built 2 new HP servers that I will install Windows Server 2008 R2 Standard on. I will be putting these 2 new servers on the network and then I want to move the domain controller functions to them, leaving the current servers in place to continue with their file server and Exchange roles, etc. I'm looking for the best, simplest method for doing this. It's a small network with no offsite equipment. So, simplistically thinking, I will install the OS on both new servers and put them on the network. I will assign them new static IPs. Then, as I understand it, I will run adprep (i'll have to go back and see which switches to add to that, /forestprep, or whatever) on the Windows 2000 server from the Windows 2008 R2 DVD. Then I can run dcpromo on the first new Windows 2008 R2 server... is that right? Somewhere in there is the option to make that the master / FSMO holder, I think. I also read something about running ipconfig /flushdns somewhere?? I need to start writing this down in a step by step fashion, so this sorta represents the first steps... before I move too far forward. Am I on the right track for this initial stuff? My current experience level with this is on the very low side of intermediate. We do our main Exchange email via the Microsoft Office 365 Online cloud. I hope these domain controller changes don't screw that up. The local exchange is for a smaller domain that we use. Thanks
September 7th, 2012 4:30pm

Hi, Following might help Prepare a Windows 2000 or Windows Server 2003 Forest Schema for a Domain Controller That Runs Windows Server 2008 or Windows Server 2008 R2 http://technet.microsoft.com/en-us/library/cc753437(v=ws.10).aspx Upgrade from Windows 2000/2003 to 2008/2008 R2 Domain Controllers http://awinish.wordpress.com/2011/03/04/upgrade-from-windows-2003-to-20082008-r2-domain-controllers/ install new 2008r2 domain controller into 2000 domain http://social.technet.microsoft.com/Forums/en-US/winserverMigration/thread/2493b92c-b45e-4b84-96a9-172edf5d3fe0 Migration specific queries, you may post them in Server Migration sub forum http://social.technet.microsoft.com/Forums/en-US/winserverMigration/threads Exchange specific queries, forum is here http://social.technet.microsoft.com/Forums/en-US/exchangesvrgeneral/threadsI do not represent the organisation I work for, all the opinions expressed here are my own. This posting is provided "AS IS" with no warranties or guarantees and confers no rights. - .... .- -. -.- ... --..-- ... .- -. - --- ... ....
Free Windows Admin Tool Kit Click here and download it now
September 7th, 2012 5:43pm

In addition to Santosh. For Microsoft Office 365 queries, post here. http://community.office365.com/en-us/forums/default.aspx Thanks
September 7th, 2012 6:29pm

Thanks for all the links. Lots of reading to do... looks like. I'm sure I'll find some answers in there, but I'm curious, since I am not 'upgrading' either of the current old domain controllers, but simply adding in 2 new servers to convert into domain controllers... 1. I can add the two new Windows 2008 R2 servers to the network. 2. I then run 'adprep /forestprep' and then 'adprep /domainprep /grprep' (or adprep32?) on just the Windows 2000 domain controller, since it is the FSMO holder. Does adprep have to be run on the Windows 2003 server as well? 3. Then I dcpromo the first Windows 2008 R2 server, and give it the Master or FSMO roles. 4. Then I dcpromo the second Windows 2008 R2 server. 5. Then I dcpromo the Windows 2000 server to demote it, right? 6. Then I dcpromo the Windows 2003 Server to demote it. Is that about it in a nutshell? When it's all said and done, the 2 current domain controllers will not be domain controllers, but will remain on the system for now, fullfilling their other roles. I have a minimally configured test lab at home with a Windows 2000 DC, a Windows 2003 DC, and Exchange 2003 installed on the Windows 2003 DC to practice on. I have another server, Windows 2008 R2, ready to be added to the lab system for testing. (These lab servers are Supermicro Atom servers, not that that matters for this, just an interesting note.) . I unmaked as answer the previous post only because I wasn't sure if this thread would get any more activity with a post marked as an answer.
Free Windows Admin Tool Kit Click here and download it now
September 19th, 2012 6:12pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics