Theldron Posted November 12, 2014 Posted November 12, 2014 Hello, I am replacing an old 2003 server with a new 2012 server. I want to rename the new server with old servers name, I know that i will have to change the old server name first then change the new server to it using netdom. Are there any other steps that i need to take? Cheers
FN-GM Posted November 12, 2014 Posted November 12, 2014 What does the server do? You are asking for trouble if you start renaming live servers.
Theldron Posted November 12, 2014 Author Posted November 12, 2014 The old server is the DC and does everything but I am replacing it with a new server to replace it completely but I though it would make life easier to chnage the name of the new server to replace the old one.
FN-GM Posted November 12, 2014 Posted November 12, 2014 You can't rename a 2003 DC. Its a limit within windows. Can you not just give it a new name?
win Posted November 12, 2014 Posted November 12, 2014 I decommissioned an old server then rebuilt a new one in it's place with the same name. It may not be necessary, but you could as a precaution disconnect the old server from the domain first rather than just renaming it.
FN-GM Posted November 12, 2014 Posted November 12, 2014 (edited) I decommissioned an old server then rebuilt a new one in it's place with the same name. It may not be necessary, but you could as a precaution disconnect the old server from the domain first rather than just renaming it. You can't just disconnect a DC from the domain. Plus you are not supposed to use the same name for a DC until the tombstone has finished. That is usally 60 days. Edited November 12, 2014 by FN-GM
tmcd35 Posted November 12, 2014 Posted November 12, 2014 You can't just disconnect a DC from the domain. Plus you are not supposed to use the same name for a DC until the tombstone has finished. That is usally 60. 100% this. New name, new IP. Make sure DNS entries are nice and tidy. Last thing you want is AD going up it's own ***, so to speak. Give the new server plenty of time to replicate everything from the old then decommission the old DC cleanly with dcpromo.
Theldron Posted November 12, 2014 Author Posted November 12, 2014 I can just change the IP of the old server and the new one around can't I?
FN-GM Posted November 12, 2014 Posted November 12, 2014 I can just change the IP of the old server and the new one around can't I? I wouldn't do. Best way is new IP new name.
tmcd35 Posted November 12, 2014 Posted November 12, 2014 If it's a DC I really, really wouldn't. AD is tied so deeply into DNS that one mistake and you'll be fighting problems for months. Been there, done that, not worth it. New name, new IP everytime. (if it's not a DC then generally there are no problems with using the old name and IP).
Davit2005 Posted November 12, 2014 Posted November 12, 2014 (edited) Create a temp domain controller, move FSMO roles if/as neccessary to the temp, obliterate the old server, wait for the tombstone to finish, create the DC in the same name and then move the FSMO roles back. If you are creating a new DC make sure that you create a DC in the current schema unless you are going to perform an Active Directory upgrade in the same move. Of course plan this carefully but best not to unless you are confident and researched any implications. Edited November 12, 2014 by Davit2005
sparkeh Posted November 12, 2014 Posted November 12, 2014 I can I was just being lazy. Reusing the name and IP of a DC certainly isn't a route to lazy town. Heed the advice and use new and and IP
win Posted November 12, 2014 Posted November 12, 2014 You can't just disconnect a DC from the domain.. didn't realise it was a dc, must have been posted while i was writing. I done it with a DC however, steps were: - Decommission old DC, transfer fsmo to other DC if needed - Delete computer account in AD - Install 2012r2 on different server, rename to old server name + same IP as old server - add DC role No problems so far
FN-GM Posted November 12, 2014 Posted November 12, 2014 didn't realise it was a dc, must have been posted while i was writing. I done it with a DC however, steps were: - Decommission old DC, transfer fsmo to other DC if needed - Delete computer account in AD - Install 2012r2 on different server, rename to old server name + same IP as old server - add DC role No problems so far You are not supposed to use the same name within such a short period of time. See above.
win Posted November 12, 2014 Posted November 12, 2014 Hate to disagree with fellow edugeek people but there is really no need to wait a few months for it to tombstone before giving it the same name. As long as the old DC was removed and cleaned up properly, and replication on other DCs are working, you're good to go!
tmcd35 Posted November 12, 2014 Posted November 12, 2014 Hate to disagree with fellow edugeek people but there is really no need to wait a few months for it to tombstone before giving it the same name. As long as the old DC was removed and cleaned up properly, and replication on other DCs are working, you're good to go! The problem is being 100% certaint the old DC is fully cleaned out of DNS in particular but also there are some entries in Sites and Services (I think). Both dcpromo and deleting the AD account is *supposed* to clean it up correctly *but* I have been in the position where it hasn't. I think there are also some command line instructions you can run to clear the metadata in AD as well. It can get very messy, very fast. Seriously, this is your AD - is it really worth the risk of not doing it properly?
FN-GM Posted November 12, 2014 Posted November 12, 2014 Hate to disagree with fellow edugeek people but there is really no need to wait a few months for it to tombstone before giving it the same name. As long as the old DC was removed and cleaned up properly, and replication on other DCs are working, you're good to go! If you have done this you obviously don't look at your event logs. If you did you will see why....
win Posted November 12, 2014 Posted November 12, 2014 I just think waiting a few months for it to tombstone isn't common practise. Some might have the DC name and user linked into to certain programs long forgotten about e.g. DC1\admin, or the IP address as a reference so you need the DC up and running sooner rather than later. The OP can check out some online bloggs on using the same DC name as before. Take note of the clean up instructions and there should be no problems.
sparkeh Posted November 12, 2014 Posted November 12, 2014 Seriously, this is your AD - is it really worth the risk of not doing it properly? Couldn't agree more, can't see why you even think about risking it. Just because you *can* do it doesn't mean you should. But anyway the question has been answered so it's up to the OP to decide which course to follow
win Posted November 12, 2014 Posted November 12, 2014 To get it done quicker here are a couple of guides that will help: https://social.technet.microsoft.com/Forums/windowsserver/en-US/72d5eda0-7185-4f97-a1cf-7952c12dc786/replacing-old-domain-controller-but-keeping-same-name-and-ip?forum=winserverDS http://blogs.msmvps.com/acefekay/2010/10/09/remove-an-old-dc-and-introduce-a-new-dc-with-the-same-name-and-ip-address/ Otherwise come back in a few months and let us know how it goes ps, i'm not saying waiting for it to tombstone is wrong, just not common practise. OP has enough info now though, hope it all goes well
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