Gardinho Posted May 19, 2010 Posted May 19, 2010 Hi guys, I have the task of transferring a Windows Server 2003 Domain Controller to a brand new server. Does anyone know of any good guides to follow? Also, the school has a volume license which enables us to use Windows Server 2008. The network only has Windows XP installed on all of the client computers. Would you upgrade the OS with the migration or is there no point? Thanks in advance for any help.
danrhodes Posted May 19, 2010 Posted May 19, 2010 If I were you I'd set the new server up seperatly add it as a DC then demote the old server and promote the new one to have full control etc. 1
featured_spectre Posted May 19, 2010 Posted May 19, 2010 Dan beat me too it!! I would do it the way Dan said aswell. Makes life much easier, and after you can do a data transfer if needed. I would upgrade to 2008R2 if possible, but still keep your XP clients if you dont want to upgrade to W7 just yet!
Gardinho Posted May 19, 2010 Author Posted May 19, 2010 That sounds too easy! There must be more to it than that? I'm trying to find a walkthrough from somewhere that will give me step by step method.
Dos_Box Posted May 19, 2010 Posted May 19, 2010 It's designed to be easy. Install Server 2008 R2 on new platform. Install DNS, DHCP (if required) etc Run DCPROMO to make it a domain controller Ensure DNS is replicating correctly and DHCP now points to new server for services. Transfer the FSMO roles Ensure FSMO info is being correctly registered on new server and in AD Wait a day (AD being the fickle beast it is at times) Check again Run DCPROMO on the old DC to demote it **This bit is very important, don't just remove it or else borkage will occur** Make coffee and sit back in the knowlege of a job jobbed. 3
danrhodes Posted May 19, 2010 Posted May 19, 2010 That sounds too easy! There must be more to it than that? I'm trying to find a walkthrough from somewhere that will give me step by step method. Exactly as Dos_Box said, it's designed to be easy, it sounds like a mamoth task if you haven't done it before but it really isn't too trciky. D
Dos_Box Posted May 19, 2010 Posted May 19, 2010 Exactly as Dos_Box said, it's designed to be easy, it sounds like a mamoth task if you haven't done it before but it really isn't too trciky. D Indeed, if you haven't done it before it sounds horribly complicated, but for many here it is just a routine task we have to do several times a year (promoting\demoting DC's), and the initial tasks, including transferring roles should take an experienced NM\techy no more than an hour so long as no problems occur.
danrhodes Posted May 19, 2010 Posted May 19, 2010 Indeed, if you haven't done it before it sounds horribly complicated, but for many here it is just a routine task we have to do several times a year (promoting\demoting DC's), and the initial tasks, including transferring roles should take an experienced NM\techy no more than an hour so long as no problems occur. Correct, an hour and a few cups of coffee later and "jobs a good en" as they say! The worst part I find is waiting for the O/S and all other software to install, the change over is the easy bit. D
Gardinho Posted May 19, 2010 Author Posted May 19, 2010 Thanks for the fantastic response to this fellas. Transferring the FSMO roles, is that as straight forward as the rest?
danrhodes Posted May 19, 2010 Posted May 19, 2010 Thanks for the fantastic response to this fellas. Transferring the FSMO roles, is that as straight forward as the rest? Yep it sure is see below for some help docs! How to transfer FSMO in Windows 2008 DC How to view and transfer FSMO roles in Windows Server 2003 D 1
Gardinho Posted May 21, 2010 Author Posted May 21, 2010 I'm going to try this in a test environment today. Does anyone know if it is possible to do this and ultimately keep the same server name? Thanks again.
danrhodes Posted May 21, 2010 Posted May 21, 2010 No, you will need to use a seperate Server name or you will run into problems. Consider a simple naming system for your Servers, for example we use Server1,2,3,4,5,6,7,8,9,10............ if you already have that convention don't get dragged into the idea of calling them Server1a, Server2a as further down the line you will kick yourself, if your currently using this convention the best way I have found if you are going to remove the old Server from the equation is to call the new one Server01. D 1
Dos_Box Posted May 21, 2010 Posted May 21, 2010 No, you will need to use a seperate Server name or you will run into problems. Consider a simple naming system for your Servers, for example we use Server1,2,3,4,5,6,7,8,9,10............ if you already have that convention don't get dragged into the idea of calling them Server1a, Server2a as further down the line you will kick yourself, if your currently using this convention the best way I have found if you are going to remove the old Server from the equation is to call the new one Server01. D That is also a good system for keeping tabs on which servers are the oldest!
danrhodes Posted May 21, 2010 Posted May 21, 2010 Yep, sure is! I do have good ideas sometimes! ;-) D
irsprint84 Posted May 21, 2010 Posted May 21, 2010 I call mine sgs-dc-001, sgs-sims-001 etc.. then if I have to move call server sgs-dc-01, sgs-sims-01
danrhodes Posted May 21, 2010 Posted May 21, 2010 Yep same idea, just other way around :-) it's a tried and tested system. D
FN-GM Posted May 21, 2010 Posted May 21, 2010 soemthing you all missed Dont forget to run domainprep and forestprep (if thats what they are called i forget) to upgrade the schema to 2008 before you add the DC. 1
Gardinho Posted May 21, 2010 Author Posted May 21, 2010 soemthing you all missed Dont forget to run domainprep and forestprep (if thats what they are called i forget) to upgrade the schema to 2008 before you add the DC. At what point to I need to do this?
CHR1S Posted May 21, 2010 Posted May 21, 2010 The biggest help for me was setting up a DFS with DFSReplication, you can then have all your shared areas mirrored and ready with the added redundancy if you decide to keep the old server up Its then a simple task of pointing your home and shared areas at the DFS instead of a single server ... simples
danrhodes Posted May 21, 2010 Posted May 21, 2010 At what point to I need to do this? You will need to run both the adprep /forestprep and adprep /domainprep commands before you add the new 2k8 server. These commands will need to be run on the domain controller on your network that contains the scheme operations master FSMO Role, probably your old server, as they will extend the schema to support the 2008 server. D 1
mavhc Posted May 21, 2010 Posted May 21, 2010 Remeber that Mac OS X doesn't like DFS that much, just found Diffiss while googling
edutech4schools Posted May 25, 2010 Posted May 25, 2010 Hi dgardner. I am about to do the same thing, how did it all go for you? Does 2003 server need to be R2 first?
danrhodes Posted May 25, 2010 Posted May 25, 2010 Hi dgardner. I am about to do the same thing, how did it all go for you? Does 2003 server need to be R2 first? If your just going to add a new server that will be running 2k8, then no the 2k3 does not need to be R2. D
edutech4schools Posted May 25, 2010 Posted May 25, 2010 fast reply :0) The new 2008 box will take the role of DC. I plan to set it up alongside the running system that is almost 5 years old and slowly move everything over so I can chuck it out. I always thought I needed R2 Thanks
Gardinho Posted May 25, 2010 Author Posted May 25, 2010 I actually got side tracked from my test, so I'm still looking at it. I'm not looking to carry out the transfer until the summer, but I wanted plenty of practise and preperation. Does anyone know if you manually put in the settings for DHCP & DNS or does the migration import them?
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now