quietriot1983 Posted March 8, 2013 Posted March 8, 2013 Bought a new server and installed Server 2008 on it...thing is, I don't know what to do next. I have a 2003 server as the DC currently, it provides DHCP, and has a separate drive in it with shares on, kids work etc. What's the best method to bring all the stuff from the old server over to the new one, with minimal downtime and fuss? Ideally the new server will just be called the same as the old one, then all the shortcuts around the school will still work. Thanks!
ricki Posted March 8, 2013 Posted March 8, 2013 HI Start by not naming them as the same thing. Prepare a plan of what you want to move over. Give your new server a static ip address. Do a full backup of the old server Prepare the forest and domain. Installing an Additional Domain Controller Join the new server to the domain Promote the new server to be a domain controller. How to promote Windows Server 2008 machine to domain controller – step-by-step guide | Windows Server 2008 and Microsoft virtualization blog Move shares onto new server by restoring from backups and share the correct folder with the correct permissions. Change group policy, scripts, and shortcuts to look at new server. Change any deployed packages to look at new shares. Make sure the new domain controller is a dns server. Backup the dhcp on the old server and restore it on the new server. How to move a DHCP database from a computer that is running Windows Server 2003 to Windows Server 2008 PLus allow enough time
quietriot1983 Posted March 8, 2013 Author Posted March 8, 2013 If the new server doesn't atleast end up with the same name, half the shortcuts, home areas etc won't work.
mdench Posted March 8, 2013 Posted March 8, 2013 If you name them the same thing when they are both on then neither one will function properly as the DNS names will be the same. Causing your shortcuts to stopping working. You can call it something else and then possibly have a DNS entry pointing the old server name to the IP of the new server.
mavhc Posted March 8, 2013 Posted March 8, 2013 Move to DFS, then you can move which server the files are on easily. There are microsoft tools for migrating file shares etc too. 1
CHR1S Posted March 8, 2013 Posted March 8, 2013 Move to DFS, then you can move which server the files are on easily. There are microsoft tools for migrating file shares etc too. This! DFS, replicate and relax
Guest Guest Posted March 8, 2013 Posted March 8, 2013 It will take you as much time to change the paths to a new server as it will to change to the DFS path. Once done you won't have to worry about this problem again. 2008 allows changes to a DCs name but personally I wouldn't do it. Do find and replaces on all your shortcuts etc. shouldn't take too long. Ricki missed moving fsmo roles to the new server. Although in theory they should move themselves I'd do it manually as its litteraly a 2 min job
Michael Posted March 8, 2013 Posted March 8, 2013 As already mentioned, you can't give it the same name otherwise it will cause conflicts in the DNS name resolution. It's like having two number 27's in one road. How does the postman know which one to deliver to? Clearly if you've not done this before, I would suggest you promote the new server as a DC then migrate shares manually one by one. DFS is for another day. You'll then need to migrate other server roles, such as Printing, File Sharing, IIS and the FSMO roles themselves which every network requires.
tmcd35 Posted March 8, 2013 Posted March 8, 2013 I'd start with running the domain and forest prep's for the new version of windows. Build the new machine (new name, new static IP) Make it a domain member Then run DCPROMO. Making sure DNS is setup and AD integrated and Global Catalogue is selected. Set robocopy running to mirror user data folders to the new server Leave to settle for a couple of days for replication Then transfer the 5 FSMO roles Again make sure robocopy is mirroring across user data Again leave to settle for a couple of days. Now you should be able to make batch changes to AD to point users profiles and home folders to the new server. Also update any logon batch files, etc to reference the the new server. Again a couple of days to confirm users are not having problems accessing files from the new server. Run DCPROMO on the old server to demote and remove it as a domain controller. Turn off the old server - job done! 1
CHR1S Posted March 8, 2013 Posted March 8, 2013 Turn off the old server - job done! Or alternatively keep it running as a load balancing/backup/fall over server
quietriot1983 Posted March 11, 2013 Author Posted March 11, 2013 I'd start with running the domain and forest prep's for the new version of windows. Build the new machine (new name, new static IP) Make it a domain member Then run DCPROMO. Making sure DNS is setup and AD integrated and Global Catalogue is selected. Set robocopy running to mirror user data folders to the new server Leave to settle for a couple of days for replication Then transfer the 5 FSMO roles Again make sure robocopy is mirroring across user data Again leave to settle for a couple of days. Now you should be able to make batch changes to AD to point users profiles and home folders to the new server. Also update any logon batch files, etc to reference the the new server. Again a couple of days to confirm users are not having problems accessing files from the new server. Run DCPROMO on the old server to demote and remove it as a domain controller. Turn off the old server - job done! Ok, So far I have: Run adprep /domainprep and /forestprep on the old server. Done a system state backup of the old server (to a different location) Joined the domain with the new server Run dcpromo on the new server. I'm about to set up robocopy to bring across the data from the old Ddrive. I'm hoping at the end of everything, I can use netdom to rename the new server.
Guest Guest Posted March 11, 2013 Posted March 11, 2013 I'm hoping at the end of everything, I can use netdom to rename the new server. You've been warned.
tmcd35 Posted March 11, 2013 Posted March 11, 2013 (edited) I'm hoping at the end of everything, I can use netdom to rename the new server. Why does the new server need renaming? surely you gave it it's correct name when you first installed Windows? Edit: just re-read post #3. I'd follow @mdench's suggestion and use a DNS alias to point to the new server rather than changing the new servers name. AD can be very touchy about these things... Edited March 11, 2013 by tmcd35
quietriot1983 Posted March 11, 2013 Author Posted March 11, 2013 (edited) I'm only looking at renaming as I have loads of teacher laptops that are standalone, and they have numerous folders and bits and bobs all shortcutted using the server name (we only have one), so rather than renew all those, and reinstall printers etc, I was hoping to use the same name. http://technet.microsoft.com/en-us/library/cc794951%28v=ws.10%29.aspx Edited March 11, 2013 by quietriot1983
Guest Guest Posted March 11, 2013 Posted March 11, 2013 use a DNS alias to point to the new server rather than changing the new servers name. AD can be very touchy about these things... ^ This then.
quietriot1983 Posted March 11, 2013 Author Posted March 11, 2013 (edited) Ok, I'll do it your way! Now I'm left with a server called 'newgateway'..oops! Anyway, we're days from that point yet, Robocopy is currently doing its thing. EDIT: Seems some people have success: http://www.edugeek.net/forums/how-do-you-do/51222-rename-dc.html Edited March 11, 2013 by quietriot1983
quietriot1983 Posted March 13, 2013 Author Posted March 13, 2013 At what point should I export DHCP from the old server and move it to the new one? Before I transfer FSMO roles, or after?
Michael Posted March 13, 2013 Posted March 13, 2013 Once you've promoted the new server to a DC, add the DHCP Server role, then migrate DHCP out of hours. That's the easiest way, then update DNS servers as required.
victory2012 Posted March 13, 2013 Posted March 13, 2013 Ok, I'll do it your way! Now I'm left with a server called 'newgateway'..oops! Anyway, we're days from that point yet, Robocopy is currently doing its thing. EDIT: Seems some people have success: http://www.edugeek.net/forums/how-do-you-do/51222-rename-dc.html i would never ever rename the dc the same name ,,, there is a reason why microsoft state when you demote the old dc that you must never use the name again.. your going to run into so many issues and problems it will take you longer to resolve.. alot people said it hear ill spell it out.. if you rename it to the old name you will cripple your active directory! best thing to do is put a dns entry in of the old server but make sure you have demoted the old server first otherwise you will break replication.. personally i would go nd modify all the laptops rather than mess about with trying get the dc the same name... i would also backtrack if i was u and demote the new server and rename it to a new name e.g DC1 or something simple and then promote it again and plan ahead before you jump in.. believe me this comes from experience of fudging a active directory in the past.
tmcd35 Posted March 13, 2013 Posted March 13, 2013 (edited) personally i would go nd modify all the laptops rather than mess about with trying get the dc the same name... i would also backtrack if i was u and demote the new server and rename it to a new name e.g DC1 or something simple and then promote it again and plan ahead before you jump in.. believe me this comes from experience of fudging a active directory in the past. Ah, the long line of experience. Fudging AD, we've all been there. If you need to demote an DC, for any reason, double check it had been completely removed and make sure you give replication enough time to do it's job before promoting another DC. Especially if you've done anything to FSMO roles! You can't demote a DC that has an FMSO role, and you want to be 110% certain ownership of the role has been successfully transferred before you demote. Check out the Meta Data Cleanup function in the ntdsutil command and check that all mention of the demoted DC has been deleted from DNS. The most important thing with DC's is time. Make sure you give it a couple of days between each step for things to settle and replication to occur. From memory default replication is every 24hrs +/- a random amount of time (upto 4 hours) - so it can be 28hrs between replications! (default settings, can be changed in local GPO's on the DC's). EDIT: As for DHCP, anytime - it's a standalone server function. Just make sure you don't have DHCP active on both DC's at the same time! I tend to setup DHCP a fresh each time rather than migrate settings, but that depends on how much your changed in the DHCP options. Edited March 13, 2013 by tmcd35
Michael Posted March 13, 2013 Posted March 13, 2013 EDIT: As for DHCP, anytime - it's a standalone server function. Just make sure you don't have DHCP active on both DC's at the same time! I tend to setup DHCP a fresh each time rather than migrate settings, but that depends on how much your changed in the DHCP options. You can have DHCP on every DC if required. You just need to enable Conflict Detection in DHCP Server.
quietriot1983 Posted March 13, 2013 Author Posted March 13, 2013 I've (successfully?!) moved DHCP to the new DC, and disabled it on the old one...time for a brew.
quietriot1983 Posted March 15, 2013 Author Posted March 15, 2013 Well, as soon as I unplugged the old server, EVERYTHING disappeared. DHCP, AD..everything. Ended up cloning, repairing then upgrading. Much easier.
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